To start and identify an interchange of zero or more functional groups and interchange-related control segments
J.H. Larson Company X12 849 Response to Product Transfer Account Adjustment
Plan X12 849 Response to Product Transfer Account Adjustment 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
- 16
- Loops
- 3
- X12 849
- Partner references ↗
Implementation guide
J.H. Larson Company (via Epicor Eclipse): 849 mapping and validation
X12 849 Response to Product Transfer Account Adjustment is used when a product-transfer adjustment is accepted or disputed. Preserve original claim, response line and authorized amount so the adjustment claim response 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 | adjustment claim response original claim, response line and authorized amount |
|
| Update the receiving system | Processing the adjustment claim response ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the adjustment claim response Original document reference and matching response |
|
The document reference includes 16 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 845 Price Authorization Acknowledgment Status
price authorization status: an authorization is issued or its status changes.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when a product-transfer adjustment is accepted or disputed. Name the operational owner of the adjustment claim response and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map original claim, response line and authorized amount. 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 adjustment claim response 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 adjustment claim response processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 849 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic adjustment claim response 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 adjustment claim response without processing it twice.
Transaction context
Where 849 Response to Product Transfer Account Adjustment 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 849
- Trading partners
- 5
partner references list 849
- Channels
- 5
channel entries list 849
Frequently listed alongside 849
The directory associates Epicor Eclipse and 849 with 3 channels.
Document structure
X12 849 Response to Product Transfer Account Adjustment at the element level
The X12 849 reference contains 27 segment entries and 80 data elements; 48 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- Segments
- 27
- Data elements
- 80
- Mandatory elements
- 48
| Segment | Elements | Mandatory |
|---|---|---|
| BRC | 4 | 2 |
| REF | 2 | 1 |
| N1 | 4 | 1 |
| N3 | 2 | 1 |
| CON | 3 | 3 |
| LIN | 5 | 2 |
| AAA | 2 | 1 |
| QTY | 2 | 1 |
| AMT | 3 | 2 |
Key identifiers in 849
- Transaction Set Purpose Code
- Date
- Reference Identification Qualifier
- Entity Identifier Code
- Address Information
- Reference Identification
- Contract Status Code
- Product/Service ID Qualifier
Segment reference — 16 segments 3 loops · X12 849 Response to Product Transfer Account Adjustment
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 Response to Product Transfer Account Adjustment Transaction Set
N1 Loop Repeat: 50
To identify a party by type of organization, name, and code
CON Loop Repeat: 10,000
To specify contract or reference number and status
PAD Loop Repeat: 1,000
To specify the product transfer type, and/or line item number
To transmit a hash total for a specific element in the transaction set
To indicate the total monetary amount
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 basic item identification data
To specify the validity of the request and indicate follow-up action authorized
To specify item unit data
To specify quantity information
To specify identifying information
To specify pertinent dates and times
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 Price Authorization Acknowledgment Status X12 845 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 849 questions
Common questions about 849 Response to Product Transfer Account Adjustment on the J.H. Larson Company (via Epicor Eclipse) channel.
What is X12 849 Response to Product Transfer Account Adjustment used for?
849 is used when a product-transfer adjustment is accepted or disputed. It carries information for the adjustment claim response. Match it to your business system using original claim, response line and authorized amount.
Is 849 required for J.H. Larson Company (via Epicor Eclipse)?
849 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 849?
Start with original claim, response line and authorized amount and the target adjustment claim response. 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 849 error handling?
Match partial approval to the submitted claim lines. Test a repeated response and prevent a second credit from being posted. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
How does 849 relate to other EDI messages?
X12 844 Product Transfer Account Adjustment; X12 845 Price Authorization Acknowledgment Status 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 849 and 844?
849 is used when a product-transfer adjustment is accepted or disputed. 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.
