Search

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

You can create an outbound relationship for each outbound message type and define the rules for processing an outbound message. For example, if you are sending two message types, say 810 and 850, then you need to create one outbound relationship for 810 and another for 850.

This section helps you in creating an outbound relationship for EDI data. 

Prerequisites 

Ensure that you have created service for one of the following service types - File TargetFTP TargetLAN File Target, and Spazio Target.

To create an EDI Outbound Relationship:

  1. Go to DevelopSolutions B2B Relationships.
  2. Select the EDI Trading Partner for which you want to define an outbound relationship from the left menu and then click Outbound Relationship tab.



  3. Click Create New.

     

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

  5. On the Basic properties, do the following:


    1. Type the name and description of the new outbound relationship in the Name and Description.
    2. Select the value from the EDI Standard Version, Associated Assigned Code, Transaction Set Code, and Test/Production Indicator. 

      The combination of Associated Assigned Code, EDI Standard, EDI Standard Version, Transaction Set Code, and Test/Production Indicator must be unique in each outbound relationship.
       
      If you want to create a custom acknowledgment then the combination of Associated Assigned Code, EDI Standard, EDI Standard Version, Transaction Set Code, and Test/Production Indicator should be same as the default outbound relationship that you have created earlier.
       
      For more information on how to create custom acknowledgments, refer to Creating Custom Acknowledgement For Inbound Relationship For EDI Data.
    3. Select whether you want to receive the acknowledgment for the sent messages from the Expect Acknowledgement.
    4. Type the number of hours elapse before an expected functional acknowledgment is considered as overdue in the Hours Overdue. This is applicable only if you select Yes in the Expect Acknowledgement.
    5. Select Use Global Transaction Control No check box to use the control number defined in the trading partner activity of this outbound relationship.
    6. Type the last used transaction control number in the Last used Transaction Control No.
    7. The value in the Responsible Agency Code is automatically filled based on the selected Transaction Set Code.
    8. Select Skip Compliance Check check box, if you do not want to execute a compliance check on your document. 
    9. Select the project for your activity from the Project.

  6. Expand Routing properties and do the following:


    1. Select the type of event that you want to execute for an outbound relationship from the Service Type.
    2. 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 inbound relationship, as events created for an outbound relationship can be used for outbound activities only.


    3. Select Decrypt Source File check box, if your incoming EDI file is encrypted. 
    4. Select the private key to decrypt an incoming EDI file from the Data Security. This option is enabled, if and only if, Decrypt Source File check box is selected.
    5. Select the Content Based Routing check box to select the partner (to whom you send the data) based on the content of the outbound source file. For example, based on the value of a particular field of the source file you want to decide to which trading partner outbound message should be sent. Content-based routing is used when data of one source file should go to multiple trading partners.
    6. Select the partner identifier activity from the Select Field. This option is enabled, if and only if, Content Based Routing check box is selected. 

      You can select from an existing Partner Identifier or create a new one. For information on how to create a Partner Identifier, refer to Configuring Partner Identifier.
    7. Type the value(s) of the input data field in Define Value. Separate multiple values by a comma (,).

  7. Expand Translation properties and do the following:



    1. Select the mapping activity for this outbound relationship from the Mapping.

      Mapping is not required; if you are creating an outbound relationship for sending an acknowledgment.
    2. Select the type in which you want to send data to the partner from the Service Type.
    3. Select the name of the target from the Service Name.

    4. Type the name of the target file in the File Name to define the pattern of target file name. In case, you want the target file name to be same as the source file name then type $$baseInputFileName$$ as a value in the File Name. 

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

       

    5. Select the date and time format from the Time Stamp. 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.
    6. Select the 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. 
    7. Type the extension of the file in the File Extension. For example, if you want the name of the target file similar to OutboundTarget<Date><Time>.edi then you need to type OutboundTarget in the text box and select date and time format from the respective drop-down list. 

      Here
      <Date> is the date when the output file is created.
      <Time> is the time when the output file is created.
      When Target File Name Pattern is defined

      Separate files are created for each message type. For example, there are two outbound EDI messages (810 and 997) for the same trading partner then two files will be created. One for 810 and another for 997.

      When Target File Name Pattern is not defined

      • Only one output file is created for all outbound messages of the same trading partner. For example, there are two outbound messages (810 and 997) for the same trading partner and Target File Name Pattern is not defined in both the outbound relationship then both messages are written in the same output file.
      • The output file name remains the same as defined in the File/FTP Target activity selected in the Outbound relationship.
    8. 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 more about Data Security.
    9. Select the mode of transfer from the Batch Mode. If No is selected, the outbound messages are sent in real time immediately after its processing. If Yes is selected, the outbound messages are queued in the outbound queue. All the queued messages are sent to the respective partners at a particular interval. For this, you can use a calendar event.
    10. Select the event activity from the Schedule drop-down list. This option is enabled, if and only if, Yes is selected in the Batch Mode. This can be a Calendar event.
    11. 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 outbound 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. 

  8. Expand Group Envelope properties and do the following:



    1. The value is automatically filled in the Functional ID based on the Transaction Set Code that you have typed in the Basic properties node.
    2. Type the sender and receiver ID in the Sender ID and Receiver ID.
    3. Select the Use Global Control No check box to use the group control number defined in the trading partner activity of this outbound relationship.
    4. Type the last used group control number in the Last Used Control Number.
       

      The values in the Responsible Agency Code and Envelope Version text boxes are populated automatically.
    5. Select the Sequence from Group check box, if you want to follow the same sequence of the group.
    6. Select the format of the control number from the Format. This option is enabled, if and only if, Sequence From Group check box is selected.

  9. Expand ISA Envelope properties and do the following:


    1. Select Use Existing option, if you want to use an existing ISA outbound envelope and then select the required ISA outbound envelope from the drop-down list.

    2. Select Create New option if you want to use a new ISA outbound envelope and then click . For information on how to create the ISA outbound envelope activity, refer to Creating ISA Outbound Envelope.

  10. Expand Advanced Properties. For more information, refer to Changing Advanced Properties.

  11. Click Save.

    If you are creating the outbound relationship for EDIFACT message, there will be UNB Envelope Properties instead of ISA Envelope Properties. For more information, refer to Creating UNB Outbound Envelope.

    This creates an outbound relationship.

  • No labels