Reviewing the list of plans

The Plans page shows the active and new contract lines for the shipment schedules and planning schedules.

To review the list of plans:

  1. Select Release Management > Plans.
  2. Review this information:
    Customer
    The customer of the contract line. 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.
    Customer Name
    The name of the customer who holds the contract.
    Ship To
    The ship to 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.
    Ship To Name
    View the name of the location that is used with the Ship To location identifier to identify where goods are shipped to.
    Message Type
    The message type of the of the last imported release order. The message type is a Planning Schedule or a Shipment Schedule. For example, if the Message Type field displays Shipment Schedule, you must look up the Shipment Schedules page for the last imported release order. If the Message Type field displays Planning Schedule, you must look up the Planning Schedules page for the last imported release order.
    Message Subtype
    The message subtype of the customer release order. These are the options for the message subtype:
    • Default: This is the default configuration that is used to integrate the requirements.
    • RAN: This configuration is used to integrate the requirements of RAN messages from 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 to integrate the requirements of Pick-up Sheet messages from a customer.
    • Manifest: This configuration is used to integrate the requirements of Manifest messages from a customer.
    • Kanban: This configuration is used to integrate the requirements of Kanban messages from 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 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.
    Internal Item
    The internal item identifier of the contract line that is used by the supplier.
    Customer Item
    The item identifier of the contract line that is used by the customer.
    Processing Date
    The last processing date of an active contract line.
    Contract
    The internal contract ID of the contract line.
    Line
    The line number of the contract line.
    Plan ID
    The plan ID of the plan that is assigned to the contract line. The plan ID is automatically created by Release Management.
    Version
    The current version number of a plan. Each release order import or other changes of a plan lead to a new version of the plan. After a change, the version number of the plan is incremented by one.
    Process Status
    This field shows the last successful processing step to import a plan.
    Accounting Entity
    A corporation or a subset of a corporation that 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.
    Internal Status
    The internal status of the contract line. The internal status of the contract line becomes Active when incoming release orders are processed. A single plan and a combined plan are created and the plans are assigned to the contract line. The internal status New indicates that plans are not yet assigned to the contract line.
    Location
    This field shows the code that identifies the accounting entity location.
    Version Created By
    This field shows the originator of the plan version:
    • Import: The plan version has been created by a release order import.
    • User: The plan version has been created manually by a user.
    • Shipment/Consumption: The plan version has been created by an import of shipment or consumption.
    Item Description
    The item description of the contract line.
    Effective to Date
    Defines the end date of the valid period for the contract line.
    Effective from Date
    Defines the start date of the valid period for the contract line.
    Person in Charge
    This field shows the name of the internal person in charge who is assigned to the contract.
    External Document Number
    This field shows the external document number of the release order from the OEM. The field can be used for these purposes:
    Handling of incoming ASC X12 864 text messages: An incoming ASC X12 864 text message is linked to the corresponding release orders by the External Document Number. The imported text messages are displayed on the Text Messages page.
    Handling of requirements from different model years: The release number of the last planning schedule is contained in this field. Requirements can have different release numbers respectively model years for the same requirement date. The option Filter by First Reference Number in the Requirement Consolidation Rules enables to store the requirements in parallel in one plan. To automatically remove requirements for older model years, you can use the field Delete Everything that Does not Match First Reference Number. The field must be set to Delete by External Document ID. If a planning schedule with an increased release number is received, the requirements for this model year are stored in the new plan revision. Other requirements for older model years are automatically removed. To delete requirements for an old model year manually, remove the requirements of the new plan for the old model year. Increase the release number in the External Document Number field.