Reviewing the settings of a CUM adjustment rule

In the detail view of the CUM Adjustment Rules page, the settings of a CUM adjustment rule are shown.

To review the settings of a CUM adjustment rule:

  1. Select Release Management > Configuration > CUM Adjustment Rules.
  2. Click the Drill down button of a CUM adjustment rule.
  3. Review the header information of the selected 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.
    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.
    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.
    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.
  4. Expand Notes and review the comments that are specified for the CUM adjustment rule.
  5. The settings for the CUM adjustment are valid for non-referenced schedules. Review these settings in the CUM field set:
    Calculation Base
    This field defines the method to calculate the in-transit quantity. Frequently, the calculation is based on the received quantities, on the last confirmed packing slip, or on the shipments in a specific time horizon. Select one of these methods from the drop-down list:
    • Referenced: For referenced schedules, a combination of reference key fields is used to determine the shipped quantities and to reduce the required quantities. This method can be used, for example, in case of Pick-Up Sheet messages. By default, the in-transit quantity is set to zero.
    • From CUM: This method uses the shipped CUM of the last packing slip and the received CUM to calculate the in-transit quantity. You can select the Check Shipments check box as an additional option for the calculation base From CUM.
    • No Received CUM: If the trading partner does not send a received CUM, then you can select this option. It keeps the in-transit quantity at zero. For example, in the sequencing process of a trading partner the planning schedule does not contain a received CUM. The planning schedule is based on the delivery forecast message EDIFACT DELFOR. Only the shipped CUM is updated based on the received inventory consumption. See the field description for Update Shipped Quantity by Inventory Consumption.
    • From Confirmed Shipments: This method uses the existing confirmed shipments to calculate the in-transit quantity. The shipped quantity of all packing slips that are newer than the last confirmed packing slip gives the resulting in-transit quantity.
      Note: This option only works if the received confirmed packing slip information is available.
    • By Horizon: Sometimes a trading partner does not send a received CUM and a confirmed packing slip or the packing slip information is not reliable. In these cases, you can select this method to calculate the in-transit quantity. The calculation is based on shipments that have been sent to the trading partner in the time horizon of the new single plan. The calculation evaluates the start date and the end date of the new single plan. It sums up the shipped quantity of those requirements from the last combined plan within the time horizon of the new single plan.
    • Without Received CUM (LSP): Some plants do not send received CUMs, which must then be calculated. The in-transit quantity is calculated from the shipped CUM of the logistics service provider (LSP) minus the shipped CUM.
      • Internal LSP: The received CUM is calculated from the shipped CUM minus in-transit quantity.
      • External LSP: The received CUM is calculated from the shipped CUM LSP minus in-transit quantity.
    • Copy CUMs from Combined Plan: This method copies the received CUMs and CUM differences from the last combined plan. The method is used, if of different message types from a trading partner only one message type contains reliable information to calculate the in-transit quantity. The method must be used, for example, for the N.P.R.C. process, traditional planning, of the trading partner A0130 Fiat Chrysler Automobiles Europe. It is used in this case to configure the message type Planning Schedule.
    No. of Digits to Be Used for Packing Slip No. Comparison
    Review or specify the number of right-aligned digits from the packing slip number that must be checked. Some trading partners take only parts from the supplier's packing slip numbers for the comparison with the internal packing slip numbers. If an identical packing slip number is found, then this packing slip number receives the status Confirmed. You can view the corresponding shipment that includes the confirmed packing slip number in the Shipment History dialog box. Click View Shipments in the detail view of the View Plans page. For example:
    Number of digits to be compared: 6
    2 0 1 0 0 0 0 1 Example of a confirmed packing slip number
    1 0 0 0 0 1 Right-aligned part of the packing slip number that is used for the comparison with the internal packing slip numbers.
    Manual CUM Reset Calculation

    You can configure this setting if trading partners send a CUM reset date, but without suitable confirmed packing slips.

    This can also happen, if the trading partner sends packing slip numbers that cannot be resolved by Release Management. For example, packing slips from an external logistics service provider (LSP) are sent in case of an indirect shipment.

    In consequence, Release Management cannot calculate automatically the correct in-transit quantity after the CUM reset. If the customer already received packing slips before the CUM reset, these quantities of goods must be subtracted from the shipped CUM. This is required to calculate the correct in-transit quantity.

    Instead of performing an automatic CUM reset, you can select this check box. An unprocessed plan is created that must be approved manually on the Manage Unprocessed Plans page. Release Management proposes a current received CUM and thus an in-transit quantity that is checked and changed or confirmed by the supplier in the unprocessed plan.

    Check Shipments
    Use this option, if the incoming packing slip number must be checked. This is an additional option for the calculation base From CUM.
    CUM Reset Day
    Review or specify the number for a day in a month of the fiscal year. On this date, the cumulative quantities of a customer are set to zero.
    CUM Reset Month
    Review or specify the number for the month of the fiscal year in that the cumulative quantities are set to zero.
  6. Referenced schedules do not require a calculation of the in-transit quantity. A combination of reference key fields is used for referenced schedules to determine the shipped quantities and to reduce the required quantities. Review these settings in the Referenced field set:
    Reference Number 1 is Key
    Use this option to define the referenced key field. The reference number 1 is used to determine the cumulative shipped quantity of referenced requirements. The referenced key number is, for example, a PUS number or a RAN number. The referenced key number is used for referenced requirements of special message types and message subtypes.
    Reference Number 2 is Key
    Use this option to define the referenced key field. The reference number 2 is used to determine the cumulative shipped quantity of referenced requirements. The referenced key number is, for example, a PUS number or a RAN number. The referenced key number is used for referenced requirements of special message types and message subtypes.
    Reference Number 3 is Key
    Use this option to define the referenced key field. The reference number 3 is used to determine the cumulative shipped quantity of referenced requirements. The referenced key number is, for example, a PUS number or a RAN number. The referenced key number is used for referenced requirements of special message types and message subtypes.
    Requirement Date is Key
    Use this option to define the requirement date as referenced key field.
    Consumption Point is Key
    Use this option to define the consumption point as referenced key field.
    Dock Code is Key
    Use this option to define the dock code as referenced key field. The dock code specifies the receiving location of a customer or the shipping location of an organization.
    Distribution Zone is Key
    Use this option to define the distribution zone as referenced key field.
    Transport ID is Key
    Use this option to define the transport ID number as referenced key field.
    Partial Shipment Allowed
    Use this option, if partial shipments must be treated like complete shipments. This is important for message subtypes that require the use of a unique reference number for each shipment that cannot be sent twice. An example is the message subtype Pick-Up Sheet.
    Note: If the option is enabled, the remaining quantity for a given RAN is still open and sent to the ERP if your shipment quantity is short. If not enabled, the effective quantity is set to zero if the shipment quantity is short because the OEM does not allow two shipments with the same RAN.
    Update Shipped Quantity by Inventory Consumption
    If you select this option, Inventory Consumption messages are used to mark requirements as Shipped and to update the shipped CUM. The option can only be used for the message type Shipment Schedule and the message subtype Sequenced.