Configuring the EDI Encoder Service for SWIFT Outbound Messages

Edit online

The EDI Encoder service determines which envelope will be used on the document. If translations are specified in an envelope, the service determines which map to use. For SWIFT outbound messages you need to configure five parameters to allow the outbound message to be sent correctly. See EDI Encoder Service for more information.

To configure the EDI Encoder service, you must specify settings for the following fields in the GPM that match the values you configured in the outbound envelope:

AccepterLookupAlias
ReceiverID
SenderID
ReceiverIDQual
SenderIDQual

You need to set the sender and receiver variables based on the desired source and destination for the outbound message. These variables also match the corresponding values in the envelope, except that the envelope allows wildcards (which will match documents encoded with any value for that variable), whereas the value used in the EDI encoder must always be the full eight-character identifier and three-character branch code of the desired source and destination.

Or, if you are editing the EDI Encoder BPML, you need to include these parameters and values, where for xxx you substitute the values set up in the outbound envelope:


    <operation name="EDI Encode">
      <participant name="EDIEncoder"/>
      <output message="EDIEnc_In">
        <assign to="AccepterLookupAlias">xxx</assign>
        <assign to="ReceiverID">xxx</assign>
        <assign to="SenderID">xxx</assign>
        <assign to="ReceiverIDQual">xxx</assign>
        <assign to="SenderIDQual">xxx</assign>
        <assign to="." from="*"/>
      </output>
      <input message="EDIEnc_Out">
        <assign to="." from="*"/>
      </input>
    </operation>