Application header options: AppHdrOptions

Name of the folder that contains the elements that specify these options in a request: AppHdr
The payload of an InterAct primitive that contains a business message might contain an application header. An application header provides information that is used by the applications that are to route and process the business message, and can be of either of the following types:
  • ISO 20022 business application headers head.001.001.01 and head.001.001.02
  • InterAct application header
The application header (AppHdr) elements of an MSIF request, response, or notification specify the contents of an application header:
For a SendMsg scenario
The SWIFT service determines which type of application header can or must be used. The MSIF transfer service uses options specified in the AppHdr folder of the request to create an application header of the appropriate type and insert it into the payload of the resulting InterAct primitive (these options can be specified only in a request, not by means of an option set):
To generate an ISO 20022 business application header
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 other elements in the first AppHdr folder besides the Hdr folder and the elements that the Hdr folder contains. For example: 
  :
<AppHdr>   [this is the beginning of the first AppHdr folder]
 <Hdr>
  <AppHdr xmlns="urn:iso:std:iso:20022:tech:xsd:head.001.001.01"...>
     [the line above is the beginning of the second AppHdr folder]
   <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]
  :
To generate an 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>  [this is the beginning of the first AppHdr folder]
 <Hdr>
  <AppHdr xmlns="urn:swift:xsd:$ahV10">
    [the line above is the beginning of the second AppHdr folder]
   <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.
For a MsgReceived scenario
The MSIF transfer service removes all application headers from the payload of the received InterAct primitive and puts each of them, unaltered and unvalidated, into a separate AppHdr folder in the ReceiveDetails.AppHdr.Hdr folder of a MsgReceived notification (if automatic response mode is used) or MsgReceived request (if flexible response mode is used). For an InterAct application header, it also includes the elements described in Application header options for an InterAct application header. It then passes the notification or request to the receiving application.