Data For Scheduling Agreement Releases

By December 6, 2020 No Comments

Note: You can only view messages created at the sharing level through the Purchases menu by selecting the configuration agreement -> delivery plan – > delivery plan – > Print/Transfer (ME9E transaction). Terms of transmission of delivery plans in the form of messages to the creditor: As of version 4.0, you need to define exactly one type of message as “main message type” for each type of sharing in the customizing for MM, searching for messages for appointment times. The `U` field (Updating print-dependent data) should be marked for the type of message in customizing for material management -> purchase -> messages -> output control -> types of message -> Definition of message types for the residue of the thought plan: quantities having a delivery date in the past, which have been passed on to the creditor through an appointment authorization, but have not yet been delivered at maturity: quantities that are immediately necessary (today or earlier) but which have not yet been transmitted to the seller through an appointment exemption. Release/Expediter -> Fine-Tuned Control: Forecast/Expediter Delivery Plan. You should always use the main message type to create all versions, otherwise print-dependent data will not be updated. This is especially important if you use several different types of messages. I have a question about the authorization of the JIT. Is there a possibility (through the creation profile or some other way) to divide the residue of the amounts of JIT provided according to the calendar line dates and not aggregate it. I tried to change the profile configuration, but every time the JIT-Idoc that goes to the creditor contains a cumulative amount for the residue. The system can create a separate message for a delivery position for each version. This means that the creditor receives a document for each release. This way, you can publish versions individually or re-enact previously transferred versions.

For the system to create a separate message for each version, you must use the `Rel. Mess` indicator. (Message by sharing) in customizing for purchase by assigning messages -> Message Determination Schemes -> Definition of message diagrams for the planning of release/acceleration of the agreement – > scheme assign to the scheduling release/Expediter agreement. You can view messages created in the ME38 transaction by selecting the corresponding item and selecting the DE sharing document, then select the appropriate sharing number and select messages by version, NOT via ME38 -> Header -> Messages. After defining the type of message that updates print-dependent data for each type of sharing (i.e. for each process), you need to make sure that versions are always created with this type of message (the primary message type). You can create a second type of message in parallel, with the type of main message to be the first (for example. B LPH2 as the second type of message for LPH1).

Basically, the version of the version “translates” the current global delivery plan into the system into one version. Permissions inform the seller of the quantities of material to be delivered and on what day. Different versions are recorded with the publication documentation and can therefore be displayed at any time. The creative profile is assigned to an SA element. (SA Release item Preview screen -> item -> Other functions -> Additional data) You create creative profiles in customizing for the purchase by appointment -> Maint. Rel. Profile of the establishment for Sched. Mr. Agmt.

w. Rel. Docu. The current overall delivery plan for equipment obtained from the delivery plan continuously releases modifications during an implementation procedure due to the requirements of this equipment (dependent requirements, etc.). The result is quantities and delivery times that must be sent to the creditor in the form of clearances against the corresponding delivery plan. Automatic classifications during needs planning are conditional on the reference to a delivery plan in the source list as a provision.