You can create an Inbound EDI Transaction by using prebuilt EDI Template bundled with Connect. Use this template to create an EDI Inbound Transaction.
Before you start creating, ensure that you have created an EDI Partner and Data Dictionary.

To create an Inbound EDI Transaction:

Click Transactions > Templates.
On the Templates screen, search EDI Inbound in the Search bar.
Click for the EDI Inbound Template to create an EDI Transaction.
Connect automatically populates the name and description for the Transaction, you can edit the name and description, if necessary.
Click Continue to define the Network and Partner.
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.
Click Next to define the EDI Configuration.

On the EDI Configuration window, do the following:

Select the EDI standard from the EDI Standard drop-down list. The available options are X12, HIPAA, and EDIFACT.
Select the version from the EDI Standard Version drop-down list. This list will have all the EDI versions you have created in the Data Dictionary. You will find 004010, 005010, and EDIFACT_D96A as a default EDI version.
Provide the assigned code in the Association Assigned Code text box.
On the basis of the selected EDI version, the list of transaction set codes is populated in the Transaction Set Code drop-down list. Select the code from the drop-down list.
Select the indicator from the Test/Production Indicator drop-down list. The available options are T-Test and P-Production.

In the Generate Acknowledgement field, select either of the following options to generate acknowledgment for the inbound messages sent.

Option	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.

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.

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	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.

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 (¡¡).

Select Skip Compliance Check check box to skip compliance check for this document.

In the Data encryption at rest field, select either of the following options.

Option	Description
Use Global Policy	Select 'Use Global Policy' to use Global Property value for Template.
Yes	Select 'Yes' to enable EAR for Template. It will not use Global Property value.
No	Select 'No' to disable EAR for Template. It will not use Global Property value.

Expand Translation Properties and Select the number of translation(s) you want to create from single EDI source. You can select the maximum number of translation(s) for single EDI source up to 3.

Expand Interchange Properties and select the type of sequence checking from the Sequence Checking drop-down list.

These are the available options:

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.

For Incremental and Chronological sequence checking, provide the values in the Use Global Control No check box and Last Used Control No text box. Select Use Global Control No check box to use the control number defined while adding a Partner else provide the last used control number in the text box. The value in the Last Used Control No text box is populated automatically.

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.
Expand Document Properties and define the values as defined in the Interchange properties.
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.

Click Next to define the Source application account.
Select the source application. The supported applications are FTP, File, JMS, and Spazio MFT/s.
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 C: 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.
Click Next to encrypt data. This screen appears only if the Template you are using is created using FTP and file-based applications.
Click Next to take the backup of source file as an archive file at runtime.
At Create Archive File step, select the Create Archive File (Optional) checkbox. This option will create an archive of the source file in the Archive folder for future access.
1. Type the folder name to archive the data in the Archive Folder Name. The Transaction will create an archive of the generated output files in the specified folder and location.
  
  You need to set the archival folder path in the abpm.solution.b2b.archive.basepath property (Administer > Update System Properties > Solution Properties > EDI Solution Properties > Default B2B Archiving Policy).
2. Click Auto Organised Archive Folder Based On Date checkbox to create folders in the format YYYY/MM/DD to the folder specified in the Archive Folder Name.
3. Click Add Archive File Time Stamp checkbox to add a time stamp to the archive files.
4. On clicking the check box, Time Stamp Format field appears. Select the date and time format from the drop-down lists.

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.

Field Name	Description
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.

Click Next to define the Destination application account. Select the supported destination applications which are Database, FTP, File, and JMS.
Click Next. The next screen differs depending upon the chosen Destination application.

For Database, you need to define the Database Target. For more information, click here.
For FTP, you need to select the action, FTP Account, and configuration details. For more information, click here.
For File, you need to define the LAN Target. For more information, click here.
For JMS, you need to define the JMS Target. For more information, click here.
Click Next to define the file generation policy details. This screen appears only for FTP and File destination applications.
Provide the details in the corresponding fields.
1. Browse to and select the file.
2. The value in the Mode Type is populated automatically.
3. Type the name of the destination file in the File Name text box to define the pattern of destination file name. In case, you want the destination file name to be same as the source file name, type $$baseInputFileName$$ as a value in the File Name text box. File Name can contain date-time stamp followed by % in the format: File_Name%%dd-mm-yy_hhmmssSS%%. For example, test_output%%01-01-2016_15-15-23%%.
4. Select Add Time Stamp check box to add the time stamp in the file. Select the date and time format from the Time Stamp Format drop-down list. This appends the selected date and time stamp in the name of the newly created file.
5. Select the Create Unique File check box to have a unique name in each destination file created. When this option is selected, a unique number is appended to the file name.
6. Type the extension of the file in the File Extension text box.
Click Next to select the target data format. This screen appears only for FTP and File destination applications.
Select the target data format and data layout for the Destination application. Target data format is the format in which you want the destination file, for example, text, excel. Target data layout is the layout of the destination file. You can either use the existing layout or create a new layout. To create a new layout, click .
Click Next to define the encryption. This screen appears only for FTP and File destination applications.
Select Want to encrypt target file? check box if you want to encrypt the destination file. On selecting the check box, new fields appear. Provide the details in the corresponding fields and click Next.
Define the Mapping between the fields of the selected source and the destination application.
Click Save & Exit to save the Transaction.
This creates an Inbound Transaction and is listed in the Transactions screen.
Next Step
Activating a Transaction

Browser not supported