Reviewing the list of unprocessed plans

On the Manage Unprocessed Plans page, a list of unprocessed customer release orders is shown.

To review the list of unprocessed plans:

  1. Select Release Management > Manage Unprocessed 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 unprocessed plan.
    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 Sequence Number
    This field is equivalent to the Message Sequence Number on the Manage Messages page of the Transformation Services area. The field shows the order in which the messages are processed by Transformation Services. You can identify the message on the Manage Messages page that leads to the specific single plan in Release Management.
    Plan ID
    The plan ID of the plan that is assigned to the contract line. The plan ID is automatically created by Release Management.
    Processing Date
    The date when the error happened or the manual approval was requested.
    Internal Item
    The internal item identifier of the unprocessed plan that is used by the supplier is displayed if the contract line is assigned successfully.
    Customer Item
    The item identifier of the unprocessed plan that is used by the customer.
    Message Type
    The message type of the unprocessed plan. The message type is a Planning Schedule or a Shipment Schedule.
    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.
    Processing Status
    This status shows the last successful processing step to import an unprocessed plan.
    Exception Status
    This status shows whether the import of an unprocessed plan failed, because an error happened. The exception status Pending indicates sequence schedules that are not yet completed by the sequencing data of sequential call-offs.
    Error Message
    The reason that caused the error. Unprocessed plans that must be approved manually are marked by the message approval required.
    Approval Status
    This status shows whether an unprocessed plan has been approved, a manual approval of the unprocessed plan is required, or has been rejected:
    • No Approval: No approval is required.
    • Approval Required: The single plan must be approved manually.
    • Approved: The single plan has been approved.
    • Approval Rejected: Approval of the single plan has been rejected.
    • Approval for CUM Reset Required: CUM reset must be approved manually.
    • Approved CUM Reset: CUM reset has been approved.
    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.
    Location
    This field shows the code that identifies the accounting entity location.
    Person in Charge
    This field shows the name of the internal person in charge who is assigned to the contract.
    Last Update User
    The user who performed the last update.
    Last Update Date
    The date of the last update.
    Archived
    A selected check box shows that the release order has been archived.
    Sequence Status
    Shows the status of the sequenced requirements.