Reviewing the list of date range rules

The Date Range Rules page includes a list of the defined date range rules.

To review the list of date range rules:

  1. Select Release Management > Configuration > Date Range Rules.
  2. Review this information:
    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.
    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.
    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.
    Remark
    Review or provide a short description that clarifies the purpose of the configuration.
    Last Update User
    The field shows the user who performed the last update.
    Last Update Date
    The field shows the date of the last update.
    Accounting Entity
    The accounting entity is a corporation or a subset of a corporation. The accounting entity is independent in regard to one or more operational functions or accounting functions. An accounting entity produces a P&L and balance sheet from a complete, balanced set of transactions, and is often a legal entity. An accounting entity is defined within a tenant and can contain locations.