Overview

The order in which the setups and configuration rules of the Configuration menu are structured represents the internal processing sequence of the configuration data. These features are available to configure processes that are performed by Release Management.

  • Phase Out Items: The requirement dates related to a customer item can be used to determine the assignment of those requirements to one or more contract lines. To enable this requirement date functionality for all customers at the accounting entity and location levels, the code list PhaseOutItemsActivation can be activated by selecting the Active check box on the code list properties. Alternately, the Phase Out Items page, which is accessed in the Release Management > Configuration menu, provides the capability to configure the functionality for a particular customer, ship to, and customer item, and the related internal supplier item numbers on an individual basis. If the code list PhaseOutItemsActivation is implemented, the Phase Out Items page is used for only data viewing purposes.
  • Message Processing Rules: The main purpose of a message processing rule is to register the supported message types and message subtypes of incoming release orders from a customer. These release orders must be processed. A message processing rule defines how requirements from incoming release orders and requirements from existing plans are calculated and integrated in a combined plan.
  • Manual Approval Rules: A manual approval rule defines the criteria to filter out the requirements of release orders that must be approved manually on the Unprocessed Plans page. After the approval, the requirements are processed. Additionally, these rules define how the requirements of the current release order are compared with the requirements of the previous release order.
  • Date Range Rules: A date range rule defines how requirement quantities from release orders that have a defined date range are scheduled. The requirements can be scheduled on a specific date in the time range. Or they are split into several equable requirements over the whole date range.
  • CUM Adjustment Rules: A CUM adjustment rule defines how the cumulative quantities, shipped quantities and received quantities, from incoming release orders are handled. It determines how the in-transit quantity is calculated.
  • Requirement Consolidation Rules: A requirement consolidation rule defines how existing requirements of a single plan are merged with new requirements from release orders of the same type.
  • BOD Separation Rules: A BOD separation rule defines how customer requirements of the combined plan are separated into PlanningSchedule and ShipmentSchedule BODs. These BODs are published to ION and sent to the ERP system.
  • Trading Partner Mappings: A trading partner mapping defines the customer-specific or ship to specific field mapping that is applied to shipment schedules, planning schedules, or shipments. If no specific trading partner mapping is configured, then the default standard mappings are used.
  • Field Mappings: A field mapping determines the fields that are mapped to or from plan fields or to the shipments. This information is used by the field mapping:
    • The reference IDs in the reference lists of ShipmentSchedule, SequenceSchedule, PlanningSchedule, and Shipment BODs
    • The message direction
    • The field names of plans and shipments