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:

In Assembly Control, a reference number/ID is generated, which represents a combination of VIN, Line Station, and Assembly Kit.
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.
For every schedule line, sequence shipping data is inserted in the Sequence Shipping data (tdpur3517m000) session.
For every sequence shipping schedule line, a record is inserted in the Production Synchronous Calls (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 Production Synchronous Calls (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/ Production Synchronous Calls (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 Production Synchronous Calls (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:

The old sequence shipping schedule line in the Purchase Schedule - Lines (tdpur3111m000) session receives the status Canceled.
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.
The canceled sequence shipping line from the Sequence Shipping data (tdpur3517m000) session is inserted in the Production Synchronous Calls (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.
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/ Production Synchronous Calls (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:

The old sequence shipping schedule line in the Purchase Schedule - Lines (tdpur3111m000) session is simply updated and keeps the Order Generated status.
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.
The modified sequence shipping line from the Sequence Shipping data (tdpur3517m000) session is inserted in the Production Synchronous Calls (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 number	Job seq.	Assembly kit	Line station	Item	Date	Qty
VIN001	JS001	K01	LS01	ITEM1	10/1/99 8:00	2
VIN001	JS001	K01	LS01	ITEM2	10/1/99 8:00	4
VIN001	JS001	K01	LS01	ITEM3	10/1/99 8:00	4
VIN002	JS002	K02	LS01	ITEM1	10/1/99 12:00	2
VIN002	JS002	K02	LS01	ITEM2	10/1/99 12:00	5
VIN002	JS002	K02	LS01	ITEM4	10/1/99 12:00	4
VIN003	JS003	K03	LS01	ITEM1	10/1/99 16:00	2
VIN003	JS003	K03	LS01	ITEM2	10/1/99 16:00	4
VIN003	JS003	K03	LS01	ITEM5	10/1/99 16:00	8

Results in the Purchase Schedule - Lines (tdpur3111m000) session:

Schedule number	Pos.	Item	Requirement date	Qty
SCH0001	10	ITEM1	10/1/99 8:00	2
SCH0002	10	ITEM2	10/1/99 8:00	4
SCH0003	10	ITEM3	10/1/99 8:00	4
SCH0001	20	ITEM1	10/1/99 12:00	2
SCH0002	20	ITEM2	10/1/99 12:00	5
SCH0004	10	ITEM4	10/1/99 12:00	4
SCH0001	30	ITEM1	10/1/99 16:00	2
SCH0002	30	ITEM2	10/1/99 16:00	4
SCH0005	10	ITEM5	10/1/99 16:00	8

Results in the Sequence Shipping data (tdpur3517m000) session:

Schedule	Pos.	Seq. revision	VIN	Job seq.	Kit	Line station	Item	Date	Qty	Status
SCH0001	10	1	VIN001	JS001	K01	LS01	ITEM1	10/1/99 8:00	2	Created
SCH0002	10	1	VIN001	JS001	K01	LS01	ITEM2	10/1/99 8:00	4	Created
SCH0003	10	1	VIN001	JS001	K01	LS01	ITEM3	10/1/99 8:00	4	Created
SCH0001	20	1	VIN002	JS002	K02	LS01	ITEM1	10/1/99 12:00	2	Created
SCH0002	20	1	VIN002	JS002	K02	LS01	ITEM2	10/1/99 12:00	5	Created
SCH0004	10	1	VIN002	JS002	K02	LS01	ITEM4	10/1/99 12:00	4	Created
SCH0001	30	1	VIN003	JS003	K03	LS01	ITEM1	10/1/99 16:00	2	Created
SCH0002	30	1	VIN003	JS003	K03	LS01	ITEM2	10/1/99 16:00	4	Created
SCH0005	10	1	VIN003	JS003	K03	LS01	ITEM5	10/1/99 16:00	8	Created

Results in the Production Synchronous Calls (tdpur3523m000) session:

Release number	Release pos.	Schedule	Schedule pos.	Seq. revision	Item	Qty	Status
REL001	10	SCH0001	10	1	ITEM1	2	Created
REL001	20	SCH0002	10	1	ITEM2	4	Created
REL001	30	SCH0003	10	1	ITEM3	4	Created
REL001	40	SCH0001	20	1	ITEM1	2	Created
REL001	50	SCH0002	20	1	ITEM2	5	Created
REL001	60	SCH0004	10	1	ITEM4	4	Created
REL001	70	SCH0001	30	1	ITEM1	2	Created
REL001	80	SCH0002	30	1	ITEM2	4	Created
REL001	90	SCH0005	10	1	ITEM5	8	Created

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
Schedule	Pos.	Item	Requirement date	Qty	Status
SCH0001	10	ITEM1	10/1/99 8:00	2	Canceled
SCH0002	10	ITEM2	10/1/99 8:00	4	Canceled
SCH0003	10	ITEM3	10/1/99 8:00	4	Canceled

Updated
Schedule	Pos.	Item	Requirement date	Qty	Status
SCH0002	30	ITEM2	10/1/99 16:00	6	Order Generated

New
Schedule	Pos.	Item	Requirement date	Qty	Status
SCH001	40	ITEM1	10/1/99 8:00	2	Order Generated
SCH002	40	ITEM2	10/1/99 8:00	4	Order Generated
SCH003	20	ITEM3	10/1/99 8:00	4	Order Generated

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

Schedule	Pos.	Seq. revision	VIN	Job seq.	Kit	Item	Date	Qty	Sent	Status
SCH0001	10	1	VIN001	JS001	K01	ITEM1	10/1/99 8:00	2	Yes	Created
SCH0001	10	2	VIN001	JS001	K01	ITEM1	10/1/99 8:00	2	No	Canceled
SCH0001	40	1	VIN004	JS001	K04	ITEM1	10/1/99 8:00	2	No	Created
SCH0002	10	1	VIN001	JS001	K01	ITEM2	10/1/99 8:00	4	Yes	Created
SCH0002	10	2	VIN001	JS001	K01	ITEM2	10/1/99 8:00	4	No	Canceled
SCH0002	40	1	VIN004	JS001	K04	ITEM2	10/1/99 8:00	4	No	Created
SCH0003	10	1	VIN001	JS001	K01	ITEM3	10/1/99 8:00	4	Yes	Created
SCH0003	10	2	VIN001	JS001	K01	ITEM3	10/1/99 8:00	4	No	Canceled
SCH0003	20	1	VIN004	JS001	K04	ITEM3	10/1/99 8:00	4	No	Created
SCH0002	30	1	VIN003	JS003	K03	ITEM2	10/1/99 16:00	4	Yes	Created
SCH0002	30	2	VIN003	JS003	K03	ITEM2	10/1/99 16:00	6	No	Modified

As a result, the following changes are made in the Production Synchronous Calls (tdpur3523m000) session:

Release number	Release revision	Release pos.	Schedule	Schedule pos.	Seq. revision	Item	Qty	Status
REL001	1	10	SCH0001	10	2	ITEM1	2	Canceled
REL001	1	20	SCH0002	10	2	ITEM2	4	Canceled
REL001	1	30	SCH0003	10	2	ITEM3	4	Canceled
REL001	1	80	SCH0002	30	2	ITEM2	6	Modified
REL001	1	100	SCH0001	40	1	ITEM1	2	Created
REL001	1	110	SCH0002	40	1	ITEM2	4	Created
REL001	1	120	SCH0003	20	1	ITEM3	4	Created