Scheduling Agreement Release Type

Object key (i.e. document number) Item Release Type (FRC or JIT) Exit number 9 999 9 LPH1 x Main Message Type for FRC 9 LPH2 Additional Message Type A LPJ1 x Main Message Type for JIT A LPJ2 Additional Message Type Release/Expediter -> Fine-Tuned: Control Forcaste Delivery/Expediter. 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. 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. I check when planning the appointment configuration with the forecast delivery plan (FRC) and the JIT delivery plan (JIT) the planning is proposed according to requirements and profile. You can process message recordings for new releases, either immediately or in a later collection edition. Messages are displayed as soon as the transmission time is 4. A collective treatment is possible if you work with the airtime `1` (released by RSNAST00) or `3` (exit by the application-specific output program). A validation profile is used to determine the period during which sharing (delivery modes) of a delivery plan is generated and transmitted to the creditor. It also controls the parity of the versions; Aggregation of expected quantities from the day after the date of availability; and conducting a tolerance test. When the system sends a message, there are specific updates that call the version “completed and out.” If the system has not yet released a version as a message, each generation of another version will be replaced by the latest version that the system has not yet issued. In the “Creation Period” section, you indicate for each type of sharing whether and, if so, how often the system should create a version of this type. In the “Tolerance Profile” section, for each type of sharing, indicate whether the system verifies how much the current version to be created differs from the last transferred version and, if so, how it performs that review. Note: There is no sharing document for transfer plans.

Even if the exit document. Indicator of THE type of LU document in the customizing, it has no effect.

This entry was posted in Uncategorized. Bookmark the permalink.