Creating a date range rule

To create a date range rule:

  1. Select Release Management > Configuration > Date Range Rules.
  2. Click Create, to display the detail view of the Date Range 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.
    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 date range rule.
  5. Specify the date range settings:
    Default Time for Daily Requirements
    Review or specify the default time for daily requirements in Coordinated Universal Time (UTC). For example, no time is defined in the incoming release order. If the frequency is daily, you can specify a time that is different from 00:00. The default time for a customer and a message type is 00:00 UTC.
    Distribution Mode for Day Range Requirements
    Review or specify the distribution mode for day range requirements:
    • First Day: To schedule day range requirements on the first day of the day range, select this option from the drop-down list.
    • Distribute to Working Days: To distribute day range requirements evenly over the working days of the day range, select this option from the drop-down list. Specify the first working day and the last working day of the week.
    Distribution Mode for Weekly Requirements
    Review or specify the distribution mode for weekly requirements:
    • Configured Weekday: To schedule weekly requirements on a specific day of the week, select this option from the drop-down list. Select the weekday from the drop-down list Weekday for Weekly Requirement.
    • Distribute to Working Days: To distribute weekly requirements evenly over the working days of the week, select this option from the drop-down list. Specify the first working day and the last working day of the week.
    Note: In this context, the setting Distribute to Working Days is exclusively used for some Japanese trading partners.
    First Day of Week
    This field shows the first working day of the week.
    When editing, select the first working day of the week from the drop-down list.
    Weekday for Weekly Requirements
    Review or specify the weekday for weekly requirements. To schedule weekly requirements on a specific day, select the weekday from the drop-down list. The option Configured Weekday must be selected from the drop-down list Distribution Mode for Weekly Requirements.
    End of Week
    This field shows the last working day of the week.
    When editing, select the last working day of the week from the drop-down list.
    Distribution Mode for Week Range Requirements
    This field defines the distribution mode for week range requirements. The requirement quantity is scheduled on the First Week, the Last Week or on Every Week of the week range. If you select Every Week, the requirement quantity is split into several equable weekly requirements over the whole week range. The remaining quantities that cannot be split into several equable weekly requirements are scheduled on the first week of the week range. For example, VDA supports date ranges of several weeks. Additionally, to distribute week range requirements evenly over the working days of the week range, select Distribute to Working Days from the drop-down list. Specify the first working day and the last working day of the week.
    Distribution Mode for Monthly Requirements

    You can select one of these options:

    • To schedule monthly requirements on a specific day of the month, select Configured Day from the drop-down list. Specify the calendar day in the field Day for Monthly Requirement.
    • Several partial requirements for a month must be scheduled according to their different requirement dates that are included in the release order. To process these requirements, select Day of Requirement from the drop-down list.
    • To distribute monthly requirements evenly over the working days of the month, select Distribute to Working Days from the drop-down list. Specify the first working day and the last working day of the week.
    • To split monthly requirements into weekly requirements, select Distribute to Weeks from the drop-down list.
    Day for Monthly Requirement
    Review or specify the number of a day for monthly requirements. If you specify 0, the requirement day is the first day of the month. If you specify a value greater than the number of days of a month, the last day of the month is set. The maximum value that you can specify is 31. The specific day of the month is calculated.
    Interpret Flexible Requirements as Monthly Requirements
    This option enables Release Management to handle flexible requirements of plans as monthly requirements.
    Merge Requirements
    Different daily requirements that are scheduled on the same date and time are accumulated and merged. They build one requirement quantity that has the same date and time. Immediate requirements, backorder requirements, weekly requirements, and monthly requirements are excluded from this rule. The rule can only be used for non-referenced requirements.
    Use RAW and FAB Releases as Planned Requirements
    Planned requirements must be created from the raw material and fabrication release data that are sent by the customer. This setting is used for some trading partners who send raw material and fabrication releases that must be handled as planned requirements by their suppliers.
    Subtract Time Offset from Backorder/Immediate
    If the default time for daily requirements is defined and backorder or immediate requirements are transferred without requirement time, you can use this setting. The setting is only relevant, if the ERP system cannot process several requirements that have the same requirement date and time. If the check box is selected, two minutes are subtracted from the default time for backorder requirements. One minute is subtracted from the default time in case of an immediate requirement. Therefore, the default time for requirements that is defined in Default Time for Daily Requirements must be greater than 00:00. This setting prevents the requirement time from being set to a time on the previous day. In all other cases, the transferred requirement time from the backorder or immediate requirements is used.
    Manual Default Time for Daily Requirements
    If new requirements must be created manually for existing or new plans with a default time, the check box must be selected. If the check box is cleared, the default creation time is used.
  6. Click Save to save the date range rule.
    A notification displays that the date range rule has been saved successfully.