Scheduling Agreement Release Type

The system stores the output messages in the NAST table with the following key: In principle, the release generation “translates” the current delivery plan in the system into a version. Declassifications inform the supplier of the quantities of a material to be delivered and on what date. The different versions are saved via the output documentation and can therefore be displayed at any time. With SAP S/4HANA Logistics` Sourcing and Procurement LoB, it is possible to use the SAP Best Practices activation approach to tailor delivery plans. However, if you use the traditional customizing approach, this blog post can be helpful. The creation profile is assigned to an SA position. (Overview of article SA -> Article -> Other functions -> Additional data) You put creation profiles in customizing for purchases via the delivery plan -> Maint. Rel. Creation profile for Sched. Agmt. W. Rel. Docu.

The automatic establishment of classifications during requirements planning is subject to the identification of a relevant delivery plan in the list of sources. This is what you can do in the menu Purchases: Basic Data -> list of sources -> Maintenance (transaction ME01). You must hold here a data set for the hardware and in this data set, the `Layout` box must contain the license plate `2`. Select the row for each item category and double-click the link – document type order requirement. In the edit view, set “Link required document type of order”: Preview of allowed document tracking. The following tables include the default settings for SAP. The IMG (SPRO) allows you to define additional types of delivery plan through IMG (SPRO) > > purchases > delivery plan > type of document. The system stores a transmitted release with a share number and integrates the evidence into the release history. The system then generates the next release of this particular type of version with an increased number of one. Forward calendars and JIT calendars have separate number ranges.

In the “Tolerance Profile” section, you indicate, for each sharing mode, whether the system checks the extent to which the current version is being voted on from the last version transmitted and, if so, how it performs this test. . . .

Comments are closed.