SAP SOP Transfer Key Figure Data to Demand Management
Study Material Contributed by Ulhas Kavle - Senior SAP Consultant
The ultimate goal of the sales and operational planning is to transfer the SOP planned requirements to demand management as planned independent requirements and have them manufactured. For both Standard SOP and Flexible SOP, this is true.
The planned independent requirements are created at the plant level for a material or at the product group level, therefore it is preferable to have a plant in the planning hierarchy as characteristics (in the information structure). With the plant in the planning hierarchy, one can easily transfer planned requirements as planned independent requirements (PIR) to demand management without any additional configuration stating the proportional distribution of materials or product groups across plants.
If “plant proportional distribution” quotas are not maintained (for a material plant combination) in cases when “plant” as a characteristics, is not included in the planning hierarchy, the system distributes the chosen key figure quantity, as planned independent requirements, equally amongst all the plants where the material is created. Another inference of this statement is that, you would only need to create “plant distributions proportions” for materials managed in multiple plants and if a material is maintained only one plant, you would not really need to maintain this distribution rule (and even if you maintain, it would be set as distribution = 1 for the material and plant combinations).
Fig – SOP_94
SPRO Path: Production > SOP > Functions > Define Proportional distribution across plants.
The transfer of key figure values to demand management can be either carried out in the background (through scheduled jobs) or it can be carried out in the foreground from the planning table or from the transaction code MC90.
The MC90 screen is shown below and the details required for the transfer are self explanatory. Maintenance of requirement type and version and version status (active or inactive) is mandatory for creation of planned independent requirements (PIR) when they reach demand management (note – the direct transaction code to enter PIR is MD61).
Fig – SOP_95
Follow the topics for SAP SOP in the sequence Mentioned Below
All the site contents are Copyright © www.sapsword.com and the content authors. All rights reserved.
All product names are trademarks of their respective companies. The site www.sapsword.com is in no way affiliated with SAP AG. Every effort is made to ensure the content integrity.
Information used on this site is at your own risk.
The content on this site may not be reproduced or redistributed without the express written permission of
www.sapsword.com or the content authors.