We Make EDI Integration Easy
Below you will essential information in regards to this EDI. If you have any specific questions about integrating your EDI with your ERP and eCommerce please reach out. Take advantage of our "start planning" feature to map out your integration needs.
>> Request a Demo
>> Map Your Ideal Integration
What is a 838 - Trading Partner Profile document?
The 838 EDI document type is an electronic version of a paper Trading Partner Profile. Standard EDI formats include X12, ANSI, EDIFACT and its subsets.
The 838 EDI document type is used to request, change, verify, or transmit business profile information between trading partners. The information can be used by the receiver to facilitate the processing of the sender's business transactions.
What makes up the 838 - Trading Partner Profile document?
An EDI 838 - Trading Partner Profile document is organized into segment and data elements. A segment can contain at least one data element. Each data element contains a data field. Data elements can include entity relationships, business name, locations, and business classification, identical to a paper partner profile. There are an infinite number of possibilities available for a company to include data on an 838 Trading Partner Profile. There are an infinite number of possibilities available for a company to include data on an 838 - Trading Partner Profile.
How is a 838 - Trading Partner Profile used?
The 838 EDI document is sent from one trading partner to another to convey information about that trading partner. After the 838 Trading Partner Profile is received, a 997 Functional Acknowledgment is sent back from the trading partner indicating that the 838 Trading Partner Profile was successfully received.
How is a 838 - Trading Partner Profile processed?
An EDI solution is required to process the EDI documents received into an ERP or accounting system or into a readable format for manual entry. Each trading partner will have an EDI Implementation guide outlining the specific segments, data elements, values accepted, and the applicable business rules to be followed.
eBridge Connections has pre-built maps for all EDI transaction documents including 850 purchase orders, 810 invoices, and 856 advance shipping notices.