Reviewing the details of a sequential call-off

In the detail view of the Sequential Call-Offs page, the sequencing information, assigned plans, and log entries of a sequential call-off are shown.

To review the details of a selected sequential call-off:

  1. Select Release Management > Sequential Call-Offs.
  2. Click the Drill down button of a sequential call-off.
  3. Review the sequencing information of the selected sequential call-off:
    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 appropriate order line of the sequence schedule on the Unprocessed Plans page. The order line 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. Sequential call-offs that have been used to update sequence schedules with sequencing data receive the status Processed. Sequential call-offs that are not yet processed have the status New. Sequential call-offs that cannot be processed receive the status Failed.
    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.
    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 completed, a sequential call-off message is processed. This field then contains the final job sequence of the vehicle. This is the job sequence on the assembly line for which the items are required.
    RAN
    The Release Authorization Number is a number assigned by the customer that uniquely identifies a firm requirement. Abbreviation: RAN. The RAN number is used instead of CUMs to synchronize release orders. A RAN number is unique per pick-up date/time, arrival date/time, transport ID, and ship to location. In consequence, the same RAN number can be valid for different distribution zones and consumption points.
    Logical Sequence Reference
    The logical sequence reference number of the manufacturer. For example, in the sequencing process of the trading partner Smart the production sequence has been finalized. A sequential call-off message is processed. When the message is processed, this field contains the planned job sequence of a vehicle.
    Additional Vehicle Specification
    The additional vehicle specification of the manufacturer.
    Pilot Run Identification
    The field shows the identification number of the pilot run from the manufacturer.
    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.
    Model Identification
    The model identification number of the manufacturer.
    Systems Sequence Reference
    The field shows the reference number of the systems sequence from the manufacturer.
    Production Area Key
    The field shows the key of the production area from the manufacturer.
    Production Area Date/Time
    The field shows the date and time at which items must be available in the production area.
    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.
    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.
    Additional Call-Off
    The additional call-off number of the manufacturer.
    Change Sequence
    The double-digit change sequence number is used by the trading partner BMW / Rolls Royce. It indicates that the sequence of vehicles on the assembly line has been changed.
    Supply Group
    The supply group that is defined by the manufacturer.
    Item Family
    The item family that is defined by the manufacturer.
    Item Group Identifier
    The item group identifier that is defined by the manufacturer.
    Label Number
    The label number that is used for the release order item.
    Line Feed Location
    The line feed location is a customer-defined delivery location. It is transferred by release orders that have the message subtype Sequenced. The line feed location indicates the place on the assembly line. If there are several assembly lines such as in a large plant, then the line feed location indicates which assembly line.
    Line Feed Location Side
    The feed side of the assembly line.
    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. For these numbers several items can exist that must be delivered and mounted, for example, a pair of exterior mirrors of a vehicle. The sequencing data must be copied into the order lines of several different sequence schedules on the 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.
    Manually Changed
    This check box indicates whether the sequential call-off has been changed manually.
    Historical
    This check box shows whether a sequential call-off is a historic 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 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 these requirements 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 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 OS Portal or 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. The requirement must be specified with 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 the 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 OS Portal or Infor Ming.le. In addition, a log entry is added to the Release Management server log.
    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.
  4. On the Assigned Plans tab, you can review a list of sequence schedules that are assigned to the selected sequential call-off. You can check whether the sequencing process of the assigned plans has been completed or is still pending:
    Plan ID
    The plan ID of the sequence schedule that is assigned to the sequential call-off. The plan ID is automatically created by Release Management.
    Version
    This field shows the revision number of a sequence schedule that is assigned to the sequential call-off.
    Customer Item
    The item identifier of the sequence schedule that is used by the customer.
    Internal Item
    The internal item identifier of the sequence schedule that is used by the supplier is displayed if the contract line is assigned successfully.
    Item Description
    The item description of the supplier.
    Requirement Date
    This field shows the requirement date and time at which the ordered goods must be available at the customer's location.
    Net Quantity
    The calculated net quantity of the sequence schedule's order line.
    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.
    Sequence Status
    Shows the status of the sequenced requirements.
    1. Reference Number
    This field shows the first document reference number of the order line. The incoming release order must be a referenced requirement. The first reference number must be defined as the referenced key field in the CUM adjustment rule.
  5. Review the Log Entries tab that shows the performed processing steps of the sequential call-off or the error that happened:
    Date
    The log date and time of the documented processing step to import the sequential call-off.
    Type
    The log type of the documented step to import the sequential call-off. These log types exist:
    • Info: The import step is completed successfully.
    • Warning: A warning happened during the sequential call-off import.
    • Error: An error happened during the sequential call-off import.
    • Fatal Error: A critical error happened during the sequential call-off import.
    • System Error: A system error happened during the sequential call-off import.
    Process
    The step of the import process that is performed.
    Process Text
    A message for the processing step is displayed. If an error happens, then the message displays a short error description.