To start and identify an interchange of zero or more functional groups and interchange-related control segments
QRS/GXS Catalog X12 832 Price/Sales Catalog
Plan X12 832 Price/Sales Catalog for QRS/GXS Catalog (via OpenText). Connect document identifiers to your business records, test exception handling and track each exchange to completion.
- Segments
- 36
- Loops
- 9
- X12 832
- Partner references ↗
Implementation guide
QRS/GXS Catalog (via OpenText): 832 mapping and validation
X12 832 Price/Sales Catalog is used when catalog entries or commercial details are published. Preserve item identifier, catalog revision and price basis so the product and price catalog in your business system stays connected to the original document.
This document is listed for QRS/GXS Catalog (via OpenText). Confirm the version, required fields and responses that apply to your account.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| Match the business record | product and price catalog item identifier, catalog revision and price basis |
|
| Update the receiving system | Processing the product and price catalog ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the product and price catalog Original document reference and matching response |
|
The document reference includes 36 segments. Use the segment reference below to locate the relevant parts of the message. Check required fields and repetition limits in the partner guide.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when catalog entries or commercial details are published. Name the operational owner of the product and price catalog and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map item identifier, catalog revision and price basis. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and QRS/GXS Catalog guide. Preserve the source reference alongside any new destination identifier.
-
Test failures before launch
Run the failure cases in the mapping table against realistic product and price catalog data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.
-
Track every document to completion
Record transport delivery and document validation separately from successful product and price catalog processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 832 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic product and price catalog data.
- Each submitted document can be traced through delivery, validation and processing in the receiving system.
- Your team knows how to investigate and recover a rejected or timed-out product and price catalog without processing it twice.
Transaction context
Where 832 Price/Sales Catalog fits on QRS/GXS Catalog (via OpenText)
- QRS/GXS Catalog channels
- 1 of 1
1 of QRS/GXS Catalog's 1 channel list 832
- Trading partners
- 10
partner references list 832
- Channels
- 26
channel entries list 832
Frequently listed alongside 832
The directory associates OpenText and 832 with 1 channel.
Document structure
X12 832 Price/Sales Catalog at the element level
The X12 832 reference contains 60 segment entries and 256 data elements; 70 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- Segments
- 60
- Data elements
- 256
- Mandatory elements
- 70
| Segment | Elements | Mandatory |
|---|---|---|
| BCT | 6 | 1 |
| DTM | 2 | 1 |
| CTB | 3 | 1 |
| CUR | 2 | 2 |
| SAC | 3 | 1 |
| N1 | 4 | 1 |
| N3 | 2 | 1 |
| REF | 3 | 1 |
| PER | 8 | 1 |
| LIN | 29 | 2 |
| G53 | 1 | 1 |
Key identifiers in 832
- Catalog Purpose Code
- Date/Time Qualifier
- Restrictions/Conditions Qualifier
- Entity Identifier Code
- Currency Code
- Allowance or Charge Indicator
- Address Information
- Reference Identification Qualifier
Segment reference — 36 segments 9 loops · X12 832 Price/Sales Catalog
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
To indicate the beginning of the Price/Sales Catalog Transaction Set and specify catalog purpose and number information
To specify pertinent dates and times
To specify restrictions/conditions (such as shipping, ordering)
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge
N1 Loop
To identify a party by type of organization, name, and code
To specify the location of the named party
To specify the geographic place of the named party
To specify identifying information
To identify a person or office to whom administrative communications should be directed
LIN Loop Repeat: 100
To specify basic item identification data
To identify the specific type of item maintenance
To identify and answer yes and no questions, including the date, time, and comments further qualifying the condition
To transmit a hash total for a specific element in the transaction set
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
To describe a product or process in coded or free-form format
To specify physical measurements or counts, including dimensions, tolerances, variances, and weights (See Figures Appendix for example of use of C001)
To describe marking, packaging, loading, and unloading requirements
To specify the carrier and sequence of routing and provide transit time information
To specify transportation special handling requirements, or hazardous materials information, or both
To specify lead time for availability of products and services
To identify a commodity or a group of commodities or a tariff page commodity
To specify tax information
To specify textual data
To provide physical characteristics relative to a consumer unit
CTP Loop Repeat: 100
To specify pricing information
To identify the type and physical attributes of the pallet, and, gross weight, gross volume, and height of the load and the pallet
G39 Loop Repeat: 20
To identify a vendor's selling unit or to provide physical characteristics relative to a vendor's selling unit
PKL Loop Repeat: 20
To identify the package level, quantity of stock-keeping units (SKUs), and other basic data related to the configuration of the package being defined
LM Loop
To transmit standard code list identification information
LQ Loop
Code to transmit standard industry codes
To provide basic information about the electronic format of the interchange data
SLN Loop
To specify product subline detail item data
PID Loop
QRS/GXS Catalog (via OpenText) EDI 832 questions
Common questions about 832 Price/Sales Catalog on the QRS/GXS Catalog (via OpenText) channel.
What is X12 832 Price/Sales Catalog used for?
832 is used when catalog entries or commercial details are published. It carries information for the product and price catalog. Match it to your business system using item identifier, catalog revision and price basis.
Is 832 required for QRS/GXS Catalog (via OpenText)?
832 is listed for QRS/GXS Catalog (via OpenText). Confirm the required version and direction for your business unit and account with the partner.
What should I map for X12 832?
Start with item identifier, catalog revision and price basis and the target product and price catalog. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.
How should I test 832 error handling?
Test a pack-size change without treating case and each prices as equivalent. Apply a future price at its effective date while preserving the current price. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
How does 832 relate to other EDI messages?
Keep 832 business processing separate from transport receipt and technical validation. Agree which preceding record, response or reconciliation completes the product and price catalog workflow; confirm any required companion messages with your partner.
Connect QRS/GXS Catalog EDI to your business systems
See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.
