This service allows the following operations for delivery plans of delivery plans: It is also advantageous to disable the change of the exercise in the SAP standard and to adapt the periodic calculation of the cumulative quantitative correction through the SPEEDI functions for the annual change to the specific requirements of the customer. A new incoming SOAP API will be made available API Hub. This asynchronous input service allows you, as a provider using SAP S/4HANA Cloud, to automatically receive and update delivery plans for distribution plans. It is based on the SOAP protocol with namespace sap.com/xi/EDI/Supplier. If you need help deciding where you want to place the correction transfer, select View. The system lists the delivery dates in chronological order. This can often be difficult, especially as a supplier in the automotive industry, due to the complex requirements of manufacturers. This is the case, for example, with the logic of release order at HONDA USA, at NISSAN or as part of the new logistics concept (NLK) at Volkswagen. Often, the manufacturer also transmits additional data, for example as part of the Release Authorization Number (RAN), which must also be added to the SAP delivery plan. In the standard system, an emergency delivery is automatically set up in the background if you save a return with the RZ distribution document type.
This should allow for immediate pickup. If necessary, your system administrator can create in customizing a new distribution mode in which the instant delivery plate is disabled. Delivery returns can then be created and processed via a worklist. Fluctuations in requirements in planned delivery plans also affect your schedule and production planning. These are usually petrified to certain limits. However, the customer does not always comply. Checking the agreed tolerances as soon as a release order is entered helps to detect infringements at an early stage and to react in a timely manner. In The Service includes head, item, delivery planning and filing entities, as well as head and item subdivisions for partners and pricing elements. Once the distribution plan is established, the distribution plan number is sent in the response along with the data contained in the distribution plan. If there is a problem creating, retrieving, updating, or deleting the distribution plan, the system displays the error messages in the response.
Once the delivery plan is established, you can manually update the cumulative delivery quantity/issued by creating a correction delivery by the modification mode, for example. It is possible that a pre-delivery number of the incoming EDI message was not provided for in the distribution plan, which means that there was a gap in the delivery numbers The delivery of goods to external agents constitutes a shipment filling. That is why, for returns, you must use the KRZU type of proof to make returns in the delivery process, with the participation of external agents (LK sales document type). In this case, place returns against the corresponding delivery plan. If the system finds multiple distribution plans, this can be explained by the following reasons: To identify the changed classifications, compare the data in the delivery plan with the original data in the EDI message. An analysis of the inter-scheduling delivery behavior at the day, week or month level also gives you insight into exceeding tolerance limits and slowly changing the customer`s release order behavior over a long period of time. . . .