Sap Schedule Agreement Output

spro – Materials Management – Purchasing – News – Exit Control – Delivery Plan – Table 503 created (for Purchasing Order and Creditor Type boxes) and Table 504 created (for type of purchase) Hello Everyone, I found the solution myself, so I present it here:If you unlock your delivery plan, z.B. code me84 t and editing is genres and distributed, but in Del. Sch. remains the status of the latest “Yellow” version you keep Shell SPRO in: Mngmnt Materials -> Purchase -> News -> output control -> Types of messages -> Set the types of messages for release/expediter, then run Fine-Tuned Control: Forecast Delivery/Expedir. There you have Shell Check the box to see for operation 9/A and the output you use for versions. It worked for me. Greetings, Tomek 2. Another thing…. The key to indicate the backlog and the instant requirement are not displayed in the SA version…. (I think it should be displayed in the “calendar line type” column.

although I established the SA with the creative profile that the relevant indicator for the backlog and the immediate requirement defined in the overall parameter of the creation profile. Did I miss something? spro – Materials Management – Purchasing – News – Exit Control – Access Sequences – Set the order of access to the delivery plan: Check if you have made a adjustment to create a new output at each exit of the SA Sch line. I have problems with the delivery plan (LPA type). I have a delivery plan in place, and I have maintained the schedule by executing the layout. The calendar can be maintained and I can run the version (generate the SA version for FRC and JIT). The publication has been directly documented (I can see it when SA`s delivery plan is displayed) and I can also print it… The problem is that the state of SA`s output documentation is always yellow (there is already information for this). As a result, the version number of this SA is still blocked at point 1, although changes in the content of the expression have taken effect (the output of the ranking line has been changed because the GR consumes SA e.V. or impact on the execution of the provision). If you have an answer to this question, use the “Your Answer” form at the bottom of the page instead. Take a closer look at the analysis of the Oracle database with expert Click here to see a free dan Hotka white paper! www.ittoolbox.com/r/quest27.asp ` www.ittoolbox.com/help/termsofuse.htm mailto:leave-sap-r3-log@openitx.com www.OpenITx.com/g/sap-r3-log.asp` No redistribution.

Hello, this seems to be a user error once its is published, it should be green of the somewe version but not save the document. The three Tcks of the deterrence procedure should be checked. Hello YOSEA, Can you explain how you solved your problem with yellow status? I`d be very happy to know!BR, Tomek.