Sequence shipping schedules

Sequence shipping schedules are pull call-off schedules that are generated from Assembly Control through the order-controlled/SILS supply system.

To update a sequence shipping schedule line, the assembly order that generated the sequence shipping schedule line must be changed.

To create sequence shipping schedule lines

If Assembly Control calls off goods via the SILS supply system, LN performs the following steps:

  1. In Assembly Control, a reference number/ID is generated, which represents a combination of VIN, Line Station, and Assembly Kit.
  2. If a call-off is made, a schedule line for every item is generated in the Purchase Schedule Lines (tdpur3111m000) session and the generated reference ID is inserted in the Reference ID field.
  3. For every schedule line, sequence shipping data is inserted in the Sequence Shipping data (tdpur3517m000) session.
  4. For every sequence shipping schedule line, a record is inserted in the Purchase Release Lines - Sequence Shipping Data (tdpur3523m000) session.
Note

Sequence shipping schedules can contain configured items. For more information, refer to Configured items on purchase schedules.

To update sequence shipping schedule lines

To update a sequence shipping schedule line, the assembly order that generated the sequence shipping schedule line must be changed.

Updates are of two types:

  • Non-unique fields
    Updates are made to fields that are not unique.

    In the Sequence Shipping data (tdpur3517m000) session, these are updates to the fields, such as:

    • Job Sequence
    • Quantity
    • Requirement Date
    • Option List ID
  • Unique fields
    Updates are made to unique fields. These are updates to other fields in the Sequence Shipping data (tdpur3517m000) session, such as Assembly Kit, VIN, Line Station, and so on.

The action LN takes does not only depend on the kind of field that must be updated, but also on whether or not the sequence shipping schedule line is already sent in a purchase release.

Note

In the Sent field of the Sequence Shipping data (tdpur3517m000) session, you can view if the sequence shipping schedule line was already sent in a purchase release.

To update not yet sent sequence shipping lines
  • If Assembly Control changes any field on a sequence shipping line, the applicable field is simply updated in the Purchase Schedule Lines (tdpur3111m000) session, the Sequence Shipping data (tdpur3517m000) session, and the Purchase Release Lines - Sequence Shipping Data (tdpur3523m000) session. The status of the schedule line remains Order Generated in the Purchase Schedule Lines (tdpur3111m000) session and Created in the Sequence Shipping data (tdpur3517m000) session/ Purchase Release Lines - Sequence Shipping Data (tdpur3523m000) session.
  • If Assembly Control wants to delete a requirement, the applicable sequence shipping schedule line in the Purchase Schedule Lines (tdpur3111m000) session and the Sequence Shipping data (tdpur3517m000) session receive the status Canceled. The line is simply removed from the Purchase Release Lines - Sequence Shipping Data (tdpur3523m000) session.
To update a unique field on a sequence shipping line that is already sent in a purchase release

If an update is made to a unique field, LN performs the following steps:

  1. The old sequence shipping schedule line in the Purchase Schedule Lines (tdpur3111m000) session receives the status Canceled.
  2. The corresponding record in the Sequence Shipping data (tdpur3517m000) session keeps the status Created, but another record is inserted with the status Canceled. The value of the canceled sequence shipping schedule line's Revision field is incremented, because the line status changes from Created to Canceled.
  3. The canceled sequence shipping line from the Sequence Shipping data (tdpur3517m000) session is inserted in the Purchase Release Lines - Sequence Shipping Data (tdpur3523m000) session under a new Release Revision. The reason for this is that the cancellation must also be communicated to the supplier by means of a (new) purchase release.
  4. A new sequence shipping schedule line is created with the status Order Generated in the Purchase Schedule Lines (tdpur3111m000) session and the status Created in the Sequence Shipping data (tdpur3517m000) session/ Purchase Release Lines - Sequence Shipping Data (tdpur3523m000) session.
To update a non-unique field on a sequence shipping line that is already sent in a purchase release

If an update is made to a field which is not unique, LN takes the following steps:

  1. The old sequence shipping schedule line in the Purchase Schedule Lines (tdpur3111m000) session is simply updated and keeps the Order Generated status.
  2. The applicable sequence shipping schedule line in the Sequence Shipping data (tdpur3517m000) session keeps the Created status, but another record is inserted with the Modified status. The value of the modified sequence shipping schedule line's Revision field is incremented, because the line status changes from Created to Modified.
  3. The modified sequence shipping line from the Sequence Shipping data (tdpur3517m000) session is inserted in the Purchase Release Lines - Sequence Shipping Data (tdpur3523m000) session under a new Release Revision. The reason for this is that the modification must also be communicated to the supplier by means of a (new) purchase release.
Example 1 - To create sequence shipping schedule lines

Requirements from Assembly Control:

VIN numberJob seq.Assembly kitLine stationItemDateQty
VIN001JS001K01LS01ITEM110/1/99 8:002
VIN001JS001K01LS01ITEM210/1/99 8:004
VIN001JS001K01LS01ITEM310/1/99 8:004
VIN002JS002K02LS01ITEM110/1/99 12:002
VIN002JS002K02LS01ITEM210/1/99 12:005
VIN002JS002K02LS01ITEM410/1/99 12:004
VIN003JS003K03LS01ITEM110/1/99 16:002
VIN003JS003K03LS01ITEM210/1/99 16:004
VIN003JS003K03LS01ITEM510/1/99 16:008

 

Results in the Purchase Schedule Lines (tdpur3111m000) session:

Schedule numberPos.ItemRequirement dateQty
SCH000110ITEM110/1/99 8:002
SCH000210ITEM210/1/99 8:004
SCH000310ITEM310/1/99 8:004
SCH000120ITEM110/1/99 12:002
SCH000220ITEM210/1/99 12:005
SCH000410ITEM410/1/99 12:004
SCH000130ITEM110/1/99 16:002
SCH000230ITEM210/1/99 16:004
SCH000510ITEM510/1/99 16:008

 

Results in the Sequence Shipping data (tdpur3517m000) session:

SchedulePos.Seq. revisionVINJob seq.KitLine stationItemDateQtyStatus
SCH0001101VIN001JS001K01LS01ITEM110/1/99 8:002Created
SCH0002101VIN001JS001K01LS01ITEM210/1/99 8:004Created
SCH0003101VIN001JS001K01LS01ITEM310/1/99 8:004Created
SCH0001201VIN002JS002K02LS01ITEM110/1/99 12:002Created
SCH0002201VIN002JS002K02LS01ITEM210/1/99 12:005Created
SCH0004101VIN002JS002K02LS01ITEM410/1/99 12:004Created
SCH0001301VIN003JS003K03LS01ITEM110/1/99 16:002Created
SCH0002301VIN003JS003K03LS01ITEM210/1/99 16:004Created
SCH0005101VIN003JS003K03LS01ITEM510/1/99 16:008Created

 

Results in the Purchase Release Lines - Sequence Shipping Data (tdpur3523m000) session:

Release numberRelease revisionRelease pos.ScheduleSchedule pos.Seq. revisionItemQtyStatus
REL001010SCH0001101ITEM12Created
REL001020SCH0002101ITEM24Created
REL001030SCH0003101ITEM34Created
REL001040SCH0001201ITEM12Created
REL001050SCH0002201ITEM25Created
REL001060SCH0004101ITEM44Created
REL001070SCH0001301ITEM12Created
REL001080SCH0002301ITEM24Created
REL001090SCH0005101ITEM58Created

 

Example 2 - To update sequence shipping schedule lines

The Assembly Control module sends the following updates:

  • VIN001 on JS001 is replaced by VIN004 on JS001.
  • For VIN003, the quantity of ITEM2 is increased from 4 to 6.
  • All requirements from Example 1 are already sent in a purchase release.

As a result, the following changes are made in the Purchase Schedule Lines (tdpur3111m000) session:

Canceled
SchedulePos.ItemRequirement dateQtyStatus
SCH000110ITEM110/1/99 8:002Canceled
SCH000210ITEM210/1/99 8:004Canceled
SCH000310ITEM310/1/99 8:004Canceled

 

Updated
SchedulePos.ItemRequirement dateQtyStatus
SCH000230ITEM210/1/99 16:006Order Generated

 

New
SchedulePos.ItemRequirement dateQtyStatus
SCH00140ITEM110/1/99 8:002Order Generated
SCH00240ITEM210/1/99 8:004Order Generated
SCH00320ITEM310/1/99 8:004Order Generated

 

As a result, the following changes are made in the Sequence Shipping data (tdpur3517m000) session:

SchedulePos.Seq. revisionVINJob seq.KitItemDateQtySentStatus
SCH0001101VIN001JS001K01ITEM110/1/99 8:002YesCreated
SCH0001102VIN001JS001K01ITEM110/1/99 8:002NoCanceled
SCH0001401VIN004JS001K04ITEM110/1/99 8:002NoCreated
SCH0002101VIN001JS001K01ITEM210/1/99 8:004YesCreated
SCH0002102VIN001JS001K01ITEM210/1/99 8:004NoCanceled
SCH0002401VIN004JS001K04ITEM210/1/99 8:004NoCreated
SCH0003101VIN001JS001K01ITEM310/1/99 8:004YesCreated
SCH0003102VIN001JS001K01ITEM310/1/99 8:004NoCanceled
SCH0003201VIN004JS001K04ITEM310/1/99 8:004NoCreated
SCH0002301VIN003JS003K03ITEM210/1/99 16:004YesCreated
SCH0002302VIN003JS003K03ITEM210/1/99 16:006NoModified

 

As a result, the following changes are made in the Purchase Release Lines - Sequence Shipping Data (tdpur3523m000) session:

Release numberRelease revisionRelease pos.ScheduleSchedule pos.Seq. revisionItemQtyStatus
REL001110SCH0001102ITEM12Canceled
REL001120SCH0002102ITEM24Canceled
REL001130SCH0003102ITEM34Canceled
REL001180SCH0002302ITEM26Modified
REL0011100SCH0001401ITEM12Created
REL0011110SCH0002401ITEM24Created
REL0011120SCH0003201ITEM34Created