Skip to Content
There are couple of weblogs already posted explaining as to how to use Variable Substitution for ‘File Name Schema’. In this weblog i will explain as to how we used the variable substitution feature for ‘Target Directory’. One of the requirements in my project is to post the output-file to a particular folder. The folder format is as follows, /usr/sap/target(SID of receiver system)/output The SID of receiver system, changes as we move from development to staging, production etc. So we had to make it dynamic.  For dev box the folder would be, /usr/sap/targetX10/output For staging box it would be, /usr/sap/targetX20/output and so on… So you can see that only a part of the folder is dynamic. We achieved that by using a variable which refers to the attribute of the message header, in our case it was,message:receiver_service(in our case the receiver_service is also the SID)  The figures below illustrates as to how went about doing it, imageimage Couple of points to note,  1) Variables can refer to attributes of message header, by adding the prefix message:The message header attribute supported are,sender_partysender_servicereceiver_partyreceiver_serviceinterface_nameinterface_namespacemessage_idmessage_id_hex 2) Variables can refer to an element in XML schema, by adding the prefix payload:
To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Michal Krawczyk
    hi Sameer,

    be careful: receiver service is not
    SAP SID it’s just a side that receives messages…
    in your case it might be SID but not always 🙂


    1. Former Member Post author
      Hey Michal

      U r too quick mate, i was thinking off editing it over the weekend, but i missed out. But you are right as always 🙂 in my case it is the SID.



Leave a Reply