Best Practices - EDI Inbound

Owned by Akash Kumar Jaiswal (Unlicensed)
Last updated: Jul 31, 2019Version comment
2 min read

Use Case Overview

EDI implementations can be complex. But with Adeptia Connect's already configured EDI templates that are pre-built and bundled with the product help jumpstart the solution development for Adeptia Solution developer who has basic knowledge of ETL and EDI.  This section provides an easy to use approach for implementing inbound and outbound EDI transactions.

This use case is handling a scenario where Connect is receiving an inbound EDI transaction and loading it to a database or a common internal format file. This would outline the key steps to quickly set up an inbound EDI based inbound transformation.

Scope of Use Case

Applicable Scenarios

  • This use case is applicable for situations where the source (i.e. AS2) is dedicated to a single partner.
  • The EDI Inbound template can be configured for multiple EDI transaction types.

Excluded Scenarios

  • A single inbound queue for multiple partners
  • Routing of outbound responses to multiple partners
  • Post-processing requirements

Pre-requisites

Following are the pre-requisites for implementing the simple EDI Outbound use case:

  1. System has a pre-built EDI Schema that is pulled automatically based on EDI Settings. 
  2. You should have knowledge of EDI exchange and transactions along with the knowledge of EDI fields and attributes needed for data (X12, EDIFACT, HIPAA) transformation.
  3. The Sender and Receiver IDs also are also needed to be set up during Partner Set up so that it matches the IDs in the transaction.
  4. Mapping of EDI elements is known as upfront or available existing EDI mapping.
  5. Source Type – File, FTP, LAN location in this example, for AS2 use MFT Server.
  6. Target schema and type – The system will select the appropriate target EDI schema.
  7. Target Type - File/Database/Application.

Next Step

Solution Design Flow: EDI Inbound

Â