MsgReceived response

<ComIbmDni>
  :
  <Function>
    <DNF_O_FT>
      :
      <MsgReceived>
        <Request>
          :
        </Request>
        <Response>
          <ReceiveOptions>
            <PayloadType>value</PayloadType>
            <SignatureOptionSet>value</SignatureOptionSet>
            <ProductInfoOptionSet>value</ProductInfoOptionSet>
          </ReceiveOptions>
          <SignatureOptions>
            <DigestRef1>value</DigestRef1>
            <DigestAlgorithm1>value</DigestAlgorithm1>
            <DigestValue1>value</DigestValue1>
              :
            <DigestRef8>value</DigestRef8>
            <DigestAlgorithm8>value</DigestAlgorithm8>
            <DigestValue8>value</DigestValue8>
          </SignatureOptions>
          <SignatureList>
            <Signature>
              <Manifest>
                <Reference>
                  <DigestRef>value</DigestRef>
                  <DigestAlgorithm>value</DigestAlgorithm>
                  <DigestValue>value</DigestValue>
                </Reference>
                  :
              </Manifest>
            </Signature>
          </SignatureList>
          <ProductInfoOptions>
            <VendorName1>value</VendorName1>
            <ProductName1>value</ProductName1>
            <ProductVersion1>value</ProductVersion1>
            <VendorName2>value</VendorName2>
            <ProductName2>value</ProductName2>
            <ProductVersion2>value</ProductVersion2>
            <VendorName3>value</VendorName3>
            <ProductName3>value</ProductName3>
            <ProductVersion3>value</ProductVersion3>
          </ProductInfoOptions> 
          <ResponseRef>value</ResponseRef>
          <PayloadAttributes>
            <attr_1>val_1</attr_1>
              :
            <attr_n>val_n</attr_n>
          </PayloadAttributes>
          <AppHdr>
            <Hdr>application header folder</Hdr>
            <From>
              <Type>value</Type>
              <Id>value</Id>
            </From>
            <To>
              <Type>value</Type>
              <Id>value</Id>
            </To>
            <SvcName>value</SvcName>
            <MsgName>value</MsgName>
            <MsgRef>value</MsgRef>
            <CrDate>value</CrDate>
            <Dup>
              <Ref>value</Ref>
              <Info>value</Info>
            </Dup>
          </AppHdr>
          <Completion>
            <Code>value</Code>
            <Explanation>value</Explanation>
          </Completion>
        </Response>
        :
      </MsgReceived>
    </DNF_O_FT>
  </Function>
  :
</ComIbmDni>
Function
  • Rep. 1
  • This folder specifies information for FTM SWIFT services.
  • Contents:
    • DNF_O_FT (folder)
DNF_O_FT in Function
  • Rep. 1
  • This folder specifies information for the MSIF transfer service.
  • Contents:
    • MsgReceived (folder)
MsgReceived in Function.DNF_O_FT
  • Rep. 1
  • This folder specifies information for a MsgReceived scenario.
  • Contents:
    • Request (folder)
    • Response (folder)
Request in Function.DNF_O_FT.MsgReceived
  • Rep. 0…1
  • If this folder is specified, it must be identical to the request folder of the corresponding request.
Response in Function.DNF_O_FT.MsgReceived
  • Rep. 1
  • This folder specifies the information for a MsgReceived response to a received InterAct request primitive.
  • Contents:
    • ReceiveOptions (folder)
    • SignatureOptions (folder)
    • SignatureList (folder)
    • ProductInfoOptions (folder)
    • ResponseRef (field)
    • PayloadAttributes (folder)
    • AppHdr (folder)
    • Completion (folder)
ReceiveOptions in Function.DNF_O_FT.MsgReceived.Response
  • Rep. 0…1
  • This folder specifies options for the MsgReceived response.
  • Contents:
    • PayloadType (field)
    • SignatureOptionSet (field)
    • ProductInfoOptionSet (field)

    For more information, see Message receive options: MsgReceiveOptions.

ProductInfoOptions in Function.DNF_O_FT.MsgReceived.Response
  • Rep. 0…1
  • This folder specifies the product information for the MsgReceived response. It contains elements with names of the form:
    • VendorNamex (field)
    • ProductNamex (field)
    • ProductVersionx (field)
    where x represents a number from 1 to 3.

    For more information, see Product information options: ProductInfoOptions.

SignatureOptionSet in Function.DNF_O_FT.MsgReceived.Response.ReceiveOptions
  • string, 1...30 characters, rep. 0…1
  • If the request to which this response corresponds used a signature list, this is the name of the signature option set that is to be used to for the response. If the corresponding request did not use a signature list, this field is ignored.
SignatureOptions in Function.DNF_O_FT.MsgReceived.Response
  • Rep. 0…1
  • If the request to which this response corresponds used a signature list, this folder specifies the signature options to be used when sending the SendMsg response. If the corresponding request did not use a signature list, this folder is ignored.
  • This folder contains elements with names of the form:
    • DigestRefx (field)
    • DigestAlgorithmx (field)
    • DigestValuex (field)
    where x represents a number from 1 to 8.

    For more information, see Signature options: SignatureOptions.

  • The folders SignatureOptions and SignatureList are mutually exclusive.
SignatureList in Function.DNF_O_FT.MsgReceived.Response
  • Rep. 0…1
  • This folder specifies the signatures to be used when sending the MsgReceived response.
  • Contents:
    • Signature (folder)
  • A SignatureList folder can only be specified in a message but not in the FTM SWIFT configuration.
  • The folders SignatureOptions and SignatureList are mutually exclusive.
Signature in Function.DNF_O_FT.MsgReceived.Response.SignatureList
  • Rep. 1
  • This folder specifies the signature manifest to be used when sending the MsgReceived response.
  • Contents:
    • Manifest (folder)
Manifest in Function.DNF_O_FT.MsgReceived.Response.SignatureList.Signature
  • Rep. 1
  • This folder specifies the signature references used when sending the MsgReceived response.
  • Contents:
    • Reference (folder)
Reference in Function.DNF_O_FT.MsgReceived.Response.SignatureList.Signature.Manifest
  • Rep. 1…n
  • This folder specifies one signature reference to be used when sending the MsgReceived response. It contains elements with names of the form:
    • DigestRef (field)
    • DigestAlgorithm (field)
    • DigestValue (field)

    The meaning of the elements are equal to the ones in the SignatureOptions folder. For more information, see Signature options: SignatureOptions.

ResponseRef in Function.DNF_O_FT.MsgReceived.Response
  • string, 1...30 characters, rep. 0…1
  • The response reference, which is a string that is transmitted to the counterpart in the SwInt:ResponseRef field of the SNL primitive and used to uniquely identify a response. If a value is not specified for this field but a value is specified for the AppHdr.MsgRef or AppHdr.Hdr.AppHdr.BizMsgIdr field, this value is transmitted to the counterpart in the SwInt:ResponseRef field of the SNL primitive.
PayloadAttributes in Function.DNF_O_FT.MsgReceived.Response
  • Rep. 0…1
  • If a MsgReceived response contains a PayloadAttribute folder with attribute specifications, then the specified payload attributes are added to the SwInt:ResponsePayload element of an SwInt:HandleResponse primitive. For example, if an attribute with name myname and value myvalue should be added to the SwInt:ResponsePayload, then the following folder must be added to the MsgReceived response:
    <PayloadAttributes>
      <myname>myvalue</myname>
    </PayloadAttributes>
AppHdr in Function.DNF_O_FT.MsgReceived.Response
  • Rep. 0…1
  • This folder determines which type of application header is to be created in the resulting InterAct response, and the contents of that application header:
    ISO 20022 business application header
    Specify the application header as an XML structure within a Hdr folder. The first element of this XML structure must be a second AppHdr folder, and there must be no elements in the first AppHdr folder except the Hdr folder and the elements that the Hdr folder contains. For example:
      :
    <AppHdr>      [beginning of the first AppHdr folder]
      <Hdr>       [below is the beginning of the second AppHdr folder]
        <AppHdr xmlns="urn:iso:std:iso:20022:tech:xsd:head.001.001…>
          <CharSet>value</CharSet>
          <Fr>value</Fr>
          <To>value</To>
          <BizMsgIdr>value</BizMsgIdr>
          <PssblDplct>true</PssblDplct>
            :
        </AppHdr> [end of the second AppHdr folder]
      </Hdr>
    </AppHdr>     [end of the first AppHdr folder]
      :
    InterAct application header
    Specify an InterAct application header in either of the following ways:
    • Specify the application header as an XML structure within an Hdr folder. The first element of this XML structure must be a second AppHdr folder, and there must be no elements in the first AppHdr folder except the Hdr folder and the elements that the Hdr folder contains. For example:
        :
      <AppHdr>      [beginning of the first AppHdr folder]
         <Hdr>      [below is the beginning of the second AppHdr folder]
           <AppHdr xmlns="urn:swift:xsd:$ahV10">
             <MsgRef>Ref123</MsgRef>
             <CrDate>2011-08-24T09:00:00</CrDate>
             <From>
               <Type>DN</Type>
               <Id>o=ptsadejj,o=swift</Id>
             </From>
             <To>
               <Type>DN</Type>
               <Id>o=ptsadejj,o=swift</Id>
             </To>
             <Dup>
               <Ref>value</Ref>
               <Info>value</Info>
             </Dup>
           </AppHdr> [end of the second AppHdr folder]
         </Hdr>
       </AppHdr>     [end of the first AppHdr folder]
         :
    • Specify one or more of the following elements:
      • From (folder)
      • To (folder)
      • SvcName (field)
      • MsgName (field)
      • MsgRef (field)
      • CrDate (field)
      • Dup (folder)
      These elements are described in Application header options for an InterAct application header.
Completion in Function.DNF_O_FT.MsgReceived.Response
  • Rep. 1
  • This folder describes the result of the attempt to process the corresponding MsgReceived request.
    Note: The MPU attribute of a Completion element is restricted for internal use and cannot be interpreted or otherwise used by an application.
  • Contents:
    • Code (field)
    • Explanation (field)
Code in Function.DNF_O_FT.MsgReceived.Response.Completion
  • string, enumerated, rep.1
  • A field that indicates whether the receiving application was able to process the MsgReceived request:
    Ok
    The application was able to process the MsgReceived request. The MSIF transfer service is to use the contents of the MsgReceived response to create an InterAct server response primitive and pass it to the SAG.
    Failed
    The application was unable to process the MsgReceived request. The MSIF transfer service creates a response with an Sw:GlobalStatus folder that indicates this.
Explanation in Function.DNF_O_FT.MsgReceived.Response.Completion
  • string, 0...260, rep. 0…1
  • A textual description that provides additional information about a failed completion code (...MsgReceived.Response.Completion.Code). If the completion code is:
    Ok
    The MSIF transfer service ignores the contents of this field.
    Failed
    The MSIF transfer service rejects the message transfer with an Sw:GlobalStatus including a description supplied by the application, and responds to the SAG.