You can create an inbound relationship for each inbound message type. For example, if you are receiving two message types, say 810 and 850, then you need to create one inbound relationship for 810 and another for 850.
This section helps you in creating an inbound relationship for EDI data.
Ensure that you have created service for one of the following service types - File Event and FTP Event.
To create an EDI inbound relationship:
Go to Develop > Solutions > B2B > Relationships.
Select the Trading Partner activity for which you want to define the inbound relationship from the left menu and then click Inbound Relationship tab.
Click Create New.
Select the data format for which you want to create the inbound relationship and click Next.
This EDI Standard, EDI Standard Version, Transaction Set Code, and Test/Production Indicator combination is unique for an inbound relationship. When you receive an inbound message, this combination is used to lookup the inbound relationship for that message.
Select the option from the Generate Acknowledgement to generate acknowledgment for the inbound messages sent. Following are the available options:
|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.|
Expand Translation properties.
The list of services appears for the selected service type. Select the name of the service from the Service Name.
|Ensure that selected event is not used in the outbound relationship, as events created for an inbound relationship can be used for inbound activities only.|
Only following mode types are available if you select XML as your target schema:
|Steps 17 to 21 are applicable only for File and LAN File Target Service Types.|
Under section Target File Name Pattern, type the name of the target file in the File Name. In case, you want the target file name to be same as the source file name, type $$baseInputFileName$$ as a value in 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%%.
Select Add TimeStamp check box to append the date and time stamp in the name of the file created. If left unchecked, the target file will be overwritten every time a new input file is processed.
Select the format of the time stamp from the Time Stamp Format. This option is enabled only if you select Add TimeStamp check box.
In case, you have not defined Target File Name Pattern then target file is created with the name as defined in the target activity.
In case, you provide date-time stamp in the File Name and select the format from the Time Stamp Format drop-down list then both time stamps will get appended to the target file name.
Select Create Unique File check box, if you want each target file created by this activity should have a unique name. When this option is selected, a unique number is appended to the file name.
Type the extension of the target file in the File Extension text box.
In case, you have selected FTP Target in Target Type then at target a new file is always created for every input file.
Expand Interchange properties.
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
No Sequence checking is done on control number.
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 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 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.
Expand Group properties.
Expand Document Properties.
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.
|For more information about Advanced Properties, refer to Changing Advanced Properties.|