850 Purchase Order

Functional Group ID=PO

Introduction:

This Standard contains the format and establishes the data contents of the Purchase Order Transaction Set (850) for use within the context of Verizon Logistics Electronic Data Interchange (EDI) environment. The transaction provides for customary and established business and industry practice relative to the placement of purchase orders for goods and services. This transaction set should not be used to convey purchase order changes or purchase order acknowledgment information. However, Verizon Logistics uses information from the purchase order to match it with the purchase order acknowledgment and the advance ship notice. Therefore, three fields from the original purchase order must be returned on these two transactions; the purchase order number, the line item number, and the buyer's part number.

Heading:

Pos. Seg. Req. Loop Notes and

No. ID Name Des. Max.Use Repeat Comments

Must Use

0100

Transaction Set Header

Must Use

0200

BEG

Beginning Segment for Purchase Order

0500

REF

Reference Identification

0600

PER

Administrative Communications Contact

0700

TAX

Tax Reference

0800

FOB

F.O.B. Related Instructions

2400

TD5

Carrier Details (Routing Sequence/Transit Time)

LOOP ID - N1

200

3100

Name

3300

Address Information

3400

Geographic Location

LOOP ID - N1

200

3100

Name

3200

Additional Name Information

3300

Address Information

3400

Geographic Location

LOOP ID - N1

200

3100

Name

3300

Address Information

3400

Geographic Location

Detail:

Pos. Seg. Req. Loop Notes and

No. ID Name Des. Max.Use Repeat Comments

LOOP ID - PO1

100000

Must Use

0100

PO1

Baseline Item Data

0500

PID

Product/Item Description

1000

REF

Reference Identification

1100

PER

Administrative Communications Contact

2100

DTM

Date/Time Reference

2100

DTM

Date/Time Reference

LOOP ID - N1

200

3500

Name

3900

REF

Reference Identification

Summary:

Pos. Seg. Req. Loop Notes and

No. ID Name Des. Max.Use Repeat Comments

LOOP ID - CTT

Must Use

0100

CTT

Transaction Totals

Must Use

0300

Transaction Set Trailer

Text Box: PER

O 3 3

3O O
PER
oOo O

Segment: ST Transaction Set Header

Position: 0100

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:

Semantic Notes: 1 The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).

Notes:

Example: ST~850~0017.

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use	ST01	143	Transaction Set Identifier Code	M	1	ID 3/3
			Code uniquely identifying a Transaction Set
			*850 Purchase Order*
			Refer to 004030 Data Element Dictionary for acceptable code values.
Must Use	ST02	329	Transaction Set Control Number	M	1	AN 4/9
			Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Segment: BEG Beginning Segment for Purchase Order

Position: 0200

Loop:

Level: Heading

Usage: Mandatory

Max Use: 1

Purpose: To indicate the beginning of the Purchase Order Transaction Set and transmit identifying numbers and dates

Semantic Notes: 1 BEG05 is the date assigned by the purchaser to purchase order.

Notes:

Example: BEG~00~SA~ 4500000883~~ 20051121.

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use	BEG01	353	Transaction Set Purpose Code			M	1	ID 2/2
			Code identifying purpose of transaction set
				00	Original
Must Use	BEG02	92	Purchase Order Type Code			M	1	ID 2/2
			Code specifying the type of Purchase Order
				BK	Blanket Order (Quantity Firm)
				SA	Stand-alone Order
Must Use	BEG03	324	Purchase Order Number			M	1	AN 1/22
			Identifying number for Purchase Order assigned by the orderer/purchaser
	BEG04	328	Release Number			O	1	AN 1/30
			Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction
Must Use	BEG05	373	Date			M	1	DT 8/8
			Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

Segment: REF Reference Identification

Position: 0500

Loop:

Level: Heading

Usage: Optional

Max Use: >1

Purpose: To specify identifying information

Syntax Notes: 1 At least one of REF02 or REF03 is required.

Notes:

Example: REF~AB~029.

REF~L1~REGULAR PURCHASE ORDER.

REF~VR~ 0600001940.

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use	REF01	128	Reference Identification Qualifier			M	1	ID 2/3
			Code qualifying the Reference Identification
				AB	Acceptable Source Purchaser ID
				L1	Letters or Notes
				VR	Vendor ID Number
	REF02	127	Reference Identification			X	1	AN 1/50
			Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
	REF03	352	Description			X	1	AN 1/80
			A free-form description to clarify the related data elements and their content

Segment: PER Administrative Communications Contact

Position: 0600

Loop:

Level: Heading

Usage: Optional

Max Use: 3

Purpose: To identify a person or office to whom administrative communications should be directed

Syntax Notes: 1 If either PER03 or PER04 is present, then the other is required.

Notes:

Example: PER~OC~ROBERT JONES~TE~6145551212.

Example: PER~ZZ~ROBERT JONES~TE~6145551212.

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use	PER01	366	Contact Function Code			M	1	ID 2/2
			Code identifying the major duty or responsibility of the person or group named
				OC	Order Contact
				ZZ	Verizon Planner
	PER02	93	Name			O	1	AN 1/60
			Free-form name
			*Verizon Logistics Buyer* *Verizon Planner*
	PER03	365	Communication Number Qualifier			X	1	ID 2/2
			Code identifying the type of communication number
				TE	Telephone
	PER04	364	Communication Number			X	1	AN 1/256
			Complete communications number including country or area code when applicable
			*Buyer telephone number* *Planner telephone number*

Segment: TAX Tax Reference

Position: 0700

Loop:

Level: Heading

Usage: Optional

Max Use: >1

Purpose: To provide data required for proper notification/determination of applicable taxes applying to the transaction or business described in the transaction

Syntax Notes: 1 At least one of TAX01 or TAX03 is required.

2 If either TAX02 or TAX03 is present, then the other is required.

Comments: 1 Tax ID number is, in many instances, referred to as a Tax Exemption Number. The paired (combined) use of data elements 309 and 310 provides for the designation of five taxing jurisdictions.

2 TAX01 is required if tax exemption is being claimed.

Notes:

Example: TAX~~SP~WV~~~~~~~~~2.

Data Element Summary

Ref. Data

Des. Element Name Attributes

TAX02	309	Location Qualifier			X	1	ID 1/2
		Code identifying type of location
			SP	State/Province
TAX03	310	Location Identifier			X	1	AN 1/30
		Code which identifies a specific location
TAX12	441	Tax Exempt Code			O	1	ID 1/1
		Code identifying exemption status from sales and use tax
			2	No (Not Tax Exempt)
			B	Material Taxable, Labor Exempt
			C	Not Taxable

Segment: FOB F.O.B. Related Instructions

Position: 0800

Loop:

Level: Heading

Usage: Optional

Max Use: >1

Purpose: To specify transportation instructions relating to shipment

Syntax Notes: 1 If FOB03 is present, then FOB02 is required.

2 If FOB04 is present, then FOB05 is required.

Semantic Notes: 1 FOB01 indicates which party will pay the carrier.

2 FOB02 is the code specifying transportation responsibility location.

Notes:

Examples: FOB~CC~DE~~02~FOB.

FOB~PC~OR~~02~FOB.

FOB~PP~DE~~02~FOB.

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use	FOB01	146	Shipment Method of Payment			M	1	ID 2/2
			Code identifying payment terms for transportation charges
				CC	Collect
				PC	Prepaid and Billed
				TP	Third Party Pay
				PO	Prepaid Only
	FOB02	309	Location Qualifier			X	1	ID 1/2
			Code identifying type of location
				DE	Destination (Shipping)
				OR	Origin (Shipping Point)
	FOB04	334	Transportation Terms Qualifier Code			O	1	ID 2/2
			Code identifying the source of the transportation terms
				02	Trade Terms Code
	FOB05	335	Transportation Terms Code			X	1	ID 3/3
			Code identifying the trade terms which apply to the shipment transportation responsibility
				FOB	Free on Board

Segment: TD5 Carrier Details (Routing Sequence/Transit Time)

Position: 2400

Loop:

Level: Heading

Usage: Optional

Max Use: >1

Purpose: To specify the carrier and sequence of routing and provide transit time information

Syntax Notes: 1 At least one of TD502 TD504 TD505 TD506 or TD512 is required.

Comments: 1 When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier within the movement, use TD502 to identify the party responsible for defining the routing sequence, and use TD503 to identify the actual routing sequence, specified by the party identified in TD502.

Notes:

Example: TD5~~~~~Carrier Name~~~~~~~ZZ.

Data Element Summary

Ref. Data

Des. Element Name Attributes

TD505	387	Routing			O	1	AN 1/35
		Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
TD512	284	Service Level Code			X	1	ID 2/2
		Code indicating the level of transportation service or the billing service offered by the transportation carrier *DEFINITIONS:* *ZZ = Call Routing Center at 800-483-0015* *G2 = Best way – shipper's option* *CB = Consignee Billing Service ( Carrier Name in TD505)*
			CB	Consignee Billing Service
			G2	Standard Service
			ZZ	Mutually Defined

Segment: N1 Name

Position: 3100

Loop: N1 Optional

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 N103 is required.

2 If either N103 or N104 is present, then the other is required.

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 N105 and N106 further define the type of entity in N101.

Notes:

Example: N1~BT~ VERIZON LOGISTICS SVCS - CMM/P~92~BC

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use	N101	98	Entity Identifier Code			M	1	ID 2/3
			Code identifying an organizational entity, a physical location, property or an individual
				BT	Bill-to-Party
	N102	93	Name			X	1	AN 1/60
			Free-form name
			*Verizon Logistics*
	N103	66	Identification Code Qualifier			X	1	ID 1/2
			Code designating the system/method of code structure used for Identification Code (67)
				92	Assigned by Buyer or Buyer's Agent
	N104	67	Identification Code			X	1	AN 2/80
			Code identifying a party or other code
			*WH1*

Segment: N3 Address Information

Position: 3300

Loop: N1 Optional

Level: Heading

Usage: Optional

Max Use: 2

Purpose: To specify the location of the named party

Notes:

Example: N3~ INVOICE UNIT - EAST~6 50 PARK AVENUE.

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use	N301	166	Address Information	M	1	AN 1/55
			Address information
			*INVOICE UNIT - EAST*
	N302	166	Address Information	O	1	AN 1/55
			Address information
			*650 PARK AVENUE*

Segment: N4 Geographic Location

Position: 3400

Loop: N1 Optional

Level: Heading

Usage: Optional

Max Use: >1

Purpose: To specify the geographic place of the named party

Comments: 1 A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.

2 N402 is required only if city name (N401) is in the U.S. or Canada.

Notes:

Example: N4~ EAST ORANGE ~NJ~07017.

Data Element Summary

Ref. Data

Des. Element Name Attributes

N401	19	City Name	O	1	AN 2/30
		Free-form text for city name
		*EAST ORANGE*
N402	156	State or Province Code	X	1	ID 2/2
		Code (Standard State/Province) as defined by appropriate government agency
		NJ
N403	116	Postal Code	O	1	ID 3/15
		Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
		*07017*

Segment: N1 Name

Position: 3100

Loop: N1 Optional

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 N103 is required.

2 If either N103 or N104 is present, then the other is required.

2 N105 and N106 further define the type of entity in N101.

Notes:

Example: N1~ST~ VARTAC - MARTINSBURG.~92~BCMB.

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use	N101	98	Entity Identifier Code			M	1	ID 2/3
			Code identifying an organizational entity, a physical location, property or an individual
				ST	Ship To
	N102	93	Name			X	1	AN 1/60
			Free-form name
			VARTAC - MARTINSBURG
	N103	66	Identification Code Qualifier			X	1	ID 1/2
			Code designating the system/method of code structure used for Identification Code (67)
				92	Assigned by Buyer or Buyer's Agent
	N104	67	Identification Code			X	1	AN 2/80
			Code identifying a party or other code
			*BCMB*

Segment: N2 Additional Name Information

Position: 3200

Loop: N1 Optional

Level: Heading

Usage: Optional

Max Use: 2

Purpose: To specify additional names

Notes:

Example: N2~ MITCHELL SMITH NTWK MGR.

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use	N201	93	Name	M	1	AN 1/60
			Free-form name
			*MITCHELL SMITH NTWK MGR*

Segment: N3 Address Information

Position: 3300

Loop: N1 Optional

Level: Heading

Usage: Optional

Max Use: 2

Purpose: To specify the location of the named party

Notes:

Example: N3~ 5158 WILLIAMSPORT PIKE.

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use	N301	166	Address Information	M	1	AN 1/55
			Address information
			*First Line of Address*
	N302	166	Address Information	O	1	AN 1/55
			Address information
			*Second Line of address*

Segment: N4 Geographic Location

Position: 3400

Loop: N1 Optional

Level: Heading

Usage: Optional

Max Use: >1

Purpose: To specify the geographic place of the named party

Syntax Notes: 1 Only one of N402 or N407 may be present.

Comments: 1 A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.

2 N402 is required only if city name (N401) is in the U.S. or Canada.

Notes:

Example: N4~ MARTINSBURG ~WV~ 25401.

Data Element Summary

Ref. Data

Des. Element Name Attributes

N401	19	City Name	O	1	AN 2/30
		Free-form text for city name
N402	156	State or Province Code	X	1	ID 2/2
		Code (Standard State/Province) as defined by appropriate government agency
N403	116	Postal Code	O	1	ID 3/15
		Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

Segment: N1 Name

Position: 3100

Loop: N1 Optional

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 N103 is required.

2 If either N103 or N104 is present, then the other is required.

Notes:

Example: N1~PF~VERIZON LOGISTICS C/O AccuShip.Com~92~XXXXX.

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use	N101	98	Entity Identifier Code			M	1	ID 2/3
			Code identifying an organizational entity, a physical location, property or an individual
				PF	Party to Receive Freight Bill
	N102	93	Name			X	1	AN 1/60
			Free-form name
			*Verizon Logistics C/O AccuShip.Com*
	N103	66	Identification Code Qualifier			X	1	ID 1/2
			Code designating the system/method of code structure used for Identification Code (67)
				92	Assigned by Buyer or Buyer's Agent
	N104	67	Identification Code			X	1	AN 2/80
			Code identifying a party or other code

Segment: N3 Address Information

Position: 3300

Loop: N1 Optional

Level: Heading

Usage: Optional

Max Use: 2

Purpose: To specify the location of the named party

Notes:

Example: N3~1900 Exeter Road.

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use	N301	166	Address Information	M	1	AN 1/55
			Address information
			1900 Exeter Road

Segment: N4 Geographic Location

Position: 3400

Loop: N1 Optional

Level: Heading

Usage: Optional

Max Use: >1

Purpose: To specify the geographic place of the named party

Syntax Notes: 1 Only one of N402 or N407 may be present.

Comments: 1 A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.

2 N402 is required only if city name (N401) is in the U.S. or Canada.

Notes:

Example: N4~GERMANTOWN~TN~38138.

Data Element Summary

Ref. Data

Des. Element Name Attributes

N401	19	City Name	O	1	AN 2/30
		Free-form text for city name
		*GERMANTOWN*
N402	156	State or Province Code	X	1	ID 2/2
		Code (Standard State/Province) as defined by appropriate government agency
		TN
N403	116	Postal Code	O	1	ID 3/15
		Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
		*38138*

Segment: PO1 Baseline Item Data

Position: 0100

Loop: PO1 Mandatory

Level: Detail

Usage: Mandatory

Max Use: 1

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

Syntax Notes: 1 If PO103 is present, then PO102 is required.

2 If PO105 is present, then PO104 is required.

3 If either PO106 or PO107 is present, then the other is required.

4 If either PO108 or PO109 is present, then the other is required.

5 If either PO110 or PO111 is present, then the other is required.

6 If either PO112 or PO113 is present, then the other is required.

7 If either PO114 or PO115 is present, then the other is required.

Comments: 1 See the Data Element Dictionary for a complete list of IDs.

2 PO101 is the line item identification.

3 PO106 through PO125 provide for ten different product/service IDs per each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.

Notes:

Example: PO1~0001~10~EA~1.17~~BP~87056767~VN~2651-110~MF~2651-110~CI~CLEIcode.

Data Element Summary

Ref. Data

Des. Element Name Attributes

PO101	350	Assigned Identification			O	1	AN 1/20
		Alphanumeric characters assigned for differentiation within a transaction set
PO102	330	Quantity Ordered			X	1	R 1/15
		Quantity ordered
PO103	355	Unit or Basis for Measurement Code			O	1	ID 2/2
		Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
PO104	212	Unit Price			X	1	R 1/17
		Price per unit of product, service, commodity, etc.
		*The layout of the PO1 shows that any qualifier could show up in any element 235. No specific order should be assumed.* The idea behind the layout in this segment is that the identification numbers have an order of importance (BP, VN, MF, EP, UP). When all identification numbers are present they will be mapped in the order shown in this document. When a specific number is not present all following numbers will move up one element. For example: if the VN (Vendor's item number) was not present, the PO108 would contain the MF qualifier, and so on.
PO105	639	Basis of Unit Price Code			O	1	ID 2/2
		Code identifying the type of unit price for an item
		Refer to 004030 Data Element Dictionary for acceptable code values.
PO106	235	Product/Service ID Qualifier			X	1	ID 2/2
		Code identifying the type/source of the descriptive number used in Product/Service ID (234)
		*The layout of the PO1 shows that any qualifier could show up in any element 235. No specific order should be assumed.*
			BP	Buyer's Part Number
			CI	CLEI Code
			EP	Buyer's End Product Number
			MF	Manufacturer
			UP	UCC - 12
				Data structure for the 12 digit EAN.UCC (EAN International.Uniform Code Council) Global Trade Identification Number (GTIN). Also known as the Universal Product Code (U.P.C.)
			VN	Vendor's (Seller's) Item Number
PO107	234	Product/Service ID			X	1	AN 1/48
		Identifying number for a product or service
PO108	235	Product/Service ID Qualifier			X	1	ID 2/2
		Code identifying the type/source of the descriptive number used in Product/Service ID (234)
			BP	Buyer's Part Number
			CI	CLEI Code
			EP	Buyer's End Product Number
			MF	Manufacturer
			UP	UCC - 12
				Data structure for the 12 digit EAN.UCC (EAN International.Uniform Code Council) Global Trade Identification Number (GTIN). Also known as the Universal Product Code (U.P.C.)
			VN	Vendor's (Seller's) Item Number
PO109	234	Product/Service ID			X	1	AN 1/48
		Identifying number for a product or service
PO110	235	Product/Service ID Qualifier			X	1	ID 2/2
		Code identifying the type/source of the descriptive number used in Product/Service ID (234)
			BP	Buyer's Part Number
			CI	CLEI Code
			EP	Buyer's End Product Number
			MF	Manufacturer
			UP	UCC - 12
				Data structure for the 12 digit EAN.UCC (EAN International.Uniform Code Council) Global Trade Identification Number (GTIN). Also known as the Universal Product Code (U.P.C.)
			VN	Vendor's (Seller's) Item Number
PO111	234	Product/Service ID			X	1	AN 1/48
		Identifying number for a product or service
PO112	235	Product/Service ID Qualifier			X	1	ID 2/2
		Code identifying the type/source of the descriptive number used in Product/Service ID (234)
			BP	Buyer's Part Number
			CI	CLEI Code
			EP	Buyer's End Product Number
			MF	Manufacturer
			UP	UCC - 12
				Data structure for the 12 digit EAN.UCC (EAN International.Uniform Code Council) Global Trade Identification Number (GTIN). Also known as the Universal Product Code (U.P.C.)
			VN	Vendor's (Seller's) Item Number
PO113	234	Product/Service ID			X	1	AN 1/48
		Identifying number for a product or service
PO114	235	Product/Service ID Qualifier			X	1	ID 2/2
		Code identifying the type/source of the descriptive number used in Product/Service ID (234)
			BP	Buyer's Part Number
			CI	CLEI Code
			EP	Buyer's End Product Number
			MF	Manufacturer
			UP	UCC - 12
				Data structure for the 12 digit EAN.UCC (EAN International.Uniform Code Council) Global Trade Identification Number (GTIN). Also known as the Universal Product Code (U.P.C.)
			VN	Vendor's (Seller's) Item Number
PO115	234	Product/Service ID			X	1	AN 1/48
		Identifying number for a product or service

Segment: PID Product/Item Description

Position: 0500

Loop: PO1 Optional

Level: Detail

Usage: Optional

Max Use: 1

Purpose: To describe a product or process in coded or free-form format

Syntax Notes: 1 If PID04 is present, then PID03 is required.

2 At least one of PID04 or PID05 is required.

Semantic Notes: 1 Use PID03 to indicate the organization that publishes the code list being referred to.

Comments: 1 If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.

Notes:

Example: PID~F~~~~CABINET X-CONNECT POLE-MT RSK900W25.

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use	PID01	349	Item Description Type			M	1	ID 1/1
			Code indicating the format of a description
				F	Free-form
	PID05	352	Description			X	1	AN 1/80
			A free-form description to clarify the related data elements and their content

Segment: REF Reference Identification

Position: 1000

Loop: PO1 Optional

Level: Detail

Usage: Optional

Max Use: >1

Purpose: To specify identifying information

Syntax Notes: 1 At least one of REF02 or REF03 is required.

2 If either C04003 or C04004 is present, then the other is required.

3 If either C04005 or C04006 is present, then the other is required.

Semantic Notes: 1 REF04 contains data relating to the value cited in REF02.

Notes:

Examples: REF~WO~~B11000519W.

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use	REF01	128	Reference Identification Qualifier			M	1	ID 2/3
			Code qualifying the Reference Identification
				WO	Work Order Number
	REF03	352	Description			X	1	AN 1/80
			A free-form description to clarify the related data elements and their content
			*TEO Number*

Segment: PER Administrative Communications Contact

Position: 1100

Loop: PO1

Level: Detail

Usage: Optional

Max Use: 3

Purpose: To identify a person or office to whom administrative communications should be directed

Syntax Notes: 1 If either PER03 or PER04 is present, then the other is required.

2 'WILL ADVISE' if name is not provided on the PO feed but the phone is present.

Notes:

Example: PER~SM~ROBERT JONES~TE~6145551212.

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use	PER01	366	Contact Function Code			M	1	ID 2/2
			Code identifying the major duty or responsibility of the person or group named
				SM	Verizon Submitting Contact Name
	PER02	93	Name			O	1	AN 1/60
			Free-form name
			*Verizon Submitting Contact Name*
	PER03	365	Communication Number Qualifier			X	1	ID 2/2
			Code identifying the type of communication number
				TE	Telephone
	PER04	364	Communication Number			X	1	AN 1/256
			Complete communications number including country or area code when applicable
			*Submitting Contact’s telephone number*

Segment: DTM Date/Time Reference

Position: 2100

Loop: PO1 Mandatory

Level: Detail

Usage: Optional

Max Use: 10

Purpose: To specify pertinent dates and times

Syntax Notes: 1 At least one of DTM02 DTM03 or DTM05 is required.

Notes:

Example: DTM~002* 20051128~

The delivery requested date is mandatory for our business process, it is not mandatory at the translator nor should it be.

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use	DTM01	374	Date/Time Qualifier			M	1	ID 3/3
			Code specifying type of date or time, or both date and time
				002	Delivery Requested
Must Use	DTM02	373	Date			X	1	DT 8/8
			Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

Segment: DTM Date/Time Reference

Position: 2100

Loop: PO1 Mandatory

Level: Detail

Usage: Optional

Max Use: 10

Purpose: To specify pertinent dates and times

Syntax Notes: 1 At least one of DTM02 DTM03 or DTM05 is required.

Notes:

Example: DTM~010~20020131.

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use	DTM01	374	Date/Time Qualifier			M	1	ID 3/3
			Code specifying type of date or time, or both date and time
				010	Requested Ship
Must Use	DTM02	373	Date			X	1	DT 8/8
			Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

Segment: N1 Name

Position: 3500

Loop: N1 Optional

Level: Detail

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 N103 is required.

Notes:

Example: N1~EN~COPS.

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use	N101	98	Entity Identifier Code			M	1	ID 2/3
			Code identifying an organizational entity, a physical location, property or an individual
				EN	End User
	N102	93	Name			X	1	AN 1/60
			Free-form name
			*Verizon Logistics requestor.*

Segment: REF Reference Identification

Position: 3900

Loop: N1 Optional

Level: Detail

Usage: Optional

Max Use: 12

Purpose: To specify identifying information

Syntax Notes: 1 At least one of REF02 or REF03 is required.

Notes:

Example: REF~C1~COPAA0538599.

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use	REF01	128	Reference Identification Qualifier			M	1	ID 2/3
			Code qualifying the Reference Identification
				C1	Customer material specification number
	REF02	127	Reference Identification			X	1	AN 1/50
			Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
			*Material Requestion Number from the Verizon Logistics Requestor..*

Segment: CTT Transaction Totals

Position: 0100

Loop: CTT Optional (Must Use)

Level: Summary

Usage: Optional (Must Use)

Max Use: 1

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

Comments: 1 This segment is intended to provide hash totals to validate transaction completeness and correctness.

Notes:

Example: CTT~1.

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use	CTT01	354	Number of Line Items	M	1	N0 1/6
			Total number of line items in the transaction set
			*Number of PO1 segments..*

Segment: SE Transaction Set Trailer

Position: 0300

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)

Comments: 1 SE is the last segment of each transaction set.

Notes:

Example: SE~32~0017.

Data Element Summary

Ref. Data

Des. Element Name Attributes

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