Versions Compared

Old Version 2

changes.mady.by.user Avinash Kumar

Saved on

compared with

New Version Current

changes.mady.by.user Avinash Kumar

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Corrected links that should have been relative instead of absolute.

A Transaction is created by using a Template. Therefore, before creating a Transaction, ensure that you have created a Template.

...

  1. Provide the name and description of the Transaction. The name and description of the Transaction are generated automatically based on the selected Template. You can edit the Transaction name and description that can be up to 48 and 300 characters long.

  2. Click Continue.

  3. Based on the template created either for X12 or EDIFACT, the screen differs.

     

    Expand
    titleX12
    1. In the Group Envelope Properties, provide the Sender ID and Receiver ID in the text boxes.
    2. Select the Use Global Control No check box to use the group control number defined while adding a Partner.

    3. Type the last used group control number in the Last Used Control Number text box. 

    4. The value in the Responsible Agency Code and Envelope Version are populated automatically based on the Transaction Set Code selected in the Template.
    5. Select the Sequence from Group check box to follow the same sequence of the group. On selecting the check box, Format drop-down list appears. Select the format of the control number from the Format drop-down list.
    6. In the ISA Envelope Properties, either select the existing ISA Envelope or click  to create the new one. On the Create EDI ISA Envelope window, do the following: 



      1. Type the name and description for the ISA Outbound Envelope activity in the Name and Description text boxes.
      2. Authorization code qualifier: Required field, Maximum two characters, default 00.
      3. Authorization code. Optional alphanumeric field, Minimum one character, Maximum 10 characters.
      4. Security code qualifier: Required field, Maximum two characters, default 00.
      5. Security code: Optional alphanumeric field, Minimum one character, Maximum 10 characters.
      6. Interchange SenderID qualifier: Required field, Maximum two characters.
      7. Interchange SenderID: Alphanumeric field, Minimum one character, Maximum 15 characters.
      8. Interchange ReceiverID qualifier: Required field, Maximum two characters.
      9. Interchange ReceiverID: Alphanumeric field, Minimum one character, Maximum 15 characters.
      10. Interchange Standards Identifier: Required field, Maximum one character.
      11. Select the version from the Interchange VersionID.
      12. Select Use Global Interchange Control No check box to use the interchange control number defined in the outbound Partners of this ISA outbound envelope activity. 
      13. Interchange Control No: Required field, Maximum nine characters. No need to define if using Global Control No.
      14. Select Yes from the Acknowledgement drop-down list to receive an acknowledgment for the messages sent.
      15. Select the indicator from the Test/Production Indicator drop-down list. 
      16. Provide the required separator in the Element Separator and Sub-element Separator. Select Hex Format check box for the hexadecimal values.  
      17. Provide the single separator in the Segment Terminator. Select Hex Format check box for the hexadecimal values. This character indicates the end of an EDI segment. In an X12 interchange, the segment terminator is defined as the character in the last character position of the ISA segment. 
      18. Provide the single separator in the Repetition Separator. Select Hex Format check box for the hexadecimal values.The repetition separator is used to separate segments that repeat within a transaction set.

      19. Select an appropriate segment line break from the Segment line break text box to display your EDI file data in a block format. Following are the available options:

        Option Name
        Description

        CR-Carriage Return

        Appends \n as a segment terminator.

        LF-Line Feed

        Appends \r as a segment terminator.

        CR LF-Carriage Return/Line Feed

        Appends \r\n as a segment terminator.


      20. Click Save.


    Expand
    titleEDIFACT

    In the UNB Envelope Properties, either select the existing UNB Envelope or click  to create the new one. On the Create EDI UNB Envelope window, do the following:


    1. Type the name and description for the EDI UNB Envelope in the Name and Description text boxes.
    2. Syntax ID: Required field, Maximum four characters. This element identifies both the level of the syntax and the agency controlling the syntax, for example, UNOA.

    3. Syntax Version: Required field, Maximum one character. This element indicates the version number identified in the syntax identifier element. 

    4. Sender ID: Required field, Minimum one character, Maximum 35 characters. This element identifies the sender of the data.
    5. Sender ID Qualifier: Optional field, Maximum four characters. This element refers to the sources for the codes of the interchanging partner's identifiers. For example, a qualifier of ZZ indicates that the partners mutually defined the codes.
    6. Reverse Routing Address: Optional field, Minimum one character, Maximum 14 characters. This element contains a return address specified by the sender of the message. The recipient may want to include this address in any response messages to this sender to facilitate internal routing.
    7. Receiver ID: Required field, Minimum one character, Maximum 35 characters. This element identifies the recipient of the data.
    8. Receiver ID Qualifier: Optional field, Maximum four characters. This element refers to the sources for the codes of the interchanging partner's identifiers. For example, a qualifier of ZZ indicates that the partners mutually defined the codes.
    9. Receiver Routing Address: Optional field, Minimum one character, Maximum 14 characters. This element contains the address specified by the recipient of the message that the sender is to include. The recipient uses this address for routing messages received by the sender.
    10. Select Use Global Interchange Control No check box to use the interchange control number defined in the outbound Partner of this UNB envelope activity. 
    11. Interchange Control No: Required field, Maximum nine characters. No need to define if using Global Control No.
    12. Receiver Password: Optional field. Password as agreed between the communicating Partners.
    13. Password Qualifier: Optional field, Maximum two characters.This element indicates the qualifier for the Recipient reference password.
    14. Application Reference: Optional field, Minimum one character, Maximum 14 characters. This element identifies the application associated with the messages in the interchange assigned by the sender.
    15. Priority Code: Optional field, Maximum one character. This element indicates the processing priority for the interchange requested from the sender.
    16. Acknowledgment Requested: Optional field, Maximum one single digit number. This element indicates a request for an acknowledgment of the interchange from the recipient. The value can be 0 - ACK not required, 1 - Acknowledgement requested, or 2 - Indication of receipt.
    17. Communications Agreement ID: Optional field, Minimum one character, Maximum 35 characters.
    18. Test/Production Indicator: Specify whether the interchange is in test mode or production mode.
    19. Component Element Separator: This is an EDI delimiter used to separate components.
    20. Element Separator: This is an EDI delimiter to use to separate elements.
    21. Decimal Notation: The recipient ignores the character transferred in this position. This segment ensures upward compatibility with earlier versions of the syntax.
    22. Release Indicator: This character is used to indicate that the text following contains one of the characters used as a composite, data, or segment separator. Therefore, this character is released from its conventional usage in this instance.
    23. Reserved for future use/Repetition Separator: Character to use to separate a group of repeated elements.
    24. Segment Terminator: This is an EDI delimiter to indicate the end of a segment.

    25. Segment Line Break: Select the segment line break to be used with the segment terminator. It can be either None, CR (carriage return), LF (line feed), or CR LF (carriage return/line feed).

      Option Name
      Description

      CR-Carriage Return

      Appends \n as a segment terminator.

      LF-Line Feed

      Appends \r as a segment terminator.

      CR LF-Carriage Return/Line Feed

      Appends \r\n as a segment terminator.



  4. Click Next to define the Destination application account. 

  5. Depending on the chosen Destination application in the Template you are using, you need to select the account.

  6. Click Next to encrypt data. This screen appears if the Template is created using a file-based application.

  7. Select the Want to encrypt target file? check box to encrypt the destination file. The below fields appears. Provide the details in the corresponding fields.



    Field NameDescription
    Key ManagerSelect the Key Manager from the list. To create a Key Manager, visit Account > Security Settings. To create a Key Manager, click here.
    Key NameThe default value is the default.


  8. Click Next to define the routing rule. This screen appears for Content Based Routing. 

  9. Type the value of the field specified in the Application ID, in the content routing while defining the Template.

  10. Click Next to define the mapping. This screen appears only if the Template you are using is created for the Partner to define the mapping. 

  11. Click Save & Exit to save the Transaction.

    This creates an Outbound Transaction.

    Next Step

    Activating a Transaction