To start and identify an interchange of zero or more functional groups and interchange-related control segments
J.H. Larson Company X12 845 Price Authorization Acknowledgment/Status
Plan X12 845 Price Authorization Acknowledgment/Status for J.H. Larson Company (via Epicor Eclipse). Connect document identifiers to your business records, test exception handling and track each exchange to completion.
- Segments
- 15
- Loops
- 5
- X12 845
- Partner references ↗
Implementation guide
J.H. Larson Company (via Epicor Eclipse): 845 mapping and validation
X12 845 Price Authorization Acknowledgment/Status is used when an authorization is issued or its status changes. Preserve authorization reference, product and effective period so the price authorization status in your business system stays connected to the original document.
This document is listed for J.H. Larson Company (via Epicor Eclipse). 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 | price authorization status authorization reference, product and effective period |
|
| Update the receiving system | Processing the price authorization status ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the price authorization status Original document reference and matching response |
|
The document reference includes 15 segments. Use the segment reference below to locate the relevant parts of the message. Check required fields and repetition limits in the partner guide.
How the related documents differ
Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.
- X12 844 Product Transfer Account Adjustment
product-transfer adjustment request: a distributor or reseller requests an account adjustment.
- X12 849 Response To Product Transfer Account Adjustment
adjustment claim response: a product-transfer adjustment is accepted or disputed.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when an authorization is issued or its status changes. Name the operational owner of the price authorization status and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map authorization reference, product and effective period. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and J.H. Larson Company guide. Preserve the source reference alongside any new destination identifier.
-
Test failures before launch
Run the failure cases in the mapping table against realistic price authorization status 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 price authorization status processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 845 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic price authorization status 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 price authorization status without processing it twice.
Transaction context
Where 845 Price Authorization Acknowledgment/Status fits on J.H. Larson Company (via Epicor Eclipse)
- J.H. Larson Company channels
- 1 of 1
1 of J.H. Larson Company's 1 channel list 845
- Trading partners
- 2
partner references list 845
- Channels
- 2
channel entries list 845
Frequently listed alongside 845
The directory associates Epicor Eclipse and 845 with 2 channels.
Document structure
X12 845 Price Authorization Acknowledgment/Status at the element level
The X12 845 reference contains 22 segment entries and 63 data elements; 39 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- Segments
- 22
- Data elements
- 63
- Mandatory elements
- 39
| Segment | Elements | Mandatory |
|---|---|---|
| BPA | 1 | 1 |
| N1 | 4 | 1 |
| CON | 3 | 3 |
| REF | 2 | 1 |
| DTM | 2 | 1 |
| N3 | 2 | 1 |
| LIN | 7 | 2 |
| CTT | 1 | 1 |
Key identifiers in 845
- Transaction Set Purpose Code
- Entity Identifier Code
- Reference Identification Qualifier
- Reference Identification
- Contract Status Code
- Date/Time Qualifier
- Address Information
- Product/Service ID Qualifier
Segment reference — 15 segments 5 loops · X12 845 Price Authorization Acknowledgment/Status
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 identify the beginning of a Price Authorization Acknowledgment/Status Transaction Set
N1 Loop Repeat: 10,000
To identify a party by type of organization, name, and code
CON Loop Repeat: 10,000
To specify contract or reference number and status
To specify identifying information
To specify pertinent dates and times
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 specify the location of the named party
To specify the geographic place of the named party
PAD Loop Repeat: 1
To specify the product transfer type, and/or line item number
LIN Loop Repeat: 1
To specify basic item identification data
CTP Loop Repeat: 25
To specify pricing information
Related references
Other transactions in J.H. Larson Company (via Epicor Eclipse)
Other EDI documents listed on this channel.
Purchase Order X12 850 Invoice X12 810 Response To Product Transfer Account Adjustment X12 849 Ship Notice Manifest X12 856 Product Transfer Account Adjustment X12 844
No references match your search.
Showing 5 of 5 references
Browse the full directoryJ.H. Larson Company (via Epicor Eclipse) EDI 845 questions
Common questions about 845 Price Authorization Acknowledgment/Status on the J.H. Larson Company (via Epicor Eclipse) channel.
What is X12 845 Price Authorization Acknowledgment/Status used for?
845 is used when an authorization is issued or its status changes. It carries information for the price authorization status. Match it to your business system using authorization reference, product and effective period.
Is 845 required for J.H. Larson Company (via Epicor Eclipse)?
845 is listed for J.H. Larson Company (via Epicor Eclipse). Confirm the required version and direction for your business unit and account with the partner.
What should I map for X12 845?
Start with authorization reference, product and effective period and the target price authorization status. 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 845 error handling?
Test an authorization ending before a resale date. Maintain separate eligibility for two customers buying the same product. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
How does 845 relate to other EDI messages?
X12 844 Product Transfer Account Adjustment; X12 849 Response To Product Transfer Account Adjustment are related documents also listed on J.H. Larson Company (via Epicor Eclipse). Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.
What is the difference between 845 and 844?
845 is used when an authorization is issued or its status changes. 844 is used when a distributor or reseller requests an account adjustment. Each message represents a different business step. Keep their record references connected and track the processing result for each message.
Connect J.H. Larson Company 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.
