Previous	Next		Contents	Index	Navigation	Glossary	Library

Each planning schedule contains one schedule header record that applies to the entire schedule. The schedule header is followed by one or more schedule lines, each representing an item. Each schedule line is followed by one or more line details representing requirements, authorizations, and the item's last and cumulative receipts.

The ship to location is at the schedule line level. All schedule quantities are discrete quantities, not cumulative quantities. The CUM enabling flag addresses only the receipt data to be provided as a CUM receipt quantity. The CUM enabling flag does not impact the schedule requirements.

The line details section includes the following:

Requirements	Up to 60 occurrences per the user-defined bucket and planning horizon for the schedule.
Prior Authorization	One occurrence if authorizations are enabled at the Approved Suppliers list.
Authorizations	One occurrence for each authorization type if authorizations are enabled at the Approved Supplier list. Authorizations cover raw material, labor, labor & material or finished goods.
Last Receipt	One occurrence identifying the quantity, date and shipment number of the last receipt for the item.
Cumulative Receipt	One occurrence identifying the cumulative receipt quantity for the item if CUM accounting is enabled.

The output file is structured as follows:

• schedule header

• schedule line and cumulative receipt

schedule line detail (requirements)

schedule line detail (authorizations)

schedule line detail (last receipt)

• schedule line and cumulative receipt

schedule line detail (requirements)

schedule line detail (last receipt)

General Information

• Planning Schedule (830) / Delivery Just in Time (DELJIT)

• Shipping Schedule (862) / Delivery Schedule (DELFOR)

Details for the ASC X12 transactions are documented below.

The shipping schedule transaction does not include the last shipment receipt records 2040 and the 4000 with Detail Descriptor set to RECEIPT or authorizations with Detail Descriptor set to AUTHORIZATION. Otherwise, the interface files are identical.

Discrete (actual) requirement quantities are indicated in the buckets in the application, i.e., in a weekly bucket, the quantity required for that week only.

The EDI Translator needs to build cumulative required quantities using the cum received quantity if the trading partner wants a cumulative schedule.

Ship to Location

ASC X12 Specifics

ASC X12 Data Element	ASC X12 Position and Values	Data
Transaction Purpose	BRF01 = 05	Replacement Schedules Only
Schedule Type Qualifier	BRF04 = DL	Delivery Based Schedules
Schedule Quantity Qualifier	BRF05 = `A'	Actual Discrete Quantity Only
Table 1 - 60. (Page 1 of 1)

Last Receipt Data (Record 2040) - Item Level

This data is mapped to the ASC X12 Shipped (SHP) and Reference (REF) segments.

			Record 4000 Source
Pos.	Interface Record	Receipt	Detail Category/ Descriptor	Data Element
		(Map to ASC X12 `SHP' segment)
	Common Key
	Record Number	2040
	Record Layout	LS
	Record Layout Qualifier	LS1
10	Last Receipt Shipment Identification	AUTHORIZATION <Shipment Number>	RECEIPT/LAST	100 Document Type
20	Last Receipt Date	PRIOR <Last Transaction Date>	RECEIPT/LAST	50 Starting Date
30	Last Receipt Quantity	<Last Quantity Received>	RECEIPT/LAST	90 Total Quantity
40	CUM Quantity after last Receipt	<Starting CUM Quantity>	RECEIPT/CUMULATIVE	90 Total Quantity
Table 1 - 61. Last Receipt and Cumulative Data-Record 2040 Details

through illustrate where data in Table 1 - 61 is mapped in SHP and REF segments. Two occurrences of SHP segments are required: one to specify last discrete quantity received or shipped, and one to specify cumulative quantity received or shipped since last cum reset.

SHP Segment	Data Element	Position	Content	Record 2040 Source
Quantity Qualifier	673	SHP01=	01	Standard for discrete quantity
Quantity	380	SHP02=	<Last Shipment Quantity>	30 Last Receipt Quantity
Date/Time Qualifier	374	SHP03=	050 or 011	Standard for Received or Standard for Shipped
Date	373	SHP04=	<Last Receipt Date>	20 Last Receipt Date
Time	337	SHP05=	n/a
Date	373	SHP06=	n/a
Time	337	SHP07=	n/a
Table 1 - 62. Data Mapping of the Last Receipt Data from Record 2040 to map to Shipped (SHP) segment

SHP Segment	Data Element	Position	ASC X12 Value	Record 2040 Source
Quantity Qualifier	673	SHP01=	02	40 Standard for Cumulative quantity
Quantity	380	SHP02=
Date/Time Qualifier	374	SHP03=	051	Standard for Cumulative quantity Start
Date	373	SHP04=
Time	337	SHP05=	n/a
Date	373	SHP06=	n/a
Time	337	SHP07=	n/a
Table 1 - 63. Data Mapping of the Cumulative Quantity Received from Record 2040 to SHP shipment

REF Segment	Data Element	Position	ASC X12 Value	Record 2040 Source
Reference Qualifier		REF01=	SI	Standard for Shipment Identifier
Reference Identification		REF02=	<shipment number>	10 Last Receipt Shipment Number
Table 1 - 64. Data Mapping of the Last Receipt Shipment Number from Record 2040 to REF segment

Forecast/Planned Details (Record 4000)

• Shipped/Received Information (SHP)

• Resource Authorization (ATH)

• Forecast Schedule (FST)

The dates on the Forecast Schedule (FST) segment represent the starting date for the bucketed period only. Ending date is applicable only for Detail Descriptor BUFFER in the Record 4000.

A given transaction may technically have a mixture of planning schedules with discrete and cumulative based quantities if the supplier scheduling process does not prohibit it across all the items within a single transaction.

The quantities and start/end dates on record 4000 data for a given Detail Category and Detail Descriptor varies depending upon if the SHIP_TO_ORG_ ENABLE_CUM_FLAG is enabled. See the Record 4000 Detail tables below for their content.

Last Receipt Data (Record 4000) - Shipment Level

and summarize the type of data found on record 4000:

	Record 4000 Detail Category (position 20)	Record 4000 Detail Descriptor (position 30)	Associated ASC X12 Segment	Record Content
A	RECEIPT	LAST	SHP	Last Receipt data (data also on record 2040)
B	RECEIPT	CUMULATIVE	SHP	CUM total attained upon last received shipment. (Data also on record 2040) Create this SHP record only if the ship to location is doing CUM management (CUM Flag is enabled).
C	AUTHORIZATION	PRIOR	ATH	Prior Authorization
D	AUTHORIZATION	FI	ATH	Authorization data for finished Inventory
	AUTHORIZATION	LB	ATH	Authorization data for labor only
	AUTHORIZATION	LM	ATH	Authorization data for labor and material
	AUTHORIZATION	MT	ATH	Authorization data for material only
E	REQUIREMENT	PAST_DUE	FST	Planned or firm requirements for Past due (immediate use) quantities
	REQUIREMENT	DAY	FST	Planned or firm requirements in daily quantities
	REQUIREMENT	BUFFER	FST	Planned or firm requirements for flexible intervals quantities
	REQUIREMENT	WEEK	FST	Planned or firm requirements for weekly quantities
	REQUIREMENT	MONTH	FST	Planned or firm requirements for monthly quantities
	REQUIREMENT	QUARTER	FST	Planned or firm requirements for quarterly quantities
Table 1 - 65. Data Content by Detail Category and Detail Descriptor for Record 4000

Key data elements for the ASC X12 segment given Detail Category and Detail Descriptor indicated.

	Record 4000 Detail Category (position 20)	Record 4000 Detail Descriptor (position 30)	Key ASC X12 Data Element	Note
A	RECEIPT	LAST	SHP01= 01 (Discrete Qty)	Also written to Record 2040
			SHP03= 050 (Received)
B	RECEIPT	CUMULATIVE	SHP02=02 (Cum Qty)	Create SHP segment only if SHIP_TO_ORG_ENABLE_CUM_FLAG is enabled.
			SHP03=051 (Cum Qty Start)	Also written to Record 2040
C	AUTHORIZATION	PRIOR	ATH01=PQ (Cum Requirement Prior to First Schedule Period)
D	AUTHORIZATION	FI	ATH01=FI (Finished Inventory)
	AUTHORIZATION	LB	ATH01= LB (labor)
	AUTHORIZATION	LM	ATH01= LM (labor, material)
	AUTHORIZATION	MT	ATH01= MT (material)
E	REQUIREMENT	PAST_DUE	FST02 =A (Immediate)
	REQUIREMENT	(all values except PAST_DUE)	FST02 =C (Firm)	If Release Quantity > 0
	REQUIREMENT	(all values except PAST_DUE)	FST02 =D (Planning)	If Forecast Quantity > 0
	REQUIREMENT	PAST_DUE	FST03=A (Immediate)
	REQUIREMENT	DAY	FST03=C (Daily)
	REQUIREMENT	BUFFER	FST03=F (Flexible Interval)
	REQUIREMENT	WEEK	FST03=W (Weekly Bucket)
	REQUIREMENT	MONTH	FST03=M (Monthly Bucket)
	REQUIREMENT	QUARTER	FST03=Q (Quarterly)
Table 1 - 66. Key ASC X12 Data Element per Detail Category and Detail Descriptor within Record 4000

through illustrate the details of record 4000 for each pair of values of the Detail Category and Detail Descriptor, followed by the placement of data on the ASC X12 transaction.

A. Receipt / Last

Position	Interface Record	Last Shipment
		(Map to ASC X12 `SHP' segment)
	Common Key
	Record Number	4000
	Record Layout	SC
	Record Layout Qualifier	SCH
10	Schedule Item Detail Sequence	<a counter>
20	Detail Category	AUTHORIZATION RECEIPT
30	Detail Descriptor	PRIOR LAST
40	Detail Descriptor (external)
50	Starting Date	<Last Shipment Date>
60	Ending Date	n/a
70	Forecast Quantity	n/a
80	Release Quantity	n/a
90	Total Quantity	<Actual Last Shipped Quantity or zero>
100	Document Type	SHIPMENT
110	Document Number	<Shipment Number>
Table 1 - 67. RECEIPT / LAST--Record 4000 Details (maps to SHP segment)

This data is also found on the Record 2040 at the schedule level.

SHP Segment	Data Element	Position	ASC X12 Value	Record 4000
Quantity Qualifier	673	SHP01=	01	Standard for Discrete Quantity
Quantity	380	SHP02=	<Last Shipment Qty>	90 Total Quantity
Date/Time Qualifier	374	SHP03=	050	Standard for Received
Date	373	SHP04=	<Last Shipment Date>	50 Starting Date
Time	337	SHP05=	n/a
Date	373	SHP06=	n/a
Time	337	SHP07=	n/a
Table 1 - 68. RECEIPT / LAST--Record 4000 mapped to Shipped (SHP) segment

B. Receipt / Cumulative

Pos.	Interface Record	Cumulative Receipt
		(Map to ASC X12 `SHP' segment)
	Common Key
	Record Number	4000
	Record Layout	SC
	Record Layout Qualifier	SCH
10	Schedule Item Detail Sequence	<a counter>
20	Detail Category	AUTHORIZATION RECEIPT
30	Detail Descriptor	PRIOR CUMULATIVE
40	Detail Descriptor (external)
50	Starting Date	<Cum Period Start Date> Ship To Org CUM Period Start Date
60	Ending Date	<Schedule Horizon Start Date> (Forecast Horizon Start Date)
70	Forecast Quantity	n/a
80	Release Quantity	n/a
90	Total Quantity	Cumulative Receipt Quantity as of schedule Horizon Start Date
100	Document Type	n/a
110	Document Number	n/a
Table 1 - 69. RECEIPT / CUMULATIVE--Record 4000 Details

This data is also moved to the Record 2040 at the item level.

SHP Shipped Segment	Data Element	Position	ASC X12 Value	Record 4000
Quantity Qualifier	673	SHP01=	02	Standard for Cum Quantity
Quantity	380	SHP02=	<CUM Receipt Qty as of schedule Horizon Start Date>	90 Total Quantity
Date/Time Qualifier	374	SHP03=	051	Standard for Cum Quantity
Date	373	SHP04=	<Ship to Org CUM Period Start Date>	50 Starting Date
Time	337	SHP05=	n/a
Date	373	SHP06=	<Forecast Horizon Start Date> *	60 Ending Date
Time	337	SHP07=	n/a
Table 1 - 70. RECEIPT / CUMULATIVE--Record 4000 mapped to SHP Segment *The ending date of the cumulative period is the starting date of the schedule.

C. Authorization / Prior

File Pos.	Interface Record	CUM Management Enabled	CUM Management Not Enabled
			This record does not exist if CUM Management is Not Enabled.
	Common Key
	Record Number	4000
	Record Layout	SC
	Record Layout Qualifier	SCH
10	Schedule Item Detail Sequence	<a counter>
20	Detail Category	AUTHORIZATION
30	Detail Descriptor	PRIOR
40	Detail Descriptor (external)
50	Starting Date	<Cum Period Start Date> *
60	Ending Date	<Schedule Horizon Start Date>
70	Forecast Quantity	n/a
80	Release Quantity	n/a
90	Total Quantity	<Starting Authorization Quantity (sum of past due and CUM received)>
100	Document Type	n/a
110	Document Number	n/a
Table 1 - 71. AUTHORIZATION / PRIOR--Record 4000 Details with CUM enabled and not enabled (to map to AASC X12 'ATH' segment). *The ending date of the cumulative period is the starting date of the schedule.

ATH Authorization Segment	Data Element	Position	ASC X12 Value	Record 4000 Source
Resource Authorization Code	672	ATH01=	PQ	Standard (CUM qty required Prior to first Schedule Period) (based on 30 Detail Descriptor is 'PRIOR')
Date (through Date)	373	ATH02=	<Schedule Horizon Start Date>	60 Ending Date
Quantity (Current Cum Requirement Qty)	380	ATH03=	<Starting Authorization Quantity>	90 Total Quantity
Quantity	380	ATH04=	n/a	n/a
Date (Cumulative Start Date)	373	ATH05=	<CUM Period Start Date>	50 Starting Date
Table 1 - 72. AUTHORIZATION / PRIOR--Record 4000 Details mapped to ATH segment

3. Authorization / FI, LB, LM, MT

File Pos.	Interface Record	CUM Management Not Enabled
	Common Key
	Record Number	4000
	Record Layout	SC
	Record Layout Qualifier	SCH
10	Schedule Item Detail Sequence	<a counter>
20	Detail Category	AUTHORIZATION
30	Detail Descriptor	FI or LB or LM or MT
40	Detail Descriptor (external)
50	Starting Date	<Schedule Horizon Start Date>
60	Ending Date	<Authorization Cut Off Date>
70	Forecast Quantity	n/a
80	Release Quantity	n/a
90	Total Quantity	<Cumulative Authorized Quantity for Schedule>
100	Document Type	n/a
110	Document Number	n/a
Table 1 - 73. AUTHORIZATION / (FL/LB/LM/MT)--Record 4000 Details with CUM enabled and not enabled (to map to ASC X12 'ATH' segment).

ATH Authorization Segment	Data Element	Position	ASC X12 Value	Record 4000 Source
Resource Authorization Code*	672	ATH01=	FI (Finished Inventory), LB (Labor), LM (Labor & Material), MT (Material	Standard (based on 30 Detail Descriptor)
Date (through Date)	373	ATH02=	If CUM or NOT CUM, <Authorization Cut Off Date>	60 Ending Date
Quantity (Current Cum Requirement Qty)	380	ATH03=	If CUM, <CUM Authorized Qty for CUM period> If NOT CUM, <Cumulative Authorized Qty for Schedule>	90 Total Quantity
Quantity	380	ATH04=	(blank)	n/a
Date (Cumulative Start Date)	373	ATH05=	If CUM, <CUM Period Start Date> If NOT CUM, <Schedule Horizon Start Date>	50 Starting Date
Table 1 - 74. AUTHORIZATION / (non-PRIOR Descriptor)--Record 4000 Details mapped to ATH segment

4. Requirement / PAST_DUE, DAY, BUFFER, WEEK, MONTH, QUARTER

Pos.	Interface Record
	Common Key
	Record Number	4000
	Record Layout	SC
	Record Layout Qualifier	SCH
10	Schedule Item Detail Sequence	<a counter>
20	Detail Category	REQUIREMENT
30	Detail Descriptor	PAST_DUE, BUFFER, DAY, WEEK, MONTH, QUARTER
40	Detail Descriptor (external)	A (Immediate (PAST_DUE)) F (Flexible Interval (BUFFER)) D (Day), W (Week), M (Month), Q (Quarter)
50	Starting Date	<Requirement Start Date>
60	Ending Date	<Requirement End Date	Only if Detail Descriptor is BUFFER
70	Forecast Quantity	<Discrete Quantity>
80	Release Quantity	<Discrete Release Quantity>
90	Total Quantity	<Cumulative Authorized Quantity for Schedule> (Sum of 70 Forecast Quantity and 80 Release Quantity	Not mapped to the standard
100	Document Type	n/a
110	Document Number	n/a
Table 1 - 75. REQUIREMENT / (all values)--Record 4000 Details (to map to ASC X12 'FST' segment).

Note: If both Release Quantity is greater than zero and Forecast Quantity is greater than zero, two ASC X12 FST segments should be generated.

If 80 Release Quantity >0,

• move 80 Release Quantity to Quantity (FST01)

• move `C' (Firm) to Forecast Qualifier (FST02)

• move 50 Start Date to Date (FST04)

• (and if Detail Descriptor is BUFFER, move 60 Ending Dates to Date (FST05)

If 80 release Quantity > 0 and Detail Descriptor is PAST_DUE

• move 80 Release Quantity to Quantity (FST01),

• move 'A' (Immediate) to Forecast Qualifier (FST02),

• more 50 Start Date to Date (FST04)

If 70 Forecast Quantity > 0,

• move 70 Forecast Quantity to Quantity (FST01),

• move `D' (Planned) to Forecast Qualifier (FST02)

• move 50 Start Date to Date (FST04)

• (and if Detail Descriptor is BUFFER, move 60 Ending Dates to Date (FST05)

Position 30 Detail Descriptor (internal) has a code conversion to determine position 40 Detail Descriptor (External) if needed for Forecast Timing Qualifier (FST03).

The Detail Descriptor of PAST_DUE is different as noted above.

Total quantity is the sum of released and forecast quantity. If needed, you can "demote" the release quantity to forecast when a bucketed period includes both. Sending both released and forecasted in the same time period is not actually done in EDI. However, Oracle data comes from two different sources that do not make each other mutually exclusive, so this could happen.

Firm Forecast Data

Planned Forecast Data

See Also

Outbound Planning Schedule and Shipping Schedule Summary Tables

Outbound Planning Schedule and Shipping Schedule Data File Definition