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

X12 855 Purchase Order Acknowledgment

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Acknowledgment Transaction Set (855) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to a seller's acknowledgment of a buyer's purchase order. This transaction set can also be used as notification of a vendor generated order. This usage advises a buyer that a vendor has or will ship merchandise as prearranged in their partnership.

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
    BAK
    020
    Beginning Segment for Purchase Order Acknowledgment
    Max use 1
    Required
    REF
    050
    Internal Customer Number
    Max use 1
    Optional
    REF
    050
    Internal Vendor Number
    Max use 1
    Required
    REF
    050
    Special Instructions Number
    Max use 1
    Optional
    PER
    060
    Administrative Communications Contact
    Max use 3
    Optional
    Ship From
    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

    PR
    Purchase Order Acknowledgement (855)
    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).
    855
    Purchase Order Acknowledgment
    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

    BAK
    020

    Beginning Segment for Purchase Order Acknowledgment

    RequiredMax use 1

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

    Example
    BAK-01
    353
    Transaction Set Purpose Code
    Required

    Code identifying purpose of transaction set

    00
    Original
    04
    Change
    BAK-02
    587
    Acknowledgment Type
    Required

    Code specifying the type of acknowledgment

    AC
    Acknowledge - With Detail and Change
    AD
    Acknowledge - With Detail, No Change
    RD
    Reject with Detail
    BAK-03
    324
    Purchase Order Number
    Required
    Min 1Max 22

    Identifying number for Purchase Order assigned by the orderer/purchaser

    BAK-04
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • BAK04 is the date assigned by the purchaser to purchase order.
    BAK-08
    127
    Reference Identification
    Optional
    Min 1Max 30

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

    • BAK08 is the seller's order number.
    Usage notes

    Grainger Sales Order Number (This segment is populated in BEG04 of the 850 for Third Party Orders only).

    REF
    050

    Internal Customer Number

    OptionalMax use >1

    To specify identifying information

    Example
    Variants (all may be used)
    REFInternal Vendor NumberREFSpecial Instructions Number
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    Usage notes

    Third Party PO Only

    IT
    Internal Customer Number

    Grainger Customer Purchase Order Number

    REF-02
    127
    Reference Identification
    Optional
    Min 1Max 30

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

    REF
    050

    Internal Vendor Number

    RequiredMax use >1

    To specify identifying information

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    IA
    Internal Vendor Number

    Grainger Internal Supplier Number

    REF-02
    127
    Reference Identification
    Optional
    Min 1Max 30

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

    REF
    050

    Special Instructions Number

    OptionalMax use >1

    To specify identifying information

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    Usage notes

    Third Party PO Only

    KD
    Special Instructions Number

    Grainger Brand Organization Code Value

    REF-02
    127
    Reference Identification
    Optional
    Min 1Max 30

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

    PER
    060

    Administrative Communications Contact

    OptionalMax use 3

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

    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
    If either Communication Number Qualifier (PER-07) or Communication Number (PER-08) 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

    BD
    Buyer Name or Department

    Grainger Buyer Name (Mandatory)

    CN
    General Contact

    Grainger Customer Contact (Optional)

    DI
    Delivery Instructions Contact

    Grainger Customer Delivery Contact (Optional)

    PER-02
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    PER-03
    365
    Communication Number Qualifier
    Optional

    Code identifying the type of communication number

    TE
    Telephone
    PER-04
    364
    Communication Number
    Optional
    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
    PER-06
    364
    Communication Number
    Optional
    Min 1Max 80

    Complete communications number including country or area code when applicable

    PER-07
    365
    Communication Number Qualifier
    Optional

    Code identifying the type of communication number

    EM
    Electronic Mail
    PER-08
    364
    Communication Number
    Optional
    Min 1Max 80

    Complete communications number including country or area code when applicable

    N1 Ship From
    RequiredMax >1
    Variants (all may be used)
    N1Ship ToN1Vendor
    N1
    300

    Name

    RequiredMax use 1

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

    Example
    N1-01
    98
    Entity Identifier Code
    Required

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

    SF
    Ship From
    N1-02
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    N2
    310

    Additional Name Information

    OptionalMax use 2

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

    Example
    N2-01
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    N3
    320

    Address Information

    RequiredMax use 2

    To specify the location of the named party

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

    Address information

    N4
    330

    Geographic Location

    RequiredMax use 1

    To specify the geographic place of the named party

    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
    Required
    Min 2Max 3

    Code identifying the country

    N1 Ship To
    RequiredMax >1
    Variants (all may be used)
    N1Ship FromN1Vendor
    N1
    300

    Name

    RequiredMax use 1

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

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

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

    9
    D-U-N-S+4, D-U-N-S Number with Four Character Suffix
    N1-04
    67
    Identification Code
    Required
    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.
    Usage notes

    Grainger plant code.

    Refer to Grainger plant location spreadsheet for a listing of all Grainger plant locations.

    N2
    310

    Additional Name Information

    OptionalMax use 2

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

    Example
    N2-01
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    N3
    320

    Address Information

    RequiredMax use 2

    To specify the location of the named party

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

    Address information

    N4
    330

    Geographic Location

    RequiredMax use 1

    To specify the geographic place of the named party

    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
    Required
    Min 2Max 3

    Code identifying the country

    N1 Vendor
    RequiredMax >1
    Variants (all may be used)
    N1Ship FromN1Ship To
    N1
    300

    Name

    RequiredMax use 1

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

    Example
    N1-01
    98
    Entity Identifier Code
    Required

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

    VN
    Vendor
    N1-02
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    N2
    310

    Additional Name Information

    OptionalMax use 2

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

    Example
    N2-01
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    N3
    320

    Address Information

    OptionalMax use 2

    To specify the location of the named party

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

    Address information

    N4
    330

    Geographic Location

    OptionalMax use 1

    To specify the geographic place of the named party

    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
    Required
    Min 2Max 3

    Code identifying the country

    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

    It is Grainger’s expectation any PO1 data generated to the supplier via the EDI 850 PO will be returned in this segment.

    Example
    If either Product/Service ID Qualifier (PO1-08) or Product/Service ID (PO1-09) is present, then the other 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-12) or Product/Service ID (PO1-13) is present, then the other is required
    If either Product/Service ID Qualifier (PO1-14) or Product/Service ID (PO1-15) is present, then the other is required
    If either Product/Service ID Qualifier (PO1-16) or Product/Service ID (PO1-17) is present, then the other is required
    If either Product/Service ID Qualifier (PO1-18) or Product/Service ID (PO1-19) 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.
    PO1-02
    330
    Quantity Ordered
    Required
    Min 1Max 15

    Quantity ordered

    PO1-03
    355
    Unit or Basis for Measurement Code
    Required
    Min 2Max 2

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

    PO1-04
    212
    Unit Price
    Required
    Min 1Max 15

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

    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.
    CB
    Buyer's Catalog Number

    Grainger Stock Number

    Grainger Sourcing (FindMRO) Stock Number

    PO1-07
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    PO1-08
    235
    Product/Service ID Qualifier
    Optional

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

    VN
    Vendor's (Seller's) Item Number
    PO1-09
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    PO1-10
    235
    Product/Service ID Qualifier
    Optional

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

    CP
    Carry-over Part Number

    Grainger Customer Material Number

    PO1-11
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    PO1-12
    235
    Product/Service ID Qualifier
    Optional

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

    PL
    Purchaser's Order Line Number

    Grainger Customer PO Line Number

    PO1-13
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    PO1-14
    235
    Product/Service ID Qualifier
    Optional

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

    MN
    Model Number

    Manufacturer Model Number

    PO1-15
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    PO1-16
    235
    Product/Service ID Qualifier
    Optional

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

    MG
    Manufacturer's Part Number
    PO1-17
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    PO1-18
    235
    Product/Service ID Qualifier
    Optional

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

    Usage notes

    This segment is a place holder for future use by Grainger and its suppliers.

    UD
    U.P.C./EAN Consumer Package Code (2-5-5)
    PO1-19
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    Usage notes

    This segment is a place holder for future use by Grainger and its suppliers.

    PID Loop
    RequiredMax >1
    PID
    050

    Product/Item Description

    RequiredMax use 1

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

    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-05
    352
    Description
    Required
    Min 1Max 80

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

    FOB
    180

    F.O.B. Related Instructions

    RequiredMax use >1

    To specify transportation instructions relating to shipment

    Example
    If Description (FOB-03) is present, then Location Qualifier (FOB-02) is required
    FOB-01
    146
    Shipment Method of Payment
    Required

    Code identifying payment terms for transportation charges

    • FOB01 indicates which party will pay the carrier.
    CC
    Collect

    Collect with exception.

    Collect and allowed.

    Consignee collect.

    PA
    Advance Prepaid

    Prepaid and add.

    PO
    Prepaid Only

    Prepaid with exception.

    TP
    Third Party Pay
    FOB-02
    309
    Location Qualifier
    Optional

    Code identifying type of location

    • FOB02 is the code specifying transportation responsibility location.
    DE
    Destination (Shipping)
    OA
    Origin (After Loading on Equipment)
    FOB-03
    352
    Description
    Optional
    Min 1Max 80

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

    FOB-05
    335
    Transportation Terms Code
    Optional

    Code identifying the trade terms which apply to the shipment transportation responsibility

    FOB
    Free on Board
    TD5
    240

    Carrier Details (Routing Sequence/Transit Time)

    OptionalMax use 12

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

    Example
    If Identification Code Qualifier (TD5-02) is present, then Identification Code (TD5-03) is required
    TD5-02
    66
    Identification Code Qualifier
    Optional

    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.
    ZZ
    Mutually Defined

    Carrier code qualifier.

    TD5-03
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    TD5-05
    387
    Routing
    Optional
    Min 1Max 35

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

    TD4
    260

    Carrier Details (Special Handling, or Hazardous Materials, or Both)

    OptionalMax use 5

    To specify transportation special handling requirements, or hazardous materials information, or both

    Example
    TD4-01
    152
    Special Handling Code
    Optional

    Code specifying special transportation handling instructions

    ZZZ
    Mutually Defined
    TD4-04
    352
    Description
    Optional
    Min 1Max 80

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

    Usage notes

    Delivery related specific instructions.

    ACK Loop
    RequiredMax >1
    ACK
    270

    Line Item Acknowledgment

    RequiredMax use 1

    To acknowledge the ordered quantities and specify the ready date for a specific line item

    Example
    If either Quantity (ACK-02) or Unit or Basis for Measurement Code (ACK-03) is present, then the other is required
    ACK-01
    668
    Line Item Status Code
    Required

    Code specifying the action taken by the seller on a line item requested by the buyer

    AA
    Item Accepted - Order Forwarded to Alternate Supplier Location
    AC
    Item Accepted and Shipped
    AR
    Item Accepted and Released for Shipment
    BP
    Item Accepted - Partial Shipment, Balance Backordered

    (ACK02 = Quantity Available)

    DR
    Item Accepted - Date Rescheduled
    IA
    Item Accepted
    IB
    Item Backordered
    IE
    Item Accepted, Price Pending
    IF
    Item on Hold, Incomplete Description
    IP
    Item Accepted - Price Changed
    IQ
    Item Accepted - Quantity Changed
    R1
    Item Rejected, Not a Contract Item
    R2
    Item Rejected, Invalid Item Product Number
    R3
    Item Rejected, Invalid Unit of Issue
    R4
    Item Rejected, Contract Item not Available
    R7
    Item Rejected, Reorder Item as a Drop Shipment
    SP
    Item Accepted - Schedule Date Pending
    ACK-02
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    ACK-03
    355
    Unit or Basis for Measurement Code
    Optional

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

    EA
    Each
    SCH Loop
    RequiredMax >1
    SCH
    310

    Line Item Schedule

    RequiredMax use 1

    To specify the data for scheduling a specific line-item

    • The SCH segment is used to specify various quantities of items ordered that are to be scheduled. When this segment is used the unit of measurement code (SCH02) should always be identical to the unit of measurement code in the associated PO1 segment (PO103) and the sum of values of quantity (SCH01) should always equal the quantity ordered (PO102) in the PO1 segment.
    Example
    SCH-01
    380
    Quantity
    Required
    Min 1Max 15

    Numeric value of quantity

    SCH-02
    355
    Unit or Basis for Measurement Code
    Required
    Min 2Max 2

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

    SCH-05
    374
    Date/Time Qualifier
    Required

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

    • SCH05 specifies the interpretation to be used for SCH06 and SCH07.
    068
    Current Schedule Ship
    SCH-06
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    N9 Loop
    RequiredMax >1
    N9
    350

    Reference Identification

    RequiredMax use 1

    To transmit identifying information as specified by the Reference Identification Qualifier

    Example
    N9-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    L1
    Letters or Notes
    N9-03
    369
    Free-form Description
    Required
    Min 1Max 45

    Free-form descriptive text

    Usage notes

    Refer to MSG segment.

    MSG
    360

    Message Text

    RequiredMax use 1000

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

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

    Free-form message text

    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.
    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*855*0004~
    BAK*00*AC*4610000000*20110725****1134256352~
    REF*IA*20001616~
    REF*KD*20~
    REF*IT*PO12345~
    PER*BD*GRAINGER BUYER NAME*TE*847-566-7711*FX*847-566-5053*EM*GRAINGERBUYER@GRAINGER.COM~
    PER*CN*GRAINGER CUSTOMER NAME*TE*CUSTOMER PHO*FX*CUSTOMER FAX NUMBER*EM*GRAINGERCUSTOMER@CUSTOMER.COM~
    PER*DI*GRAINGER DELIVERY*TE*CUST DELIVRY*FX*CUSTOMER DELIVERY FAX NUMBER*EM*GRAINGERCUSTOMERDELIVERYCONTACT@CUSTOMER.COM~
    N1*VN*W.W. GRAINGER~
    N1*SF*SUPPLIER COMPANY~
    N2*ATTN: DELIVERY~
    N3*100 MAIN STREET~
    N4*CHICAGO*IL*60601*US~
    N1*ST*ABC COMPANY*92*TPSO~
    N2*TOOL CRIB~
    N3*157 WEST 57TH STREET~
    N4*COLUMBUS*OH*43017~US
    PO1*1*1*EA*5.5**VP*GRAINGER PART NO*VN*SUPPLIER ITEM NO*CP*CUSTOMER MATERIAL NO*PL*GRAINGER CUSTOMER LINE ITEM NO*MN*MFR MODEL NO*MG*NFR PART NO~
    PID*F****FREEFORM DESCRIPTION1~
    PID*F****FREEFORM DESCRIPTION2~
    FOB*TP*DE*THIRD PARTY PAY ACCOUNT NUMBER**FOB~
    TD5**ZZ*GRAINGER CARRIER CODE**CODE DESCRIPTION~
    TD4*ZZZ***DELIVERY INSTRUCTIONS~
    ACK*IP*1*EA*~
    SCH*1*EA***068*20110809~
    MSG*INFORMATION AS TO WHY AN ITEM WAS CHANGED, MODIFIED, ETC. OTHER NOTES BY SUPPLIER~
    MSG*THIS IS MESSAGE LINE NUMBER 2~
    CTT*1~
    SE*27*0004~

    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.