Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Corrected links that should have been relative instead of absolute.

...

This Use Case would help you jumpstart solution development for Adeptia Solution developer with basic , IT, and Business User with 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 Template 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 will outline the key steps to very quickly set up an inbound EDI based transformationquickly 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:

...

  • There is clarity of functions required to be performed by internal and partner users involved in building the B2B transaction.
  • Network needed for whom the template is to be created.

 

Next Step

Solution Design Flow - Inbound Template