Adobe
/
Purchase Order (Shrinkwrapped Orders)
  • Specification
  • EDI Inspector
Stedi maintains this guide based on public documentation from Adobe. Contact Adobe for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Adobe logo

X12 850 Purchase Order (Shrinkwrapped Orders)

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Transaction Set (850) 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 placement of purchase orders for goods and services. This transaction set should not be used to convey purchase order changes or purchase order acknowledgment information.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI sample
  • sample
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/adobe/purchase-order-shrinkwrapped-orders/01GY07PVS460ANXFTN2NFT8DPV
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
ST
010
Transaction Set Header
Max use 1
Required
BEG
020
Beginning Segment for Purchase Order
Max use 1
Required
CUR
040
Currency
Max use 1
Required
REF
050
Reference Identification
Max use 1
Required
DTM
150
Delivery Requested
Max use 1
Optional
DTM
150
Requested Ship
Max use 1
Optional
Bill-to-Party
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Example
ISA-01
I01
Authorization Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Authorization Information

00
No Authorization Information Present (No Meaningful Information in I02)
ISA-02
I02
Authorization Information
Required
String (AN)
Min 10Max 10

Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)

ISA-03
I03
Security Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Security Information

00
No Security Information Present (No Meaningful Information in I04)
ISA-04
I04
Security Information
Required
String (AN)
Min 10Max 10

This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)

ISA-05
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-06
I06
Interchange Sender ID
Required
String (AN)
Min 15Max 15

Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element

ISA-07
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-08
I07
Interchange Receiver ID
Required
String (AN)
Min 15Max 15

Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them

ISA-09
I08
Interchange Date
Required
Date (DT)
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
Time (TM)
HHMM format

Time of the interchange

ISA-11
I10
Interchange Control Standards Identifier
Required
Identifier (ID)

Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer

U
U.S. EDI Community of ASC X12, TDCC, and UCS
ISA-12
I11
Interchange Control Version Number
Required
Identifier (ID)

This version number covers the interchange control segments

00401
Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
ISA-13
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested
Required
Identifier (ID)
Min 1Max 1

Code sent by the sender to request an interchange acknowledgment (TA1)

0
No Acknowledgment Requested
1
Interchange Acknowledgment Requested
ISA-15
I14
Usage Indicator
Required
Identifier (ID)
Min 1Max 1

Code to indicate whether data enclosed by this interchange envelope is test, production or information

I
Information
P
Production Data
T
Test Data
ISA-16
I15
Component Element Separator
Required
String (AN)
Min 1Max 1

Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator

>
Component Element Separator

Functional Group Header

RequiredMax use 1

To indicate the beginning of a functional group and to provide control information

Example
GS-01
479
Functional Identifier Code
Required
Identifier (ID)

Code identifying a group of application related transaction sets

PO
Purchase Order (850)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 15

Code identifying party sending transmission; codes agreed to by trading partners

GS-03
124
Application Receiver's Code
Required
String (AN)
Min 2Max 15

Code identifying party receiving transmission. Codes agreed to by trading partners

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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)

GS-06
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
Identifier (ID)
Min 1Max 2

Code used in conjunction with Data Element 480 to identify the issuer of the standard

T
Transportation Data Coordinating Committee (TDCC)
X
Accredited Standards Committee X12
GS-08
480
Version / Release / Industry Identifier Code
Required
String (AN)

Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed

004010
Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997

Heading

ST
010
Heading > ST

Transaction Set Header

RequiredMax use 1

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

Example
ST-01
143
Transaction Set Identifier Code
Required
Identifier (ID)

Code uniquely identifying a Transaction Set

  • 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).
850
Purchase Order
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

BEG
020
Heading > BEG

Beginning Segment for Purchase Order

RequiredMax use 1

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

Usage notes

Example: BEG00NE*MH80312**20150831

Example
BEG-01
353
Transaction Set Purpose Code
Required
Identifier (ID)

Code identifying purpose of transaction set

00
Original
BEG-02
92
Purchase Order Type Code
Required
Identifier (ID)

Code specifying the type of Purchase Order

NE
New Order

Adobe: Shrink Wrap

SA
Stand-alone Order

Adobe: Shrink Wrap

BEG-03
324
Purchase Order Number
Required
String (AN)
Min 1Max 22

Identifying number for Purchase Order assigned by the orderer/purchaser

Usage notes

Adobe: The maximum PO length for Adobe's back office is 20 characters. PO numbers exceeding 20 characters will be truncated by Adobe's back office system to the first 20 characters read.

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • BEG05 is the date assigned by the purchaser to purchase order.
CUR
040
Heading > CUR

Currency

RequiredMax use 1

To specify the currency (dollars, pounds, francs, etc.) used in a transaction

Usage notes

Currency is MANDATORY and must be sent.

Example: CURSEUSD

Example
CUR-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

SE
Selling Party
CUR-02
100
Currency Code
Required
Identifier (ID)
Min 3Max 3

Code (Standard ISO) for country in whose currency the charges are specified

REF
050
Heading > REF

Reference Identification

RequiredMax use >1

To specify identifying information

Usage notes

This reference identification is used by Adobe to communicate the buying party's contract number.

Example: REFCT123456

Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

Usage notes

REF with CT qualifier contains the contract number between the partner originating the PO and Adobe.

CT
Contract Number
REF-02
127
Reference Identification
Required
String (AN)
Min 1Max 30

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

DTM
150
Heading > DTM

Delivery Requested

OptionalMax use 1

To specify pertinent dates and times

Usage notes

Example: DTM00220150901

Example
Variants (all may be used)
DTMRequested Ship
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

002
Delivery Requested
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

DTM
150
Heading > DTM

Requested Ship

OptionalMax use 1

To specify pertinent dates and times

Usage notes

Example: DTM01020150831

Example
Variants (all may be used)
DTMDelivery Requested
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

010
Requested Ship
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

N1 Bill-to-Party
RequiredMax 1
N1
310
Heading > Bill-to-Party > N1

Name

RequiredMax use 1

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

Usage notes

COMPTIA: In this Header position of the Purchase Order document, this segment identifies the destination party. It is encouraged that the trading partners codify all addresses within their systems.

Adobe: ID codes are utilized for location identification. Additions, Enhancements, or Changes to the Bill-To ID will require extra configuration on Adobe’s Part. Please contact your Adobe Business Representative to provide any changes or additions for Bill-To ID.

Example: N1BTBILL TOZZ04332571

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

Usage notes

Adobe: All parties are required to process the purchase order.

BT
Bill-to-Party

This code represents the Bill-To Party.

Required
String (AN)
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Optional
Identifier (ID)

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

91
Assigned by Seller or Seller's Agent
92
Assigned by Buyer or Buyer's Agent
ZZ
Mutually Defined
N1-04
67
Identification Code
Required
String (AN)
Min 2Max 80

Code identifying a party or other code

  • 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.
N1 Bill-to-Party end
N1 Buying Party (Purchaser)
RequiredMax 1
N1
310
Heading > Buying Party (Purchaser) > N1

Name

RequiredMax use 1

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

Usage notes

COMPTIA: In this Header position of the Purchase Order document, this segment identifies the destination party. It is encouraged that the trading partners codify all addresses within their systems.

Adobe: ID codes are utilized for location identification. Additions, Enhancements, or Changes to the Sold-To ID will require extra configuration on Adobe’s Part. Please contact your Adobe Business Representative to provide any changes or additions for Sold-To ID.

Example: N1BYBUYING PARTYZZ04332571

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

Usage notes

Adobe: All parties are required to process the purchase order.

BY
Buying Party (Purchaser)

This code represents the Sold to party.

Required
String (AN)
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Optional
Identifier (ID)

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

91
Assigned by Seller or Seller's Agent
92
Assigned by Buyer or Buyer's Agent
ZZ
Mutually Defined
N1-04
67
Identification Code
Required
String (AN)
Min 2Max 80

Code identifying a party or other code

  • 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.
N1 Buying Party (Purchaser) end
N1 Party to Receive Invoice for Goods or Services
RequiredMax 1
N1
310
Heading > Party to Receive Invoice for Goods or Services > N1

Name

RequiredMax use 1

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

Usage notes

COMPTIA: In this Header position of the Purchase Order document, this segment identifies the destination party. It is encouraged that the trading partners codify all addresses within their systems.

Adobe: ID codes are utilized for location identification. Additions, Enhancements, or Changes to the Payer ID will require extra configuration on Adobe’s Part. Please contact your Adobe Business Representative to provide any changes or additions for Payer ID.

Example: N1POPAYER PARTYZZ04332571

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

Usage notes

All parties are required to process the purchase order.

PO
Party to Receive Invoice for Goods or Services

This code represents the Payer party.

Required
String (AN)
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Optional
Identifier (ID)

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

91
Assigned by Seller or Seller's Agent
92
Assigned by Buyer or Buyer's Agent
ZZ
Mutually Defined
N1-04
67
Identification Code
Required
String (AN)
Min 2Max 80

Code identifying a party or other code

  • 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.
N1 Party to Receive Invoice for Goods or Services end
N1
310
Heading > Ship To > N1

Name

RequiredMax use 1

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

Usage notes

COMPTIA: In this Header position of the Purchase Order document, this segment identifies the destination party. It is encouraged that the trading partners codify all addresses within their systems.

Adobe: ID codes are utilized for location identification. Additions, Enhancements, or Changes to the Ship-To ID will require extra configuration on Adobe’s Part. Please contact your Adobe Business Representative to provide any changes or additions for Ship-To ID.

Example: N1STSHIP TOZZ04332571

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

Usage notes

Adobe: All parties are required to process the purchase order.

ST
Ship To

This code represents the ship-to party.

Required
String (AN)
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Optional
Identifier (ID)

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

91
Assigned by Seller or Seller's Agent
92
Assigned by Buyer or Buyer's Agent
ZZ
Mutually Defined
N1-04
67
Identification Code
Required
String (AN)
Min 2Max 80

Code identifying a party or other code

  • 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.
N2
320
Heading > Ship To > N2

Additional Name Information

OptionalMax use 2

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

Usage notes

COMPTIA: In this Header position of the Purchase Order document, this segment provides additional detail to the N1 segment. It is encouraged that the trading partners codify all addresses within their systems.

Example: N2*M. BUYER

Example
Required
String (AN)
Min 1Max 60

Free-form name

N3
330
Heading > Ship To > N3

Address Information

RequiredMax use 2

To specify the location of the named party

Usage notes

Adobe: Adobe accepts up to 3 iterations of the N3. This first iterations contains address lines 1 and 2 and the second iteration contains address line 3. Only the N301 will be used from the second iteration. If an N302 is sent it will not be mapped.

Example: N3*123 MAIN STREET, SE

Example
N3-01
166
Address Information
Required
String (AN)
Min 1Max 55

Address information

Usage notes

Adobe: The maximum length for Adobe's back office is 35 characters. A street address exceeding 35 characters will be truncated by Adobe's back office system to the first 35 characters read.

N3-02
166
Address Information
Optional
String (AN)
Min 1Max 55

Address information

Usage notes

Adobe: The maximum length for Adobe's back office is 35 characters. A street address exceeding 35 characters will be truncated by Adobe's back office system to the first 35 characters read.

N4
340
Heading > Ship To > N4

Geographic Location

RequiredMax use >1

To specify the geographic place of the named party

Usage notes

COMPTIA: In this Header position of the Purchase Order document, this segment identifies the city, state/province, and postal code of the destination party.

Example: N4CEDAR RAPIDSIA*524032140

Example
N4-01
19
City Name
Required
String (AN)
Min 2Max 30

Free-form text for city name

  • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
N4-02
156
State or Province Code
Required
Identifier (ID)
Min 2Max 2

Code (Standard State/Province) as defined by appropriate government agency

  • N402 is required only if city name (N401) is in the U.S. or Canada.
N4-03
116
Postal Code
Required
Identifier (ID)
Min 3Max 15

Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

N4-04
26
Country Code
Optional
Identifier (ID)
Min 2Max 3

Code identifying the country

Usage notes

COMPTIA: For U.S. and Canadian locations, CompTIA does not recommend the use of N404. For non-U.S./Canadian locations the two-character country code qualifier established by ISO 3166(E/F) should be used.

Adobe: For non-U.S./Canadian locations, the two-character country code qualifier established by ISO 3166(E/F) is MANDATORY.

PER
360
Heading > Ship To > PER

Administrative Communications Contact

OptionalMax use >1

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

Usage notes

COMPTIA: In this Header position of the Purchase Order document, this segment identifies the parties responsible for originating the Purchase Order.

Example: PERICJ SMITHTE8015551234FX8015554321EMjohn@doe.com

Example
If either Communication Number Qualifier (PER-03) or Communication Number (PER-04) is present, then the other is required
If either Communication Number Qualifier (PER-05) or Communication Number (PER-06) is present, then the other is required
PER-01
366
Contact Function Code
Required
Identifier (ID)

Code identifying the major duty or responsibility of the person or group named

IC
Information Contact

Adobe: Used to communicate general contact information.

Required
String (AN)
Min 1Max 60

Free-form name

PER-03
365
Communication Number Qualifier
Optional
Identifier (ID)

Code identifying the type of communication number

TE
Telephone
PER-04
364
Communication Number
Optional
String (AN)
Min 1Max 80

Complete communications number including country or area code when applicable

PER-05
365
Communication Number Qualifier
Optional
Identifier (ID)

Code identifying the type of communication number

FX
Facsimile
PER-06
364
Communication Number
Optional
String (AN)
Min 1Max 80

Complete communications number including country or area code when applicable

PER-07
365
Communication Number Qualifier
Required
Identifier (ID)

Code identifying the type of communication number

EM
Electronic Mail
PER-08
364
Communication Number
Required
String (AN)
Min 1Max 80

Complete communications number including country or area code when applicable

Usage notes

Adobe: Adobe's back office allows for an email address with a MAXIMUM of 58 characters in length.

N1 Ship To end
Heading end

Detail

PO1 Loop
RequiredMax >1
PO1
010
Detail > PO1 Loop > PO1

Baseline Item Data

RequiredMax use 1

To specify basic and most frequently used line item data

  • PO102 is required.
Usage notes

Adobe: There is one PO1 segment for each line item. Product/Service ID's must be sent in the order listed.

Example: PO1111EA588.00CABP12345678MG*65158494

Example
If either Product/Service ID Qualifier (PO1-06) or Product/Service ID (PO1-07) is present, then the other is required
PO1-01
350
Assigned Identification
Optional
String (AN)
Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • PO101 is the line item identification.
Usage notes

Adobe: This element is used to identify the purchase order line item number.

PO1-02
330
Quantity Ordered
Required
Decimal number (R)
Min 1Max 15

Quantity ordered

PO1-03
355
Unit or Basis for Measurement Code
Required
Identifier (ID)

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

EA
Each
PO1-04
212
Unit Price
Required
Decimal number (R)
Min 1Max 15

Price per unit of product, service, commodity, etc.

PO1-05
639
Basis of Unit Price Code
Required
Identifier (ID)

Code identifying the type of unit price for an item

CA
Catalog
PE
Price per Each
PO1-06
235
Product/Service ID Qualifier
Optional
Identifier (ID)

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

  • 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.
BP
Buyer's Part Number
PO1-07
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

PO1-08
235
Product/Service ID Qualifier
Required
Identifier (ID)

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

MG
Manufacturer's Part Number
PO1-09
234
Product/Service ID
Required
String (AN)
Min 1Max 48

Identifying number for a product or service

DTM
210
Detail > PO1 Loop > DTM

Date/Time Reference

OptionalMax use 10

To specify pertinent dates and times

Usage notes

Example: DTM01020150831

Example
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Adobe: Code specifying type of date or time, or both date and time

010
Requested Ship

A requested ship date provided at this detail level will override the date provided in the DTM segment at the header level.

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

PO1 Loop end
Detail end

Summary

CTT Loop
RequiredMax >1
CTT
010
Summary > CTT Loop > CTT

Transaction Totals

RequiredMax use 1

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

  • 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.
Usage notes

Example: CTT*1

Example
CTT-01
354
Number of Line Items
Required
Numeric (N0)
Min 1Max 6

Total number of line items in the transaction set

AMT
020
Summary > CTT Loop > AMT

Monetary Amount

OptionalMax use 1

To indicate the total monetary amount

  • If AMT is used in the summary area, then AMT01 will = TT and AMT02 will indicate total transaction amount as calculated by the sender.
Usage notes

Adobe: All monetary amounts must be provided in USD. This segment will be used to verify that the total extended values of the line items match this total amount. If there is any discrepancy our translator will reject the 850 document.

Example : AMTTT6468

Example
AMT-01
522
Amount Qualifier Code
Required
Identifier (ID)

Code to qualify amount

TT
Total Transaction Amount
AMT-02
782
Monetary Amount
Required
Decimal number (R)
Min 1Max 15

Monetary amount

CTT Loop end
SE
030
Summary > SE

Transaction Set Trailer

RequiredMax use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Example
SE-01
96
Number of Included Segments
Required
Numeric (N0)
Min 1Max 10

Total number of segments included in a transaction set including ST and SE segments

SE-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Summary end

Functional Group Trailer

RequiredMax use 1

To indicate the end of a functional group and to provide control information

Example
GE-01
97
Number of Transaction Sets Included
Required
Numeric (N0)
Min 1Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

GE-02
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

Interchange Control Trailer

RequiredMax use 1

To define the end of an interchange of zero or more functional groups and interchange-related control segments

Example
IEA-01
I16
Number of Included Functional Groups
Required
Numeric (N0)
Min 1Max 5

A count of the number of functional groups included in an interchange

IEA-02
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

EDI Samples

sample

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *231030*0231*U*00401*000000001*0*T*>
GS*PO*SENDERGS*RECEIVERGS*20231030*023108*000000001*X*004010
ST*850*130581
BEG*00*NE*MH80312**20150831
CUR*SE*USD
REF*CT*123456
DTM*010*20150831
DTM*002*20150901
N1*BY*BUYING PARTY*ZZ*04332571
N1*PO*PAYER PARTY*ZZ*04332571
N1*BT*BILL TO*ZZ*04332571
N1*ST*SHIP TO*ZZ*04332571
N2*M. BUYER
N3*123 MAIN STREET, SE
N4*CEDAR RAPIDS*IA*524032140
PER*IC*J SMITH*TE*8015551234*FX*8015554321*EM*john@doe.com
PO1*1*11*EA*588.00*CA*BP*12345678*MG*65158494
DTM*010*20150831
CTT*1
AMT*TT*6468
SE*19*130581
GE*1*000000001
IEA*1*000000001

Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.