Error You are using an unlicensed and unsupported version of DotNetNuke Professional Edition. Please contact sales@dnncorp.com for information on how to obtain a valid license.


EDI 816

EDI 816 Organizational Relationships:

The EDI 816 Organizational Relationships transaction set is used in two formats for transmitting location information. One format of the 816 is for providing location addresses. The second format is to communicate information about the organizational relationships between locations, such as stores services by specific Distribution Centers, warehouses, etc.

Many of the most commonly used EDI transactions, such as 850 Purchase Orders and 810 Invoices, typically do not include detailed location information. Instead, in order to reduce cost and complexity, these documents simply identify locations by unique codes. The EDI 816 transaction provides trading partners with the sender’s location addresses and their corresponding codes. It can also provide information on each location’s eligibility to purchase under terms of the relationship with a seller.

A parent organization with various locations may include any of the following:
  • Manufacturers with multiple locations for production, assembly, distribution, etc.
  • Multi-hospital and medical facility healthcare systems
  • A chain of retail stores and regional distribution centers
  • Associations with regional membership locations
It is important for these types of organizations to help trading partners understand the relationships between their various locations, and between the locations and the parent organization.

816 transactions include a code to identify whether the information provided is either original, an addition to previously provided information, or represents previous information to be deleted.

Get the most out of your EDI data. EDI/HQ™, our advanced EDI software, includes advanced data management tools providing total access to your EDI transaction data for management reporting and decision making. Contact us to schedule a demonstration.

EDI 816 Format:

ISA*00*          *00*          *12*ABCCOM         *01*999999999      *101127*1719*U*00400*000003438*0*P*>
GS*OR*4405197800*999999999*20101127*1719*1421*X*004010VICS
ST*816*1001
BHT*0059*00*NATCON*20010101**ML
N1*MF*HC MAUFACTURER*21*08KUG8732
N1*BG*HC BUYING GROUP*21*097YT593J
PER*CD*MARY AUDETTE*TE*440-519-7800*FX*440-519-9370*EM*FEEDBACK@1EDISOURCE.COM
HL*01**24*1
N1*BG*HC BUYING GROUP*21*097YT593J
HL*02*01*26*0
N1*1O*CARE HOSPITAL*21*00YLI7430
N3*400 VENDUE AVENUE
N4*CHARLESTON*SC*29401
QTY*88*150
DTM*007*20010331
ASI*2*009
N1*1T*SOUTHERN PRACTICE*21*955UY8230
N3*413 PORTCALL DRIVE
N4*SAVANNAH*GA*45671
QTY*88*0
DTM*007*20010331
ASI*1*008
SE*21*1001
GE*1*1421
IEA*1*000003438

EDI 816 Specification:

This X12 Transaction Set 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.

Sources
Accredited Standards Committee X12. ASC X12 Standard [Table Data].
Data Interchange Standards Association, Inc., Falls Church, VA.


Page Title: Learn about the EDI 816 Organizational Relationships