Configuring the RAN process

To support the referenced process that uses RAN numbers in planning schedules, some configuration steps are required in Release Management.

To configure the referenced RAN process using planning schedules:

  1. Select Release Management > Configuration > Message Processing Rules.
  2. Click the Drill down button of a message processing rule.
  3. In the detail view of the Message Processing Rules page, click Edit.
  4. In the Message Processing Rule Lines, select Planning Schedule from the Message Type column. Select RAN from the Message Subtype column.
    Note: For requirements of the type Planning Schedule, there is no check whether the Reference 1 field is filled during the import process.
  5. To save the settings, click Save.
  6. Select Release Management > Configuration > Requirement Consolidation Rules.
  7. Select the requirement consolidation rule for the message type Planning Schedule and the message subtype RAN and click Edit.
  8. Select the Delete all Planned Requirements prior to First Requirement Date check box.
    Based on the Requirement Consolidation Rules settings, three different scenarios are supported to adjust the single plan of type Planning Schedule:
    • Adjust the single plan with one firm requirement: All planned requirements from the old single plan with a requirement date before or equal to the new firm requirement date are not copied to the new single plan. All firm requirements from the old single plan are copied to the new single plan.
    • Adjust the single plan with one planned requirement: All planned requirements from the old single plan with the same date and time are not copied to the new single plan. All firm requirements from the old single plan are copied to the new single plan.
    • Adjust the single plan with multiple requirements: All planned requirements from the old single plan are not copied to the new single plan when the requirement date is before or equal to the latest requirement date from the new single plan. Firm requirements with different RAN numbers must be copied to the new single plan.
  9. To save the settings, click Save.
  10. Select Release Management > Configuration > CUM Adjustment Rules.
  11. Select the CUM adjustment rule for the message type Planning Schedule and the message subtype RAN and click Edit.
  12. To support the referenced RAN process, select Referenced from the Calculation Base field.
  13. Select the Reference Number 1 is Key check box.
    Note: These settings prevent the calculation of the net requirement based on the in-transit quantity from being performed in the combined plan.
  14. To save the settings, click Save.
  15. Select Release Management > Configuration > Trading Partner Mappings.
  16. Select the trading partner mappings for the customer and click Edit.
  17. To support the referenced RAN process using planning schedules, these field mappings must be added:
    Planning Schedule Mapping
    Select Referenced Planning Schedule (RAN) from the drop-down list. This field mapping controls the import of RAN numbers on requirement level. The RAN numbers are not published in the PlanningSchedule BOD.
    Shipment Schedule Mapping
    Select Referenced Shipment Schedule (RAN) from the drop-down list. This field mapping controls the publishing of the RAN numbers in the ShipmentSchedule BOD.
    Shipment Mapping
    Select Standard Shipment (Reference) from the drop-down list. This field mapping contains the RAN number that is stored as shipment line reference. The mapping is used to match the shipment line against the requirement based on the RAN number.
  18. To save the settings, click Save.