855 Purchase Order Acknowledgment 
 
   
Functional Group ID=PR
 
 
Introduction: 
 
This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Acknowledgment Transaction Set (855) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to a seller's acknowledgment of a buyer's purchase order. This transaction set can also be used as notification of a vendor generated order. This usage advises a buyer that a vendor has or will ship merchandise as prearranged in their partnership. 
                                                       
 
Heading:
 
 
  Pos. Seg. Req. Loop Notes and
  No. ID Name Des. Max.Use Repeat Comments
 
Must Use 010 ST Transaction Set Header M 1
Must Use 020 BAK Beginning Segment for Purchase Order Acknowledgment M 1
  040 CUR Currency O 1
  080 FOB F.O.B. Related Instructions O >1
  LOOP ID - SAC 25  
  120 SAC Service, Promotion, Allowance, or Charge Information O 1  
  125 CUR Currency O 1  
 
  150 DTM Date/Time Reference O 10
  LOOP ID - N1 200  
  300 N1 Name O 1  
  320 N3 Address Information O 2  
  330 N4 Geographic Location O 1  
 
 
Detail:
 
 
  Pos. Seg. Req. Loop Notes and
  No. ID Name Des. Max.Use Repeat Comments
 
  LOOP ID - PO1 100000  
  010 PO1 Baseline Item Data O 1 n1  
  015 LIN Item Identification O >1  
  040 CTP Pricing Information O >1  
  LOOP ID - PID 1000    
  050 PID Product/Item Description O 1    
 
  100 REF Reference Identification O >1  
  190 SDQ Destination Quantity O 500  
  200 DTM Date/Time Reference O 10  
  LOOP ID - ACK 104    
  270 ACK Line Item Acknowledgment O 1    
 
 
Summary:
 
 
  Pos. Seg. Req. Loop Notes and
  No. ID Name Des. Max.Use Repeat Comments
 
  LOOP ID - CTT 1  
  010 CTT Transaction Totals O 1 n2  
 
Must Use 030 SE Transaction Set Trailer M 1
 
Transaction Set Notes 
 
       
1. PO102 is required.
2. The number of line items (CTT01) is the accumulation of the number of PO1 segments. If used, hash total (CTT02) is the sum of the value of quantities ordered (PO102) for each PO1 segment.
 

           
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:
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).
Comments:
Notes: Segment Example: ST*855*121653^
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
>> ST01 143 Transaction Set Identifier Code M ID 3/3
  Code uniquely identifying a Transaction Set
  Refer to 004010 Data Element Dictionary for acceptable code values.
>> ST02 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

           
Segment: BAK Beginning Segment for Purchase Order Acknowledgment
Position: 020
Loop:
Level: Heading
Usage: Mandatory
Max Use: 1
Purpose: To indicate the beginning of the Purchase Order Acknowledgment Transaction Set and transmit identifying numbers and dates
Syntax Notes:
Semantic Notes: 1 BAK04 is the date assigned by the purchaser to purchase order.
  2 BAK08 is the seller's order number.
  3 BAK09 is the date assigned by the sender to the acknowledgment.
Comments:
Notes: Segment Example: BAK*00*AC*AEL12345*950123*****950123^
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
>> BAK01 353 Transaction Set Purpose Code M ID 2/2
  Code identifying purpose of transaction set
  Suggested codes for aftermarket usage. Any ASC X12 approved code may be used.
   
  00 Original
  04 Change
 
>> BAK02 587 Acknowledgment Type M ID 2/2
  Code specifying the type of acknowledgment
  Suggested codes for aftermarket usage. Any ASC X12 approved code may be used.
   
  AC Acknowledge - With Detail and Change
  AE Acknowledge - With Exception Detail Only
  AK Acknowledge - No Detail or Change
  AP Acknowledge - Product Replenishment
  RD Reject with Detail
 
>> BAK03 324 Purchase Order Number M AN 1/22
  Identifying number for Purchase Order assigned by the orderer/purchaser
>> BAK04 373 Date M DT 8/8
  Date expressed as CCYYMMDD
  BAK09 373 Date O DT 8/8
  Date expressed as CCYYMMDD
  BAK10 640 Transaction Type Code O ID 2/2
  Code specifying the type of transaction
  Refer to 004010 Data Element Dictionary for acceptable code values.

           
Segment: CUR Currency
Position: 040
Loop:
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To specify the currency (dollars, pounds, francs, etc.) used in a transaction
Syntax Notes: 1 If CUR08 is present, then CUR07 is required.
  2 If CUR09 is present, then CUR07 is required.
  3 If CUR10 is present, then at least one of CUR11 or CUR12 is required.
  4 If CUR11 is present, then CUR10 is required.
  5 If CUR12 is present, then CUR10 is required.
  6 If CUR13 is present, then at least one of CUR14 or CUR15 is required.
  7 If CUR14 is present, then CUR13 is required.
  8 If CUR15 is present, then CUR13 is required.
  9 If CUR16 is present, then at least one of CUR17 or CUR18 is required.
  10 If CUR17 is present, then CUR16 is required.
  11 If CUR18 is present, then CUR16 is required.
  12 If CUR19 is present, then at least one of CUR20 or CUR21 is required.
  13 If CUR20 is present, then CUR19 is required.
  14 If CUR21 is present, then CUR19 is required.
Semantic Notes:
Comments: 1 See Figures Appendix for examples detailing the use of the CUR segment.
Notes: Segment Example: CUR*BY*USA.
  This is an optional segment.
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
>> CUR01 98 Entity Identifier Code M ID 2/3
  Code identifying an organizational entity, a physical location, property or an individual
  Sugested codes for aftermarket usage. Any ASC X12 approved code may be used.
   
  BY Buying Party (Purchaser)
  SE Selling Party
 
>> CUR02 100 Currency Code M ID 3/3
  Code (Standard ISO) for country in whose currency the charges are specified

           
Segment: FOB F.O.B. Related Instructions
Position: 080
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.
  3 If FOB07 is present, then FOB06 is required.
  4 If FOB08 is present, then FOB09 is required.
Semantic Notes: 1 FOB01 indicates which party will pay the carrier.
  2 FOB02 is the code specifying transportation responsibility location.
  3 FOB06 is the code specifying the title passage location.
  4 FOB08 is the code specifying the point at which the risk of loss transfers. This may be different than the location specified in FOB02/FOB03 and FOB06/FOB07.
Comments:
Notes: Segment Example: FOB*CC^
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
>> FOB01 146 Shipment Method of Payment M ID 2/2
  Code identifying payment terms for transportation charges
  Suggested codes for aftermarket usage. Any ASC X12 approved code may be used.
   
  BP Paid by Buyer
  The buyer agrees to the transportation payment term requiring the buyer to pay transportation charges to a specified location (origin or destination location)
  CC Collect
  PC Prepaid but Charged to Customer
  PP Prepaid (by Seller)
  PU Pickup
 

           
Segment: SAC Service, Promotion, Allowance, or Charge Information
Position: 120
Loop: SAC Optional
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge
Syntax Notes: 1 At least one of SAC02 or SAC03 is required.
  2 If either SAC03 or SAC04 is present, then the other is required.
  3 If either SAC06 or SAC07 is present, then the other is required.
  4 If either SAC09 or SAC10 is present, then the other is required.
  5 If SAC11 is present, then SAC10 is required.
  6 If SAC13 is present, then at least one of SAC02 or SAC04 is required.
  7 If SAC14 is present, then SAC13 is required.
  8 If SAC16 is present, then SAC15 is required.
Semantic Notes: 1 If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.
  2 SAC05 is the total amount for the service, promotion, allowance, or charge.
  If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.
  3 SAC08 is the allowance or charge rate per unit.
  4 SAC10 and SAC11 is the quantity basis when the allowance or charge quantity is different from the purchase order or invoice quantity.
  SAC10 and SAC11 used together indicate a quantity range, which could be a dollar amount, that is applicable to service, promotion, allowance, or charge.
  5 SAC13 is used in conjunction with SAC02 or SAC04 to provide a specific reference number as identified by the code used.
  6 SAC14 is used in conjunction with SAC13 to identify an option when there is more than one option of the promotion.
  7 SAC16 is used to identify the language being used in SAC15.
Comments: 1 SAC04 may be used to uniquely identify the service, promotion, allowance, or charge. In addition, it may be used in conjunction to further the code in SAC02.
  2 In some business applications, it is necessary to advise the trading partner of the actual dollar amount that a particular allowance, charge, or promotion was based on to reduce ambiguity. This amount is commonly referred to as "Dollar Basis Amount". It is represented in the SAC segment in SAC10 using the qualifier "DO" - Dollars in SAC09.
 
 
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
>> SAC01 248 Allowance or Charge Indicator M ID 1/1
  Code which indicates an allowance or charge for the service specified
  Refer to 004010 Data Element Dictionary for acceptable code values.
  SAC02 1300 Service, Promotion, Allowance, or Charge Code X ID 4/4
  Code identifying the service, promotion, allowance, or charge
  Refer to 004010 Data Element Dictionary for acceptable code values.
  SAC03 559 Agency Qualifier Code X ID 2/2
  Code identifying the agency assigning the code values
  Refer to 004010 Data Element Dictionary for acceptable code values.
  SAC04 1301 Agency Service, Promotion, Allowance, or Charge Code X AN 1/10
  Agency maintained code identifying the service, promotion, allowance, or charge
  SAC05 610 Amount O N2 1/15
  Monetary amount
  SAC06 378 Allowance/Charge Percent Qualifier X ID 1/1
  Code indicating on what basis allowance or charge percent is calculated
  Refer to 004010 Data Element Dictionary for acceptable code values.
  SAC07 332 Percent X R 1/6
  Percent expressed as a percent
  SAC08 118 Rate O R 1/9
  Rate expressed in the standard monetary denomination for the currency specified
  SAC09 355 Unit or Basis for Measurement Code X ID 2/2
  Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
  Refer to 004010 Data Element Dictionary for acceptable code values.
  SAC10 380 Quantity X R 1/15
  Numeric value of quantity
  SAC11 380 Quantity O R 1/15
  Numeric value of quantity
  SAC12 331 Allowance or Charge Method of Handling Code O ID 2/2
  Code indicating method of handling for an allowance or charge
  Refer to 004010 Data Element Dictionary for acceptable code values.
  SAC13 127 Reference Identification X AN 1/30
  Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
  SAC14 770 Option Number O AN 1/20
  A unique number identifying available promotion or allowance options when more than one is offered
  SAC15 352 Description X AN 1/80
  A free-form description to clarify the related data elements and their content
  SAC16 819 Language Code O ID 2/3
  Code designating the language used in text, from a standard code list maintained by the International Standards Organization (ISO 639)

           
Segment: CUR Currency
Position: 125
Loop: SAC Optional
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To specify the currency (dollars, pounds, francs, etc.) used in a transaction
Syntax Notes: 1 If CUR08 is present, then CUR07 is required.
  2 If CUR09 is present, then CUR07 is required.
  3 If CUR10 is present, then at least one of CUR11 or CUR12 is required.
  4 If CUR11 is present, then CUR10 is required.
  5 If CUR12 is present, then CUR10 is required.
  6 If CUR13 is present, then at least one of CUR14 or CUR15 is required.
  7 If CUR14 is present, then CUR13 is required.
  8 If CUR15 is present, then CUR13 is required.
  9 If CUR16 is present, then at least one of CUR17 or CUR18 is required.
  10 If CUR17 is present, then CUR16 is required.
  11 If CUR18 is present, then CUR16 is required.
  12 If CUR19 is present, then at least one of CUR20 or CUR21 is required.
  13 If CUR20 is present, then CUR19 is required.
  14 If CUR21 is present, then CUR19 is required.
Semantic Notes:
Comments: 1 See Figures Appendix for examples detailing the use of the CUR segment.
 
 
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
>> CUR01 98 Entity Identifier Code M ID 2/3
  Code identifying an organizational entity, a physical location, property or an individual
  Refer to 004010 Data Element Dictionary for acceptable code values.
>> CUR02 100 Currency Code M ID 3/3
  Code (Standard ISO) for country in whose currency the charges are specified
  CUR03 280 Exchange Rate O R 4/10
  Value to be used as a multiplier conversion factor to convert monetary value from one currency to another
  CUR04 98 Entity Identifier Code O ID 2/3
  Code identifying an organizational entity, a physical location, property or an individual
  Refer to 004010 Data Element Dictionary for acceptable code values.
  CUR05 100 Currency Code O ID 3/3
  Code (Standard ISO) for country in whose currency the charges are specified
  CUR06 669 Currency Market/Exchange Code O ID 3/3
  Code identifying the market upon which the currency exchange rate is based
  Refer to 004010 Data Element Dictionary for acceptable code values.
  CUR07 374 Date/Time Qualifier X ID 3/3
  Code specifying type of date or time, or both date and time
  Refer to 004010 Data Element Dictionary for acceptable code values.
  CUR08 373 Date O DT 8/8
  Date expressed as CCYYMMDD
  CUR09 337 Time O TM 4/8
  Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
  CUR10 374 Date/Time Qualifier X ID 3/3
  Code specifying type of date or time, or both date and time
  Refer to 004010 Data Element Dictionary for acceptable code values.
  CUR11 373 Date X DT 8/8
  Date expressed as CCYYMMDD
  CUR12 337 Time X TM 4/8
  Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
  CUR13 374 Date/Time Qualifier X ID 3/3
  Code specifying type of date or time, or both date and time
  Refer to 004010 Data Element Dictionary for acceptable code values.
  CUR14 373 Date X DT 8/8
  Date expressed as CCYYMMDD
  CUR15 337 Time X TM 4/8
  Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
  CUR16 374 Date/Time Qualifier X ID 3/3
  Code specifying type of date or time, or both date and time
  Refer to 004010 Data Element Dictionary for acceptable code values.
  CUR17 373 Date X DT 8/8
  Date expressed as CCYYMMDD
  CUR18 337 Time X TM 4/8
  Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
  CUR19 374 Date/Time Qualifier X ID 3/3
  Code specifying type of date or time, or both date and time
  Refer to 004010 Data Element Dictionary for acceptable code values.
  CUR20 373 Date X DT 8/8
  Date expressed as CCYYMMDD
  CUR21 337 Time X TM 4/8
  Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

           
Segment: DTM Date/Time Reference
Position: 150
Loop:
Level: Heading
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.
  2 If DTM04 is present, then DTM03 is required.
  3 If either DTM05 or DTM06 is present, then the other is required.
Semantic Notes:
Comments:
Notes: Segment Example: DTM*085*950124*1659**19^
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
>> DTM01 374 Date/Time Qualifier M ID 3/3
  Code specifying type of date or time, or both date and time
  Suggested codes for aftermarket usage. Any ASC X12 approved code may be used.
   
  011 Shipped
  072 Promised for Delivery (After and Including)
  075 Promised for Delivery (Prior to and Including)
  082 Promised for Shipment (After and Including)
  085 Promised for Shipment (Prior to and Including)
  088 Promised for Shipment (Week of)
  101 No Production Schedule Established as of
 
  DTM02 373 Date X DT 8/8
  Date expressed as CCYYMMDD
  DTM03 337 Time X TM 4/8
  Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

           
Segment: N1 Name
Position: 300
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.
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 N105 and N106 further define the type of entity in N101.
Notes: Segment Example: N1*ST**92*123456789^
  This is an optional segment.
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
>> N101 98 Entity Identifier Code M ID 2/3
  Code identifying an organizational entity, a physical location, property or an individual
  Suggested code for aftermarket usage. Any ASC X12 approved code may be used.
   
  SF Ship From
  ST Ship To
 
  N103 66 Identification Code Qualifier X ID 1/2
  Code designating the system/method of code structure used for Identification Code (67)
  Suggested codes for aftermarket usage. Any ASC X12 approved codes may be used.
   
  91 Assigned by Seller or Seller's Agent
  92 Assigned by Buyer or Buyer's Agent
 
  N104 67 Identification Code X AN 2/80
  Code identifying a party or other code
  N105 706 Entity Relationship Code O ID 2/2
  Code describing entity relationship
  Refer to 004010 Data Element Dictionary for acceptable code values.
  N106 98 Entity Identifier Code O ID 2/3
  Code identifying an organizational entity, a physical location, property or an individual
  Refer to 004010 Data Element Dictionary for acceptable code values.

           
Segment: N3 Address Information
Position: 320
Loop: N1 Optional
Level: Heading
Usage: Optional
Max Use: 2
Purpose: To specify the location of the named party
Syntax Notes:
Semantic Notes:
Comments:
 
 
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
>> N301 166 Address Information M AN 1/55
  Address information
  N302 166 Address Information O AN 1/55
  Address information

           
Segment: N4 Geographic Location
Position: 330
Loop: N1 Optional
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To specify the geographic place of the named party
Syntax Notes: 1 If N406 is present, then N405 is required.
Semantic Notes:
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.
 
 
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
  N401 19 City Name O AN 2/30
  Free-form text for city name
  N402 156 State or Province Code O ID 2/2
  Code (Standard State/Province) as defined by appropriate government agency
  N403 116 Postal Code O ID 3/15
  Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
  N404 26 Country Code O ID 2/3
  Code identifying the country
  N405 309 Location Qualifier X ID 1/2
  Code identifying type of location
  Refer to 004010 Data Element Dictionary for acceptable code values.
  N406 310 Location Identifier O AN 1/30
  Code which identifies a specific location

           
Segment: PO1 Baseline Item Data
Position: 010
Loop: PO1 Optional
Level: Detail
Usage: Optional
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.
  8 If either PO116 or PO117 is present, then the other is required.
  9 If either PO118 or PO119 is present, then the other is required.
  10 If either PO120 or PO121 is present, then the other is required.
  11 If either PO122 or PO123 is present, then the other is required.
  12 If either PO124 or PO125 is present, then the other is required.
Semantic Notes:
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: Segment Example: PO1*1*4*EA*12345*NT*VN*RP1045^
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
  PO101 350 Assigned Identification O AN 1/20
  Alphanumeric characters assigned for differentiation within a transaction set
  This element is required if the purchase order was received with line numbers. If the p.o. was received without line numbers the original part number may be substituted.
  PO102 330 Quantity Ordered X R 1/15
  Quantity ordered
  Value should be the same as that on the original p.o.
  PO103 355 Unit or Basis for Measurement Code O ID 2/2
  Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
  Value should be the same as that on the original p.o.
  Refer to 004010 Data Element Dictionary for acceptable code values.
  PO104 212 Unit Price X R 1/17
  Price per unit of product, service, commodity, etc.
  Use the CTP segment to communicate a price change. Use this element only when communicating the same price as on the original p.o.
  PO105 639 Basis of Unit Price Code O ID 2/2
  Code identifying the type of unit price for an item
  Value should be the same as that on the original p.o.
  Refer to 004010 Data Element Dictionary for acceptable code values.
  PO106 235 Product/Service ID Qualifier X ID 2/2
  Code identifying the type/source of the descriptive number used in Product/Service ID (234)
  Value should be the same as that on the original p.o.
  If PO106 and PO107 elements are not used, the PID segment must be included.
  Refer to 004010 Data Element Dictionary for acceptable code values.
  PO107 234 Product/Service ID X AN 1/48
  Identifying number for a product or service
  Value should be the same as that on the original p.o.

           
Segment: LIN Item Identification
Position: 015
Loop: PO1 Optional
Level: Detail
Usage: Optional
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.
  3 If either LIN08 or LIN09 is present, then the other is required.
  4 If either LIN10 or LIN11 is present, then the other is required.
  5 If either LIN12 or LIN13 is present, then the other is required.
  6 If either LIN14 or LIN15 is present, then the other is required.
  7 If either LIN16 or LIN17 is present, then the other is required.
  8 If either LIN18 or LIN19 is present, then the other is required.
  9 If either LIN20 or LIN21 is present, then the other is required.
  10 If either LIN22 or LIN23 is present, then the other is required.
  11 If either LIN24 or LIN25 is present, then the other is required.
  12 If either LIN26 or LIN27 is present, then the other is required.
  13 If either LIN28 or LIN29 is present, then the other is required.
  14 If either LIN30 or LIN31 is present, then the other is required.
Semantic Notes: 1 LIN01 is the line item identification
Comments: 1 See the Data Dictionary for a complete list of IDs.
  2 LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
 
 
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
  LIN01 350