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`. Each time the system creates a share, it calculates the next transfer date for the periodic transfer based on the date. Once the system has given the release via the main message type (see below for an explanation), the “Release Date” and “Release Time” fields are filled in. Another important detail updated at this point is the reset the “Modified” license plate in the position of the delivery plan. This means that after an unlock is issued, the position of the delivery plan in question is no longer considered “changed” (compared to the overall delivery plan in the system) until, in this example, if you look at the classifications individually, the system would set up a clearance because you changed the quantity of the first line by more than 20% and therefore exceeds the tolerance limit. Overall Process The settlement of the appointment agreement consists of three main steps:-Planning of material requirements -Unlocking (FRC/JIT) -Issuance/Transmission of LPA shares for delivery plans with release documentation. If there are messages that have not been issued for the delivery plan and you then put the license plate `Messages by sharing`, you will still find the messages that have not been issued via header -> messages. New messages are available via the output documentation (ME38 -> select the corresponding point -> document of its version.
-> select the corresponding share in -> messages per version). In principle, the output generation “translates” the current delivery plan in the system into a version. Declassifications shall inform the supplier of the quantities of a material to be delivered and on what date. . . . .