Creating Inbound Relationship for Non-EDI Data

You can create an inbound relationship to define the rules for processing an inbound message. This section helps you in creating an inbound relationship for Non-EDI data.

To create a Non-EDI inbound relationship:

1. Go to Develop > Solutions > B2B > Relationships. 

2. Select the Trading Partner activity for which you want to define the inbound relationship from the left menu and then click Inbound Relationship tab.

   

3. Click CreateNew.

   

4. Select Others(Non-EDI) and click Next.

   
   
   

5. Type the name and description for the Inbound relationship in the Name and Description.
6. Select the project from the Project for which you want to create a non-EDI inbound relationship.
7. Select the format of the data receiving from the partner from the Sender Format Type.
8. Provide the type of the inbound document in the Document Type.
9. Type the document version of the inbound document in the Document Version.
10. Select the type of event that you want to use to look up the inbound data from the Event Type. The supported event types are File, Mail, JMS, and FTP.
11. Depending on the chosen Event Type, select the event from the Event Service. This is the event that you have configured to look up the inbound data.
12. Select Decrypt Source File check box to decrypt an incoming encrypted EDI file and then select a decryption activity from the Data Security in order to decrypt source file. 
13. Select Partner Identification Required check box to identify a partner based on the content. You need to define a partner identifier. The event and the Partner Identifier is same for another trading partner also. 

    1. Select the partner identifier from the Partner Identifier or click to create a new partner identifier.

       Using Partner Identifier, you can define the two XPath expression to filter the inbound data.
       

       For information on how to create a Partner Identifier, refer to Creating Partner Identifier.

    2. Type the value of Identifier1 XPath and Identifier2 XPath (defined in selected Partner Identifier) in the Identifier1value and Identifier2 value.

14. Select the process flow to process inbound data from the Process Flow.

    Ideally, you should select default B2BI_Default as a process flow. In case you select another process flow, the logs will not be generated.

15. Select the mode for processing Non-EDI file from the Processing Mode. The available options are Transform and Route.

    Transform: This will transform and route your non-EDI file to HL7 formats.

    Route: This will move your non-EDI file from one location to another.

16. Select the mapping activity to map the fields of inbound data with the fields of the target data from the Mapping.

    Mapping is applicable only if you select Transform option as a Processing Mode.

17. Select the target type from the Target Type. Depending upon the selection of the Processing Mode (Transform or Route), the target type options may differ.

18. Select the target activity from the Target Service.

    Steps 19 to 22 are applicable only for File, LAN File, and FTP Target types.

19. Type the name of the target file in the File Name. This field is enable for File, FTP, LAN File, and Mail Target type.

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

    If you have selected Mail Target as Target Type then you can dynamically override the file name. For more information, refer to Dynamically Overriding File Name.

    
    

20. Select the format of the time stamp from Time Stamp Format of the time stamp format. This appends the selected date and time stamp in the name of the newly created file. 

    In case, you provide date-time stamp in the File Name and select the format from the Time Stamp Format then both time stamps will get appended to the target file name.
21. Select Create Unique File check box to create a target file with a unique name. When this option is selected, a unique number is appended to the file name.

22. Type the extension of the target file in the File Extension.

23. Select Encrypt Target file check box to encrypt the target file and then select the encryption key to encrypt the file from the Data Security. 

    Click here to know about Data Security.
24. Select Create Archive File check box to create an archive of the generated output file. This creates a direct copy of the generated output file in the Archive Target as mentioned in an inbound relationship for future access. You have two strategies to create an archive file:
    1. Default: For default strategy type, do the following:
       1. Provide the path to the archived file in the Archive Folder Name. Provide the folder path with the path provided in the abpm.solution.b2b.archive.basepath property (Administer > Update System Properties > Solution Properties > EDI Solution Properties > Default B2B Archiving Policy). 
       2. Select Auto Organised Archive Folder Based On Date check box to create folders in the format YYYY/MM/DD on the path specified in the Archive Folder Name.
       3. Select the time stamp in the Archive File Time Stamp.
          
          
    2. Create Target Activity: For this option, you can further select the Archive Service Type and Name.
    3. Select View Plain Text Archived File check box to view the encrypted files generated at the archival location in a plain text. This option appears if you have selected Encrypt Target File check box. 

25. Select Send Error Notification check box to receive the error notifications.

    If you select this option, you need to do some additional settings. For more information, refer to Receiving EDI Notification.

26. Expand Advanced Properties.
    
    

    For information on Advanced Properties, refer to Changing Advanced Properties.
27. Click Save. This creates your inbound relationship.

Dynamically Overriding File Name

In Non-EDI relationship, you can dynamically override the file name while using Mail Target as a target type. Follow the below steps to dynamically override the file name:

1. In Data Mapping activity, create a context variable and define the filename. For example, set-context variable ('filename_variable','Dynamic') in data mapping.
   Where, filename_variable is the context variable and Dynamic is the value of the file name which you want to use for the mail target filename.
   
   

2. Now, in Non-EDI relationship, enter the File Name value as $$filename_variable$$.
   Where, filename_variable is the context variable you set in the Data Mapping activity.
   
   

3. In case, you want to dynamically override the mail target file name in a Process flow, then set the File Name value as $$filename_variable$$ in Mail Target.