Reviewing the detail settings of a message processing rule

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.

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.

Internal Item

Review or specify the internal item number of the contract line that is used by the supplier and identifies the item.

When editing, click the Lookup button of the field. Select the item that is used by the supplier from the list that is displayed in the dialog box. The items that are displayed are valid for the selected customer and ship to.

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.

The Message Processing Rule Lines configure the replacement or combination of requirements, incoming release orders and existing order lines of the single plans. The field Replacement Strategy defines how to build a new combined plan. The strategy can be configured for each combination of a message type and message subtype. You can, for example, add requirement quantities, replace remaining requirement quantities, or replace requirement quantities that have the same date.

You can configure that the requirement date sent by the customer is interpreted as arrival date or as pick-up date. This option can be configured for each combination of a message type and message subtype.

Replacement Level

The replacement level defines the order in which the requirements of different message types and message subtypes are processed. The order depends on the assigned strategies for replacement and combination of requirements. The requirements of the single plans are processed in descending order. First, the requirements of the message type that is assigned to the replacement strategy of the highest replacement level are processed. Then the requirements of the message type of the next lower replacement level are processed. For example, shipment schedules that are defined with replacement level 2 are processed first, then planning schedules with replacement level 1. The maximum replacement level is 10.

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.

Replacement Strategy

The replacement strategy defines how requirements of a message type and message subtype are replaced and combined with other requirements in a combined plan. You can select one of these replacement strategy options:

• Add

  Requirement quantities that have the defined message type and message subtype are added to the requirements of the combined plan. All requirements are transferred to the new combined plan. Exception: The difference between the current received CUM from the combined plan and the current received CUM from the single plan is subtracted from the requirements. Both types of plans are considered, to avoid the consequence that first requirements are not transferred or are reduced.

• Add, and Ignore Last Requirement Date

  You can use this replacement strategy to configure message processing rules for incoming customer release orders of the message type Shipment Schedule. Requirement quantities for this message type are added to the requirements of the combined plan. Exception: Requirements on the latest requirement date are not transferred to the new combined plan.

  For example, the trading partner Fuji Heavy Industries sends shipment schedule revisions. The requirements on the latest requirement date must not be transferred to the new combined plan and must not be published in the ShipmentSchedule BOD. Potentially available planned requirements for the same requirement date are copied to the new combined plan. The second part of the requirement on this individual requirement date is received with the next shipment schedule. Then also the first part of the requirement must be transferred to the combined plan. The requirements are published in the ShipmentSchedule BOD.

  The difference between the current received CUM from the combined plan and the current received CUM from the single plan is subtracted from the requirements. See replacement strategy Add.

• Replace and Use Existing Remaining Weekly Quantity

  Start date and end date are set to the next day that follows on the current latest end date. This is, for example, the current latest end date of the last shipment schedule. The remaining requirement quantity is the quantity of the original weekly requirement less all requirement quantities of shipment schedules that already exist in this week. Example: 2 shipment schedules with quantities of 100 and 80 are scheduled in the last week. The weekly requirement quantity is 500. This requirement situation results in a remaining weekly requirement of 320.

• Replace and Recalculate Remaining Weekly Quantity Based on Daily Average of Week

  Start date and end date are set to the next day that follows on the current latest end date. This is, for example, the current latest end date of the last shipment schedule. The quantity of the weekly requirement is divided by the number of weekdays to receive the average daily requirement. The average daily requirement is multiplied by the remaining weekdays after the last shipment schedule day. Example: 2 shipment schedules with quantities of 100 and 80 are scheduled in the last week. The weekly requirement quantity is 500. The number of remaining days of the week after the last shipment schedule day is 3. This requirement situation results in a remaining weekly requirement of 500/5 according to the defined date range rule * 3 = 300.

• Replace and Distribute Remaining Weekly Quantity to Daily Requirements

  The remaining quantity and the remaining days are calculated as with the replacement strategy Replace and Recalculate Remaining Weekly Quantity Based on Daily Average of Week. For the remaining days, the daily requirement quantity is calculated. Example: 2 shipment schedules with quantities of 100 and 80 are scheduled in the last week. The weekly requirement quantity is 500. The number of remaining days of the week after the last shipment schedule day is 3. This requirement situation results in three daily requirements of 500/5 according to the defined date range rule = 100.

• Replace on Same Date

  Requirement quantities that have the defined message type and message subtype are transferred to the new combined plan. Exception: A requirement from the current combined plan that already exists with the start date and the end date, without time comparison, of the new requirement is replaced. The difference between the current received CUM from the combined plan and the current received CUM from the single plan is subtracted from the requirements. See replacement strategy Add.

• Replace and Recalculate Remaining Daily Quantity on Same Date

  Firm requirement quantities are transferred to the new combined plan. In addition, the summarized firm requirement quantity of the last requirement date is subtracted from the planned requirement quantity of the same day. The calculation is performed as follows:

  1. The firm requirement quantities on the last requirement date are summarized, if there are more than one.
  2. If the planned requirement is greater than the summarized firm requirement quantity:
     1. The planned requirement quantity is reduced by the summarized firm quantity.
     2. The newly calculated planned requirement is added to the combined plan along with the firm requirement.
     3. The requirement time of the planned requirement may be adjusted to have firm and planned requirements separated in the combined plan.

  Example: A shipment schedule with a firm quantity of 50 is scheduled on 03/25/2019. The planned requirement quantity on the same date is 200. The newly calculated planned requirement 200 - 50 = 150 is added to the combined plan along with the firm requirement.

• Replace and Recalculate Remaining Daily Quantity on Same Date (based on Customer time zone)

  Firm requirement quantities are transferred to the new combined plan. In addition, the summarized firm requirement quantity of the last requirement date is subtracted from the planned requirement quantity of the same day in the customer's time zone. The calculation is performed as follows:

  1. The firm requirement quantities on the last requirement date are summarized, if there are more than one.
  2. If the planned requirement is greater than the summarized firm requirement quantity:
     1. The planned requirement quantity is reduced by the summarized firm quantity.
     2. The newly calculated planned requirement is added to the combined plan along with the firm requirement.
     3. The requirement time of the planned requirement may be adjusted to have firm and planned requirements separated in the combined plan.

The replacement strategies that use, recalculate, and distribute a remaining weekly quantity only differ in the way how remaining weekly requirements are calculated and scheduled. To calculate the remaining weekly requirements, the system extracts this data from the new combined plan. The new combined plan already includes, for example, the shipments schedule requirements of the last release order import:

1. The latest end date of all existing requirements
2. The week number of the latest requirement
3. The month of the latest requirement
4. The year of the latest requirement
5. The sum of all requirement quantities in the last week
6. The sum of all requirement quantities in the last month

Then the new requirements are processed:

1. All requirements that have an earlier end date, without time comparison, than the existing maximum end date are ignored independent of their requirement types.
2. Weekly or monthly requirements that exist in the last week or month are calculated as described in the table above.

The remaining monthly requirements are treated in the same way by these replacement strategies.

The dates of the start date and the end date are set to the next day that follows on the current latest end date. This is, for example, the current latest end date of the last shipment schedule.

The remaining monthly requirement quantity is the original monthly requirement less all requirements of shipment schedules that are already scheduled in the last month.

Pick-up Date

The requirement date that is sent by the customer is interpreted as pick-up date, if this check box is selected. If the check box is cleared, the requirement date is interpreted as arrival date.

Check Requirement Date Mode

To check the release order's requirement date type, select this check box. If a change from pick-up date to arrival date is detected, the release order is blocked. A blocked release order must be approved manually in the detail view of the Manage Unprocessed Plans page.

Check for Ascending Transmission Number

If a customer supports the processing of transmission numbers, select this check box. This option verifies that the transmission numbers of messages are in complete ascending order. The transmission number is incremented by one with each message exchange. Older messages that have lower transmission numbers are filtered out.

Check for Ascending Message Sequence Number

This option enables you to process those EDI messages that generally do not contain a sequential control number from the OEM. Release Management imports an EDI message based on the message sequence number from Transformation Services. If a message is out of sequence, an unprocessed plan is created that can be managed on the Manage Unprocessed Plans page in Release Management.