Page tree
Skip to end of metadata
Go to start of metadata

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.

Prerequisites:

Ensure that you have created service for one of the following service types - File Event and FTP Event

To create an 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 Create New.

  4. Select the data format for which you want to create the inbound relationship and click Next



  5. On the New Inbound Relationship window, type the name and description of the new inbound relationship in the Name and Description.
  6. Select the following values in their respective fields:
    • EDI Standard Version
    • Association Assign Code
    • Transaction Set Code
    • Test/Production Indicator

      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.

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

    Option NameDescription
    No - Do not generate acknowledgmentsSelect this option if you don't want to generate an acknowledgment for the inbound messages sent.
    Yes - No error detailSelect this option to generate an acknowledgment for an inbound message sent without error details.
    Yes - With error detailSelect 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 NameDescription
      ReconcileSends acknowledgment for receiving the acknowledgment of an outbound message sent.
      TransformTransforms 997 EDI Transaction Set Code to another EDI Transaction Set Code.
      Reconcile and TransformSends 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 (b).


  8. Select Skip Compliance Check check box to skip compliance check for this document.
  9. Select a project from the Project for which you are creating an EDI inbound relationship.
  10. Expand Translation properties

  11. Under the section Receive Data From Trading Partner, select the type of event from Service Type from the following options - File Event and FTP Event.  
  12. 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.
  13. 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 the source file.
  14. Under section Translation1, select the mapping activity that you want to use, when this inbound relationship is used to parse the inbound EDI Message, from the Mapping.
  15. Under section Send Data to Backend Application, select the type and the name of the target activity from the Service Type and Service Name.
  16. Mode Type is a property that is defined while creating an inbound relationship. This property is used for creating the translated output file and it defines the basis on which this output file is created. This option is applicable only for File Target and LAN File Target. There are following five types of mode types:
      • Append: All the records are appended to the same target file.
      • Create: This will create a new target file for each input file.
      • Create Per Interchange: This will create a new file for each ISA segment. Suppose there are 5 ISA in a file then only 5 output files will be created at the target.
      • Create Per Group: This will create a new file based on the number of Groups (GS Segments) in the file. For 5 GS Segments, only 5 files will be created.
      • Create Per Transaction: This will create a new file based on the number of Transaction Sets (ST Segments) in the file. For 50 Transaction Sets, 50 separate files will be created.
      • CreatePerTransactionSetProcesscount: This will create a target file on the following three basis:
          • A separate file is created for each ISA.
          • A separate file is created for each GS.
          • A separate file will be created for the Transaction Set on the basis of "Transaction sets Process Count" set in Advanced Properties. Its default value is 2000 so a separate file will be created for every 2000 Transaction sets.

      Only following mode types are available if you select XML as your target schema:

      • Create Per Transaction
      • CreatePerTransactionSetProcesscount
      Steps 17 to 21 are applicable only for File and LAN File Target Service Types.
  17. 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%%.

     

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

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

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

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

  22. Select Encrypt Target File check box to send an encrypted target file. You can only encrypt File Target, FTP Target, and JMS Target EDI file types. Select an encryption activity from the Data Security in order to encrypt the target file.
  23. Provide the details in each translation. You can define only three translations in one inbound relationship.
  24. Expand Interchange properties

     

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

  26. Select Use Global Control No check box to use interchange control numbers defined in the trading partner activity of this inbound relationship.
  27. Type the last used control number in Last Used Control Number text box.
  28. Expand Group properties.

  29. Functional ID is automatically populated based on Transaction Set Code that you have selected.
  30. Define the sequence checking and control numbers in the similar way as defined in the Interchange Properties.
  31. Expand Document Properties.

  32. Define the values as defined in the Interchange properties.
  33. Expand Advanced Properties.



  34. 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.
  35. 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.
  36. Click Save. This creates an inbound relationship.
  • No labels