EDI X12 Mapping
What data does the Coupler translate?
X12 & EDIFACT transactions such as :
- EDI 810 Invoice
- EDI 850 Purchase Order
- EDI 855 Purchase Order Acknowledgment
- EDI 856 S hip Notice Manifest
- EDI 857 Shipment and Billing Notice, etc.
-
EDI 204
Motor Carrier Load Tender Transaction
-
EDI 990 Response to a Load Tender
-
EDI 214 Transportation Carrier Shipment status
-
EDI 210 Motor Carrier Freight Details and Invoice
-
EDI 856 Advance Ship Notice/Manifest.
- HIPPA x12 documents such as 835, 837...
- .etc
Coupler can translate the following to xml such as PapiNET Delivery Message
, P.O, invoice and delivery. It can insert EDI data into a
Database, such as DB2.
Coupler can also translate XML, .csv, fixed length files,
delimited. It can extract data from a database and insert them
into any of the following formats.
How does the eLife Coupler establish a B2B Communication between partners?
How does the eLife Coupler send /receive data?
- FTP
- HTTP
- LAN
- POP3 / SMTP
- HTTP Listener / Talker
Send your documents securely using:
- Encoding
- Certificates
- Encryption
- Digital Signature
- Compression
This feature of the coupler allows EDI companies who have been using x12 for a long time to
communicate with partners that use the new xml technology
seamlessly.
For more information, send us an email
