Skip to content
X12 EDI

Dillard's Department Stores, Inc. X12 816 Organizational Relationships

Plan X12 816 Organizational Relationships for Dillard's Department Stores, Inc. / Dillards Department Stores via InterTrade. Connect document identifiers to your business records, test exception handling and track each exchange to completion.

Segments
12
Loops
2
X12 816
Partner references ↗

Implementation guide

Dillard's Department Stores, Inc. / Dillards Department Stores via InterTrade: 816 mapping and validation

X12 816 Organizational Relationships is used when trading-party or location relationships change. Preserve organization, location and parent references so the organization and location hierarchy in your business system stays connected to the original document.

This document is listed for Dillard's Department Stores, Inc. / Dillards Department Stores via InterTrade. Confirm the version, required fields and responses that apply to your account.

Map records and test the business result
Document or decisionRecord and matching IDsWhat to test
Match the business record organization and location hierarchy

organization, location and parent references

  • Define which combination of organization, location and parent references identifies one business record, its lines and any later revision.
Update the receiving system Processing the organization and location hierarchy

ID assigned by the receiving system and processing result

  • Move a store between parent organizations without changing its stable location identity.
  • Test an inactive ship-to location referenced by an open order.
Check the processing result Processing status for the organization and location hierarchy

Original document reference and matching response

  • Reconcile the organization and location hierarchy with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document.

The document reference includes 12 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.

Implementation steps

  1. Choose the starting event and owner

    Decide which application acts when trading-party or location relationships change. Name the operational owner of the organization and location hierarchy and the team that resolves rejected or ambiguous messages.

  2. Keep record IDs connected

    Map organization, location and parent references. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and Dillard's Department Stores, Inc. guide. Preserve the source reference alongside any new destination identifier.

  3. Test failures before launch

    Run the failure cases in the mapping table against realistic organization and location hierarchy data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.

  4. Track every document to completion

    Record transport delivery and document validation separately from successful organization and location hierarchy processing. Give unresolved errors an owner and check the receiving system before approving retries.

Go-live checklist

  • An approved 816 sample and the agreed version and partner guide are available.
  • The mapping tests pass with realistic organization and location hierarchy 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 organization and location hierarchy without processing it twice.

Transaction context

Where 816 Organizational Relationships fits on Dillards Department Stores via InterTrade

Dillard's Department Stores, Inc. channels
3 of 3

3 of Dillard's Department Stores, Inc.'s 3 channels list 816

Trading partners
4

partner references list 816

Channels
6

channel entries list 816

The directory associates InterTrade and 816 with 1 channel.

Document structure

X12 816 Organizational Relationships at the element level

The X12 816 reference contains 17 segment entries and 79 data elements; 38 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.

Segments
17
Data elements
79
Mandatory elements
38
Segments with elements marked mandatory in this reference
Segment Elements Mandatory
BHT 6 2
N1 6 1
HL 4 2
N3 2 1
PER 9 1
REF 3 1
DTM 6 1
ASI 3 2
Key identifiers in 816
  • Hierarchical Structure Code
  • Transaction Set Purpose Code
  • Entity Identifier Code
  • Hierarchical ID Number
  • Hierarchical Level Code
  • Address Information
  • Contact Function Code
  • Reference Identification Qualifier
Segment reference — 12 segments 2 loops · X12 816 Organizational Relationships
ISA Interchange Control Header 16 elements

To start and identify an interchange of zero or more functional groups and interchange-related control segments

GS Functional Group Header 8 elements

To indicate the beginning of a functional group and to provide control information

ST Transaction Set Header 2 elements

To indicate the start of a transaction set and to assign a control number

BHT Beginning of Hierarchical Transaction 4 elements

To define the business hierarchical structure of the transaction set and identify the business application purpose and reference data, i.e., number, date, and time

N1 Loop
N1 Name 2 elements

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

HL Loop
HL Hierarchical Level 3 elements

To identify dependencies among and the content of hierarchically related groups of data segments

N3 Address Information 1 element

To specify the location of the named party

N4 Geographic Location 3 elements

To specify the geographic place of the named party

SE Transaction Set Trailer 2 elements

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

REF Reference Identification 2 elements

To specify identifying information

DTM Date/Time Reference 2 elements

To specify pertinent dates and times

ASI Action or Status Indicator 2 elements

To indicate the action to be taken with the information provided or the status of the entity described

Related references

816 Organizational Relationships on other Dillard's Department Stores, Inc. channels

Compare the listed channel references and confirm their current implementation guides.

Dillard's Department Stores, Inc. / Dillards Department Stores via InterTrade EDI 816 questions

Common questions about 816 Organizational Relationships on the Dillards Department Stores via InterTrade channel.

What is X12 816 Organizational Relationships used for?

816 is used when trading-party or location relationships change. It carries information for the organization and location hierarchy. Match it to your business system using organization, location and parent references.

Is 816 required for Dillard's Department Stores, Inc. / Dillards Department Stores via InterTrade?

816 is listed for Dillard's Department Stores, Inc. / Dillards Department Stores via InterTrade. Confirm the required version and direction for your business unit and account with the partner.

What should I map for X12 816?

Start with organization, location and parent references and the target organization and location hierarchy. 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 816 error handling?

Move a store between parent organizations without changing its stable location identity. Test an inactive ship-to location referenced by an open order. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.

How does 816 relate to other EDI messages?

X12 850 Purchase Order; X12 856 Ship Notice Manifest are related documents also listed on Dillards Department Stores via InterTrade. Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.

What is the difference between 816 and 850?

816 is used when trading-party or location relationships change. 850 is used when a buyer places an order. Each message represents a different business step. Keep their record references connected and track the processing result for each message.

Connect Dillard's Department Stores, Inc. 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.