Entering content frameFunction documentation Receiving Delivery Schedules by EDI (SD-SLS-OA-SCH) Locate the document in its SAP Library structure


In this EDI scenario, you receive and process delivery schedules sent by a customer from an R/3 purchasing system.




You can create delivery schedules in your system only on the basis of an existing Structure link scheduling agreement.

The system cannot receive a delivery schedule from the customer if you are working in the referenced scheduling agreement. Make sure that you are not in change mode when processing incoming delivery schedules for a scheduling agreement.


To process incoming delivery schedules, you need to make the necessary settings in Customizing, as well as settings for Structure link controlling incoming EDI specific to scheduling agreements. This includes:

Customers do not generally send their customer number along with delivery schedules. So, you set the system to determine a sold-to party number based on other data sent in by the customer, such as the vendor number, partner description, or unloading point.

Special features for delivery schedules allow you to define for each sold-to party or combination of sold-to party/unloading point how delivery schedules are to be processed. Note that the system checks this record in Customizing for every incoming delivery schedule. If it cannot find a record for the particular sold-to party, it issues an error message and stops processing of the IDoc (status 51).

Do not set the "Test run" indicator here. If you do, the system does not process any incoming delivery schedules. Rather, it sends them (by workflow) to the employees responsible for manual processing.

Many errors that occur in processing incoming EDI delivery schedules are due to missing or incorrect settings for these two Customizing activities.

IDoc Interface

Define the EDI partner profile for your partner (transaction WE20) by entering the following data in the header and detail screen for inbound parameters:



Partner type

KU (customer); if the IDoc is sent from an R/3 system via tRFC (in a typical case with ALE scenarios), enter LS for logical system!

Message type


Process code



Trigger immediately

Allowed Agents

Enter an R/3 user or an organizational unit, for example.



This graphic is explained in the accompanying text

Inbound Processing

The IDoc interface receives the IDoc and reviews its control record. According to this record and the corresponding partner profile, the IDoc is transferred to the function module IDOC_INPUT_DELINS_START in Sales and Distribution. The ALE services are called.

The system processes the IDoc in the background, using the data records in the IDoc to determine the sold-to party, and then the scheduling agreement.

If processing is successful, the system creates or updates the delivery schedule in the scheduling agreement. The IDoc is sent back to the IDoc interface which updates the status records in the IDoc.

Exception Handling

If it cannot determine a scheduling agreement, or if an error occurs in processing, the system Structure link determines the relevant agent(s) and sends a workitem to the integrated inbox(es). An agent can pick up the workitem to process the IDoc or simply end processing.

To display the IDoc for the current delivery schedule, choose DlvSch.Hdr on the delivery schedule tabstrip. Then choose Edit ® Curr. IDoc for dlv.sched.



Leaving content frame