Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This Use Case would help you jumpstart solution development for Adeptia Solution developer with basic knowledge of ETL 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 filefor generating an outbound EDI transaction either in response to an incoming acknowledgement EDI transaction or outbound EDI request. This document will outline the key steps to very quickly set up an inbound EDI based transformationoutbound acknowledgement and EDI outbound Transaction.

Scope of Use Case

...

This use case is applicable for situations where

...

out bound EDI is dedicated to a single partner. 

The EDI

...

outbound template can be configured for multiple EDI transaction types.

...

Excluded Scenarios

...

Pre-requisites

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

...