Reviewing the list of sequential call-offs

The Manage Sequential Call-Offs page shows a list of sequential call-offs that contain the sequencing data for pending sequence schedules on the Manage Unprocessed Plans page. The sequencing information of a sequential call-off is used to complete the order lines of pending sequence schedules.

To review the list of sequential call-offs:

  1. Select Release Management > Manage Sequential Call-Offs.
  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.
    Sequence
    Each Original Equipment Manufacturer (OEM) who sends sequential call-offs to the suppliers uses a unique number as a reference point. This reference number defines the exact sequence and time of vehicles that are manufactured on the assembly line. The valid reference number of a sequential call-off from an OEM is internally copied into the Sequence field. This sequence number is used by Release Management to evaluate the order line of the appropriate sequence schedule. The sequence schedule on the Manage Unprocessed Plans page must be completed with sequencing data. See the description of the Manufacturing Reference Number field.
    Requirement Date
    This field shows the requirement date and time at which the ordered goods must be available at the customer's location.
    Status
    This field shows the status of a sequential call-off. The status is Processed for sequential call-offs that have been used to update sequence schedules with sequencing data. The status is New for sequential call-offs that are not yet processed. Sequential call-offs that cannot be processed receive the status Failed.
    Version
    This field shows the revision number of a sequential call-off.
    Plans Assigned
    This field shows the number of sequence schedules that are assigned to the sequential call-off. A unique sequence number is a manufacturing reference number or another reference number of an OEM. Several items can exist that must be delivered and mounted, for example, a pair of exterior mirrors that are built into a vehicle. The sequencing data must be copied into the order lines of several different sequence schedules on the Manage Unprocessed Plans page. These sequence schedules are assigned to the sequence number of the sequential call-off. The sequence number of a sequential call-off is stored in the Sequence field.
    Manufacturing Reference Number
    This field shows a unique reference number that identifies a particular assembly or another manufacturing process. Some OEMs use the Logical Sequence Reference, the Job Sequence Number, or the Vehicle Identification Number as an equivalent for the Manufacturing Reference Number. See the description of the Sequence field. The valid reference number of a sequential call-off from an OEM is internally copied into the Sequence field.
    Job Sequence Number
    The sequence number of the job for which the items are required. For example, in the sequencing process of the trading partner Smart a sequential forecast message is processed. When the message is processed, this field contains the planned job sequence of a vehicle. When the production sequence is finalized and a sequential call-off message is processed, this field contains the final job sequence. This is the job sequence on the assembly line for which the items are required.
    Vehicle Identification Number
    The Vehicle Identification Number (VIN) consists of a structured combination of characters that are assigned to each vehicle by its manufacturer. The VIN is used by some OEMs to identify a vehicle on the assembly line for which an item is required. If, for example, the item is an assembly part of a car, then the number in the current field is the number of the car.
    Historical
    This check box shows whether a sequential call-off is a historical schedule.
    Purpose Code

    Sequence schedules and sequential call-offs are sent with different purpose codes to the supplier. Purpose codes control how requirements and sequencing data of incoming sequence schedules and sequential call-offs are processed. As a prerequisite, a generic reference field must be available in the sequence schedules, which makes a requirement unique per item. The field mapping of a sequence schedule stores this generic reference field in the 1. Reference Number field of the sequence schedule's order line. The field mapping of the sequential call-off stores this generic reference field in the Sequence field.

    These purpose codes are supported:

    • Insert: Release Management checks whether another order line with the same generic reference number exists. If the generic reference number is unique per plan, then a new order line is added. If the generic reference number already exists, then the new requirement and sequencing data replace the existing data of the order line.
    • Update: The order line that must be updated is evaluated by comparing the generic reference numbers of the existing requirements and the new requirement. The reference numbers of the order line and the new requirement must be unique. If a matching order line is found, then the order line is updated with the available field information. If no matching order line is found, then the new requirement is added to the existing order lines.
    • Delete: The order line that must be deleted is evaluated by comparing the generic reference numbers of the existing requirements and the new requirement. The reference numbers of the order line and the new requirement must be unique. If a matching order line is found, then the order line is deleted. If no matching requirement is found, then the sequence schedule revision is stored as an unprocessed plan. If alerting is configured correctly, then an alert message is sent per email to the responsible user. The user is informed that the unprocessed plan must be deleted on the Manage Unprocessed Plans page.
    • Deactivate: This purpose code is used to set a sequenced requirement with message subtype Sequenced With Shipping Window to Shipped. Individual requirements can be deactivated when a new schedule revision is created. The deactivation indicates that it is not necessary to ship the requirement to the customer. This is required, for example, in case of an item revision cutover. Multiple items are ordered for one vehicle whereby only one of the items must be shipped to the customer. In this case, it is up to the supplier to decide, which item must be shipped. When you select the purpose code and submit the single plan on the Manage Shipment Schedule page, the shipped quantity is set to the requirement quantity. The net quantity is set to zero on the Shipment Schedule tab and the Combined Plan tab. The deactivated requirements are published in the SequenceSchedule BOD to the ERP system with net quantity zero to remove these requirements. If alerting is configured correctly, then an alert message is sent to ION Pulse. The responsible users are informed in Infor Ming.le. In addition, a log entry is added to the Release Management server log.
    • Reactivate: This purpose code is used to create a new regular open requirement that can be shipped to the customer. If the purpose code Deactivate was set by mistake, then a new sequenced requirement must be specified. Specify the requirement quantity, requirement date, and purpose code Reactivate. You must specify the vehicle identification number in the fields 1. Reference Number and Vehicle Identification Number. The sequence is identified by the job sequence number that must be specified in the Job Sequence Number field. The requirements with a matching vehicle identification number and job sequence number of the same plan are treated as if they were not shipped. The manually entered requirements are added to combined plan as regular open requirements. They are published with purpose code Reactivate to the ERP system. If alerting is configured correctly, then an alert message is sent to ION Pulse. The responsible users are informed in Infor Ming.le. In addition, a log entry is added to the Release Management server log.
    Last Update User
    Name of the user who performed the last update of the sequential call-off.
    Last Update Date
    Date and time of the last update.
    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.
  3. Review these examples for the use of purpose codes:
    Purpose code Insert:
    New requirement/sequence:
    Current plan:
    Date Quantity Reference number VIN
    8/10/yyyy 1 PC 1232400019
    8/10/yyyy 1 PC 1232400029
    New requirement/sequence:
    8/10/yyyy 1 PC 1232400039
    Current plan after import:
    8/10/yyyy 1 PC 1232400019
    8/10/yyyy 1 PC 1232400029
    8/10/yyyy 1 PC 1232400039
    Requirement/sequence already exists:
    Current plan:
    Date Quantity Reference number VIN
    8/10/yyyy 1 PC 1232400019 123
    8/10/yyyy 1 PC 1232400029 124
    New requirement/sequence:
    8/10/yyyy 1 PC 1232400029 125
    Current plan after import:
    8/10/yyyy 1 PC 1232400019 123
    8/10/yyyy 1 PC 1232400029 125
    Purpose code Update:
    Requirement/sequence already exists:
    Current plan:
    Date Quantity Reference number VIN
    8/10/yyyy 1 PC 1232400019 VV1233
    8/10/yyyy 1 PC 1232400029 VV1234
    New requirement/sequence:
    8/10/yyyy 1 PC 1232400029 VV1235
    Current plan after import:
    8/10/yyyy 1 PC 1232400019 VV1233
    8/10/yyyy 1 PC 1232400029 VV1235
    New requirement/sequence:
    Current plan:
    Date Quantity Reference number VIN
    8/10/yyyy 1 PC 1232400019 VV1233
    8/10/yyyy 1 PC 1232400029 VV1234
    New requirement/sequence:
    8/10/yyyy 1 PC 1232400039 VV1235
    Current plan after import:
    8/10/yyyy 1 PC 1232400019 VV1233
    8/10/yyyy 1 PC 1232400029 VV1234
    8/10/yyyy 1 PC 1232400039 VV1235
    Purpose code Delete:
    Requirement/sequence already exists:
    Current plan:
    Date Quantity Reference number VIN
    8/10/yyyy 1 PC 1232400019 VV1233
    8/10/yyyy 1 PC 1232400029 VV1234
    New requirement/sequence:
    8/10/yyyy 1 PC 1232400029 VV1234
    Current plan after import:
    8/10/yyyy 1 PC 1232400019 VV1233