A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010

861 Receiving Advice/Acceptance Certificate

Functional Group= RC
This Draft Standard for Trial Use contains the format and establishes the data contents of the Receiving Advice/Acceptance Certificate
Transaction Set (861) 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 the notification of receipt or formal acceptance of goods and
services.

Notes:
1/020 This transaction set is a Receiving Advice unless BRA04 contains a value of "8". When BRA04 contains a value of "8", the transaction set is an
Acceptance Certificate and the units received is the units accepted.
3/010 The number of line items (CTT01) is the accumulation of the number of RCD segments. If used, hash total (CTT02) is the sum of the value of
quantities received (RCD02) for each RCD segment.

User:
There is one header area per Meter Ticket Transaction Set. The detail area of the Meter Ticket Transaction Set consists of sequentially
numbered line items. Each line item transmits one meter ticket. Each transaction set may send 200,000 tickets.

Heading:
Pos Id Segment Name Req Max Repeat Notes Usage
Use
010 ST Transaction Set Header M 1 Req
020 BRA Beginning Segment for Receiving Advice or M 1 N1/020 Req
Acceptance Certificate
070 DTM Date/Time Reference M 10 Req

LOOP ID - N1 200
130 N1 Name O 1 Req
140 N2 Additional Name Information O 2 Used
150 N3 Address Information O 2 Used
160 N4 Geographic Location O 1 Used

Detail:
Pos Id Segment Name Req Max Repeat Notes Usage
Use

LOOP ID - RCD 200000

010 RCD Receiving Conditions O 1 Req
040 LIN Item Identification O 100 Req
050 PID Product/Item Description O 1000 Used
070 REF Reference Identification O 12 Used
090 DTM Date/Time Reference O 10 Req
110 MEA Measurements O >1 Used
170 SAC Service, Promotion, Allowance, or Charge O 10 Used
Information

LOOP ID - SLN 100

190 SLN Subline Item Detail O 1 Used
203 NM1 Individual or Organizational Name O 1 Used

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 1 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010

LOOP ID - N1 200

210 N1 Name O 1 Used

250 REF Reference Identification O 100 Used

260 PER Administrative Communications Contact O 3 Used

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 2 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010

Summary:
Segment Name Reg Max Repeat Notes Usage
Use
010 CTT Transaction Totals 0 N3/010 Req
020 SE Transaction Set Trailer M Req

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 3 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010

Pos: 010 Max: 1

ST Transaction Set Header Heading - Mandatory
Loop: N/A Elements: 2

To indicate the start of a transaction set and to assign a control number

Semantics:
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).

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max Usage_

ST01 143 Transaction Set Identifier Code M ID 3/3 Req
Description: Code uniquely identifying a Transaction Set

Code Name
_
861 Receiving Advice/Acceptance Certificate

ST02 329 Transaction Set Control Number M AN 4/9 Req

Description: Identifying control number that must be unique within the
transaction set functional group assigned by the originator for a transaction
set
User: The control number is assigned by the sender. It is sequentially
assigned within each functional group. Sequential numbering aids in
error recovery and research. ST02 must equal SE02.

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 4 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010

BRA Beginning Segment for Receiving Pos: 020 Max: 1

Heading - Mandatory
Loop: N/A Elements: 4
Advice or Acceptance Certificate
To indicate the beginning of a Receiving Advice or Acceptance Certificate Transaction Set and transmit an identifying number, date, and time
Semantics:
1. BRA02 is the date that the receiving advice transaction set is created.
2. BRA05 is the time that the receiving advice transaction set is created.

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max Usage_

BRA01 127 Reference Identification M AN 1/30 Req
Description: Reference information as defined for a particular Transaction
Set or as specified by the Reference Identification Qualifier
User: This data field must contain a code value of "M" to denote "Meter
Ticket".

BRA02 373 Date M DT 8/8 Req

Description: Date expressed as CCYYMMDD
User: For example, January 1, 1999 would be expressed as 19990101.

BRA03 353 Transaction Set Purpose Code M ID 2/2 Req

Description: Code identifying purpose of transaction set

Code Name
_
00 Original
01 Cancellation
04 Change
05 Replace
07 Duplicate
22 Information Copy

BRA04 962 Receiving Advice or Acceptance Certificate Type Code M ID 1/1 Req
Description: Code specifying type of receiving advice
User: This data field must contain a code value of "2" to denote "Post
Receipt Advice".

Code Name
_
2 Post Receipt Advice

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 5 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010

Pos: 070 Max: 10

DTM Date/Time Reference Heading - Mandatory
Loop: N/A Elements: 3

To specify pertinent dates and times

Syntax:
R020305 -- At least one of DTM02, DTM03 or DTM05 is required.
C0403 -- If DTM04 is present, then DTM03 is required
P0506 -- If either DTM05 or DTM06 are present, then the others are required.

User:
The date is identical to the date contained in BRA02. Use of this segment is mandatory according to the syntactical rules of ASC X12 as well
as for PIPENET. DTM01- DTM03 must be sent.

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max Usage_

DTM01 374 Date/Time Qualifier M ID 3/3 Req
Description: Code specifying type of date or time, or both date and time

Code Name
_
009 Process

DTM02 373 Date C DT 8/8 Req

Description: Date expressed as CCYYMMDD
User: For example, January 1, 1999 would be expressed as 19990101.

DTM03 337 Time C TM 4/8 Req

Description: 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)

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 6 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010

Pos: 130 Max: 1

N1 Name Heading - Optional
Loop: N1 Elements: 4

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

Syntax:
R0203 -- At least one of N102 or N103 is required.
P0304 -- If either N103 or N104 are present, then the others are 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.

User:
PIPENET allows for three (3) iterations of the N1 loop. They are to relay the carrier name, the ticket transaction set destination and the
account identification information. The use of codes CA - Carrier and UC - Ultimate Consignee are MANDATORY. The use of code AO -
Account of is optional for PIPENET.

The preferred method for sending the name is to use the N103 and N104 data elements. If the name is sent in the N103 and N104, do not send
N102. However, if the name is sent as alpha-numeric in N102, do not send N103 and N104.

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max Usage_

N101 98 Entity Identifier Code M ID 2/3 Req
Description: Code identifying an organizational entity, a physical
location, property or an individual

Code Name
_
AO Account Of
CA Carrier
CN Consignee
OP Operator of property or unit
SH Shipper
SU Supplier/Manufacturer
TF Tank Farm
UC Ultimate Consignee
User: Use this code value to designate the Ticket Transaction
Set Destination.

WF Tank Farm Owner

Description: Use this code value to designate the destination
terminal.

N102 93 Name C AN 1/60 Used

Description: Free-form name

N103 66 Identification Code Qualifier C ID 1/2 Used

Description: Code designating the system/method of code structure used
for Identification Code (67)

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 7 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010

Code Name
_

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 8 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010

Ref _ Id_ Element Name _ Req Type

Min/Max Usage_
1 D-U-N-S Number,Dun & Bradstreet
9 D-U-N-S+4,D-U-N-S Number with Four Character Suffix
22 Council of Petroleum Accounting Societies code (COPAS)
TL Transport4 Location Code
User: Refer to Code Source 841 in the Appendix.

TS Transport4 Shipper Code

User: Refer to Code Source 841 in the Appendix.

N104 67 Identification Code C AN 2/80 Used

Description: Code identifying a party or other code

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 9 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010

Pos: 140 Max: 2

N2 Additional Name Information Heading - Optional
Loop: N1 Elements: 2

To specify additional names or those longer than 35 characters in length

User:
Do not send this segment if the entity has been identified by using N103 (DE 66 - Identification Code Qualifier) and N104 (DE 67 -
Identification Code).

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max Usage_

N201 93 Name M AN 1/60 Req
Description: Free-form name

N202 93 Name O AN 1/60 Used

Description: Free-form name

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 10 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010

Pos: 150 Max: 2

N3 Address Information Heading - Optional
Loop: N1 Elements: 2

To specify the location of the named party

User:
Do not send this segment if the entity has been identified by using N103 (DE 66 - Identification Code Qualifier) and N104 (DE 67 -
Identification Code).

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max Usage_

N301 166 Address Information M AN 1/55 Req
Description: Address information

N302 166 Address Information O AN 1/55 Used

Description: Address information

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 11 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010

Pos: 160 Max: 1

N4 Geographic Location Heading - Optional
Loop: N1 Elements: 4

To specify the geographic place of the named party

Syntax:
C0605 -- If N406 is present, then N405 is required

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.

User:
Do not send this segment if the entity has been identified by using N103 (DE 66 - Identification Code Qualifier) and N104 (DE 67 -
Identification Code).

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max Usage_

N401 19 City Name O AN 2/30 Used
Description: Free-form text for city name

N402 156 State or Province Code O ID 2/2 Used

Description: Code (Standard State/Province) as defined by appropriate
government agency
User: Refer to PIDX Bulletin D12A and Code Source 22 in the Appendix.

N403 116 Postal Code O ID 3/15 Used

Description: Code defining international postal zone code excluding
punctuation and blanks (zip code for United States)
User: Refer to PIDX Bulletin D12A and Code Source 22 in the
Appendix.

If N404 is used, then the use of N401 - N403 is required.

N404 26 Country Code O ID 2/3 Used

Description: Code identifying the country

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 12 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010

Pos: 010 Max: 1

RCD Receiving Conditions Detail - Optional
Loop: RCD Elements: 3

To report receiving conditions and specify contested quantities

Syntax:
R020406 -- At least one of RCD02, RCD04 or RCD06 is required.
P0203 -- If either RCD02 or RCD03 are present, then the others are required.
P0405 -- If either RCD04 or RCD05 are present, then the others are required.
P060708 -- If either RCD06, RCD07 or RCD08 are present, then the others are required.
P091011 -- If either RCD09, RCD10 or RCD11 are present, then the others are required.
P121314 -- If either RCD12, RCD13 or RCD14 are present, then the others are required.
P151617 -- If either RCD15, RCD16 or RCD17 are present, then the others are required.
P181920 -- If either RCD18, RCD19 or RCD20 are present, then the others are required.

Semantics:
1. RCD01 is the receiving advice line item identification.
2. RCD21 is the cumulative quantity of goods received for a specific time period.

Comments:
1. See the Data Element Dictionary for a complete list of receiving condition IDs.
2. RCD06 through RCD20 provide for five different quantities whose condition upon receipt is under question.

User:
The RCD segment is used to define the start of a meter ticket. For PIPENET, if RCD02 is sent, then RCD03 is required.

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max Usage_

RCD01 350 Assigned Identification O AN 1/20 Req
Description: Alphanumeric characters assigned for differentiation within
a transaction set
User: This data field must contain the pipeline number assigned by the
carrier.

RCD02 663 Quantity Units Received or Accepted C R 1/9 Req

Description: Number of Units Received or Accepted
User: This data field must be used to relay the ticket net volume.

RCD03 C001 Composite Unit of Measure C Comp Used

Description: To identify a composite unit of measure (See Figures
Appendix for examples of use)
User: PIPENET permits the user to implement other valid Unit of
Measure code values (DE 355) published in version/release 4010. Code
values not listed below that are needed for implementations should be
submitted to the PIPENET User Group for inclusion in the
implementation guide.

The Unit of Measure composite data element allows for reporting a unit of
measure that does not appear in the DE 355 code list but is composed of
entries published in the list by implementing the composite Unit of
861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 13 of 50 Version 004
Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010
Ref _ Id_ Element Name _ Req Type
Min/Max Usage_
Measure syntax.

PIPENET will accommodate 2 levels of Unit of Measure:

· C001-01 Unit of Measure (published code) == (usage is Mandatory)

· C001-02 Exponent == (usage is Optional)
· C001-03 Multiplier == (usage is Optional)
· C001-04 Unit of Measure (published code) == (usage is Optional)
· C001-05 Exponent == (usage is Optional)
· C001 06 Multiplier == (usage is optional)

EXAMPLES OF USE:

· C001: BR for barrels

· C001: BR C004: HT C005: -1 for barrels per half hour

NOTE:
Also refer to the Appendix in this publication for more information about
using the composite unit of measure.

355 Unit or Basis for Measurement Code M ID 2/2 Req

Description: Code specifying the units in which a value is being
expressed, or manner in which a measurement has been taken

Code Name
_
CO Cubic Meters (Net)
GN Gross Gallons
ND Net Barrels
NG Net Gallons
PN Pounds Net

1018 Exponent O R 1/15 Not

Description: Power to which a unit is raised used

649 Multiplier O R 1/10 Not

Description: Value to be used as a multiplier to obtain a new value used

355 Unit or Basis for Measurement Code O ID 2/2 Not

Description: Code specifying the units in which a value is being used
expressed, or manner in which a measurement has been taken
All valid X12 codes are used.
1018 Exponent O R 1/15 Not
Description: Power to which a unit is raised used

649 Multiplier O R 1/10 Not

Description: Value to be used as a multiplier to obtain a new value used

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 14 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010

Pos: 040 Max: 100

LIN Item Identification Detail - Optional
Loop: RCD Elements: 11

To specify basic item identification data

Syntax:
P0405 -- If either LIN04 or LIN05 are present, then the others are required.
P0607 -- If either LIN06 or LIN07 are present, then the others are required.
P0809 -- If either LIN08 or LIN09 are present, then the others are required.
P1011 -- If either LIN10 or LIN11 are present, then the others are required.
P1213 -- If either LIN12 or LIN13 are present, then the others are required.
P1415 -- If either LIN14 or LIN15 are present, then the others are required.
P1617 -- If either LIN16 or LIN17 are present, then the others are required.
P1819 -- If either LIN18 or LIN19 are present, then the others are required.
P2021 -- If either LIN20 or LIN21 are present, then the others are required.
P2223 -- If either LIN22 or LIN23 are present, then the others are required.
P2425 -- If either LIN24 or LIN25 are present, then the others are required.
P2627 -- If either LIN26 or LIN27 are present, then the others are required.
P2829 -- If either LIN28 or LIN29 are present, then the others are required.
P3031 -- If either LIN30 or LIN31 are present, then the others are required.

Semantics:
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.

User:
The following rules supercede the attributes outlined by ASC X12:

LIN06 and LIN07 are optional, but may ONLY be used to send the Primary Movement Identifier.

LIN08 and LIN09 are optional, but may ONLY be used to sent the Transaction Code.

LIN10 and LIN11 are optional, but may ONLY be used to sent the Ticket Type.

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max Usage_

LIN01 350 Assigned Identification O AN 1/20 Used
Description: Alphanumeric characters assigned for differentiation within
a transaction set

LIN02 235 Product/Service ID Qualifier M ID 2/2 Req

Description: Code identifying the type/source of the descriptive number
used in Product/Service ID (234)

Code Name
_
PQ Product ID Attribute Code
861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 15 of 50 Version 004
Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010

Description: Required by PIPENET

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 16 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010
Ref _ Id_ Element Name _ Req Type Min/Max Usage_

LIN03 234 Product/Service ID M AN 1/48 Req

Description: Identifying number for a product or service
User:
PRODUCT ID ATTRIBUTE CODE LIST

C Crude Oil
P Product
N Natural Gas Liquids

LIN04 235 Product/Service ID Qualifier C ID 2/2 Used

Description: Code identifying the type/source of the descriptive number
used in Product/Service ID (234)
User: Use of this data element is required. Refer to the Appendix for
information about the PIDX Product Code List and the Transport4
Commodity Code.

Code Name
_
DH Transport4 Commodity Code
Description: Refer to Code Source 841 in the Appendix.
TP Product Type Code
Description: Use of this data element is required. Refer to the
Appendix for information about the PIDX Product Code List
and the Transport4 Commodity Code.

LIN05 234 Product/Service ID C AN 1/48 Used

Description: Identifying number for a product or service

LIN06 235 Product/Service ID Qualifier C ID 2/2 Used

Description: Code identifying the type/source of the descriptive number
used in Product/Service ID (234)

Code Name
_
GC Grade Code

LIN07 234 Product/Service ID C AN 1/48 Used

Description: Identifying number for a product or service

LIN08 235 Product/Service ID Qualifier C ID 2/2 Used

Description: Code identifying the type/source of the descriptive number
used in Product/Service ID (234)

Code Name
_
TA Pipeline Transaction Code

LIN09 234 Product/Service ID C AN 1/48 Used

Description: Identifying number for a product or service
User:
PIPELINE TRANSACTION CODE

10 Receipt - Custody (into tanks)

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 17 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010
Ref _ Id_ 11 Receipt - Custody (into line)
Element Name _ Req Type Min/Max Usage_

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 18 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010
Ref _ Id_ Element Name _ Req Type Min/Max Usage_
12 Receipt - Gathering Location
17 Receipt - Transfer Record
21 Delivery - Custody (from line)
22 Delivery - Custody (from tanks)
24 Transmix Delivery (out of tanks)
31 Water Adjustment Record
32 Inventory - Adjustment
33 Void Ticket
35 In-tank Transfer

LIN10 235 Product/Service ID Qualifier C ID 2/2 Used

Description: Code identifying the type/source of the descriptive number
used in Product/Service ID (234)

Code Name
_
MO Movement Type Code
Description: The code value MO - Movement Type Code is
used to declare the Ticket Type Qualifier Code.

LIN11 234 Product/Service ID C AN 1/48 Used

Description: Identifying number for a product or service
User:
TICKET TYPE QUALIFIER CODE LIST

BU Bulk
LE Lease
PL Pipeline
TE Terminal Representative
PF Pipeline Facility
CR Credit
SK Skid Ticket
UT Underground Tanks
TR Truck Rack

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 19 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010

Pos: 050 Max: 1000

PID Product/Item Description Detail - Optional
Loop: RCD Elements: 5

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

Syntax:
C0403 -- If PID04 is present, then PID03 is required
R0405 -- At least one of PID04 or PID05 is required.
C0703 -- If PID07 is present, then PID03 is required
C0804 -- If PID08 is present, then PID04 is required
C0905 -- If PID09 is present, then PID05 is required

Semantics:
1. Use PID03 to indicate the organization that publishes the code list being referred to.
2. PID04 should be used for industry-specific product description codes.
3. PID08 describes the physical characteristics of the product identified in PID04. A "Y" indicates that the specified attribute applies to this item; an "N"
indicates it does not apply. Any other value is indeterminate.
4. PID09 is used to identify the language being used in PID05.

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.
2. Use PID06 when necessary to refer to the product surface or layer being described in the segment.
3. PID07 specifies the individual code list of the agency specified in PID03.

User:
PIPENET allows for multiple iterations of the PID segment to relay quality control data, regulatory statements and previous movement
identifier.

The use of the PID segment allows quality control data items to be sent using alpha-numeric descriptions.

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max Usage_

PID01 349 Item Description Type M ID 1/1 Req
Description: Code indicating the format of a description

Code Name
_
F Free-form
X Semi-structured (Code and Text)

PID02 750 Product/Process Characteristic Code O ID 2/3 Used

Description: Code identifying the general class of a product or process
characteristic

Code Name
_
35 Color
40 Shade
Description: Used to declare the Millipore Qualifier Code.
56 Special Processing
Description: Use this code value to declare the CFR Part 80
statements and other governing jurisdiction statements.
84 Special Specification
Description: Use this code value to declare the RVP statement.
861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 20 of 50 Version 004
Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010
SYN Synonym

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 21 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010
Ref _ Id_ Element Name _ Req Type Min/Max Usage_
Description: Used to declare the previous movement identifier
defined by a connecting carrier or other associated party.
WD Warranty Description
Description: Use this code value to declare the CARB
statement.

PID03 559 Agency Qualifier Code C ID 2/2 Used

Description: Code identifying the agency assigning the code values

Code Name
_
AP PIDX
Description: This code value MUST BE USED when a code
value of 84, WD or 56 is used in PID02.

PID04 751 Product Description Code C AN 1/12 Used

Description: A code from an industry code list which provides specific
data about a product characteristic
User: If PID02 = 56 use:

00 - Implies statement of EPA CFR 40 Part 80 paragraph 80.106 (a) (7)

01- First part of statement of EPA CFR Part 80 paragraph 80.106 (a) (7)
follows in PID05

02 - Second part of statement of EPA CFR 40 Part 80 paragraph 80.106

(a) (7) follows in PID05

03 - Implies statement of EPA CFR 40 Part 80 paragraph 80.106 (b)

follows in PID05

04 - First part of statement in EPA CFR 40 Part 80 paragraph 80.106 (b)

follows in PID05.

05 - Second part of statement of EPA CFR 40 Part 80 paragraph 80.106

(b) follows in PID05.

06 - Third part of statement of EPA CFR 40 Part 80 paragraph 80.106 (b)

follows in PID05.

07 - implies oxygen content statement

08 - First part of low sulfur diesel statement

09 - Second part of low sulfur diesel statement

10 - First part of RVP statement

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 22 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010
Ref _ Id_ 11 - Second part of RVP statement
Element Name _ Req Type Min/Max Usage_

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 23 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010
Ref _ Id_ Element Name _ Req Type Min/Max Usage_

If PID02=84 use:

00 - Implies SFPP RVP statement

01- First part of SFPP RVP statement follows in PID05

02 - Second part of SFPP RVP statement follows in PID05

03 - Implies statement of base gasoline

If PID02 = WD use:

00 - implies statement of CARB Non-OPRG

01- implies statement of CARB OPRG

PID05 352 Description C AN 1/80 Used

Description: A free-form description to clarify the related data elements
and their content
User: If PID02 equals "84" and PID04 equals "01", "Verification
received from supplier and SFPP pipeline oversight program indicate"

If PID02 equals "84" and PID04 equals "02", "this product meets federal
and state RVP regulations."

If PID02 equals "84" and PID04 equals "03", "Base gasoline not for sale
to the ultimate consumer"

If PID02 equals "WD" and PID04 equals "00", "This gasoline is not
Oxygenate Fuels Program Reformulated Gasoline (NON-OPRG)"

If PID02 equals "WD" and PID04 equals "01", "This gasoline is

Oxygenate Fuels Program Reformulated Gasoline (ORPG)"

If PID02 equals "56" and PID04 equals "01", "This product does not meet
the requirements for reformulated gasoline,"

If PID02 equals "56" and PID04 equals "02", "and may not be used in any
861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 24 of 50 Version 004
Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010
Ref _ Id_ Element Name _ Req Type Min/Max Usage_
reformulated gasoline covered area."

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 25 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010
Ref _ Id_ Element Name _ Req Type Min/Max Usage_

If PID02 equals "56" and PID04 equals "04", "For purposes of the Anti-
dumping requirements under 40 CFR Subpart E, "

If PID02 equals "56" and PID04 equals "05", "this blendstock has been
accounted for by the refiner that produced it,"

If PID02 equals "56" and PID04 equals "06", "and must be excluded from
any subsequent compliance calculations."

If PID02 equals "56" and PID04 equals "07", "The oxygen content of this
product is 2.7-2.9 percent by weight with ethers"

If PID02 equals "56" and PID04 equals "08", "Shipper/refiner has

certified that diesel"

If PID02 equals "56" and PID04 equals "09", "meets low sulfur diesel
requirements"

If PID02 equals "56" and PID04 equals "10", "Shipper/refiner has

certified that"

If PID02 equals "56" and PID04 equals "11", "gasoline tendered meets
RVP requirements"

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 26 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010

Pos: 070 Max: 12

REF Reference Identification Detail - Optional
Loop: RCD Elements: 4

To specify identifying information

Syntax:
R0203 -- At least one of REF02 or REF03 is required.

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

User:
PIPENET allows four iterations of the REF segment. They are Tariff Number, Bill of Lading Number, Tank Number and Customer Reference
Number.

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max Usage_

REF01 128 Reference Identification Qualifier M ID 2/3 Req
Description: Code qualifying the Reference Identification

Code Name
_
BM Bill of Lading Number
CR Customer Reference Number
TK Tank Number
TS Tariff Number

REF02 127 Reference Identification C AN 1/30 Used

Description: Reference information as defined for a particular Transaction
Set or as specified by the Reference Identification Qualifier

REF03 352 Description C AN 1/80 Used

Description: A free-form description to clarify the related data elements
and their content
User: The reference identification can be described by a numeric value
than send this number in REF02. Otherwise, send the reference as alpha-
numeric text in REF03.

REF04 C040 Reference Identifier O Comp Used

Description: To identify one or more reference numbers or identification
numbers as specified by the Reference Qualifier

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 27 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010

Pos: 090 Max: 10

DTM Date/Time Reference Detail - Optional
Loop: RCD Elements: 3

To specify pertinent dates and times

Syntax:
R020305 -- At least one of DTM02, DTM03 or DTM05 is required.
C0403 -- If DTM04 is present, then DTM03 is required
P0506 -- If either DTM05 or DTM06 are present, then the others are required.

User:
For PIPENET, at least one DTM at the detail level is mandatory.

PIPENET allows three iterations of the DTM segment. They are Ticket Date, Ticket Start Date/Time, and Ticket Stop Date/Time.

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max Usage_

DTM01 374 Date/Time Qualifier M ID 3/3 Req
Description: Code specifying type of date or time, or both date and time

Code Name
_
035 Delivered
Description: Used to declare the Ticket Date DTM segment
090 Report Start
091 Report End

DTM02 373 Date C DT 8/8 Req

Description: Date expressed as CCYYMMDD
User: For PIPENET, the format of the date must be expressed as
YYYYMMDD. For example, January 1, 1999 would be expressed as
19990101.

DTM03 337 Time C TM 4/8 Used

Description: 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)
User: Required for PIPENET for Ticket Start Date/Time DTM segment
and Ticket Stop Date/Time DTM segment.

Use of this data element is optional for Ticket Date DTM segment.

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 28 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010

Pos: 110 Max: >1

MEA Measurements Detail - Optional
Loop: RCD Elements: 4

To specify physical measurements or counts, including dimensions, tolerances, variances, and weights(See Figures Appendix for example of
use of C001)

Syntax:
R03050608 -- At least one of MEA03, MEA05, MEA06 or MEA08 is required.
C0504 -- If MEA05 is present, then MEA04 is required
C0604 -- If MEA06 is present, then MEA04 is required
L07030506 -- If MEA07 is present, then at least one of MEA03, MEA05 or MEA06 is required.
E0803 -- Only one of MEA08 or MEA03 may be present.

Semantics:
1. MEA04 defines the unit of measure for MEA03, MEA05, and MEA06.

Comments:
1. When citing dimensional tolerances, any measurement requiring a sign (+ or -), or any measurement where a positive (+) value cannot be assumed, use
MEA05 as the negative (-) value and MEA06 as the positive (+) value.

User:
Units of measurement of PIPENET document parameters will use the codes publishedd in the implementation guidelines.
PIPENET permits the user to implement other Unit of Measure codes (DE 355) codes published in the version release.
New code implementations should be submitted to the PIPENET User Group committee for inclusion in the implementation guide.
The Unit of Measure data element will permit reporting a unit of measure that does not appear in the DE 355 code list but is composed of
entries published in the list by implementing the composite Unit of Measure syntax.
PIPENET will accommodate 2 levels of Unit of Measure:
· C001 01 Unit of Measure (published code) – usage is Mandatory
· C001 02 Exponent (usage is optional)
· C001 03 Multiplier (usage is optional)
· C001 03 Unit of Measure (published code) – usage is optional)
· C001 04 Exponent (usage is optional)
· C001 05 Multiplier (usage is optional)
Examples:
· C001: BR for barrels
· C001: BR C004: HT C005: -1 for barrels per half hour
Refer to ANSI X-12 version release 4010 Composite Data Structure Figures

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max Usage_

MEA01 737 Measurement Reference ID Code O ID 2/2 Used
Description: Code identifying the broad category to which a measurement
applies

Code Name
_
AV Average Reading
DT Dimensional Tolerance
R1 Opening Reading
R2 Closing Reading
SH Shipping Tolerance

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 29 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010
MEA02 738 Measurement Qualifier O ID 1/3

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 30 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010
Ref _ Id_ Element Name _ Req Type Min/Max Usage_
Description: Code identifying a specific product or process
characteristic to which a measurement applies

Code Name
_
FP Flashpoint
MK Microseperometer (MSEP)
PB Pressure
PY Percent of Water
TC Temperature
ZO Oxygen
BSW Percent Bottom Sediment and Water
CCF Composite Corrected Factor
DMF Distributed Meter Factor
H2O Water Volume
HAZ Haze
LPG Liquefied Petroleum Gas Factor
OAP Observed PIDX Gravity
OBT Observed Temperature
ODR Odor
Description: The quality of a substance that stimulates the
olfactory organ
PRF Pressure Factor
RVP Reid Vapor Pressure
SPG Specific Gravity
TPF Temperature Factor
VSO Volume Split to Others

MEA03 739 Measurement Value C R 1/20 Used

Description: The value of the measurement

MEA04 C001 Composite Unit of Measure C Comp Used

Description: To identify a composite unit of measure(See Figures
Appendix for examples of use)

355 Unit or Basis for Measurement Code M ID 2/2 Req

Description: Code specifying the units in which a value is being
expressed, or manner in which a measurement has been taken

Code Name
_
BR Barrel
CE Centigrade,Celsius
CO Cubic Meters (Net)
CR Cubic Meter
DD Degree
FA Fahrenheit GD
Gross Barrels
GN Gross Gallons
KG Kilogram
ND Net Barrels
NG Net Gallons
PG Pounds Gross
PN Pounds Net
PS Pounds per Sq. Inch
PU Mass Pounds
ZZ Mutually Defined

1018 Exponent O R 1/15 Used

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 31 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010
Ref _ Id_ Element Name _ Req Type Min/Max Usage_
Description: Power to which a unit is raised

649 Multiplier O R 1/10 Used

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 32 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010
Ref _ Id_ Element Name _ Req Type Min/Max Usage_
Description: Value to be used as a multiplier to obtain a new value

355 Unit or Basis for Measurement Code O ID 2/2 Used

Description: Code specifying the units in which a value is being
expressed, or manner in which a measurement has been taken
User: See C001-01 for applicable code values.

1018 Exponent O R 1/15 Used

Description: Power to which a unit is raised

649 Multiplier O R 1/10 Used

Description: Value to be used as a multiplier to obtain a new value

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 33 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010

SAC Service, Promotion, Allowance, or Pos: 170 Max: 10

Detail - Optional
Loop: RCD Elements: 10
Charge Information
To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or
charge

Syntax:
R0203 -- At least one of SAC02 or SAC03 is required.
P0304 -- If either SAC03 or SAC04 are present, then the others are required.
P0607 -- If either SAC06 or SAC07 are present, then the others are required.
P0910 -- If either SAC09 or SAC10 are present, then the others are required.
C1110 -- If SAC11 is present, then SAC10 is required
L130204 -- If SAC13 is present, then at least one of SAC02 or SAC04 is required.
C1413 -- If SAC14 is present, then SAC13 is required
C1615 -- If SAC16 is present, then SAC15 is required

Semantics:
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.
3. If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.
4. SAC08 is the allowance or charge rate per unit.
5. SAC10 and SAC11 is the quantity basis when the allowance or charge quantity is different from the purchase order or invoice quantity.
6. SAC10 and SAC11 used together indicate a quantity range, which could be a dollar amount, that is applicable to service, promotion, allowance, or charge.
7. SAC13 is used in conjunction with SAC02 or SAC04 to provide a specific reference number as identified by the code used.
8. SAC14 is used in conjunction with SAC13 to identify an option when there is more than one option of the promotion.
9. 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.

User:
The ITA segment has been replaced by the SAC segment. However, the functionality remains the same.

User Note 1:
For each meter used for the ticket transmit the meter number and other essential data using this SAC segment. If the meter factor is greater
than or equal to 1 then SAC01 = "A". If the meter factor is less than 1 then SAC01 = "C". If the meter factor is not sent in the SAC segment
then SAC01 = "N". If SAC01 is "A" or "C" then the meter factor must be sent in SAC08.

User Note 2:
If one meter is used for the ticket then this segment is used to transmit the ticket meter factor in SAC08.

If one meter is used for the ticket then percent distribution is implied as 100% and SAC06 and SAC07 are not included in the segment.

User Note 3:
If ending meter reading is sent then SAC10 is mandatory. If the meter reading is combined then the beginning meter reading data element is

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 34 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010

the combined beginning reading. If the meter reading is combined then the ending meter reading data element is the
combined ending reading.

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 35 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010
Transmit Meter Proving Reports only for the meters used for the ticket.

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max Usage_

SAC01 248 Allowance or Charge Indicator M ID 1/1 Req
Description: Code which indicates an allowance or charge for the service
specified

Code Name
_
A Allowance
C Charge
N No Allowance or Charge

SAC03 559 Agency Qualifier Code C ID 2/2 Used

Description: Code identifying the agency assigning the code values

Code Name
_
A4 Assigned by Carrier

SAC04 1301 Agency Service, Promotion, Allowance, or Charge Code C AN 1/10 Used
Description: Agency maintained code identifying the service, promotion,
allowance, or charge
User: Use this data field to relay the meter number.

SAC06 378 Allowance/Charge Percent Qualifier C ID 1/1 Used

Description: Code indicating on what basis allowance or charge percent is
calculated

Code Name
_
Z Mutually Defined

SAC07 332 Percent C R 1/6 Used

Description: Percent expressed as a percent
User: For PIPENET, this is the volume distribution (% distribution) for
the meter defined in SAC04.

SAC08 118 Rate O R 1/9 Used

Description: Rate expressed in the standard monetary denomination for
the currency specified
User: For PIPENET, this is the meter factor for the meter defined in
SAC04.

SAC09 355 Unit or Basis for Measurement Code C ID 2/2 Used

Description: Code specifying the units in which a value is being
expressed, or manner in which a measurement has been taken

Code Name
_
CR Cubic Meter
GD Gross Barrels
GN Gross Gallons
PG Pounds Gross

SAC10 380 Quantity C R 1/15 Used

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 36 of 50 Version 004
Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010

Description: Numeric value of quantity

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 37 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010
Ref _ Id_ Element Name _ Req Type
Min/Max Usage_
User: For PIPENET, this is the ending meter reading.

SAC11 380 Quantity O R 1/15 Used

Description: Numeric value of quantity
User: For PIPENET, this is the beginning meter reading.

SAC13 127 Reference Identification C AN 1/30 Used

Description: Reference information as defined for a particular Transaction
Set or as specified by the Reference Identification Qualifier
User: For PIPINET, this is the proving report number for the meter
defined in SAC04.

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 38 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010

Pos: 190 Max: 1

SLN Subline Item Detail Detail - Optional
Loop: SLN Elements: 4

To specify product subline detail item data

Syntax:
P0405 -- If either SLN04 or SLN05 are present, then the others are required.
C0706 -- If SLN07 is present, then SLN06 is required
C0806 -- If SLN08 is present, then SLN06 is required
P0910 -- If either SLN09 or SLN10 are present, then the others are required.
P1112 -- If either SLN11 or SLN12 are present, then the others are required.
P1314 -- If either SLN13 or SLN14 are present, then the others are required.
P1516 -- If either SLN15 or SLN16 are present, then the others are required.
P1718 -- If either SLN17 or SLN18 are present, then the others are required.
P1920 -- If either SLN19 or SLN20 are present, then the others are required.
P2122 -- If either SLN21 or SLN22 are present, then the others are required.
P2324 -- If either SLN23 or SLN24 are present, then the others are required.
P2526 -- If either SLN25 or SLN26 are present, then the others are required.
P2728 -- If either SLN27 or SLN28 are present, then the others are required.

Semantics:
1. SLN01 is the identifying number for the subline item.
2. SLN02 is the identifying number for the subline level. The subline level is analogous to the level code used in a bill of materials.
3. SLN03 is the configuration code indicating the relationship of the subline item to the baseline item.
4. SLN08 is a code indicating the relationship of the price or amount to the associated segment.

Comments:
1. See the Data Element Dictionary for a complete list of IDs.
2. SLN01 is related to (but not necessarily equivalent to) the baseline item number. Example: 1.1 or 1A might be used as a subline number to relate to
baseline number 1.
3. SLN09 through SLN28 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model
No., or SKU.

User:
For PIPENET, this segment is used to include a split ticket volume.

The SLN Loop accommodates split ticket volumes where the associated parties must be identified.

Units of measurement of PIPENET document parameters will use the codes publishedd in the implementation guidelines.
PIPENET permits the user to implement other Unit of Measure codes (DE 355) codes published in the version release.
New code implementations should be submitted to the PIPENET User Group committee for inclusion in the implementation guide.
The Unit of Measure data element will permit reporting a unit of measure that does not appear in the DE 355 code list but is composed of
entries published in the list by implementing the composite Unit of Measure syntax.
PIPENET will accommodate 2 levels of Unit of Measure:
· C001 01 Unit of Measure (published code) – usage is Mandatory
· C001 02 Exponent (usage is optional)
· C001 03 Multiplier (usage is optional)
· C001 03 Unit of Measure (published code) – usage is optional)
· C001 04 Exponent (usage is optional)
· C001 05 Multiplier (usage is optional)
Examples:
· C001: BR for barrels
· C001: BR C004: HT C005: -1 for barrels per half hour
Refer to ANSI X-12 version release 4010 Composite Data Structure Figures

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 39 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010
Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max Usage_

SLN01 350 Assigned Identification M AN 1/20 Req
Description: Alphanumeric characters assigned for differentiation within
a transaction set
User: A sequential numeric sub-line item counter.

SLN03 662 Relationship Code M ID 1/1 Req

Description: Code indicating the relationship between entities

Code Name
_
A Add

SLN04 380 Quantity C R 1/15 Used

Description: Numeric value of quantity
User: The split ticket volume

SLN05 C001 Composite Unit of Measure C Comp Used

Description: To identify a composite unit of measure(See Figures
Appendix for examples of use)

355 Unit or Basis for Measurement Code M ID 2/2 Req

Description: Code specifying the units in which a value is being
expressed, or manner in which a measurement has been taken

Code Name
_
CO Cubic Meters (Net)
GN Gross Gallons
ND Net Barrels
NG Net Gallons
PN Pounds Net

1018 Exponent O R 1/15 Used

Description: Power to which a unit is raised

649 Multiplier O R 1/10 Used

Description: Value to be used as a multiplier to obtain a new value

355 Unit or Basis for Measurement Code O ID 2/2 Used

Description: Code specifying the units in which a value is being
expressed, or manner in which a measurement has been taken
User: Refer to C001-01 for applicable code values.

1018 Exponent O R 1/15 Used

Description: Power to which a unit is raised

649 Multiplier O R 1/10 Used

Description: Value to be used as a multiplier to obtain a new value

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 40 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010

Pos: 203 Max: 1

NM1 Individual or Organizational Name Detail - Optional
Loop: SLN Elements: 9

To supply the full name of an individual or organizational entity

Syntax:
P0809 -- If either NM108 or NM109 are present, then the others are required.
C1110 -- If NM111 is present, then NM110 is required

Semantics:
1. NM102 qualifies NM103.

Comments:
1. NM110 and NM111 further define the type of entity in NM101.

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max Usage_

NM101 98 Entity Identifier Code M ID 2/3 Req
Description: Code identifying an organizational entity, a physical
location, property or an individual

Code Name
_
AO Account Of
CN Consignee
SH Shipper
SU Supplier/Manufacturer
UC Ultimate Consignee

NM102 1065 Entity Type Qualifier M ID 1/1 Req

Description: Code qualifying the type of entity

Code Name
_
2 Non-Person Entity

NM103 1035 Name Last or Organization Name O AN 1/35 Used

Description: Individual last name or organizational name

NM104 1036 Name First O AN 1/25 Used

Description: Individual first name

NM105 1037 Name Middle O AN 1/25 Used

Description: Individual middle name or initial

NM106 1038 Name Prefix O AN 1/10 Used

Description: Prefix to individual name

NM107 1039 Name Suffix O AN 1/10 Used

Description: Suffix to individual name

NM108 66 Identification Code Qualifier C ID 1/2 Used

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 41 of 50 Version 004
Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010

Description: Code designating the system/method of code structure used

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 42 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010
Ref _ Id_ Element Name _ Req Type
Min/Max Usage_
for Identification Code (67)

Code Name
_
1 D-U-N-S Number,Dun & Bradstreet
9 D-U-N-S+4,D-U-N-S Number with Four Character Suffix
22 Council of Petroleum Accounting Societies code (COPAS)
TL Transport4 Location Code
Description:

User: Refer to Code Source 841 in the Appendix.

TS Transport4 Shipper Code

User: Refer to Code Source 841 in the Appendix.

NM109 67 Identification Code C AN 2/80 Not

Description: Code identifying a party or other code used

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 43 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010

Pos: 210 Max: 1

N1 Name Detail - Optional
Loop: N1 Elements: 4

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

Syntax:
R0203 -- At least one of N102 or N103 is required.
P0304 -- If either N103 or N104 are present, then the others are 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.

User:
A typical third pary transaction can be envisioned as a three link chain. The left link owns the ticket data and allows the middle link access to
the ticket. The right link is granted access to the ticket by the middle link.

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max Usage_

N101 98 Entity Identifier Code M ID 2/3 Req
Description: Code identifying an organizational entity, a physical
location, property or an individual

Code Name
_
AO Account Of
CI Consignor
CN Consignee
DT Destination Terminal
IK Intermediate Carrier
Description: Use this code value to denote Connecting Carrier.
NC Cross-Town Switch
Description: Local Rail Movement
OC Origin Carrier
OP Operator of property or unit
OV Owner of Vessel
PP Property
RF Refinery
SF Ship From
SH Shipper
ST Ship To
SU Supplier/Manufacturer
TF Tank Farm
UC Ultimate Consignee
WF Tank Farm Owner
User: Use this code value to designate the destination terminal.

Z6 Transferring Party
Description: An organization that is sending material
User: This is the left link in the chain. This party "owned" the
product first. This party is the transferor to the middle link in
the chain. This party grants access to the ticket stored in the
TPTS respository to the middle link in the chain.

Z8 Last Known Source of Supply

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 44 of 50 Version 004
Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010
Description: The last organization known to hold a transaction

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 45 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010
Ref _ Id_ Element Name _ Req Type
Min/Max Usage_
for the needed material
User: This is the right link in the chain. This party owned the
product last in this three link chain of custody. This party is
granted access to the ticket by the middle link. This name
qualifier identifies this party as the transferee due to a change of
custody from the party identified in the N1 segment with a code
value of "ZL" in N101.

ZD Party to Receive Reports

Description: The organization designated to receive reports
User: This is the middle link in the chain requesting a copy of
the ticket stored in the TPTS respository. This party "owned"
the product second. This party is the transferee to the transferor
identified by the N1 segment with the code value "Z6" in N101.

ZL Party Passing the Transaction

Description: The party forwarding a transaction
User: This is the middle link in the chain requesting a copy of
the ticket stored in the TPTS respository. This party which
transferred ownership of the product to the right link in the
chain. This name qualifier identifies this party as the transferor
to the right link..

N102 93 Name C AN 1/60 Used

Description: Free-form name

N103 66 Identification Code Qualifier C ID 1/2 Used

Description: Code designating the system/method of code structure used
for Identification Code (67)

Code Name
_
1 D-U-N-S Number,Dun & Bradstreet
9 D-U-N-S+4,D-U-N-S Number with Four Character Suffix
20 Standard Point Location Code (SPLC)
22 Council of Petroleum Accounting Societies code (COPAS)
ZY Temporary Identification Number
Description: A data maintenance item is pending for the
addition of a code value to denote "Transport 4 Identification
Code". Use the code value "ZY" until the data maintenance item
is approved by the ASC X12 standards-setting body.

N104 67 Identification Code C AN 2/80 Used

Description: Code identifying a party or other code

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 46 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010

Pos: 250 Max: 100

REF Reference Identification Detail - Optional
Loop: N1 Elements: 2

To specify identifying information

Syntax:
R0203 -- At least one of REF02 or REF03 is required.

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

User:
When N101 (Table 2/210) contains the code value "OV", then REF01 will be "ABS". This identifies a vessel name (REF segment) with the
owner of the vessel (N1 segment).

When N101 (Table 2/210) contains the code value "OP", then REF01 will be "LC". This identifies a lease number (REF segment) with the
owner of the lease (N1 segment).

When N101 (Table 2/210) contains the code values "ST" or "SF", then Loop 200 may be include a second instance of (Table 2/250) then
REF01 will be "PG". This identifies a foreign crude code and description.

When N101 (Table 2/210) contains the code values "ST" or "SF", then REF01 will be "MT". This identifies a meter ticket number associated
with Ship To or Ship From location.

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max Usage_

REF01 128 Reference Identification Qualifier M ID 2/3 Req
Description: Code qualifying the Reference Identification

Code Name
_
LC Lease Number
MT Meter Ticket Number
PG Product Group
ABS Vessel Name

REF02 127 Reference Identification C AN 1/30 Used

Description: Reference information as defined for a particular Transaction
Set or as specified by the Reference Identification Qualifier

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 47 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010

PER Administrative Communications Pos: 260 Max: 3

Detail - Optional
Loop: N1 Elements: 2
Contact
To identify a person or office to whom administrative communications should be directed

Syntax:
P0304 -- If either PER03 or PER04 are present, then the others are required.
P0506 -- If either PER05 or PER06 are present, then the others are required.
P0708 -- If either PER07 or PER08 are present, then the others are required.

User:
PIPENET allows that the information contact in the PER segment of the N1 loop sending the Point of Origin (N101="SF") or Point of Delivery
(N101="ST").

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max Usage_

PER01 366 Contact Function Code M ID 2/2 Req
Description: Code identifying the major duty or responsibility of the
person or group named

Code Name
_
IC Information Contact

PER02 93 Name O AN 1/60 Used

Description: Free-form name
User: Use this data field to relay the name or initials of the field
employee responsible for the creation of the ticket.

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 48 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010

Pos: 010 Max: 1

CTT Transaction Totals Summary - Optional
Loop: N/A Elements: 1

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

Syntax:
P0304 -- If either CTT03 or CTT04 are present, then the others are required.
P0506 -- If either CTT05 or CTT06 are present, then the others are required.

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

User:
This data field should contain the number of LIN segments present in the transaction set.

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max Usage_

CTT01 354 Number of Line Items M N0 1/6 Req
Description: Total number of line items in the transaction set
User: For PIPENET a count of the number of RCD segments present in
the transaction.

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 49 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.
 A PIPENET CONVENTION FOR EDI VERSION 004 RELEASE 010

Pos: 020 Max: 1

SE Transaction Set Trailer Summary - Mandatory
Loop: N/A Elements: 2

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.

Element Summary:

Ref _ Id_ Element Name _ Req Type Min/Max Usage_

SE01 96 Number of Included Segments M N0 1/10 Req
Description: Total number of segments included in a transaction set
including ST and SE segments

SE02 329 Transaction Set Control Number M AN 4/9 Req

Description: Identifying control number that must be unique within the
transaction set functional group assigned by the originator for a transaction
set
User: SE02 must be the same number as ST02.

861 Receiving Advice/Acceptance Certificate (Meter Ticket) Page 50 of 50 Version 004

Document ID: 01-292-20-50-1998 1998-05-01
© PIDX, Inc. 2011
Use of this copyrighted material is subject to the PIDX End User License Agreement available at [Link]/license.
Each user agrees to such End User License Agreement by making any use of the copyrighted material.

This document was prepared and is maintained in accordance with the PIDX Procedures for Standards Development,
a copy of which is available at [Link]/procedures, and the PIDX Antitrust Guidelines, a copy of which is available at [Link]/antitrust.