Creating a BOD separation rule

  1. Select Release Management > Configuration > BOD Separation Rules.
  2. Click Create, to display the detail view of the BOD Separation 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.
    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 field entry is disabled. The accounting entity is automatically set when you save the data. The default is the accounting entity where you are currently working.
  4. Expand the Notes field set and specify an explanatory text for the BOD separation rule.
  5. To add a BOD separation line, click the Create button of the BOD separation line list.
    The BOD Separation Rule dialog box is displayed.
  6. Select the BOD type from the BOD Type drop-down list. The BOD type is a Shipment Schedule or a Planning Schedule. The selected requirements from the combined plan are assigned to this BOD type.
  7. To assign the requirements from the combined plan to the planning schedule that are not assigned to the shipment schedule, select the check box Transfer All Requirements Not Specified in Shipment Schedule. You can select this check box if the BOD type is Planning Schedule.
  8. Expand Level of Commitment:
    Transfer Plan by Level of Commitment
    Specify the schedule status that controls the transfer of the requirements from the combined plan to the ShipmentSchedule and the PlanningSchedule BODs. Firmed and planned requirements from the combined plan are separated and assigned to PlanningSchedule and ShipmentSchedule BODs according to their schedule status. You can select these plan statuses:
    Firm Requirements
    To assign requirements that have the schedule status Firm Requirement to the defined BOD type, select this check box.
    Planned Requirements
    To assign requirements that have the schedule status Planned Requirements to the defined BOD type, select this check box.
  9. Expand Frequency:
    Transfer Schedules by Frequency
    Specify the frequency that controls the transfer of the requirements from the combined plan to the ShipmentSchedule and the PlanningSchedule BODs. To separate and assign requirements to the defined BOD type according to their frequencies, you can select these options:
    Day
    To assign the requirements that have a frequency specified in days to the defined BOD type, select this check box.
    Week
    To assign the requirements that have a frequency specified in weeks to the defined BOD type, select this check box.
    Month
    To assign the requirements that have a frequency specified in months to the defined BOD type, select this check box.
    Other
    To assign the requirements that have another frequency to the defined BOD type, select this check box.
  10. Expand Time Periods:
    Transfer Schedules in Time Period
    The requirements from the combined plan within a specified time horizon are transferred to the defined BOD type. To assign requirements to the defined BOD type, select this check box and specify the time horizon in days in the Days field.
    Transfer Schedules after Time Period
    The requirements from the combined plan that are scheduled after a specified time horizon are transferred to the defined BOD type. To assign requirements to the defined BOD type, select this check box and specify the time horizon in days in the Days field.
  11. Expand Type-Specific:
    Referenced
    To transfer referenced requirements from the combined plan to the defined BOD type, select this check box.
    Message Type
    Transfers requirements of a specific message type from the combined plan to the defined BOD type. Select a message type from the drop-down list:
    • Planning Schedule: Requirements from planning schedules are transferred to the defined BOD type.
    • Shipment Schedule: Requirements from shipment schedules are transferred to the defined BOD type.
    Note: The configured message type and message subtype are used if the original message type or message subtype of the incoming BOD controls the outgoing BOD. All requirements of the incoming BOD with this configured message type are published in the outgoing BOD type. No other attributes such as Firm Requirement or Planned Requirements may be configured in the BOD separation line. For example, a trading partner sends firmed and planned requirements exclusively in a PlanningSchedule BOD. These requirements must be shipped without exception by the supplier. Therefore, the message type of the BOD separation line for the outgoing ShipmentSchedule BOD must be set to Planning Schedule. The check box Transfer All Requirements not Specified in Shipment Schedule of the BOD separation line for the outgoing PlanningSchedule BOD must be selected. Through this configuration, all requirements are transferred to ShipmentSchedule BODs and no requirements to the PlanningSchedule BODs. The message subtype is not necessarily required for this configuration.
    Message Subtype
    Transfers the requirements of a specific message subtype from the combined plan to the defined BOD type. You can select a message subtype from the drop-down list:
    • Default: By default, requirements are transferred to the defined BOD type.
    • RAN: Requirements of the RAN message subtype are transferred to the defined BOD type.
    • 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: Requirements of the Pick-up Sheet message subtype are transferred to the defined BOD type.
    • Manifest: Requirements of the Manifest message subtype are transferred to the defined BOD type.
    • Kanban: Requirements of the Kanban message subtype are transferred to the defined BOD type.
    • 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, select the Referenced check box. Then, a SequenceSchedule BOD is published.
    • 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 that is also expected from the customer. In this case, the ShipmentSchedule BOD is merged with the current single plan of type Shipment Schedule. 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.
  12. Click OK to close the BOD Separation Rule dialog box.
  13. To create the next BOD separation line, repeat steps 5–12.
    Note: You must create a BOD separation line for each BOD type, for a Shipment Schedule, and for a Planning Schedule.
  14. To edit a BOD separation line, click the Drill down button of a BOD separation line. Edit the field entries in the BOD Separation Rule dialog box as required.
  15. To delete a BOD separation line, select the line and click the Delete button of the BOD separation line.
  16. Click Save to save the BOD separation rule.
    A notification displays that the BOD separation has been saved successfully.