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.

...

  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 Outbound