Using the Predefined EDI Translation Business Processes

About this task

To use the predefined EDI translation business processes, you must complete the following tasks:

Procedure

  1. Create the appropriate inbound or outbound envelopes.
    For more information, see Creating Envelopes to Use with EDI Translation Business Processes.
  2. Modify the service configuration if you want to use auto collection or another non-default option.
    For more information, see Predefined EDI Translation File System Adapters.
  3. Modify the predefined business process if you want to use a non-default option.
  4. Create the maps necessary to perform the EDI translation to or from the format you require.
  5. For outbound EDI data, provide a Document Extraction map and name it according to the mailbox or File System path where the input file is collected. If the input file is collected from the default directory (install_dir/edioutbound/collect), you should provide a Data Extraction map named EDIOUTBOUND_DOCEXTRACT. If you want to use multiple Data Extraction maps, you do so by nesting the maps in subfolders using a variation of the EDIOUTBOUND_DOCEXTRACT map name. For example, if the input file is dropped into directory install_dir/edioutbound/collect/folder1/folder2, the Data Extraction map must be named EDIOUTBOUND_folder1_folder2_DOCEXTRACT. More generally, if the input file is dropped into directory install_dir/edioutbound/collect/folder1/folder2/…/folderN, the map used for Data Extraction must be named EDIOUTBOUND_folder1_folder2_…_folderN_DOCEXTRACT.
    Note: Outbound XML data does not require a map because extraction occurs according to the File System adapter parameters you set. For inbound EDI data, you need to provide the name of the map in the incoming document (transaction-level) envelope.