SendMsg response

<ComIbmDni>
  :
  <Function>
    <DNF_O_FT>
      <SendMsg>
        <Request>
          :
        </Request>
        <Response>
          <Reference>value</Reference>
          <SwiftRef>value</SwiftRef>
          <SnFInputSeq>value</SnFInputSeq>
          <SnFInputTime>value</SnFInputTime>
          <ResponseRef>value</ResponseRef>
          <PayloadType>value</PayloadType>
          <PayloadAttributes>
            <attr_1>val_1</attr_1>
               :
            <attr_n>val_n</attr_n>
          </PayloadAttributes>
          <RequestSignatureList>value</RequestSignatureList>
          <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>
            <ReasonList>
              <Reason>
                <Code>value</Code>
                <Value>value</Value>
                <Explanation>value</Explanation>
                <Parameter1>value</Parameter1>
                <Parameter2>value</Parameter2>
                <Parameter3>value</Parameter3>
                <Parameter4>value</Parameter4>
                <Parameter5>value</Parameter5>
                <Parameter6>value</Parameter6>
                <Parameter7>value</Parameter7>
                <Parameter8>value</Parameter8>
                <Parameter9>value</Parameter9>
                <Parameter10>value</Parameter10>
              </Reason>
            </ReasonList>
            <Explanation>value</Explanation>
          </Completion>
        </Response>
      </SendMsg>
    </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:
    • SendMsg (folder)
SendMsg in Function.DNF_O_FT
  • Rep. 1
  • This folder specifies information for a SendMsg scenario.
  • Contents:
    • Request (folder)
    • Response (folder)
Request in Function.DNF_O_FT.SendMsg
  • Rep. 1
  • This folder contains the elements of the original SendMsg request. These elements are described in SendMsg request.
Response in Function.DNF_O_FT.SendMsg
  • Rep. 1
  • This folder specifies the contents of a SendMsg response.
  • Contents:
    • Reference (field)
    • SwiftRef (field)
    • ResponseRef (field)
    • RequestSignatureList (folder)
    • PayloadType (field)
    • PayloadAttributes (folder)
    • SnFInputSeq (field)
    • SnFInputTime (field)
    • AppHdr (folder)
    • Completion (folder)
Reference in Function.DNF_O_FT.SendMsg.Response
  • bin.hex, 48 characters (hex double byte rep. of MQBYTE24), rep. 1
  • The MSIF reference, which is an ID generated by MSIF transfer service that uniquely identifies a scenario. It is identical to the MQMD.MsgId of the corresponding SendMsg request. Use this reference to identify this scenario, for example, when issuing a list or cancel command, or when querying the message warehouse.
    Note: Because the MSIF reference is identical to the MQMD.MsgId of the request and is used to uniquely identify the request, the application must ensure that the MQMD.MsgId of each request is unique. Requests with duplicate MQMD.MsgIds are rejected.
SwiftRef in Function.DNF_O_FT.SendMsg.Response
  • string, 1…50 characters, rep. 0…1
  • A message reference, set by the SIPN, that uniquely identifies an InterAct message. An application can use this reference to check for duplicate messages. The format is that of SwGbl:SwiftRef, which is described in SWIFTNet Link: Interface Specification.
SnFInputSeq in Function.DNF_O_FT.SendMsg.Response
  • int, 0…n, rep. 0…1
  • If the message was sent via an input channel, this field indicates the SnF input sequence number used for the channel transfer. An application can use this number to find out the sequence in which messages were sent to SWIFT.
SnFInputTime in Function.DNF_O_FT.SendMsg.Response
  • string, 24 characters, rep. 0…1
  • For a request primitive that was sent using SnF delivery mode, this field indicates the date and time that the primitive was stored by SWIFT for subsequent processing. It has the format: 
    ddrr:yyyy-mm-ddThh:mm:ss
    where:
    dd
    Two digits that identify the SWIFT database.
    rr
    A two-digit number from 01 to 99 that identifies the run. This number is incremented after each system recovery. After it reaches 99, it rolls over to 01.
    yyyy
    Year.
    mm
    Month.
    dd
    Day.
    hh
    Hour.
    mm
    Minute.
    ss
    Second.
    For example: 
    0102:2011-12-31T15:54:13
ResponseRef in Function.DNF_O_FT.SendMsg.Response
  • string, 1…30 characters, rep. 0…1
  • A string, specified by the responding application and transferred to the counterpart, that uniquely identifies this response. This applies to real-time transfers only; for SnF transfers, this element is not used.
PayloadType in Function.DNF_O_FT.SendMsg.Response
  • string, 1…256 characters, rep. 0…1
  • This specifies the type of the response payload as defined by the SWIFT service.
PayloadAttributes in Function.DNF_O_FT.SendMsg.Response
  • Rep. 0…1
  • If the SwInt:ResponsePayload element of an SwInt:ExchangeResponse primitive specifies one or more attributes, the corresponding SendMsg response includes a PayloadAttributes folder that contains one element for each of these attributes. For example, if an SwInt:ResponsePayload element specifies the attributes dt="ZIP-Base64" and type="swift.snf.ackresponse", the PayloadAttributes folder of the corresponding SendMsg response would look like this:
    <PayloadAttributes>
  <dt>ZIP-Base64</dt>
  <type>swift.snf.ackresponse</type>
</PayloadAttributes>
RequestSignatureList in Function.DNF_O_FT.SendMsg.Response
  • XML subtree, rep. 0…1
  • This element contains the signature list of the corresponding InterAct request primitive. The signatures in this list are Sw:SignatureList XML structures in the after-sign form. For more information, see SWIFTNet Link: Interface Specification.
AppHdr in Function.DNF_O_FT.SendMsg.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.SendMsg.Response
  • Rep. 1
  • This folder specifies the result of a SendMsg request. For more information, see Completion.
    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)
    • ReasonList (folder)
    • Explanation (field)