X12 880 DAX Grocery Products Invoice
This Draft Standard for Trial Use contains the format and establishes the data contents of the Grocery Products Invoice Transaction Set (880) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to provide for customary and established grocery industry practice relative to billing details for finished goods in a retail or wholesale consumer market. The transaction set can be used by the supplier or broker organization to request payment from a retailer or wholesaler organization. This transaction set is to be used for standalone detail billing and cannot be used for statement billing or credit/debit adjustments.
- ~ Segment
- * Element
- > Component
- None included
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
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)
Code to identify the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
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)
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
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
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
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
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
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
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
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
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- GP
- Grocery Products Invoice (880)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission. Codes agreed to by trading partners
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)
Assigned number originated and maintained by the sender
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
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
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
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).
- 880
- Grocery Products Invoice
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Invoice Identification
To transmit identifying dates and numbers for this transaction set
Date expressed as CCYYMMDD
- G0101 is the invoice issue date.
Date expressed as CCYYMMDD
- G0103 is the date assigned by the purchaser to the purchase order.
Accounting Date
Identifying number for Purchase Order assigned by the orderer/purchaser
PO Number consists of a 'P' Purchase, 3 digit plant code and 7-8 digit PO Number.
Example: PSAS12345678, where P is 'Purchase', SAS is 'San Antonio Snacks', and 12345678 is the PO Number.
Plant Codes are as follows:
SAS- San Antonio Snacks
HUS- Houston Snacks
SAD- San Antonio Dairy
SAI-San Antonio Ice Cream
SAM-San Antonio Meat
SAP- San Antonio Print
HCC- Houston Culinary Center
HUB- Houston Bakery
HUD- Houston Dairy
CCO- Corpus Christi Bakery
SAB- San Antonio Bakery
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
Terms of Sale
To specify the terms of sale
- The G23 segment can be used at the header level or detail level, but not both.
When it is used at the detail level, there must be at least one occurrence of the G23 segment for each iteration of the G17 segment.
Code identifying type of payment terms
- If G2301 equals "04" (deferred or installment) then either G2313 or G2314 is required and the data in the segment pertains only to the portion of the invoice described in G2313 or G2314. If G2301 equals "11" (elective) then G2304 is required. If G2301 is not equal to "05"' (discount not applicable) then (G2305 or G2310) and (G2306 or G2307) is required. If G2301 equals "ZZ" (other) then G2315 is required. Multiple use of this segment when G2301 equals "04" (deferred or installment) always implies an "AND" relationship. When G2301 equals "06" (mixed) or "11" (elective) an "OR" relationship is always implied.
Code identifying the beginning of the terms period
Terms discount percentage, expressed as a percent, available to the purchaser if an invoice is paid on or before the Terms Discount Due Date
Date payment is due if discount is to be earned expressed in format CCYYMMDD
Number of days in the terms discount period by which payment is due if terms discount is earned
Date when total invoice amount becomes due expressed in format CCYYMMDD
Number of days until total invoice amount is due (discount not applicable)
Total amount of terms discount
- G2310 is a memo figure requiring specific payment performance and therefore should not be negative.
Name
To identify a party by type of organization, name, and code
- One occurrence of the N1 loop must be used to identify the party to whom the merchandise was shipped.
Code identifying an organizational entity, a physical location, property or an individual
- BT
- Bill-to-Party
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
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.
D-U-N-S number with four character suffix.
Name
To identify a party by type of organization, name, and code
- One occurrence of the N1 loop must be used to identify the party to whom the merchandise was shipped.
Code identifying an organizational entity, a physical location, property or an individual
- SF
- Ship From
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
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.
D-U-N-S number with four character suffix.
Allowance or Charge
To specify allowances, charges, or services
Code identifying the type of allowance or charge
Code indicating method of handling for an allowance or charge
- ZZ
- Mutually Defined
The number assigned by a vendor referencing an allowance, promotion, deal or charge
Total dollar amount for the allowance or charge
Up to a 9 digit real number / 2 implied decimal places.
Detail
Item Detail - Invoice
To specify the basic and most frequently used line item data for the invoice and related transactions
- Either the 0300 loop or the 0400 loop must be used, but both loops cannot be used within a single transaction set.
Number of units invoiced (supplier units)
Up to a 10 digit real number / up to 3 decimal places.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- G1702 qualifies G1701.
- CA
- Case
- EA
- Each
- LB
- Pound
- UN
- Unit
Gross unit cost within the appropriate price bracket for a line item
Up to a 9 digit real number / up to 4 decimal places.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IN
- Buyer's Item Number
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
Line Item Detail - Description
To describe an item in free-form format
Summary
Total Invoice Quantity
To specify summary details of total items shipped in terms of quantity, weight, and volume, and to specify payment method
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- G3102 qualifies G3101.
Total Dollars Summary
To specify the total invoice amount, including charges less allowances, before terms discount
Monetary amount
Up to a 10 digit real number / 2 implied decimal places.
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Assigned number originated and maintained by the sender
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
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.