Manually creating and processing a sequential call-off

Sequential call-offs are usually imported and processed automatically. Sometimes an automatic import of a sequential call-off is not possible for technical reasons. For example, if you receive sequencing information from a customer by fax, you can create a sequential call-off manually. A pending sequence schedule that needs additional sequencing data must exist on the Unprocessed Plans page.

To create a sequential call-off:

  1. Select Release Management > Sequential Call-Offs.
  2. Click Create.
  3. Specify the sequencing information for the sequential call-off:
    Sequence
    Specify the Sequence number. Each Original Equipment Manufacturer (OEM) who sends sequential call-offs to the suppliers uses a unique number as a reference point. This number defines the exact sequence and time of vehicles that are manufactured on the assembly line. The sequence number is used by Release Management to evaluate the appropriate sequence schedule order line 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
    Specify the requirement date and time at which the ordered goods must be available at the customer's location.
    Vehicle Identification Number
    Specify the Vehicle Identification Number (VIN). The 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, the number in the current field is the number of the car.
    Job Sequence Number
    Specify 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. If the production sequence is finalized and a sequential call-off message is processed, this field contains the final job sequence of the vehicle. This is the job sequence on the assembly line for which the items are required.
    RAN
    Specify the Release Authorization Number (RAN). The RAN number that is assigned by the customer uniquely identifies a firm requirement. 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
    Specify the logical sequence reference number of the manufacturer. For example, in the sequencing process of the trading partner Smart a sequential call-off message is processed by Release Management. If a sequential call-off message is processed and the production sequence is finalized, this field contains the planned job sequence of a vehicle.
    Additional Vehicle Specification
    Specify the additional vehicle specification of the manufacturer.
    Pilot Run Identification
    Specify the pilot run identification number of the manufacturer.
    Manufacturing Reference Number

    Specify the Manufacturing Reference Number. The Manufacturing Reference Number is a unique 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.

    Model Identification
    Specify the model identification number of the manufacturer.
    Systems Sequence Reference
    Specify the manufacturer's number for the systems sequence reference.
    Production Area Key
    Specify the production area key of the manufacturer.
    Production Area Date/Time
    Specify the date and time at which items must be available in the production area.
    Customer
    Click the Lookup button of the field. Select the customer of the contract line from the dialog box. 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
    Click the Lookup button of the field. Select the ship to location of the customer from the dialog box. The ship to locations that are displayed in the dialog box are valid for the selected customer.
    Additional Call-Off
    Specify the additional call-off number of the manufacturer.
    Change Sequence
    Specify the change sequence number of the manufacturer. The double-digit change sequence number is used, for example, by the trading partner BMW / Rolls Royce. The number indicates that the sequence of vehicles on the assembly line has been changed.
    Supply Group
    Specify the supply group that is defined by the manufacturer.
    Item Family
    Specify the item family that is defined by the manufacturer.
    Item Group Identifier
    Specify the item group identifier that is defined by the manufacturer.
    Label Number
    Specify the label number that is used for the release order item.
    Line Feed Location
    Specify the 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, the line feed location indicates which assembly line.
    Line Feed Location Side
    Specify the feed side of the assembly line.
    Purpose Code

    Select the Purpose Code that is used for the sequential call-off from the drop-down list. 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, a new order line is added. If the generic reference number already exists, 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, the order line is updated with the available field information. If no matching order line is found, 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, the order line is deleted. If no matching requirement is found, the sequence schedule revision is stored as an unprocessed plan. If alerting is configured correctly, 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 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 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, 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, a new sequenced 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, 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.
  4. To save the sequential call-off, click Save.
    A notification displays that the sequential call-off has been saved successfully.
  5. To process the sequential call-off, click Process Sequential Call-Off.
    The sequential call-off is processed and the status changes from New to Processed.