GameStop
/
Purchase Order
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from GameStop. Contact GameStop for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
GameStop

X12 850 Purchase Order

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
    View the latest version of this implementation guide as an interactive webpage
    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
    REF
    050
    Reference Identification
    Max use 1
    Required
    FOB
    080
    F.O.B. Related Instructions
    Max use 1
    Optional
    CSH
    110
    Sales Requirements
    Max use 5
    Optional
    DTM
    150
    Cancel After
    Max use 10
    Optional
    DTM
    150
    Requested Ship Date
    Max use 10
    Optional
    TD5
    240
    Carrier Details (Routing Sequence/Transit Time)
    Max use 12
    Optional
    N9 Loop
    Bill To
    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

    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
    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

    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
    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
    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
    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
    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
    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
    YYMMDD format

    Date of the interchange

    ISA-10
    I09
    Interchange Time
    Required
    HHMM format

    Time of the interchange

    ISA-11
    I10
    Interchange Control Standards Identifier
    Required

    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

    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
    Min 9Max 9

    A control number assigned by the interchange sender

    ISA-14
    I13
    Acknowledgment Requested
    Required
    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
    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
    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

    Code identifying a group of application related transaction sets

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

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

    GS-03
    124
    Application Receiver's Code
    Required
    Min 2Max 15

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

    GS-04
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    GS-05
    337
    Time
    Required
    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
    Min 1Max 9

    Assigned number originated and maintained by the sender

    GS-07
    455
    Responsible Agency Code
    Required
    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

    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

    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

    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
    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

    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

    Sample BEG Segment

    ---

    BEG00SA*3131986**20110508

    Example
    BEG-01
    353
    Transaction Set Purpose Code
    Required

    Code identifying purpose of transaction set

    00
    Original
    BEG-02
    92
    Purchase Order Type Code
    Required

    Code specifying the type of Purchase Order

    SA
    Stand-alone Order
    BEG-03
    324
    Purchase Order Number
    Required
    Min 1Max 22

    Identifying number for Purchase Order assigned by the orderer/purchaser

    BEG-04
    328
    Release Number
    Optional
    Min 1Max 30

    Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction

    BEG-05
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • BEG05 is the date assigned by the purchaser to purchase order.
    Usage notes

    PO create date

    REF
    050

    Reference Identification

    RequiredMax use >1

    To specify identifying information

    Usage notes

    Sample REF Segments

    ---

    REFVR1713

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    VR
    Vendor ID Number
    REF-02
    127
    Reference Identification
    Required
    Min 1Max 30

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

    Usage notes

    The assigned vendor number

    FOB
    080

    F.O.B. Related Instructions

    OptionalMax use >1

    To specify transportation instructions relating to shipment

    Usage notes

    Sample REF Segments

    ---

    FOBPODE

    Example
    FOB-01
    146
    Shipment Method of Payment
    Required

    Code identifying payment terms for transportation charges

    • FOB01 indicates which party will pay the carrier.
    PO
    Prepaid Only
    FOB-02
    309
    Location Qualifier
    Required

    Code identifying type of location

    • FOB02 is the code specifying transportation responsibility location.
    DE
    Destination (Shipping)
    CSH
    110

    Sales Requirements

    OptionalMax use 5

    To specify general conditions or requirements of the sale

    Usage notes

    Sample CSH Segments

    ---

    CSHSC
    CSH
    BK

    Example
    If Action Code (CSH-02) is present, then Amount (CSH-03) is required
    CSH-01
    563
    Sales Requirement Code
    Required

    Code to identify a specific requirement or agreement of sale

    BK
    Ship Partial - Balance Back Order
    SC
    Ship Complete
    CSH-02
    306
    Action Code
    Optional
    Min 1Max 2

    Code indicating type of action

    CSH-03
    610
    Amount
    Optional
    Min 1Max 15

    Monetary amount

    • CSH03 is the maximum monetary amount value which the order must not exceed.
    CSH-04
    508
    Account Number
    Optional
    Min 1Max 35

    Account number assigned

    • CSH04 is the account number to which the purchase amount is charged.
    CSH-05
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • CSH05 is the date specified by the sender to be shown on the invoice.
    DTM
    150

    Cancel After

    OptionalMax use 10

    To specify pertinent dates and times

    Usage notes

    Sample DTM Segment

    ---

    DTM00120110531

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

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

    001
    Cancel After
    DTM-02
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    DTM
    150

    Requested Ship Date

    OptionalMax use 10

    To specify pertinent dates and times

    Usage notes

    Sample DTM Segment

    ---

    DTM01020110508

    Example
    Variants (all may be used)
    DTMCancel After
    DTM-01
    374
    Date/Time Qualifier
    Required

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

    010
    Requested Ship
    DTM-02
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    TD5
    240

    Carrier Details (Routing Sequence/Transit Time)

    OptionalMax use 12

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

    Usage notes

    Sample TD5 Segment

    ---

    TD52*UPSNNS*******G2

    Example
    TD5-02
    66
    Identification Code Qualifier
    Required

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

    • When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier within the movement, use TD502 to identify the party responsible for defining the routing sequence, and use TD503 to identify the actual routing sequence, specified by the party identified in TD502.
    2
    Standard Carrier Alpha Code (SCAC)
    TD5-03
    67
    Identification Code
    Required

    Code identifying a party or other code

    FDE
    Federal Express
    UPSN
    United Parcel Service
    USPS
    United States Postal Service
    TD5-05
    387
    Routing
    Required
    Min 1Max 35

    Free-form description of the routing or requested routing for shipment, or the originating carrier's identity

    TD5-12
    284
    Service Level Code
    Required

    Code indicating the level of transportation service or the billing service offered by the transportation carrier

    3D
    Three Day Service
    CG
    Ground
    G2
    Standard Service
    ND
    Next Day Air
    SC
    Second Day Air
    N9 Loop
    RequiredMax >1
    N9
    295

    Reference Identification

    RequiredMax use 1

    To transmit identifying information as specified by the Reference Identification Qualifier

    Usage notes

    Sample N9 Segment

    ---

    N9L1Notes

    Example
    N9-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    L1
    Letters or Notes
    N9-02
    127
    Reference Identification
    Required

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

    Notes
    Notes
    MSG
    300

    Message Text

    OptionalMax use 1000

    To provide a free-form format that allows the transmission of text information

    Usage notes

    Sample MSG Segment

    Note: If the message is greater than 264 characters, the MSG segment will repeat as many times as needed to display the entire message.

    ---

    MSGVen comments 1 (SAY 6/26/2012) Ven comments 2
    MSG
    Ven comments 3 (SAY 6/26/2012) Ven comments 4

    Example
    MSG-01
    933
    Free-Form Message Text
    Required
    Min 1Max 264

    Free-form message text

    N1 Bill To
    OptionalMax >1
    Usage notes

    Multiple occurrences of the N1 though N4 may be sent.

    Sample N1 through N4 Segments

    ---

    N1BT Accounts Payable
    N3789 Main Street
    N4
    MinneapolisMN55440*USA

    Variants (all may be used)
    N1Ship To
    N1
    310

    Name

    RequiredMax use 1

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

    Usage notes

    Sample N1

    ---

    N1BT Accounts Payable

    Example
    At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
    If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
    N1-01
    98
    Entity Identifier Code
    Required

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

    BT
    Bill-to-Party
    N1-02
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    N1-03
    66
    Identification Code Qualifier
    Optional

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

    92
    Assigned by Buyer or Buyer's Agent
    N1-04
    67
    Identification Code
    Optional
    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

    Additional Name Information

    OptionalMax use 2

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

    Usage notes

    Sample N2 Segment

    ---

    N2*Attn John Smith

    Example
    N2-01
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    Usage notes

    Used to provide name such as Attention or Company

    N3
    330

    Address Information

    RequiredMax use 2

    To specify the location of the named party

    Usage notes

    Sample N3

    ---

    N3*789 Main Street

    Example
    N3-01
    166
    Address Information
    Required
    Min 1Max 55

    Address information

    N3-02
    166
    Address Information
    Optional
    Min 1Max 55

    Address information

    N4
    340

    Geographic Location

    RequiredMax use >1

    To specify the geographic place of the named party

    Usage notes

    Sample N4

    ---

    N4MinneapolisMN55440USA

    Example
    N4-01
    19
    City Name
    Required
    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
    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
    Min 3Max 15

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

    N4-04
    26
    Country Code
    Optional
    Min 2Max 3

    Code identifying the country

    PER
    360

    Administrative Communications Contact

    OptionalMax use >1

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

    Usage notes

    Sample PER Segment

    ---

    PERCNCONTACT NAME**TE826 803-9087

    Example
    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

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

    CN
    General Contact
    PER-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    PER-03
    365
    Communication Number Qualifier
    Required

    Code identifying the type of communication number

    FX
    Facsimile
    TE
    Telephone
    PER-04
    364
    Communication Number
    Required
    Min 1Max 80

    Complete communications number including country or area code when applicable

    PER-05
    365
    Communication Number Qualifier
    Optional

    Code identifying the type of communication number

    FX
    Facsimile
    TE
    Telephone
    PER-06
    364
    Communication Number
    Optional
    Min 1Max 80

    Complete communications number including country or area code when applicable

    N1 Ship To
    RequiredMax >1
    Usage notes

    Multiple occurrences of the N1 though N4 may be sent.

    Sample N1 through N4 Segments

    ---

    N1STJane Doe92D20
    N3123 Some StreetApt 1
    N4AnyplaceMN55555USA

    Variants (all may be used)
    N1Bill To
    N1
    310

    Name

    RequiredMax use 1

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

    Usage notes

    Sample N1

    ---

    N1STJane Doe92D20

    Example
    At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
    If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
    N1-01
    98
    Entity Identifier Code
    Required

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

    ST
    Ship To
    N1-02
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    N1-03
    66
    Identification Code Qualifier
    Optional

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

    92
    Assigned by Buyer or Buyer's Agent
    N1-04
    67
    Identification Code
    Optional
    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

    Additional Name Information

    OptionalMax use 2

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

    Usage notes

    Sample N2 Segment

    ---

    N2*Attn John Smith

    Example
    N2-01
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    Usage notes

    Used to provide name such as Attention or Company

    N3
    330

    Address Information

    RequiredMax use 2

    To specify the location of the named party

    Usage notes

    Sample N3

    ---

    N3123 Some StreetApt 1

    Example
    N3-01
    166
    Address Information
    Required
    Min 1Max 55

    Address information

    N3-02
    166
    Address Information
    Optional
    Min 1Max 55

    Address information

    N4
    340

    Geographic Location

    RequiredMax use >1

    To specify the geographic place of the named party

    Usage notes

    Sample N4

    ---

    N4AnyplaceMN55555USA

    Example
    N4-01
    19
    City Name
    Required
    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
    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
    Min 3Max 15

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

    N4-04
    26
    Country Code
    Optional
    Min 2Max 3

    Code identifying the country

    PER
    360

    Administrative Communications Contact

    OptionalMax use >1

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

    Usage notes

    Sample PER Segment

    ---

    PERCNCONTACT NAME**TE826 803-9087

    Example
    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

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

    CN
    General Contact
    PER-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    PER-03
    365
    Communication Number Qualifier
    Required

    Code identifying the type of communication number

    FX
    Facsimile
    TE
    Telephone
    PER-04
    364
    Communication Number
    Required
    Min 1Max 80

    Complete communications number including country or area code when applicable

    PER-05
    365
    Communication Number Qualifier
    Optional

    Code identifying the type of communication number

    FX
    Facsimile
    TE
    Telephone
    PER-06
    364
    Communication Number
    Optional
    Min 1Max 80

    Complete communications number including country or area code when applicable

    Detail

    PO1 Loop
    RequiredMax >1
    PO1
    010

    Baseline Item Data

    RequiredMax use 1

    To specify basic and most frequently used line item data

    • PO102 is required.
    Usage notes

    Sample PO1 Segment

    ---

    PO1011000EA19.45PEVC9876543UP102398765423SK*123456

    Example
    If Basis of Unit Price Code (PO1-05) is present, then Unit Price (PO1-04) is required
    If either Product/Service ID Qualifier (PO1-10) or Product/Service ID (PO1-11) is present, then the other is required
    If either Product/Service ID Qualifier (PO1-08) or Product/Service ID (PO1-09) is present, then the other is required
    PO1-01
    350
    Assigned Identification
    Required
    Min 1Max 20

    Alphanumeric characters assigned for differentiation within a transaction set

    • PO101 is the line item identification.
    Usage notes

    Order Line Number

    PO1-02
    330
    Quantity Ordered
    Required
    Min 1Max 15

    Quantity ordered

    PO1-03
    355
    Unit or Basis for Measurement Code
    Required

    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
    Min 1Max 15

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

    PO1-05
    639
    Basis of Unit Price Code
    Optional

    Code identifying the type of unit price for an item

    PE
    Price per Each
    PO1-06
    235
    Product/Service ID Qualifier
    Required

    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.
    SK
    Stock Keeping Unit (SKU)
    UP
    U.P.C. Consumer Package Code (1-5-5-1)
    VC
    Vendor's (Seller's) Catalog Number
    PO1-07
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    Usage notes

    When PO106 = SK, this value is the buyers SKU
    When PO106 = IN, this value is the Buyer’s item ID
    When PO106 =VP, this value is the vendors Part number

    PO1-08
    235
    Product/Service ID Qualifier
    Optional

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

    SK
    Stock Keeping Unit (SKU)
    UP
    U.P.C. Consumer Package Code (1-5-5-1)
    VC
    Vendor's (Seller's) Catalog Number
    PO1-09
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    Usage notes

    When PO108 = SK, this value is the Vendor SKU
    When PO108 = IN, this value is the Buyer’s item ID
    When PO108 =VP, this value is the vendors Part number

    PO1-10
    235
    Product/Service ID Qualifier
    Optional

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

    SK
    Stock Keeping Unit (SKU)
    UP
    U.P.C. Consumer Package Code (1-5-5-1)
    VC
    Vendor's (Seller's) Catalog Number
    PO1-11
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    Usage notes

    When PO110 = SK, this value is the Vendor SKU
    When PO110 = IN, this value is the Buyer’s item ID
    When PO110 =VP, this value is the vendors Part number

    PID Loop
    RequiredMax >1
    PID
    050

    Product/Item Description

    RequiredMax use 1

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

    Usage notes

    Sample PID Segment

    ---

    PIDF08***Description

    Example
    PID-01
    349
    Item Description Type
    Required

    Code indicating the format of a description

    • 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.
    F
    Free-form
    PID-02
    750
    Product/Process Characteristic Code
    Optional

    Code identifying the general class of a product or process characteristic

    08
    Product
    PID-05
    352
    Description
    Required
    Min 1Max 80

    A free-form description to clarify the related data elements and their content

    Summary

    CTT Loop
    RequiredMax >1
    CTT
    010

    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

    Sample CTT Segment

    ---

    CTT*1

    Example
    CTT-01
    354
    Number of Line Items
    Required
    Min 1Max 6

    Total number of line items in the transaction set

    SE
    030

    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
    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
    Min 4Max 9

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

    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
    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
    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
    Min 1Max 5

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

    IEA-02
    I12
    Interchange Control Number
    Required
    Min 9Max 9

    A control number assigned by the interchange sender

    EDI Samples

    Sample

    ST*850*0001
    BEG*00*SA*123456789**20110508
    REF*VR*12345
    DTM*010*20120101
    TD5**2*UPSN**NS*******G2
    N9*L1*Notes
    MSG*Ven comments 1 (SAY 6/26/2012) Ven comments 2 (SAY 6/26/2012) Ven Comments 3 (SAY 6/26/2012) Ven comments 4 (SAY 6/26/2012) Ven comments 5 (SAY 6/26/2012) Ven Comments 6 (SAY 6/26/2012) Ven comments 7 (SAY 6/26/2012)
    MSG*Ven comments8 (SAY 6/26/2012) Ven comments 9
    N1*ST*Jane Doe
    N3*123 Some Street*Apt 1
    N4*Anyplace*MN*55555*USA
    PER*CN*CONTACT NAME*TE*826 803-9087
    PO1*01*1000*EA*19.45*PE*VC*9876543*UP*102398765423*SK*123456
    PID*F*08***Description
    PO1*02*1500*EA*9.99*PE*VC*9876542*UP*1012354754424*SK*123457
    PID*F*08***Item Description
    CTT*2
    SE*20*0001

    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.