ANSI X12 - DELJIT - 862 - V4010 - O - v1.0 - 20090225

Download as doc, pdf, or txt
Download as doc, pdf, or txt
You are on page 1of 22

Version 1.

0 ANSI X12_DELJIT_862_V4010_O

Kia Motor Manufacturing Georgia, LLC


IMPLEMENTATION GUIDELINES FOR ASC X12 EDI CONVENTIONS
SHIPPING SCHEDULE (862)
VERSION/RELEASE 004010

Guideline Version 1.0


Issue Date 02/25/2009

Hyundai Motor Manufacturing Alabama, LLC


700 Hyundai Boulevard
Copyright 2009 by Kia Motor Manufacturing Georgia. All rights reserved. 1
Montgomery, Alabama 36105
Version 1.0 ANSI X12_DELJIT_862_V4010_O

862 Shipping Schedule


Functional Group ID= SS
Introduction:
This Draft Standard for Trial Use contains the format and establishes the data contents of the Shipping Schedule
Transaction Set (862) for use within the context of an Electronic Data Interchange (EDI) environment. The
transaction set can be used by a customer to convey precise shipping schedule requirements to a supplier, and is
intended to supplement the planning schedule transaction set (830). The shipping schedule transaction set will
supersede certain shipping and delivery information transmitted in a previous planning schedule transaction, but it
does not replace the 830 transaction set. The shipping schedule transaction set shall not be used to authorize labor,
materials or other resources.
The use of this transaction set will facilitate the practice of Just-In-Time (JIT) manufacturing by providing the
customer with a mechanism to issue precise shipping schedule requirements on a more frequent basis than with the
issuance of a planning schedule transaction, e.g., daily shipping schedules versus weekly planning schedules. The
shipping schedule transaction also provides the ability for a customer location to issue shipping requirements
independent of other customer locations when planning schedule transactions are issued by a consolidated
scheduling organization.

Copyright  2009 by Kia Motor Manufacturing Georgia. All rights reserved. 2


Version 1.0 ANSI X12_DELJIT_862_V4010_O
Data Format Specification:

Data Elements

Data elements and data segments can be classified differently in different transaction sets:

M Mandatory
O Optional
X Conditional – depends on contents of other field or condition All
data
elements are assigned minimum required and maximum permissible character lengths specified in the data element
dictionary. If a data element is transmitted, it must meet minimum/maximum length requirements, regardless of the
element’s content.
Each data element has a defined data type specified in the data element dictionary. Data types include:

ID Identification
Nn Numeric without decimal point, positive if there is not minus
R Explicit
AN Alphanumeric
DT Date
TM Time

4/10 Element Length 10, use at least 4

For transmission purposes, numeric (Nn) and decimal (R) fields are assumed to be positive unless a leading minus
sign indicating a negative value is transmitted. A plus sign is never transmitted. When transmitted, the minus sign (-)
and the decimal point (data type [R]), are not counted as part of the data element’s length.

 The decimal point for numeric (Nn) data types is implicitly located within the data element according to the
specified data type, but is not transmitted with the data. For example, data type N3 implies three decimal
places.

Example: Value to be communicated: -123.45


Data Element Type: N3
Transmission content: -123450
(Computed length equals 6)

 The decimal point for decimal (R) data types is explicitly located within the data element. There is no limit
on the number of fractional digits, as long as the total number of digits does not exceed the maximum
length specified.

Example: Value to be communicated: -123.45


Data Element Type: R
Transmission content: -123.45
(Computed length equals 5)

 If a data element is not transmitted, its default value cannot be assumed (e.g.,a numeric data element not
transmitted cannot be assumed to have a value of zero {0}).

 Numeric and decimal data should be transmitted with only significant zeros. Alphanumeric data elements
should be transmitted with no leading or trailing blanks.

 Conditional relationships within a data segment are noted and explained in the specification

Copyright  2009 by Kia Motor Manufacturing Georgia. All rights reserved. 3


Version 1.0 ANSI X12_DELJIT_862_V4010_O
Table 1: Heading
Pos. Seg. Req. Loop Notes and
Name Max. Use
No. ID Repeat Comments
010 ST Transaction Set Header M 1
Beginning Segment for Shipping Schedule/Production
020 BSS M 1
Sequence
LOOP ID - N1 200
050 N1 Name O 1

Table 2: Detail
Pos. Seg. Req. Loop Notes and
Name Max. Use
No. ID Repeat Comments
LOOP ID - LIN 10000
010 LIN Item Identification M 1
020 UIT Unit Detail M 1
050 REF Reference Identification O 12

LOOP ID - FST 100


080 FST Forecast Schedule O 1

Table 3: Summary
Pos. Seg. Req. Loop Notes and
Name Max. Use
No. ID Repeat Comments
010 CTT Transaction Totals O 1
020 SE Transaction Set Trailer M 1

Copyright  2009 by Kia Motor Manufacturing Georgia. All rights reserved. 4


Version 1.0 ANSI X12_DELJIT_862_V4010_O

Segment: ISA Interchange Control Header


Position:
Loop:
Level: N/A
Usage: Mandatory 1 per interchange
Max Use: 1
Purpose: To start and identify an interchange of one or more functional groups and interchange-related
control segments
Syntax Notes:
Semantic Notes: 1. The actual values of the data element separator and the data segment terminator for this
interchange are set by the interchange control header. For a particular interchange, the value at
the fourth character position is the data element separator, and the value of the last character
position is the value of the data segment terminator. The extent of this particular usage of the
data element separator and the data segment separator terminator is from this header to and
including the next interchange trailer.
The interchange control number value in ISA13 in this header must match the value in the same
data element n the corresponding interchange control trailer in IEA02 .
Comments: The first occurrence of the data element separator (byte 4) defines the actual value of the data
element separator and is graphically displayed as an asterisk “*”. The first occurrence of the
segment terminator, 1 byte after the data element ISA16, defines the actual value of the data
segment terminator and is graphically displayed as ~.
Example:
ISA*00* *00* *ZZ*KMMG-USA *ZZ*Supplier *040218*1438*U*00401*000000031*0*T*>~

Data Element Summary


Data
Ref. Element
Des. Name Attributes
ISA01 I01 Authorization Information Qualifier M ID 2/2
00 No Authorization Information Present
ISA02 I02 Authorization Information M AN 10/10
10 empty spaces must be entered here as the ISA segment is space sensitive.
ISA03 I03 Security Information Qualifier M ID 2/2
00 No Password
ISA04 I04 Security Information M ID 10/10
10 empty spaces must be entered here as the ISA segment is space sensitive.
ISA05 I05 Interchange ID Qualifier M ID 2/2
ZZ Mutually Defined
ISA06 I06 Interchange Sender ID M ID 15/15
Left justify, space fill
KMMG-USA
ISA07 I05 Interchange ID Qualifier M ID 2/2
ZZ Mutually Defined
ISA08 I07 Interchange Receiver ID M ID 15/15

Left justify, space fill


Supplier
ISA09 I08 Interchange Date M DT 6/6
Date of creation
ISA10 I09 Interchange Time M TM 4/4

Copyright  2009 by Kia Motor Manufacturing Georgia. All rights reserved. 5


Version 1.0 ANSI X12_DELJIT_862_V4010_O
Time of creation

Copyright  2009 by Kia Motor Manufacturing Georgia. All rights reserved. 6


Version 1.0 ANSI X12_DELJIT_862_V4010_O

ISA11 I10 Interchange Control Standards Identifier M ID 1/1


U United States
ISA12 I11 Interchange Control Version Number M ID 5/5
00401
ISA13 I12 Interchange Control Number M N0 9/9
A number that cannot be repeated within a 1 year period at a time
ISA14 I13 Acknowledgment Requested M ID 1/1
Use “0” for no Ack. Req., use “1” for Ack. Req.
0 No Acknowledgement requested
ISA15 I14 Test Indicator M ID 1/1
Use “T” for test data or “P” for production data
ISA16 I15 Component Element Separator M ID 1/1

Copyright  2009 by Kia Motor Manufacturing Georgia. All rights reserved. 7


Version 1.0 ANSI X12_DELJIT_862_V4010_O

Segment: GS Functional Group Header


Position:
Loop:
Level: N/A
Usage: Mandatory 1 per functional group
Max Use: 1
Purpose: To indicate the beginning of a functional group and to provide control information
Syntax Notes:
Semantic Notes: See the ASC X12 segment directory for rules and notes
Comments: Strict compliance and agreement on content by trading partners is required.
Example: GS*SS*KMMG-USA*Supplier*20090218*1438*31*X*004010~

Data Element Summary


Data
Ref. Element
Des. Name Attributes
GS01 479 Functional Identifier Code M ID 2/2
SS Shipping Schedule
GS02 142 Application Sender’s Code M ID 2/15
KMMG-USA
GS03 124 Application Receiver’s Code M ID 2/15
Supplier
GS04 373 Date M DT 8/8
Date Created
GS05 337 Time M TM 4/8
Time created
GS06 25 Group Control Number M N0 1/9
Start with 1 and increment by 1 for each subsequent GS segment
GS07 455 Responsible Agency Code M ID 1/2
Code used in conjunction with Data Element GS08 to identify the issuer of the
standard
X ASC X12 format
GS08 480 Version/Release/Industry ID Code M ID 6/12

This code indicates the version, release and subrelease of the EDI standard
being used, including the GS and GE segments. Positions 1-3 are the version
number; positions 4-6 are the release and subrelease, level of the version
004010 Draft Standard

Copyright  2009 by Kia Motor Manufacturing Georgia. All rights reserved. 8


Version 1.0 ANSI X12_DELJIT_862_V4010_O

Segment: ST Transaction Set Header


Position: 010
Loop:
Level: Heading
Usage: Mandatory
Max Use: 1
Purpose: To indicate the start of a transaction set and to assign a control number
Syntax Notes: 1. The transaction set identifier (ST01) used by the translation routines of the interchange
partners to select the appropriate transaction set definition (e.g. 810 selects the Invoice
Transaction Set).
Semantic Notes:
1. The Transaction Set Control Number (ST02) in this header must match the Transaction
Set Control Number (SE02) in the Transaction Set Trailer (SE).
Comments:
Example: ST*862*123456789~

Data Element Summary


Data
Ref. Element
Des. Name Attributes
ST01 143 Transaction Set Identifier Code M ID 3/3
Code uniquely identifying a Transaction Set
862 Shipping Schedule
ST02 329 Transaction Set Control Number M AN 4/9
Identifying control number that must be unique within the transaction set.

Copyright  2009 by Kia Motor Manufacturing Georgia. All rights reserved. 9


Version 1.0 ANSI X12_DELJIT_862_V4010_O

Segment: BSS Beginning Segment for Shipping Schedule/Production Sequence


Position: 020
Loop:
Level: Heading
Usage: Mandatory
Max Use: 1
Purpose: To transmit identifying numbers, dates, and other basic data relating to the transaction set
Syntax Notes:
Semantic Notes:1. Use BSS02 to indicate a document number
2. Use BSS03 to indicate the date of this document
3. Use BSS05 to indicate the schedule horizon start date (the date when the schedule begins)
4. Use BSS06 to indicate the schedule horizon end date (the date when the schedule ends)
5. BSS10 is the identifying number for a forecast assigned by the orderer/purchaser
Comments: Either BSS07 or BSS08 must be used, but not both
Example: BSS*05*4112*20090205*DL*20090206*20090208*4600000786****A~

Data Element Summary


Data
Ref. Element
Des. Name Attributes
BSS01 353 Transaction Set Purpose Code M ID 2/2
Code identifying purpose of transaction set
05 Replace
BSS02 127 Reference Number M AN 1/30
Reference information as defined for a particular Transaction Set or as
specified by the Reference Identification Qualifier
BSS03 373 Issue Date M DT 8/8
Date (CCYYMMDD)
BSS04 675 Schedule Type Qualifier M ID 2/2
Code identifying the type of dates used when defining a shipping or delivery
time in a schedule or forecast
DL Delivery Based
Specifies when the material must be at the receiving
location.
BSS05 373 Horizon Start Date M DT 8/8
Date (CCYYMMDD)
BSS06 373 Horizon End Date M DT 8/8
Date (CCYYMMDD)
BSS07 328 Release Number X AN 1/30
Number identifying a release against a Purchase Order previously placed by
the parties involved in the transaction
Reference this value for the 856 ASN in PFR01
BSS11 676 Schedule Quantity Qualifier O ID 1/1
Code identifying the type of quantities used when defining a schedule or
forecast
A Actual Discrete Quantities

Copyright  2009 by Kia Motor Manufacturing Georgia. All rights reserved. 10


Version 1.0 ANSI X12_DELJIT_862_V4010_O

Segment: N1 Name
Position: 050
Loop: N1
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To identify a party by type of organization, name, and code
Syntax Notes: 1. At least one of N102 or N104 is required
2. If either N103 or N104 is present, then the other is required
Semantic Notes:
Comments: 1. This segment, used alone, provides the most efficient method of providing organizational
identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table
maintained by the transaction processing party.
2. This N1 loop in the header area can be used to identify the shipping schedule issuer, the
supplier, and the ship-to and ship-from locations.
Example: N1*SF*ABC*92*N021~

Data Element Summary


Data
Ref. Element
Des. Name Attributes
N101 98 Entity Identifier Code M ID 2/2
Code identifying an organizational entity, a physical location, or an individual
SF Ship From
Party responsible for the material or service.
N102 93 Name X AN 1/35
Free-form name
N103 66 Identification Code Qualifier X ID 1/2
Code designating the system/method of code structure used for Identification
Code (67)
92 Assigned By Buyer
N104 67 Identification Code X AN 2/20
Code identifying a party or other code
Reference this value for the 856 ASN in N104

Copyright  2009 by Kia Motor Manufacturing Georgia. All rights reserved. 11


Version 1.0 ANSI X12_DELJIT_862_V4010_O

Segment: N1 Name
Position: 050
Loop: N1
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To identify a party by type of organization, name, and code
Syntax Notes: 1. At least one of N102 or N104 is required
2. If either N103 or N104 is present, then the other is required
Semantic Notes:
Comments: 1. This segment, used alone, provides the most efficient method of providing organizational
identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table
maintained by the transaction processing party.
2. This N1 loop in the header area can be used to identify the shipping schedule issuer, the
supplier, and the ship-to and ship-from locations.
Example: N1*ST*Kia Car Assembly*6*P001~

Data Element Summary


Data
Ref. Element
Des. Name Attributes
N101 98 Entity Identifier Code M ID 2/2
Code identifying an organizational entity, a physical location, or an individual
ST Ship To
Location where the Material Release Issuer (MI) wants
the Supplier (SU) to ship to.
N102 93 Name X AN 1/35
Free-form name
N103 66 Identification Code Qualifier X ID 1/2
Code designating the system/method of code structure used for Identification
Code (67)
6 Plant Code
N104 67 Identification Code X AN 2/20
Code identifying a party or other code
Reference this value for the 856 ASN in N104

Copyright  2009 by Kia Motor Manufacturing Georgia. All rights reserved. 12


Version 1.0 ANSI X12_DELJIT_862_V4010_O

Segment: LIN Item Identification


Position: 010
Loop: LIN
Level: Detail
Usage: Mandatory
Max Use: 1
Purpose: To specify basic item identification data
Syntax Notes: 1. If either LIN04 or LIN05 is present, then the other is required
2. If either LIN06 or LIN07 is present, then the other is required
Semantic Notes: 1. LIN01 is the item identification
Comments: “KK” is not according to AIAG Guide
Example: LIN*1*BP*833023D021YU*PL*1*KK*ABCD~

Data Element Summary


Data
Ref. Element
Des. Name Attributes
LIN01 350 Assigned Identification M AN 1/20
Alphanumeric characters assigned for differentiation within a transaction set
LIN02 235 Product/Service ID Qualifier M ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234)
BP Buyer's Part Number
LIN03 234 Product/Service ID - Buyer's Part M AN 1/40
Identifying number for a product or service
LIN04 235 Product/Service ID Qualifier X ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234)
PL Purchaser’s Order Line Number
Reference this value for the 856 ASN in PRF05
LIN05 234 Product/Service ID – Line Item Number on Contract X AN 1/40
Identifying number for a product or service
LIN06 235 Product/Service ID Qualifier X ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234)
KK Special Material Identifier Code
LIN07 234 Product/Service ID – Broadcast Code X AN 4/40
Identifying number for a product or service

Copyright  2009 by Kia Motor Manufacturing Georgia. All rights reserved. 13


Version 1.0 ANSI X12_DELJIT_862_V4010_O

Segment: UIT Unit Detail


Position: 020
Loop: LIN
Level: Detail
Usage: Mandatory
Max Use: 1
Purpose: To specify item unit data
Syntax Notes:
Semantic Notes:
Comments:
Example: UIT*EA~

Data Element Summary


Data
Ref. Element
Des. Name Attributes
UIT01 355 Unit or Basis for Measurement Code M ID 2/2
Code specifying the units in which a value is being expressed, or manner in
which a measurement has been taken.
This should be the same unit of measure as specified in the Planning
Schedule Transaction Set (830).
Any valid X12 code value except mutually defined; ’ZZ’
Reference this value for the 856 ASN in SN103

Copyright  2009 by Kia Motor Manufacturing Georgia. All rights reserved. 14


Version 1.0 ANSI X12_DELJIT_862_V4010_O

Segment: REF Reference Identification


Position: 050
Loop: LIN
Level: Detail
Usage: Optional
Max Use: 12
Purpose: To specify identifying information
Syntax Notes: “M1” is not according to AIAG Guide
Semantic Notes:
Comments:
Example: REF*9H*001~
REF*DK*PR1~
REF*LF*A01~
REF*M1*6785~

Data Element Summary


Data
Ref. Element
Des. Name Attributes
REF01 128 Reference Identification Qualifier M ID 2/3
Code qualifying the Reference Identification
9H Packaging Group Number
DK Dock Number
LF Assembly Line Feed Location
M1 Material Storage Location
REF02 127 Reference Identification - Dock Code X AN 1/30
Reference information as defined for a particular Transaction Set or as
specified by the Reference Identification Qualifier
RPCNumber
DockNumber
AssemblyLineLocation
StorageLocation

Copyright  2009 by Kia Motor Manufacturing Georgia. All rights reserved. 15


Version 1.0 ANSI X12_DELJIT_862_V4010_O

Segment: FST Forecast Schedule


Position: 080
Loop: LIN/FST
Level: Detail
Usage: Required
Max Use: 1
Purpose: To specify the forecasted dates and quantities
Syntax Notes: 1. If either FST06 or FST07 is present, then the other is required
Semantic Notes:
Comments: 1. Firm and planning discrete quantities daily
2. FST06 qualifies the time in FST07. The purpose of the FST07 element is to express the
specific time of day in a 24-hour clock to satisfy "just-in-time" requirements.
3. At least one FST loop is required
4. FST02 Qualifier “P” is not according to AIAG Guide
Example: FST*310*C*D*20090205**002*0800~
FST*100*P*D*20090206~

Data Element Summary


Data
Ref. Element
Des. Name Attributes
FST01 380 Net Quantity M R 1/15
Numeric value of quantity
If the JIT segment is used, then this must equal the sum of all JIT
requirements for the period covered by the FST segment.
Reference this value for the 856 ASN in SN102
FST02 680 Forecast Qualifier M ID 1/1
Code specifying the sender's confidence level of the forecast data or an action
associated with a forecast
C Firm
P Planning
FST03 681 Forecast Timing Qualifier M ID 1/1
Code specifying interval grouping of the forecast
D Discrete
FST04 373 Requirement Date M DT 8/8
Date (CCYYMMDD)
Reference this value for the 856 ASN in DTM02, where DTM01 = “002”
FST06 374 Requirement Date/Time Qualifier O ID 3/3
Code specifying type of date or time, or both date and time
002 Delivery Requested
Reference this value for the 856 ASN in DTM03, where DTM01 = “002”

FST07 337 Requirement Time X TM 4/8


Time of shipment or delivery when only one shipment is made on a given
day. Time expressed in 24-hour clock time as follows: HHMM where HH =
hours (00-23), MM = minutes (00-59)
If there are multiple requirements per day, the times/quantities will be
transmitted in the JIT segment.

Copyright  2009 by Kia Motor Manufacturing Georgia. All rights reserved. 16


Version 1.0 ANSI X12_DELJIT_862_V4010_O

Segment: CTT Transaction Totals


Position: 010
Loop:
Level: Summary
Usage: Mandatory
Max Use: 1
Purpose: To transmit a hash total for a specific element in the transaction set
Syntax Notes:
Semantic Notes:
Comments: 1. This segment is intended to provide hash totals to validate transaction completeness and
correctness.
Example: CTT*2~

Data Element Summary


Data
Ref. Element
Des. Name Attributes
CTT01 354 Number of Line Items M N0 1/6
Total number of line items (LIN segments) in the transaction set

Copyright  2009 by Kia Motor Manufacturing Georgia. All rights reserved. 17


Version 1.0 ANSI X12_DELJIT_862_V4010_O

Segment: SE Transaction Set Trailer


Position: 020
Loop:
Level: Summary
Usage: Mandatory
Max Use: 1
Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments
(including the beginning (ST) and ending (SE) segments)
Syntax Notes:
Semantic Notes:
Comments: 1. SE is the last segment of each transaction set.
2. The Transaction Set Control Number value in this trailer must match the same element value
in the Transaction Set Header (ST02).
Example: SE*45*123456789~

Data Element Summary


Data
Ref. Element
Des. Name Attributes
SE01 96 Number of Included Segments M N0 1/10
Total number of segments included in a transaction set including ST and SE
segments
SE02 329 Transaction Set Control Number M AN 4/9
Identifying control number that must be unique within the transaction set
functional group assigned by the originator for a transaction set

Copyright  2009 by Kia Motor Manufacturing Georgia. All rights reserved. 18


Version 1.0 ANSI X12_DELJIT_862_V4010_O

Segment: GE Functional Group Trailer


Position:
Loop:
Level: N/A
Usage: Mandatory 1 per functional group
Max Use: 1
Purpose: To indicate the end of a functional group and to provide control information
Syntax Notes:
Semantic Notes: The data interchange control number (GE02) in this trailer must be identical to the same data
element in the associated functional group header (GS06).
Comments:
Example: GE*1*31~

Data Element Summary


Data
Ref. Element
Des. Name Attributes
GE01 97 Number of Transaction Sets Included M N0 1/6
Total number of ST segments in group
GE02 28 Group Control Number M N0 1/9
Must be identical to the same data element in the associated group header
(GS06)

Copyright  2009 by Kia Motor Manufacturing Georgia. All rights reserved. 19


Version 1.0 ANSI X12_DELJIT_862_V4010_O

Segment: IEA Interchange Control Trailer


Position:
Loop:
Level: N/A
Usage: Mandatory 1 per Interchange
Max Use: 1
Purpose: To define the end of an interchange of zero or more functional groups and interchange-related
control segments
Syntax Notes:
Semantic Notes: The interchange control number IEA02 in this trailer must match the value in ISA13
Comments:
Example: IEA*1*000000031~

Data Element Summary


Data
Ref. Element
Des. Name Attributes
IEA01 I16 Number of Included Functional Groups M N0 1/5
Number of GS segments included between ISA and this IEA
IEA02 I12 Interchange Control Number M N0 9/9
Must match ISA13

Copyright  2009 by Kia Motor Manufacturing Georgia. All rights reserved. 20


Version 1.0 ANSI X12_DELJIT_862_V4010_O
Example 1 EDI Structure

EDI FORMAT INTERPRETATION

ST*862*0030~ X12 Transaction Set = 862 (Shipping Schedule)


Transaction Set Control Number = 0030

BSS*05*1102*20090318*DL*20090318*20090322*4600001 Transaction Set Purpose = 05 (Replace)


285****A~ Unique Reference Number = 1102
Current Date = 03/18/2009
Delivery Based
Horizon Start Date = 03/18/2009
Horizon End Date = 03/22/2009
Purchase Order Number = 4600001285
Actual discrete quantities

N1*SF*ABC*92*N021~ Ship From ID Code Number = N021

N1*ST*Kia Car Assembly, AL*6*P001~ Ship To ID Plant Code Number = P001

LIN*1*BP*9861039500*PL*1~ Customer-assigned Part Number = 9861039500


Purchase Order Line = 1

UIT*EA~ Unit of Measure = Each

REF*9H*001 RPC Number = 001

REF*DK*PR1~ Dock Number = PR1

REF*LF*A01~ Assembly Line Location = A01

REF*M1*6785~ Storage Location = 6785

FST*210*C*D*20090318**002*0800~ Daily Firm Shipment Quantity = 210


Shipment Date = 03/18/2009
Shipment Time = 8:00
Delivery requested

FST*1000*C*D*20090319**002*0800~ Daily Firm Shipment Quantity = 1000


Shipment Date = 03/19/2009
Shipment Time = 8:00
Delivery requested

FST*300*C*D*20090322**002*0800~ Daily Firm Shipment Quantity = 300


Shipment Date = 03/22/2009
Shipment Time = 8:00
Delivery requested

FST*280*P*D*20090323~ Daily Planning Shipment Quantity = 280


Shipment Date = 03/23/2009

FST*360*P*D*20090324~ Daily Planning Shipment Quantity = 360


Shipment Date = 03/24/2009

FST*310*P*D*20090325~ …
FST*420*P*D*20090326~
FST*310*P*D*20090329~

Copyright  2009 by Kia Motor Manufacturing Georgia. All rights reserved. 21


Version 1.0 ANSI X12_DELJIT_862_V4010_O
FST*420*P*D*20090330~
FST*310*P*D*20090331~
FST*420*P*D*20090401~
FST*450*P*D*20090402~
FST*480*P*D*20090405~
FST*320*P*D*20090406~
FST*220*P*D*20090407~
FST*480*P*D*20090408~
FST*420*P*D*20090409~
CTT*1~ Total number of Lin Items = 1

SE*29*0030~ Total Number of Segments = 31


Transaction Set Control Number = 0030

Copyright  2009 by Kia Motor Manufacturing Georgia. All rights reserved. 22

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy