Copy of Creating an Inbound EDI Transactions

A Transaction is created by using a Template. Adeptia Connect has an activated prebuilt EDI Inbound Template that you can use to create a Transaction.

This section helps you in creating an inbound EDI Transactions.

 To create an Inbound Transaction:

1. Click Transactions > Templates.

2. On the Templates screen, search EDI Inbound.

3. Select the EDI Inbound Template to create a Transaction.

4. Provide the name and description of the Transaction. The name and description of the Transaction are generated automatically based on the selected Template.

   You can edit the Transaction name and description that can be up to 48 and 300 characters long.

   

    

5. Click Continue.

6. Select the Network  and Partner for which you are creating the Transaction. Only EDI Partners will be listed in the drop-down list. 

   To select multiple Networks from the drop-down list, click on the networks one by one. 

   
   
   
   

7. Click Next.

8. On the EDI Configuration window, do the following:
   
   1. Select the following values in their respective fields.
      
      • EDI Standard
      • EDI Standard Version
      • Association Assigned Code
      • Transaction Set Code
      • Test/Production Indicator

   2. Select the option from the Generate Acknowledgement to generate acknowledgment for the inbound messages sent. Following are the available options:

      Option Name	Description
      No - Do not generate acknowledgments	Select this option if you don't want to generate an acknowledgment for the inbound messages sent.
      Yes - No error detail	Select this option to generate an acknowledgment for an inbound message sent without error details.
      Yes - With error detail	Select this option to generate an acknowledgment for an inbound message sent with error details.

      1. If you want to send a customized acknowledgment then select either Yes - No error detail or Yes - With error detail option from the Generate Acknowledgement. 
      2. In case of EDI X12 format, when you choose 997 as a transaction set code, you will have an option to select from the following processing acknowledgement:
         • Reconcile
         • Transform
         • Reconcile and Transform
           
           

         

         Option Name	Description
         Reconcile	Sends acknowledgment for receiving the acknowledgment of an outbound message sent.
         Transform	Transforms 997 EDI Transaction Set Code to another EDI Transaction Set Code.
         Reconcile and Transform	Sends acknowledgment for receiving the acknowledgment of an outbound message sent and transform 997 EDI Transaction Set Code to another EDI Transaction Set Code.

      3. In case of HIPAA Data Format, if you choose EDI Standard Version as 005010X231A1 with 999 as transaction code, you will have the same options as defined in step (¡¡). 
   3. Select Skip Compliance Check check box to skip compliance check for this document.
   4. Expand Translation Properties and Select the number of translation(s) you want to create from single EDI source.
      
      
      
      

   5. Expand Interchange Properties and select type of sequence checking from Sequence Checking. 

      

      The types of sequence checking supported by EDI ACCELERATOR and their descriptions are given below.

       

      Sequence Checking Type	Description
      None	No Sequence checking is done on control number.
      Duplicate	Duplicate means inbound document contains duplicate control numbers. If you select this option then control numbers of inbound messages should not be duplicated. In case control number is duplicated then the inbound message is not processed and an error message is generated in the EDI Interchange inbound log.
      Incremental	Incremental means control numbers should be in the incremental order. If you select this option then control numbers of inbound messages should be in the incremental order. In case control number of any message is not in the incremental order then the inbound message is processed but a warning message is generated in the EDI Interchange Inbound Log.
      Chronological	Chronological means control number should be greater than the previous control number. If you select this option then control numbers of inbound messages should be in the chronological order. In case control number of any message is not in the chronological order then the message is processed but a warning message is generated in the EDI Interchange Inbound Log.

      
      
      

      In case of Incremental and Chronological Sequence Checking:

      • Select Use Global Control No check box to use interchange control numbers defined in the trading partner activity of this inbound relationship.
      • Type the last used control number in Last Used Control Number text box.
        
        
   6. Expand Group properties.
      
      
      
      
      • Functional ID is automatically populated based on Transaction Set Code that you have selected.
      • Define the Sequence Checking and control numbers in the similar way as defined in the Interchange Properties.
        
        
   7. Expand Document Properties and define the values as defined in the Interchange properties.
      
      
      
      
   8. Expand Advanced Properties.
      
      
      
      
      • Define a value in setting the number of transaction sets that a B2BI process flow can process at a time within a group in the Transaction sets Process Count. The default value is 2000.
      • Type a value in setting up the number of concurrent child processes that can run at a time in the Concurrent Processes. The default value is 1.
        
        
9. Click Next to define the Source application account. 
   
   
   
   

10. Depending on the chosen Source application in the Template you are using, you need to select the account. You can either use an existing account or create a new one. Click  to add a new account. For information on how to add a new account, refer to Appendix D: Supported Applications.

     

    For FTP, you need to select the event, FTP Account, and configuration details. For more information, click here.

    For File, you need to define the File Event. For more information, click here.

    For JMS, you need to define the JMS Event. For more information, click here.

    For Spazio MFT/s, you need to define the Spazio MFT Listener. For more information, click here.

11. Click Next to encrypt data. This screen appears only if the Template you are using is created using a file-based application.

12. Select the Is Source File encrypted? check box if the source file is in the encrypted format. The below fields appears. Provide the details in the corresponding fields.
    
    
    
    

    Key Name	The default value is the default.
    Key Manager	Select the Key Manager from the list. To create a Key Manager, visit Account > Security Settings. To create a Key Manager, click here.
    Private Key Password	Password of the key.
    Confirm Password	Confirm password of the key.
    Field Name	Description

13. Click Next to define the Destination application account. 

14. Once Destination application account setting is done, click Next to define the mapping.

15. Mapping screen appears only if the Template you are using is created for the Partner to Define the Mapping. 

16. Click Save & Exit to save the Transaction.

    This creates an Inbound Transaction.
    
    

    Next Step

    Activating a Transaction