Creating a requirement consolidation rule

  1. Select Release Management > Configuration > Requirement Consolidation Rules.
  2. Click Create, to display the detail view of the Requirement Consolidation Rules page.
  3. Specify this header information:
    Effective from Date
    This field defines the start date of the valid period for the configuration.
    When editing, click the Calendar button to select the start date from a calendar.
    Effective to Date
    This field defines the end date of the valid period for the configuration.
    When editing, click the Calendar button to select the end date from a calendar.
    Message Type
    The message type is a Shipment Schedule or a Planning Schedule.
    Message Subtype
    These options are available for the message subtype:
    • Default: This is the default configuration that is used for the replacement or combination of requirements in the combined plan.
    • RAN: This configuration is used for the replacement or combination of requirements from RAN messages of a customer.
    • GPI: This message subtype is used for the message type Shipment Schedule in the Renault process GPI. GPI is an integrated production control system that is used by Renault assembly plants. In the GPI process, suppliers receive release orders with a unique transport ID on requirement line level and a consumption point on plan level. Shipments are grouped by transport ID.
    • L3P: This message subtype is used for the message type Shipment Schedule in the Renault process L3P. In the L3P process, suppliers receive release orders with a transport ID, a consumption point, and a distribution zone on requirement line level. Shipments are structured by distribution zone, transport ID, and consumption point. Each shipper has a unique transport ID. Consequently, shipments are grouped by transport ID, if more than one shipment is contained in a shipper.
    • CINDI: This message subtype is used for the message type Shipment Schedule in the Renault process CINDI. The CINDI process works with GPI or L3P. In this process, suppliers receive a shipment schedule with RAN or Kanban number. The expected arrival date is included in the message in addition to the fields that are known from GPI and L3P. The RAN or Kanban number is unique for release orders on requirement line level. The transport ID is unique per shipper. Multiple shipments per shipper/transport ID are possible. Multiple RAN or Kanban numbers per shipment and per item in a shipment are possible. The message subtype CINDI is used for the LISA process as well.
    • Pick-up Sheet: This configuration is used for the replacement or combination of requirements from Pick-up Sheet messages of a customer.
    • Manifest: This configuration is used for the replacement or combination of requirements from Manifest messages of a customer.
    • Kanban: This configuration is used for the replacement or combination of requirements from Kanban messages of a customer.
    • Sequenced: This message subtype is selected for the message type Shipment Schedule. The message subtype is used to process shipment schedules that require sequential information, for example, production-synchronous release orders. If you use the message subtype Sequenced, the Calculation Base in the CUM adjustment rules configuration must be Referenced. The Reference Number 1 is Key check box must be selected.
    • Sequenced with Shipping Window: This message subtype is selected for the message type Shipment Schedule. If Release Management receives a ShipmentSchedule BOD, the Message Processing Rules page is checked for a sequenced call-off with message subtype Sequenced with Shipping Window. This message subtype is also expected from the customer. In this case, the ShipmentSchedule BOD is merged with the current single plan of type Shipment Schedule into a new single plan. The new single plan contains the sequenced requirements. This feature is especially used by trading partner A0061 Ford North America.
    • Loading Sequence: This message subtype is selected for the message type Shipment Schedule and is used for Honda when lot sequence information is sent. In this case, the reference field consists of the Schedule Order Number and the Lot Sequence to load the truck as requested by Honda.
    Remark
    Review or provide a short description that clarifies the purpose of the configuration.
    Customer
    The customer is an arbitrary set of characters that is used to uniquely identify a customer in an accounting entity. The customer is taken from the ERP system.
    When editing, click the Lookup button of the field. Select the customer from the list that is displayed in the dialog box.
    Customer Name
    The field shows the name of the customer who holds the contract.
    When you select a customer, the name of the customer is automatically displayed.
    Ship To
    Review or specify the ship to location of the contract line. This field indicates the location code that is used with the ship to location to identify where the goods are shipped.
    When editing, click the Lookup button of the field. Select the ship to location of the customer from the list that is displayed in the dialog box. The ship to locations that are displayed are valid for the selected customer.
  4. Expand the Notes field set and specify an explanatory text for the requirement consolidation rule.
  5. Specify the calculation settings of requirements:
    Delete all Existing Requirements
    Use this option to delete the existing requirements of the single plan. The selection criteria of the requirement consolidation rule determine the requirements to be deleted: For example, requirements of a specific message type and message subtype. The requirements of the new release orders are transferred to the consolidated plan. The consolidated plan represents the complete requirement situation of the customer.
    Delete Existing Requirements before First Requirement Date
    Use this option to delete the requirements that have a requirement date before the first requirement date of the new single plan.
    Delete all Planned Requirements prior to First Requirement Date

    Use this option to delete the existing requirements of the single plan that are planned before the first requirement date of the new release order. This option cannot be used, if the Delete Existing Requirements before First Requirement Date check box is selected.

    Note: The option has special effects in a RAN process (Nissan). All planned requirements before and equal to the last date of the incoming firmed requirements are removed from the new single plan. If a planned requirement comes in, then an existing planned requirement that has the same date is removed from the new single plan.
    Delete Monthly Requirements before First Date
    Monthly requirements of the single plan before the first requirement date of the new release order are deleted. This option cannot be used if the Delete Existing Requirements before First Requirement Date check box is selected.
    Delete Weekly Requirements before First Date
    Use this option to delete the requirements of the single plan that are planned weekly before the first requirement date of the new release order. This option cannot be used if the Delete Existing Requirements before First Requirement Date check box is selected.
    Delete all Requirements before Calculation Date
    Use this option to delete the requirements of the single plan that are planned before the calculation date of the new consolidated plan. This option cannot be used if the Delete Existing Requirements before First Requirement Date check box is selected.
    Delete Existing Requirements after Last Requirement Date
    Use this option to delete the requirements that have a requirement date after the last requirement date of the new release order items.
    Replace Existing Requirements outside Horizon Date Range on new Requirement Dates
    The option replaces existing requirements outside the horizon date range for single demands from a new plan. Without existing requirements outside the horizon date range, the functionality performs a full replacement of requirements within the horizon date range.
    Filter by First Reference Number
    A field that is mapped to the Reference Number 1 field is used as selection criterion to consolidate and filter out requirements. For example, the field Model Year is mapped to the Reference Number 1 field. Then only requirements of the same model year are compared, replaced or merged if required. To use this option, a field mapping must be defined for the required release order process on the Field Mappings page. This field mapping maps the selection criterion, for example, the model year to the Reference Number 1 field on requirement level. The field mapping must be assigned to the trading partner on the Trading Partner Mappings page. This option to filter out requirements can also be used for other selection criteria.
    Supersede Demands that have a lower Transmission Number with the same date or with the same Reference Number
    This option determines the order in which the demands are processed. If there are demands that have a lower Transmission Number with the same date or with the same Reference Number (depending on Plan Subtype), those demands should be superseded by the demands with a higher Transmission Number.
    Delete Everything that Does not Match First Reference Number
    Requirements from the current plan that do not match the Reference Number 1 field are removed. This option can be used to automatically remove requirements if the model year changes. A change of the model year is detected if the release number that is received with the next planning schedule is increased. The release number is stored in the External Document Number field of the Release Information field set.
    • No Deletion: Requirements with an old model year are not removed automatically when a new release number is received from the customer. Requirements with different model years for the same requirement date are stored in parallel in one plan. The option Filter by First Reference Number must be activated.
    • Delete by External Document ID: The requirements that do not match the new release number are removed automatically. The option Filter by First Reference Number must be activated.
  6. Click Save to save the requirement consolidation rule.
    A notification displays that the requirement consolidation rule has been saved successfully.