0% found this document useful (0 votes)
180 views34 pages

EDI Implementation Guidelines For The 850 - Purchase Order

The document provides guidelines for implementing the 850 Purchase Order transaction set between Lands' End and its trading partners. It outlines the segment usage, overview of the transaction set, initial implementation procedures involving testing, and procedures for migrating to a new version. Trading partners are expected to acknowledge orders, develop transitional paper acknowledgments, and participate in parallel testing while continuing to receive hard copy purchase orders.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
180 views34 pages

EDI Implementation Guidelines For The 850 - Purchase Order

The document provides guidelines for implementing the 850 Purchase Order transaction set between Lands' End and its trading partners. It outlines the segment usage, overview of the transaction set, initial implementation procedures involving testing, and procedures for migrating to a new version. Trading partners are expected to acknowledge orders, develop transitional paper acknowledgments, and participate in parallel testing while continuing to receive hard copy purchase orders.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 34

EDI Implementation Guidelines

For The
850 – Purchase Order
LANDS' END, INC. Section 850
Page 1
Version.................004010-01 Update Date: 2/14/2011
Transaction Set.....850-Purchase Order

TABLE OF CONTENTS
CONTENTS PAGE

Purpose Statement....................………………………..……….2
Segment Usage Diagram........................….................................2
850 Purchase Order Overview..................……………………...3
Initial Implementation Procedures...........……………………....4
Version Migration Procedures ................………………………6

SEGMENTS

ISA - Interchange Control Header .....……………………....….7


GS - Functional Group Header …..……..........………………..8
ST - Transaction Set Header…...............………………………9
BEG - Begin Purchase Order............... ...……………………..10
CUR - Currency .....................…………………..……………..11
REF - Reference Numbers .....................………………………12
FOB - F.O.B Related Instruction..............……………………..13
ITD - Terms of Sale..........................…………………………..14
DTM – Date...................................…………………………….15
TD5 - Transportation Method/Type........………………….......16
N1 - Identify LE Location ................………………………....17
PO1 - PO Baseline Item Information ....…………………........19
TC2 - Commodity.............................…………………….…….21
TD5 - Transportation Method/Type ....…………………...........22
N9 – ReferenceIdentification.………………..........…….……..23
N1 - Identify LE Ship to Location ............…………….............24
DTM- Date/Time Reference....................……………………...25
CTT - Transaction Totals ...................…………………………26
SE - Transaction Set Trailer...............………………………...27
GE - Functional Group Trailer..............………………………28
IEA - Interchange Control Trailer ..........……………………...29
Transmission Examples..................……………………….......30
LANDS' END, INC. Section 850
Page 2
Version...........004010-01 Update Date: 10/05/99
Transaction Set...850-Purchase Order

Purpose: This transaction is used by Lands' End to notify their suppliers of merchandise
needed. It contains all of the Purchase Order information needed for shipping goods to a
specific location. The sequence and usage of the various segments generated is shown
below.

SEGMENT USAGE

SEGMENT ID DESCRIPTION

HEADER
ST Transaction Set Header
BEG Beginning Segment for Purchase Order.
CUR Currency
REF Reference Identification
FOB F.O.B. Related Instructions
ITD Terms of Sale
DTM Date/Time Reference
TD5 Carrier Detail
N1 Name
DETAIL
PO1 PO Baseline Item Data
TC2 Commodity
TD5 Carrier Detail
N9 Reference Identification
N1 Reference Identification
DTM Date/Time Reference
SUMMARY
CTT Transaction Totals
SE Transaction Set Trailer

Note: The ISA segment will determine what will be used in the rest of the document for
segment terminators and element separators. Lands' End will use the following:

Segment Terminator : HEX "15"


For Doc Examples Only : "?"
Element Separator : HEX "2F"
For Doc Examples Only : "*"
Subelement Separator : HEX "6E"
For Doc Examples Only: ">"
LANDS' END, INC. Section 850
Page 3
Version.................004010-01 Update Date: 06/26/98
Transaction Set.....850-Purchase Order

850 PURCHASE ORDER OVERVIEW

Terms and Conditions


All terms printed on the current paper purchase order document will remain in effect. By
accepting the transmission of an electronic purchase order, both Lands' End and it's trading
partners agree to accept and abide by the terms as written.

Acknowledgment of Orders
Immediately upon receipt of an 850 - Purchase Order, a 997 functional acknowledgment is
required to confirm successful receipt of the transmission.

If, at the time an order is first received, all quantities, ship date, and cost are acceptable and the
order is anticipated to be filled as written, a detail level acknowledgement (870) is requested.
SKU level information is necessary.

During the development of the 870, Lands' End will accept a transitional paper acknowledgment,
confirming cost, quantity and ship date, factory, country or origin, and mill. The specific
format of this acknowledgment will be approved by the Lands' End Supply Chain Specialist
prior to the elimination of the hard copy purchase order.

If a transitional paper acknowledgment cannot be developed, the hard copy purchase order will
be sent along with the 850 transmission until the 870 - Purchase Order Status document is
implemented.

Parallel Test

Following a successful testing period (refer to Initial Implementation Procedure), Lands' End
will begin to transmit 850 documents while continuing to send hard copy purchase orders. This
period of parallel testing will continue for approximately two weeks, but may be extended by
the vendor, Inventory Manager, or the Lands' End Supply Chain Specialist, or until the 870
document has been developed.
LANDS' END, INC. Section 850
Page 4
Version.............004010-01 Update Date: 06/26/98
Transaction Set.....850-Purchase Order

INITIAL IMPLEMENTATION PROCEDURES

The following procedures illustrate, step by step, how to implement receipt of the 850 purchase
order transaction set from Lands' End, Inc.:

1. To initiate EDI development with Lands' End, the vendor should contact the Lands’ End
Supply Chain Specialist by electronic mail. The initial message should contain:
- vendor name and mailing address
- technical contact name and number
- partner id and qualifier
- IBM acct and userid, or other network name
Also include whether you have received a copy of the Lands' End EDI Implementation
Guidelines. If you have, include the version id. This will help the Supply Chain Specialist
verify that you have the most current version of the documentation. If the vendor does not have
access to electronic mail, Lands' End will accept a fax with this information.

2. After successful testing of your translator and processing system with internal data, contact
the Lands' End Supply Chain Specialist to request a test transmission be sent. If you have
never received an EDI document from Lands' End before, be ready to verify all pertinent
network information (ie. your network address, partner-id and qualifier, any special networking
considerations you have, etc).

3. Lands' End, Inc. will send you a test 850 - Purchase Order transaction. This test will
determine your ability to receive the transmission from your network provider, and to send
back a 997 - Functional Acknowledgement.

4. Run the test order through your EDI translator to verify that no compliance errors exist.
Please note that the information contained on this test purchase order is fictitious, and should not
be used in your order processing systems.

5. After the test Purchase order has been successfully processed by your system, contact the I
Supply Chain Specialist to request that actual purchase orders now be sent.

6. Lands' End will then set you up in a parallel testing mode. During this time you will receive
the original hard-copy purchase order along with the new EDI 850 - Purchase Order.
Compare the hardcopy purchase orders to the test purchase orders to make sure the EDI data is
being received and interpreted successfully. Note that the ISA test/production indicator will be
set to 'T' at this time.

(Continue on next page)


LANDS' END, INC. Section 850
Page 5
Version.............004010-01 Update Date: 06/26/98
Transaction Set.....850-Purchase Order

(Continued from previous page)

7. After having successfully processed the data through your systems to your satisfaction,
contact the Supply Chain Specialist to coordinate the elimination of the duplicate hard-copy
purchase orders. At this point, the next 850 - Purchase Order transaction received will have a 'P'
in the ISA test/production indicator.
LANDS' END, INC. Section 850
Page 6
Version.............004010-01 Update Date: 06/26/98
Transaction Set.....850-Purchase Order

VERSION MIGRATION PROCEDURES

The following procedures illustrate, step by step, the testing and implementation methodology
for a new VICS version of the 850 Purchase Order transaction set from Lands. End, Inc. Note
that Lands' End will notify suppliers of new version mapping changes and of the date we will be
capable of sending 850 transactions mapped to the new format.

1. Insure that your site has obtained a current version of the Lands' End, Inc. EDI
Implementation Guidelines for the 850 - Purchase Order transaction set which contains mapping
for the new version. Also be sure to have a copy of the VICS Retail Industry Conventions and
Guidelines for EDI, for the version being implemented.

2. Contact Lands' End to receive a test file of the current version of the 850 which will contain
fictitious information.

3. After successfully processing the test file, contact Lands' End to initiate parallel testing.
(Interchange will be marked as T.)

4. After having successfully received two separate transmissions of the 850 file in the parallel
mode, contact Lands' End to trigger a change to the production mode. (Interchange will be
marked P.)

5. Note that we will only support one version prior to the latest upgrade. For example, if Lands'
End upgrades to 4010 from 3040, only 3040 and 4010 will be supported. If at any point you
feel you are not able to comply with this requirement, notify the Lands' End Supply Chain
Specialist.
LANDS' END, INC. Section 850
Page 7
Version..............004010-01 Update Date: 06/26/98
Transaction Set......850-Purchase Order
Segment..............ISA - Interchange Control Header Level................Envelope
Usage................Mandatory
Max Us...............00001

Purpose: To start and identify an interchange

Data Element Summary

Ref No- ANSI Lands' End Comments/Exceptions


Element Name Attributes Attributes to VICS standards
=========================== ========== ========== ====================
ISA-01 Authorization Info. M ID 02/02 "00"
Qualifier
ISA-02 Authorization Info. M AN 10/10 All blanks.
ISA-03 Security Information M ID 02/02 "00"
Qualifier
ISA-04 Security Information M AN 10/10 All blanks.
ISA-05 Interchange ID Qualifier M ID 02/02 "01"
(for Lands' End)
ISA-06 Interchange Sender ID M ID 15/15 "025197609"
ISA-07 Interchange ID Qualifier M ID 02/02
(for receiver)
ISA-08 Interchange Receiver ID M ID 15/15
ISA-09 Interchange Date M DT 06/06
ISA-10 Interchange Time M TM 04/04
ISA-11 Interchange Control M ID 01/01 "U"
Standards Identifier
ISA-12 Interchange Control M ID 05/05 "00401"
Version Number
ISA-13 Interchange Control Num M N0 09/09
ISA-14 Acknowledgement Request M ID 01/01 "0"
ISA-15 Test Indicator M ID 01/01 "T" or "P"
ISA-16 Subelement Separator M AN 01/01 ">" (HEX 6E")
LANDS' END, INC. Section 850
Page 8
Version....................... 004010-01 Update Date: 06/26/98
Transaction Set...........850-Purchase Order
Segment..................... GS - Functional Group Header
Level.......................... Envelope
Usage.......................... Mandatory

Max Use..................... 00001

Purpose: To indicate the beginning of a functional group, and to send control information.

Data Element Summary

Ref No- ANSI Lands' End Comments/Exceptions


Element Name Attributes Attributes to VICS standards
=========================== ========== ========== ====================
GS-01 Functional Identifier Code M ID 02/02 "PO"

GS-02 Application Sender's Code M AN 02/15 M AN 09/09 "025197609"

GS-03 Application Receiver's Code M AN 02/15 Same as ISA08

GS-04 Group Date M DT 08/08

GS-05 Group Time M TM 04/08

GS-06 Group Control Number M N0 01/09

GS-07 Responsible Agency Code M ID 01/02 M ID 01/01 "X"

GS-08 Version M ID 01/12 M ID 12/12 "004010VICS"


LANDS' END, INC. Section 850
Page 9
Version....................... 004010-01 Update Date: 06/26/98
Transaction Set.......... 850-Purchase Order
Segment..................... ST - Transaction Set Header
Level.......................... Header
Usage.......................... Mandatory

Max Use.................... 00001

Purpose: To indicate the start of the 850 transaction set, and to assign a control number.

Data Element Summary

Ref No- ANSI Lands' End Comments/Exceptions


Element Name Attributes Attributes to VICS standards
=========================== ========== ========== ====================
ST-01 Transaction Set Identifier M ID 03/03 "850"
Code

ST-02 Transaction Set Control M AN 04/09


Number
LANDS' END, INC. Section 850
Page 10
Version....................... 004010-01 Update Date: 06/26/98
Transaction Set.......... 850-Purchase Order
Segment..................... BEG - Beginning Segment for Purchase Order
Level.......................... Header
Usage.......................... Mandatory

Max Use.................... 00001

Purpose: Indicate the beginning of the purchase order transaction set, and transmit
identifying numbers and dates.

Data Element Summary

Ref No- ANSI Lands' End Comments/Exceptions


Element Name Attributes Attributes to VICS standards
=========================== ========== ========== ====================
BEG-01 Transaction Set Purpose M ID 02/02 "00"
Code
"00" - Original
"04" - Modification

BEG-02 PO Type Code M ID 02/02 "SA"


"SA" - Stand Alone Order

BEG-03 Purchase Order Number M AN 01/22 M N0 01/07

BEG-05 Purchase Order Date M DT 08/08 Original PO date.


(CCYYMMDD)

BEG-06 Contract Number O AN 01/30


Reserved for Future Appl.

Example:
BEG*00*SA*123456**19991015?
LANDS' END, INC. Section 850
Page 11
Version....................... 004010-01 Update Date: 09/28/01
Transaction Set.......... 850-Purchase Order
Segment..................... CUR - Currency
Level.......................... Header
Usage..........................Mandatory
Max Use.................... 00001

Purpose: To specify the currency (dollars, pounds, Euro, etc) used in a transaction.

Data Element Summary

Ref No- ANSI Lands' End Comments/Exceptions


Element Name Attributes Attributes to VICS standards
=========================== ========== ========== ====================
CUR-01 Entity Identifier Code M ID 02/03 "BY"
"BY" - Buying Party (Purchaser

CUR-02 Curreny Code M ID 03/03 "USD", "GBP",


“USD" - US-Dollars “EUR”, “CHF”
"GBP" - Pound-Sterling
"EUR“ – Euro
"CHF" - Swiss-Franc

Example:
CUR*BY*USD?
LANDS' END, INC. Section 850
Page 12
Version....................... 004010-01 Update Date: 06/26/98
Transaction Set.......... 850-Purchase Order
Segment..................... REF - Reference Numbers
Level.......................... Header
Usage.......................... Optional
Max Use.................... 00001

Purpose: To specify the Lands' End season code

Data Element Summary

Ref No- ANSI Lands' End Comments/Exceptions


Element Name Attributes Attributes to VICS standards
=========================== ========== ========== ====================
REF-01 Reference Number Qualifier M ID 02/03 M ID 02/02 "DP"

REF-02 Reference Number C AN 01/30 M AN 06/06 L.E. Season Code

Examples:
REF*DP*1999SS?
LANDS' END, INC. Section 850
Page 13
Version....................... 004010-01 Update Date: 06/26/98
Transaction Set.......... 850-Purchase Order
Segment..................... FOB Related Instructions
Level.......................... Header
Usage.......................... Optional
Max Use.................... >1

Purpose: To specify transportation instructions relating to shipment.

Data Element Summary

Ref No- ANSI Lands' End Comments/Exceptions


Element Name Attributes Attributes to VICS standards
=========================== ========== ========== ====================

FOB-01 Shipment Method of Payment M ID 02/02 "DF"


"DF" - Defined by Buyer and Seller

FOB-04Transportation Terms O ID 02/02 "01"


Qualifier Code
"01" - Incoterms

FOB-05Transportation Terms Code C ID 03/03 "FOB"


"FOB" - Free on Board

FOB-06Location Qualifier C ID 01/02 "WH" "OV"


"WH" - Warehouse
"OV" - On Vessel (Free On Board point)

Example:

FOB*DF***01*FOB*WH?
LANDS' END, INC. Section 850
Page 14
Version....................... 004010-01 Update Date: 04/27/99
Transaction Set.......... 850-Purchase Order
Segment..................... ITD - Terms of Sale
Level.......................... Header
Usage..........................Manditory
Max Use.................... 00001

Purpose: To specify the Lands' End term of sale.

Data Element Summary

Ref No- ANSI Lands' End Comments/Exceptions


Element Name Attributes Attributes to VICS standards
=========================== ========== ========== ====================
ITD-01 Terms Type Code O ID 02/02 "12"
"12" - 10 Days After End of Month (10 EOM)

ITD-02 Terms Basis Date Code O ID 01/02 "15"


"15"-Receipt of Goods

ITD-07 Term Net Days O N0 01/03

Example:
ITD*12?
ITD**15*****30?

NOTE: We will send either the ITD-01 if your term of sales is 10 days EOM, or the ITD-02 and
ITD-07 if your term of sale is net days. If you are questioning what term of sale is set-up for
you, please contact your Supply Chain Specialist.
LANDS' END, INC. Section 850
Page 15
Version....................... 004010-01 Update Date: 10/05/99
Transaction Set.......... 850-Purchase Order
Segment..................... DTM - Date/Time Reference
Level.......................... Headerl
Usage.......................... Optional
Max Use.................... 00001

Purpose: To specify dates and times for specific actions related to the Purchase Order.

Data Element Summary

Ref No- ANSI Lands' End Comments/Exceptions


Element Name Attributes Attributes to VICS standards
=========================== ========== ========== ====================
1st Occurrence:
DTM-01 Date/Time Qualifier M ID 03/03 "010"
"010" - Requested Ship Date

DTM-02 Date C DT 08/08


date expressed as CCYYMMDD

Example:
DTM*010*19990315? (Requested Ship)

NOTE: To determine delivery date in Dodgeville, refer to the TD5-05 for the number of
intransit days to add to the requested ship date.

NOTE: This is an interim solution if your system will not handle receiving ship dates at the
detail level.
LANDS' END, INC. Section 850
Page 16
Version....................... 004010-01 Update Date: 10/05/99
Transaction Set.......... 850-Purchase Order
Segment..................... TD5 - Carrier Detail
Level.......................... Header
Usage..........................Optional
Max Use.................... 00001

Purpose: To identify Lands' End transportation method/type code.

Data Element Summary

Ref No- ANSI Lands' End Comments/Exceptions


Element Name Attributes Attributes to VICS standards
=========================== ========== ========== ====================
TD5-04 Transportation Method C ID 01/02 "A", "C", "M"
"A" - Air
"C" - Consolidation (Sea)
"M" - Motor (Common Carrier-Ground)

TD5-05 Routing C AN 01/35 Number days Intransit


Note: The number you will receive in this segment represents the intransit time
in days.

Example:
TD5****A*15?

NOTE: This is an interim solution if your system will not handle receiving ship dates at the
detail level and you are using the DTM at the header level.
LANDS' END, INC. Section 850
Page 17
Version....................... 004010-01 Update Date: 2/14/2011
Transaction Set.......... 850-Purchase Order
Segment..................... N1 - Name
Level.......................... Header
Usage.......................... Mandatory

Max Use.................... 00002

Purpose: To identify a party by type of organization, name, and code.

Data Element Summary

Ref No- ANSI Lands' End Comments/Exceptions


Element Name Attributes Attributes to VICS standards
=========================== ========== ========== ====================
1st Occurrence:
N1-01 Entity Identifier Code M ID 02/03 "BT"
"BT" - Bill To
N1-03 Identification Code C ID 01/02 "92"

Qualifier
"92" - Assigned by Buyer
N1-04 Identification Code C AN 02/80 C ID 02/17 "01", "02",
Lands' End Location ID "03", "04",
"01" - Lands' End Dodgeville-USA "06", "08"
"02" - Lands' End Great Britain
"03" - Lands' End Japan KK
"04" - Coming Home,Dodgeville - USA
"06" - Lands' End Corporate Sales, Dodgeville - USA
"08" - Willis & Geiger,Dodgeville - USA
"09" - Lands'End DVSears Store Ready
2nd Occurrence:
N1-01 Entity Identifier M ID 02/03 "ST"
"ST" - Ship To
N1-03 Identification Code C ID 01/02 "92"
Qualifier
"92" - Assigned by Buyer
N1-04 Identification Code C AN 02/80 C ID 02/17 "01", "02",
Lands' End Location ID "04", "06",
"01" - Lands' End Dodgeville-USA "07"
"02" - Lands' End Great Britain
"04" - Lands' End Reedsburg-USA
"06" - Lands' End Japan
"07" - Lands' End Corporate Sales, Dodgeville - USA

LANDS' END, INC. Section 850


Page 18
Version....................... 004010-01 Update Date: 2/14/2011
Transaction Set.......... 850-Purchase Order
Segment..................... N1 - Name
Level.......................... Header
Usage.......................... Mandatory

Max Use.................... 00002

(continued from previous page)

Example:
N1*BT**92*01? (Bill To)
N1*ST**92*02? (Ship To)
LANDS' END, INC. Section 850
Page 19
Version....................... 004010-01 Update Date: 2/14/2011
Transaction Set.......... 850-Purchase Order
Segment..................... PO1 Purchase Order Baseline Item Data
Level.......................... Detail
Usage.......................... Mandatory

Max Use.................... 00001

Purpose: To specify basic and most frequently used purchase order line item data.

Data Element Summary

Ref No- ANSI Lands' End Comments/Exceptions


Element Name Attributes Attributes to VICS standards
=========================== ========== ========== ====================
PO1-01 Line Number C R 01/15
PO1-02 Quantity Ordered C R 01/15
M R 01/05
PO1-03 Unit of Measurement Code O ID 02/02 "EA"
"EA" - Each
PO1-04 Unit Price C R 01/17
PO1-05 Basis of Unit Price Code O ID 02/02 "TE"
"TE" - Contract Price per
Each
PO1-06 Product/Service ID C ID 02/02 M ID 02/02 "IT"
Qualifier
"IT" - Buyers Style Number
PO1-07 Product/Service ID C AN 01/48 C AN 01/06 Style Number
PO1-08 Product/Service ID C ID 02/02 "BO"
Qualifier
"BO" - Buyers Color
PO1-09 Product/Service ID C AN 01/48 C AN 01/03 Color Code
PO1-10 Product/Service ID C ID 02/02 "IZ"
Qualifier
"IZ" - Buyers Size Code
PO1-11 Product/Service ID C AN 01/48 C AN 01/05 Size Code
PO1-12 Product/Service ID C ID 02/02 "IN"
Qualifier
"IN" - Buyers Item Number
PO1-13 Product/Service ID C AN 01/48 C AN 01/07 SKU Number
.
(Continued on next page)

LANDS' END, INC. Section 850


Page 20
Version....................... 004010-01 Update Date: 2/14/2011
Transaction Set.......... 850-Purchase Order
Segment..................... PO1 Purchase Order Baseline Item Data

(Continued from previous page)

Note: When a style has no color or no size associated with it, the corresponding
elements will be empty. See the examples below. .
Examples:
PO1*1*25*EA*23.15*TE*IT*123456*BO*RED*IZ*16H35*IN*1234567?
PO1*1*25*EA*25.25*TE*IT*654321***IZ*XL*IN*7654321? <-- Style has no color.
PO1*1*50*EA*15.76*TE*IT*98765*BO*GRE***IN*987654? <-- Style has no size.
PO1*1*175*EA*33.50*TE*IT*54321*****IN*123456? <-- Style has no color or size
LANDS' END, INC. Section 850
Page 21
Version....................... 004010-01 Update Date: 05/14/99
Transaction Set.......... 850-Purchase Order
Segment..................... TC2 - Commodity
Level.......................... Detail
Usage.......................... Optional
Max Use.................... >1

Purpose: To identify a commodity of a group of commodities.

Data Element Summary

Ref No- ANSI Lands' End Comments/Exceptions


Element Name Attributes Attributes to VICS standards
=========================== ========== ========== ====================
1st Occurrence:
TC2-01Commodity Code Qualifier M ID 1/1 O ID 1/1 "J"
"J" - Harmonized Code

TC2-02 Commodity Code M AN 1/30 C AN 1/30

2nd Occurrence:
TC2-01 Commodity Code Qualifier M ID 1/1 O ID 1/1 "Q"
"Q" - Quota Category

TC2-02 Commodity Code M AN 1/30 C AN 1/30

Examples:
TC2*J*6202-93-4500?
TC2*Q*635?
LANDS' END, INC. Section 850
Page 22
Version....................... 004010-01 Update Date: 11/06/98
Transaction Set.......... 850-Purchase Order
Segment..................... TD5 - Carrier Detail
Level.......................... Detail
Usage.......................... Mandatory

Max Use.................... 00001

Purpose: To identify Lands' End transportation method/type code.

Data Element Summary

Ref No- ANSI Lands' End Comments/Exceptions


Element Name Attributes Attributes to VICS standards
=========================== ========== ========== ====================
TD5-04 Transportation Method C ID 01/02 "A", "C", "M"
"A" - Air
"C" - Consolidation (Sea)
"M" - Motor (Common Carrier-Ground)

TD5-05 Routing C AN 01/35 Number days Intransit


Note: The number you will receive in this segment represents the intransit time
in days.

Example:
TD5****A*15?
LANDS' END, INC. Section 850
Page 23
Version....................... 004010-01 Update Date: 06/26/98
Transaction Set.......... 850-Purchase Order
Segment..................... N9 - Reference Identification
Level.......................... Detail
Usage..........................Optional
Max Use.................... 00001

Purpose: To identify U.S Customs Service (USCS) Binding Ruling number.

Data Element Summary

Ref No- ANSI Lands' End Comments/Exceptions


Element Name Attributes Attributes to VICS standards
=========================== ========== ========== ====================
N9-01 Reference Identification M ID 02/03 O ID 02/03 "3R"
Qualifier
N9-02 Reference Identification C AN 1/30 C AN 1/30
Binding Ruling Number

Example:
N9*3R*PCA81455?
LANDS' END, INC. Section 850
Page 24
Version....................... 004010-01 Update Date: 11/06/98
Transaction Set.......... 850-Purchase Order
Segment..................... N1 - Name
Level.......................... Detail
Usage.......................... Mandatory

Max Use.................... 00001

Purpose: To identify a party by type of organization, name, and code.


Data Element Summary

Ref No- ANSI Lands' End Comments/Exceptions


Element Name Attributes Attributes to VICS standards
=========================== ========== ========== ====================
N1-01 Entity Identifier Code M ID 02/03 "ST"
"ST" - Ship To

N1-02 Name C AN 1/60 "01", "02",


"01" - Lands' End Dodgeville, USA "04", "06",
"02" - Lands' End Great Britian "07"
"04" - Lands' End Reedsburg, USA
"06" - Lands' End Japan
"07" - Lands' End Corporate Sales, Dodgeville, USA
"09" - Lands'End DVSears Store Ready

Example:
N1*ST*01?
LANDS' END, INC. Section 850
Page 25
Version....................... 004010-01 Update Date: 05/19/99
Transaction Set.......... 850-Purchase Order
Segment..................... DTM - Date/Time Reference
Level.......................... Detail
Usage.......................... Mandatory

Max Use.................... 00001

Purpose: To specify dates and times for specific actions related to the Purchase Order.

Data Element Summary

Ref No- ANSI Lands' End Comments/Exceptions


Element Name Attributes Attributes to VICS standards
=========================== ========== ========== ====================
1st Occurrence:
DTM-01 Date/Time Qualifier M ID 03/03 "010"
"010" - Requested Ship Date

DTM-02 Date C DT 08/08


date expressed as CCYYMMDD

Example:
DTM*010*19990315? (Requested Ship)

NOTE: To determine delivery date in Dodgeville, refer to the TD5-05 for the number of
intransit days to add to the requested ship date.
LANDS' END, INC. Section 850
Page 26
Version....................... 004010-01 Update Date: 06/26/98
Transaction Set.......... 850-Purchase Order
Segment..................... CTT - Transaction Totals
Level.......................... Summary
Usage.......................... Mandatory

Max Use.................... 00001

Purpose: To transmit a hash total for a specific element in the transaction set

Data Element Summary

Ref No- ANSI Lands' End Comments/Exceptions


Element Name Attributes Attributes to VICS standards
=========================== ========== ========== ====================
CTT-01 Number of Line Items M N0 01/06
LANDS' END, INC. Section 850
Page 27
Version....................... 004010-01 Update Date: 06/26/98
Transaction Set.......... 850-Purchase Order
Segment..................... SE Transaction Set Trailer
Level.......................... Summary
Usage.......................... Mandatory

Max Use.................... 00001

Purpose: To indicate the end of the transaction set and provide the count of the
transmitted segments.

Data Element Summary

Ref No- ANSI Lands' End Comments/Exceptions


Element Name Attributes Attributes to VICS standards
=========================== ========== ========== ====================
SE-01 Number of Included M N0 01/10
Segments
LANDS' END, INC. Section 850
Page 28
Version....................... 004010-01 Update Date: 06/26/98
Transaction Set.......... 850-Purchase Order
Segment..................... GE - Functional Group Trailer
Level.......................... Group
Usage.......................... Mandatory

Max Use.................... 00001

Purpose: To define the end of a functional group of related transaction sets

Data Element Summary

Ref No- ANSI Lands' End Comments/Exceptions


Element Name Attributes Attributes to VICS standards
=========================== ========== ========== ====================
GE-01 Number of Included M N0 01/06
Transaction Sets

GE-02 Data Interchange Control M N0 01/09


Number
LANDS' END, INC. Section 850
Page 29
Version....................... 004010-01 Update Date: 06/26/98
Transaction Set.......... 850-Purchase Order
Segment..................... IEA - Interchange Control Trailer
Level.......................... Envelope
Usage.......................... Mandatory

Max Use.................... 00001

Purpose: To define the end of an interchange of one or more functional groups

Data Element Summary

Ref No- ANSI Lands' End Comments/Exceptions


Element Name Attributes Attributes to VICS standards
=========================== ========== ========== ====================
IEA-01 Number of Included M N0 01/05
Groups

IEA-02 Interchange Control M N0 09/09


Number
LANDS' END, INC. Section 850
Page 30
Version....................... 004010-01 Update Date: 10/05/99
Transaction Set.......... 850-Purchase Order

TRANSMISSION EXAMPLES
The following example illustrates the actual makeup of the 850 - Purchase Order transaction set,
as defined in these documents.

ISA*00* *00* *01*025197609 *01*012345678 *990315*19


18*U*00401*000000026*1*P*>?
GS*PO*025197609*012345678*19990315*1918*29*X*004010VICS?
ST*850*000000533?
BEG*00*SA*436798**19990315?
CUR*BY*USD?
REF*DP*1999SS?
FOB*DF***01*FOB*WH?
ITD**15*****30?
DTM*010*19990515?
TD5****A*15?
N1*BT**92*01?
N1*ST**92*01?
PO1*1*15*EA*18.86*TE*IT*54321*BO*CHA*IZ*30*IN*111115?
TC2*J*6202-93-4500?
TC2*Q*635?
TD5****A*15?
N9*3R*PCA81455?
N1*ST*01?
DTM*010*19990515?
PO1*2*15*EA*18.86*TE*IT*54321*BO*CHA*IZ*31*IN*111112?
TC2*J*6202-93-4500?
TC2*Q*635?
TD5****A*15?
N9*3R*PCA81455?
N1*ST*01?
DTM*010*19990515?
PO1*3*15*EA*18.86*TE*IT*54321*BO*CHA*IZ*32*IN*111119?
TC2*J*6202-93-4500?
TC2*Q*635?
TD5****A*15?
N9*3R*PCA81455?
N1*ST*01?
DTM*010*19990515?
PO1*4*30*EA*18.86*TE*IT*54321*BO*CHA*IZ*33*IN*111116?
TC2*J*6202-93-4500?TC2*Q*635?
TD5****A*15?
N9*3R*PCA81455?
N1*ST*01?
DTM*010*19990515?
PO1*5*60*EA*18.86*TE*IT*54321*BO*CHA*IZ*34*IN*111113?
TC2*J*6202-93-4500?
TC2*Q*635?
TD5****A*15?
N9*3R*PCA81455?
N1*ST*01?
DTM*010*19990515?
PO1*6*30*EA*18.86*TE*IT*54321*BO*CHA*IZ*35*IN*111110?
TC2*J*6202-93-4500?
TC2*Q*635?
TD5****A*15?
N9*3R*PCA81455?
N1*ST*01?
DTM*010*19990515?
PO1*7*45*EA*18.86*TE*IT*54321*BO*CHA*IZ*36*IN*111117?
TC2*J*6202-93-4500?
TC2*Q*635?
TD5****A*15?
N9*3R*PCA81455?
N1*ST*01?
DTM*010*19990515?
PO1*8*15*EA*18.86*TE*IT*54321*BO*CHA*IZ*36 30*IN*111118?
TC2*J*6202-93-4500?
TC2*Q*635?
TD5****A*15?
N9*3R*PCA81455?
N1*ST*01?
DTM*010*19990515?
PO1*9*15*EA*18.86*TE*IT*54321*BO*CHA*IZ*36 32*IN*111120?
TC2*J*6202-93-4500?
TC2*Q*635?
TD5****A*15?
N9*3R*PCA81455?
N1*ST*01?
DTM*010*19990515?
PO1*10*45*EA*18.86*TE*IT*54321*BO*CHA*IZ*37*IN*111124?
TC2*J*6202-93-4500?
TC2*Q*635?
TD5****A*15?
N9*3R*PCA81455?
N1*ST*01?
DTM*010*19990515?
PO1*11*30*EA*18.86*TE*IT*54321*BO*CHA*IZ*38*IN*111125?
TC2*J*6202-93-4500?
TC2*Q*635?
TD5****A*15?
N9*3R*PCA81455?
N1*ST*01?
DTM*010*19990515?
PO1*12*30*EA*18.86*TE*IT*54321*BO*CHA*IZ*40*IN*111122?
TC2*J*6202-3-4500?
TC2*Q*635?
TD5****A*15?
N9*3R*PCA81455?
N1*ST*01?
DTM*010*19990515?
PO1*13*15*EA*18.86*TE*IT*54321*BO*CHA*IZ*42*IN*111139?
TC2*J*6202-93-4500?
TC2*Q*635?
TD5****A*15?
N9*3R*PCA81455?
N1*ST*01?
DTM*010*19990515?
CTT*13?
SE*103*000000533?
GE*1*29?
IEA*1*000000026?

You might also like