Page Comparison

...

This Use Case would help you jumpstart solution development for Adeptia Solution developer , IT and Business User with basic knowledge of ETL Connect and EDI.  EDI implementations can be complex, Adeptia has built an easy to use approach for implementing inbound and outbound EDI transactions.This use case is for receiving an inbound EDI transaction and loading it onto a database or a common internal format file. This document will outline the key steps to very quickly set up an inbound EDI based transformationTemplate usage.

B2B Use Cases involving Partner collaboration and self-service wherein Business Users can create and enable transactions and also perform basic data mapping that would be needed on a day to day basis and for quick on-boarding. 

This document  describes the steps to quickly create a custom template for inbound transactions. The Inbound template can be used to setup the Partner User to manage source configuration and the Business user to manage destination configuration.

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
• Customer requiring their partners to quickly create a Transaction for enabling an inbound file to Connect.
• Customer requiring their partners to select and map data to an output format and deliver to a pre-defined location in the template.

Excluded Scenarios

• This template will not support additional custom pre and post processing requirements.
• Enabling partners or business users to use existing custom process flows not supported in this template.

Pre-requisites

Following are the pre-requisites for to implementing the simple EDI Outbound B2B  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
   There is clarity of functions required to be performed by internal and partner users involved in building the B2B transaction.
8. Network needed for whom the template is to be created.