X12 816 Organizational Relationships
This Draft Standard for Trial Use contains the format and establishes the data contents of the Organizational Relationships Transaction Set (816) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to transmit pertinent information about a parent organization, its members and the relationship of a member to another member, and/or to the parent organization. A parent organization could be an association, a multi-hospital system, a chain of retail stores, a holding company, etc.
This transaction set can be used to convey the identity and relationship of members to a parent organization; identify eligibility to purchase under the terms and conditions negotiated by a parent organization on behalf of its members; and to update application databases.
- ~ Segment
- * Element
- > Component
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
- OR
- Organizational Relationships (816)
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).
- 816
- Organizational Relationships
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning of Hierarchical Transaction
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
- BHT03 and BHT04 are mandatory.
BHT00650414080420100519
Code indicating the hierarchical application structure of a transaction set that utilizes the HL segment to define the structure of the transaction set
- 0065
- Company, Operating Unit
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- BHT03 is the number assigned by the originator to identify the transaction within the originator's business application system.
Date expressed as CCYYMMDD
- BHT04 is the date the transaction was created within the business application system.
Name
To identify a party by type of organization, name, and code
- The N1 loop shall identify the transaction set issuer and optionally provide contact information if necessary.
N1FR**93095391173
Code identifying an organizational entity, a physical location, property or an individual
- FR
- Message From
Code designating the system/method of code structure used for Identification Code (67)
- 93
- Code assigned by the organization originating the transaction set
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.
- 095391173
- Shoe Carnival DUNS Number
Detail
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- 35
- Company/Corporation
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Name
To identify a party by type of organization, name, and code
- N105, when used, defines the relationship of the entity designated in N102 or N104 to its parent organization.
N1CQSHOE CARNIVAL***07
Code identifying an organizational entity, a physical location, property or an individual
- CQ
- Corporate Office
Code describing entity relationship
- N105 and N106 further define the type of entity in N101.
- 07
- Company
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- 36
- Operating Unit
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
Name
To identify a party by type of organization, name, and code
- N105, when used, defines the relationship of the entity designated in N102 or N104 to its parent organization.
N1BUSHOE CARNIVAL #39303**SN
Code identifying an organizational entity, a physical location, property or an individual
- BU
- Place of Business
Code designating the system/method of code structure used for Identification Code (67)
- 93
- Code assigned by the organization originating the transaction set
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.
Shoe Carnival Store Number
Code identifying an organizational entity, a physical location, property or an individual
- SN
- Store
Additional Name Information
To specify additional names or those longer than 35 characters in length
N2SHOE CARNIVAL #3EASTLAND PLACE
Address Information
To specify the location of the named party
N35241 FREDERICA STREETSUITE A
Geographic Location
To specify the geographic place of the named party
N4EVANSVILLEIN*47715
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
5- or 9-digit Zip Code
Action or Status Indicator
To indicate the action to be taken with the information provided or the status of the entity described
Shoe Carnival sends new store addresses on an 816 transaction, but does not use the ASI02 code of “021” to signify this. New stores will use the “001” Maintenance Type Code.
AS12001
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
Example 816
GS*OR*SENDERGS*RECEIVERGS*20231001*215818*000000001*X*004010
ST*816*1001
BHT*0065*04*140804*20100519
N1*FR**93*095391173
HL*1**35
N1*CQ*SHOE CARNIVAL, INC.***07
HL*2*1*36
N1*BU*SHOE CARNIVAL #3*93*03**SN
N2*SHOE CARNIVAL #3*EASTLAND PLACE
N3*805 N. GREEN RIVER ROAD
N4*EVANSVILLE*IN*47715
ASI*2*001
HL*3*1*36
N1*BU*SHOE CARNIVAL #4*93*04**SN
N2*SHOE CARNIVAL #4*OWENSBORO TOWNE CENTRE
N3*5241 FREDERICA STREET*SUITE A
N4*OWENSBORO*KY*42301
ASI*2*001
SE*18*1001
GE*1*000000001
IEA*1*000000001
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.