Dick's Sporting Goods
/
Purchase Order (Rithum)
  • Specification
  • EDI Inspector
Import guide into your account
Dick's Sporting Goods logo

X12 850 Purchase Order (Rithum)

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 samples
  • None included
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/dicks/purchase-order-rithum/01HV1ZEW88KHE0WANMY86CKNV6
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
SAC Loop
DTM
150
Date/Time Reference
Max use 10
Optional
TD5
240
Carrier Details (Routing Sequence/Transit Time)
Max use 12
Required
N9 Loop
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

GS-04
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

GS-05
337
Time
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

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

RE
Reorder
SA
Stand-alone Order
BEG-03
324
Purchase Order Number
Required
String (AN)
Min 1Max 22

Identifying number for Purchase Order assigned by the orderer/purchaser

Usage notes

This element contains the DSG purchase order number. This element is required to be included in the packing slip if you are creating your own.

BEG-05
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • BEG05 is the date assigned by the purchaser to purchase order.
REF
050
Heading > REF

Reference Identification

RequiredMax use >1

To specify identifying information

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

Code qualifying the Reference Identification

Usage notes

The IA and X9 qualifiers are always used.

7U: Secondary ID for the customer's order - ERP number

CO: This qualifier indicates that the REF02 contains the customer order number.

IA: This qualifier indicates that the REF02 contains the DICK'S Sporting Goods vendor ID for the party receiving this purchase order.

IT: Customer's membership ID w/merchant

PQ: Data specific to customer payment method that is described in REF 9V. This data is provided in the REF03. Example,If REF02"9V"qualified ="CC", REF 03 could be "Visa", "Discover", etc).

X9: Rithum internal ID

7U
Related Transaction Reference Number
CO
Customer Order Number
IA
Internal Vendor Number
IT
Internal Customer Number
PQ
Payee Identification
X9
Internal Control 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

Usage notes

The REF02 CO qualified element is required to be included in the packing slip if you are creating your own

REF-03
352
Description
Optional
String (AN)
Min 1Max 80

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

SAC Loop
OptionalMax >1
SAC
120
Heading > SAC Loop > SAC

Service, Promotion, Allowance, or Charge Information

RequiredMax use 1

To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge

Example
SAC-01
248
Allowance or Charge Indicator
Required
Identifier (ID)

Code which indicates an allowance or charge for the service specified

  • If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.
Usage notes

Special processing/handling information

S
Service
SAC-02
1300
Service, Promotion, Allowance, or Charge Code
Required
Identifier (ID)

Code identifying the service, promotion, allowance, or charge

Usage notes

Gift processing

H151
Special Services
SAC-15
352
Description
Optional
String (AN)
Min 1Max 80

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

Usage notes

If SAC-02 = H151 then gift message.

SAC Loop end
DTM
150
Heading > DTM

Date/Time Reference

OptionalMax use 10

To specify pertinent dates and times

Example
At least one of Date (DTM-02) or Time (DTM-03) is required
If Time Code (DTM-04) is present, then Time (DTM-03) is required
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

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

004
Purchase Order
006
Sold
DTM-02
373
Date
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Usage notes

Depending on the qualifier used this element contains the corresponding value.

DTM-03
337
Time
Optional
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)

DTM-04
623
Time Code
Optional
Identifier (ID)
Min 2Max 2

Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow

Usage notes

See HubEDI User Guide.pdf for interpretation of time codes.

TD5
240
Heading > TD5

Carrier Details (Routing Sequence/Transit Time)

RequiredMax use 12

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

Example
TD5-05
387
Routing
Required
String (AN)
Min 1Max 35

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

Usage notes

This element will contain a DICK'S Sporting Goods specific code that indicates who the shipper is and what the service level is. Contact
Rithum to obtain a complete list of codes that apply to your relationship with DICK'S Sporting Goods

N9 Loop
RequiredMax >1
N9
295
Heading > N9 Loop > N9

Reference Identification

RequiredMax use 1

To transmit identifying information as specified by the Reference Identification Qualifier

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

Code qualifying the Reference Identification

Usage notes

Code 'SD' is used in this context to denote 'Sales Division'

SD
Subday Number
N9-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

Usage notes

Sales Division

CL_ECOM : Calia Studio
DSG_ECOM : DICK’S Sporting Goods
FS_ECOM : Field & Stream
GG_ECOM: Golf Galaxy
PL_ECOM: Public Lands
TR_ECOM: True Runner

N9 Loop end
N1 Loop
RequiredMax >1
N1
310
Heading > N1 Loop > N1

Name

RequiredMax use 1

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

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

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

Usage notes

The ST qualifier will always be used

BT
Bill-to-Party
ST
Ship To
N1-02
93
Name
Required
String (AN)
Min 1Max 60

Free-form name

Usage notes

The N1 segment contains the full name for the party. If the first and
last names are reported separately, they will be found in the N2 segment.

N2
320
Heading > N1 Loop > N2

Additional Name Information

RequiredMax use 2

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

Example
N2-01
93
Name
Required
String (AN)
Min 1Max 60

Free-form name

Usage notes

First name of party if reported separately

N2-02
93
Name
Optional
String (AN)
Min 1Max 60

Free-form name

Usage notes

Last name of party if reported separately

N3
330
Heading > N1 Loop > N3

Address Information

RequiredMax use 2

To specify the location of the named party

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

Address information

Usage notes

This element will contain address line 1 for the Ship To Party.

This element is required to be included in the packing slip if you are creating your own.

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

Address information

Usage notes

This element will contain line 2 address information for the Ship To party.

This element is required to be included in the packing slip if you are creating your own.

N4
340
Heading > N1 Loop > N4

Geographic Location

RequiredMax use >1

To specify the geographic place of the named party

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

This element is required to be included in the packing slip if you are creating your own.

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

This element is required to be included in the packing slip if you are creating your own.

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)

Usage notes

This element is required to be included in the packing slip if you are creating your own.

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

Code identifying the country

Usage notes

This element is required to be included in the packing slip if you are creating your own.

PER
360
Heading > N1 Loop > PER

Administrative Communications Contact

RequiredMax use >1

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

Usage notes

Used for primary instance of PER segment in N1 loop

BD
Buyer Name or Department
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-07
365
Communication Number Qualifier
Optional
Identifier (ID)

Code identifying the type of communication number

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

Complete communications number including country or area code when applicable

N1 Loop 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.
Example
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
String (AN)
Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • PO101 is the line item identification.
Usage notes

Merchant's PO line number

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

Quantity ordered

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

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

Usage notes

Unit cost the merchant expects to be billed for each unit fulfilled

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

Code identifying the type of unit price for an item

Usage notes

FX: Used to convey unit cost adjustment flag

FX
Fixed Price
TE
Contract Price per Each
PO1-06
235
Product/Service ID Qualifier
Required
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.
SK
Stock Keeping Unit (SKU)
PO1-07
234
Product/Service ID
Required
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

Merchant's SKU code

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

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

Usage notes

DSG sends the UPC in the VN and UP qualified PO1 segments

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

Identifying number for a product or service

Usage notes

Vendor's product SKU

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

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

Usage notes

This code is used to qualify the product UPC code

UP
U.P.C. Consumer Package Code (1-5-5-1)
PO1-13
234
Product/Service ID
Required
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

UPC code

CTP Loop
RequiredMax >1
CTP
040
Detail > PO1 Loop > CTP Loop > CTP

Pricing Information

RequiredMax use 1

To specify pricing information

Example
CTP-01
687
Class of Trade Code
Required
Identifier (ID)

Code indicating class of trade

RS
Resale
CTP-02
236
Price Identifier Code
Required
Identifier (ID)

Code identifying pricing specification

RES
Resale
CTP-03
212
Unit Price
Required
Decimal number (R)
Min 1Max 15

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

  • See Figures Appendix for an example detailing the use of CTP03 and CTP04.
  • See Figures Appendix for an example detailing the use of CTP03, CTP04 and CTP07.
Usage notes

Unit price to customer

CTP Loop end
PID Loop
RequiredMax >1
PID
050
Detail > PO1 Loop > PID Loop > PID

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
Identifier (ID)

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
Required
Identifier (ID)

Code identifying the general class of a product or process characteristic

08
Product
73
Vendor color description
74
Vendor size description
PID-05
352
Description
Required
String (AN)
Min 1Max 80

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

PID Loop end
DTM
210
Detail > PO1 Loop > DTM

Date/Time Reference

RequiredMax use 10

To specify pertinent dates and times

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

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

Usage notes

Expected ship by date

002
Delivery Requested
038
Ship No Later
DTM-02
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

TD5
250
Detail > PO1 Loop > TD5

Carrier Details (Routing Sequence/Transit Time)

RequiredMax use 12

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

Example
TD5-05
387
Routing
Required
String (AN)
Min 1Max 35

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

Usage notes

This element will contain a DICK'S Sporting Goods specific code that indicates who the shipper is and what the service level is. Contact Rithum to obtain a complete list of codes that apply to your
relationship with DICK'S Sporting Goods

MSG
289
Detail > PO1 Loop > MSG

Message Text

OptionalMax use >1

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

Example
MSG-01
933
Free-Form Message Text
Required
String (AN)
Min 1Max 264

Free-form message text

Usage notes

This may contain personalization information. Personalization data is presented as “name = value” where name is the type of personalization data being provided and value is the actual personalized data. The equal sign is not part of the personalized data. In cases where a merchant does not provide a name for the type of personalization, the
data string will begin with the equal sign followed by the uncategorized personalized data.

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.
Example
CTT-01
354
Number of Line Items
Required
Numeric (N0)
Min 1Max 6

Total number of line items in the transaction set

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

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.