This part is called Header von Scheduling Agreement Press to find out the current status of the delivery plan: State of the delivery plan Very good information in this forum on Denplan We have never been so satisfied with the reporting of SAP delivery plans until we found it in the supply chain Management book with SAP APO. Here: There are two ways to start the process of developing a delivery plan: A delivery plan is a framework agreement between you and a portion sold valid for a specified period. The delivery plan contains fixed delivery dates and quantities. These dates are included in the delivery plan classifications. Once the delivery plan is due, you can place the delivery as usual or using a list of deliveries. If the amount in the classifications exceeds the target amount, the system issues a warning message. If the debtor needs it, you can edit invoices periodically, for example. B once a month. All deliveries due for the billing document are grouped into a bundled invoice. Once a classification has been entered, the conditions are updated. Check the Terms tab in the Data position: Price conditions have been updated and net worth is not zero The ability to check whether SAP delivery plans have been created is to go to SAP APO and the transaction (/SAPAPO/PWBSRC1 – Show external purchasing relationships). This is a very convenient transaction that represents sap delivery plans, contracts and information set in a highly compressed field.
Filling out the validity dates of the delivery plan, i.e. “Valid” and “Valid until” Date: Entering the validity dates of the delivery plan A delivery contract with validity dates normally contains properly completed SAP-SD delivery plans: Delivery plans (in SAP APO) are only a source of supply. SAP delivery plans are two things for SAP APO. The framework agreement is a long-term sales contract between Kreditor and Debitor. The structure agreement is of two types: here you can see that the Ship-to Party A7000 has two deliveries that are against the delivery plan number 30000053 that we have previously established.