Dynamic Receiver Determination using Soap header

Hi ,
I am trying to use a field in SOAP Header to determine the receivers dynamically.
1, Using XPATH gives me only values in the Payload and not the SOAP header. Is it possible to pull the value from the SOAP header to the payload and then do dynamic receiver determination.
2. Using Context Object is it possible to transfer the value of the field in SOAP header to variable header Xheadername1 and then use it to determine the receiver. I am having problems in passing the value of the field in soap header to XHeadername1.
Any help is appreciated and points will be awarded.
Joe Vellaiparambil

Hi Joe,
This is a good blog by William, hope this is helpful.
/people/william.li/blog/2009/07/30/how-to-read-soap-header-information
Let us know if you need more information.
Regards,
Neetesh

Similar Messages

Multi Mapping using condition & Dynamic Receiver determination – Used XSLT Mapping

Dear Experts,
     I am struggling to identify an error on the Technical Routing. Firstly according to my scenario, I receive an XML file with multiple PO's and I have to split the file to 2 different target messages. and also according to the source payload I have to send the file to 2 different receivers. first receiver is ABAP Proxy to the back end system and the 2nd one is to a file location. I have used XSLT to split the message into 2 target message type and I have used a XSLT mapping for receiver determination. Does any one have any idea of what I am doing wrong.
Note: some time I will only be able to fill in on target message.
I have attached my XSLT message split mapping with this post, please let me know if you have further question.
Your help is more appreciated.
Advance Thanks,
Pradeep
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:sap="http://www.sap.com/sapxsl" version="1.0">
<xsl:variable name="vFlag"/>
<xsl:variable name="vPONUM" select="POTRACKING/Lines[1]/PONumber"/>
<xsl:template match="/">
    <ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
      <ns0:Message1>
        <ns1:MT_Tracking xmlns:ns1="http://www.findel-education.co.uk/axapta">
          <xsl:for-each select="POTRACKING/Lines">
            <sap:call-external class="ZCL_VNAP_OBJECTS" method="CHECK_PO_EXIST">
              <sap:callvalue param="IP_EBELN" select="string(PONumber)"/>
              <sap:callvariable name="vFlag" param="EP_BOLEAN" type="string"/>
            </sap:call-external>
            <xsl:if test="$vFlag = 0">
              <Lines>
                <DDate>
                  <xsl:value-of select="DespatchDate"/>
                </DDate>
                <PONumber>
                  <xsl:value-of select="PONumber"/>
                </PONumber>
                <POLine>
                  <xsl:value-of select="POLine"/>
                </POLine>
                <QTY>
                  <xsl:value-of select="Quantity"/>
                </QTY>
                <VendorMaterial>
                  <xsl:value-of select="VendorMaterialNumber"/>
                </VendorMaterial>
                <AccountRef>
                  <xsl:value-of select="AccountReference"/>
                </AccountRef>
                <ConsignNumber>
                  <xsl:value-of select="ConsignmentNumber"/>
                </ConsignNumber>
                <CarrierURL>
                  <xsl:value-of select="CarrierURL"/>
                </CarrierURL>
                <ConsignURL>
                  <xsl:value-of select="ConsignmentURL"/>
                </ConsignURL>
              </Lines>
            </xsl:if>
          </xsl:for-each>
        </ns1:MT_Tracking>
      </ns0:Message1>
      <ns0:Message2>
        <ns2:MT_Tracking xmlns:ns2="http://www.findel-education.co.uk/ecc/ax/po/ftp">
          <xsl:for-each select="POTRACKING/Lines">
            <sap:call-external class="ZCL_VNAP_OBJECTS" method="CHECK_PO_EXIST">
              <sap:callvalue param="IP_EBELN" select="string(PONumber)"/>
              <sap:callvariable name="vFlag" param="EP_BOLEAN" type="string"/>
            </sap:call-external>
            <xsl:if test="$vFlag = 1">
              <Lines>
                <DDate>
                  <xsl:value-of select="DespatchDate"/>
                </DDate>
                <PONumber>
                  <xsl:value-of select="PONumber"/>
                </PONumber>
                <POLine>
                  <xsl:value-of select="POLine"/>
                </POLine>
                <QTY>
                  <xsl:value-of select="Quantity"/>
                </QTY>
                <VendorMaterial>
                  <xsl:value-of select="VendorMaterialNumber"/>
                </VendorMaterial>
                <AccountRef>
                  <xsl:value-of select="AccountReference"/>
                </AccountRef>
                <ConsignNumber>
                  <xsl:value-of select="ConsignmentNumber"/>
                </ConsignNumber>
                <CarrierURL>
                  <xsl:value-of select="CarrierURL"/>
                </CarrierURL>
                <ConsignURL>
                  <xsl:value-of select="ConsignmentURL"/>
                </ConsignURL>
              </Lines>
            </xsl:if>
          </xsl:for-each>
        </ns2:MT_Tracking>
      </ns0:Message2>
    </ns0:Messages>
</xsl:template>
</xsl:stylesheet>

Hi Hareesh,
Please find my determination in the XSLT below, I am using enhanced receiver determination.
<xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:sap="http://www.sap.com/sapxsl" xmlns:p1="http://sap.com/xi/XI/System" xmlns:ns="urn:sap-com:document:sap:idoc:messages" version="1.0">
<xsl:variable name="vFlag"/>
<xsl:variable name="vAX" select="0"/>
<xsl:variable name="vSAP" select="0"/>
<xsl:variable name="vBoth" select="0"/>

<xsl:template match="/">
    <xsl:for-each select="POTRACKING/Lines">
      <sap:call-external class="ZCL_VNAP_OBJECTS" method="CHECK_PO_EXIST">
        <sap:callvalue param="IP_EBELN" select="string(PONumber)"/>
        <sap:callvariable name="vFlag" param="EP_BOLEAN" type="string"/>
      </sap:call-external>
      <xsl:choose>
        <xsl:when test="$vFlag = 0">
          
          <xsl:variable name="vAX" select="$vAX + 1"/>
        </xsl:when>
        <xsl:when test="$vFlag = 1">
          
          <xsl:variable name="vSAP" select="$vSAP + 1"/>
        </xsl:when>
      </xsl:choose>
    </xsl:for-each>
    <xsl:if test="$vSAP > 0">
      <xsl:if test="$vAX > 0">
        <xsl:variable name="vBoth" select="$vBoth + 1"/>
        <xsl:variable name="vSAP" select="0"/>
        <xsl:variable name="vAX" select="0"/>
      </xsl:if>
    </xsl:if>
    <xsl:if test="$vBoth > 0">
      <p1:Receivers>
        <Receiver>
          <Service>
            <xsl:text>BS_AXAPTA_TST</xsl:text>
          </Service>
        </Receiver>
        <Receiver>
          <Service>
            <xsl:text>BS_ECQCLNT300</xsl:text>
          </Service>
        </Receiver>
      </p1:Receivers>
    </xsl:if>
    <xsl:if test="$vAX > 0">
      <p1:Receivers>
        <Receiver>
          <Service>
            <xsl:text>BS_AXAPTA_TST</xsl:text>
          </Service>
        </Receiver>
      </p1:Receivers>
    </xsl:if>
    <xsl:if test="$vSAP > 0">
      <p1:Receivers>
        <Receiver>
          <Service>
            <xsl:text>BS_ECQCLNT300</xsl:text>
          </Service>
        </Receiver>
      </p1:Receivers>
    </xsl:if>
</xsl:template>
</xsl:transform>

Dynamic receiver Determination for Sync Scenario??

Hello Experts,
I have a SOAP -> Xi -> R3 sync scenario i,e, R3 to send back response to SOAP client.
Also I need the Dynamic receiver determination.
When I try to create the Interface Mapping, I get the error:
"Interface modi are different. "
Source interface MI_My_sync_iface is synchronous.
Target interface ReceiverDetermination | http://sap.com/xi/XI/System is asynchronous
I coud find few threads on forum related to this but i think there is no clear solution provided.
I do not wanna use BPM.
Please suggest.
Thanks in Advance!
Appropriate point will be awarded.

> So when I try to define a interface Mapping using a Sync interface as Source and Async interface as target, XI does not allow me to do so.
You are getting this error because in Interface mapping when you use sync source then it generates request and response tab so if at target side if you put anync interface then definetly it will go into error. You have to make both the interfaces as sync.
BTW, after getting the message in R3, how are processing the message? Are you using sync proxy??
You can solve the problem by creating one additional message interface of type inbound-asyn. Use this additional Message interfce in your Interface Determination. And create additional Receiver Agreement to deliver the message to it's destination.
Note: When you careate additional Interface Determination then you have to chose the response message interface (Sync message interface which returns the response from R3) as a source.
Regards,
Sarvesh

How to get a dynamic receiver determination based on a table an SAP PI ABAP Stack

Hello folks,
currently I get stuck dealing with a problem about the receiver determination. Let me first describe the Problem: We are using to different SAP ERP- backend system in our test enviroment. But only of this systems is marked as current "actuall" test system. Every once in a while we need to switch between these two systems and mark the other one as the actual test system.
This is the point were it get's a little bit time consuming for me: We have about 50 interfaces were I need to change the receiver from test system A to test system B or vice versa. So I thought about creating a more dynamic way to determine the actual test system:
Therefore I have created a table on the ABAP stack of our PI (7.31 double stack) with just one field that holds the current test system. Now I would like to create a dynamic receiver determination where I call the RFC-function RFC_READ_TABLE. But how can I acess a table from the grapchical mapping of the pi which is stored on the PI?
Is there mybe another fundamental way to retrieve the actuall test system within the mapping?

You can go for enhanced receiver determination, where in you can determine the receiver system using a graphical mapping.
Now in that graphical mapping, use the standard function " RFC Look up" and make a call to bapi and get the actual receiver system.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40b64ca6-b1e3-2b10-4c9b-c48234ccea35?QuickLink=index&…
Step by Step guide to Explain Enhanced Receiver Determination - Application Server Infrastructure - SCN Wiki

Dynamic receiver determination for synchron interface

Hello everybody,
I want to use dynamic receiver determination for a synchron scenario.
The problem is, that the interface 'ReceiverDetermination' (http://sap.com/xi/XI/System SAP BASIS 7.00) is a asynchron interface.
This leads to an error when activating the Interface-Mapping (synch source Interface -> asynch destination Interface ReceiverDetermination)
Is there a way to use the dynamic receiver determination for synchron interface?
Thanks a lot,
Thomas

Hi Thomas,
I guess your scenario is not possible ASIS, since XI doesn't support 1:n for sync interfaces (and even if your mapping condition reduces it to 1:1, actually it is still 1:n, since your receiver list is unbounded).
Theoretically, you could make it work with BPM, though.
But I've never worked with a Receiver Determination Step reading from an enhanced receiver determination in ID (though there should be no problems).
Use sync async bridge, then use receiver determination step to obtain the receiver from an enhanced Receiver Determination. Pay attention that this enhanced receiver determination is a dummy one, using a mapping from your async abstract interface to the ReceiverDetermination interface. Once your mapping has determined the receiver, the enhanced receiver determination will return that receiver to the Receiver Determination step in the BPM. Then use this receiver in the sync send step (in mode receiver from receiver list, not from context).
The receiver determination of the actual sync send step may be a standard one, with the several receivers there (even if there are several there, at the moment of the sending, only one will be used).
Maybe it will work, maybe not.
Just try it.
Regards,
Henrique.

Dynamic Receiver Determination [W/O using BPM] Sync interface

I have been exploring options w.r.t. performance sensitive service interface.
This has following issues :
1. Gets a org code looking up instance and route the msg. accordingly to an RFC and get response back.
2. Prominent answer would be Enhanced receiver determination step but that doesnt work in sync case.
3. Classic Receiver Determination needs the condition to be evaluated in source msg. which is not going to happen.
4. Use BPM i designed one but performance its not all acceptable it has a round trip of 10Sec.
are there any ways to overcome this ?

Hi Bujji,
can you explain the point 1.
<i>1. Gets a org code looking up instance and route the msg. accordingly to an RFC and get response back.</i>
Thanks and Regards,
Himadri
null

Dynamic Receiver Determination (Enhanced RD doesn't attend)

Guys,
we have a BPM scenario where we need to determine the receiver of a message based on some conditions which are known only in the runtime of the BPM. In particular, we want to determine the receiver of Message A based on a condition checked over Message B. We can't change the payload of Message A (XSD determined by client).
As you can notice, using Enhanced RD or Standard RD with condition won't solve my problem (since both of these methods only use Message A's payload to determine its own receiver).
Do you have any sugestions on how to accomplish this?
Thanks in advance,
Henrique.

Vijaya,
thanks for your reply.
I don't know if you understood the whole problem.
I'm already using a Switch step. In each of the branchs I have a Async Send Step to send Message A and the condition of the Switch is based on Message B. But the problem is on configuration.
When I create the routing objects, if I create two interface determinations from the same receiver determination, any of the send steps will try to send the message to both receiver systems, since I cannot define a condition in receiver determination itself, because the condition doesn't deppend on the sent message payload.
Regards,
Henrique.

Receiver determination using substring in filename in file adapter

Hi
In PI 7.11 I would like to determine the receiver based on a substring in the filename in a file receiver adapter. I am planning on using a context object but am having trouble entering the correct code in the "Right Operand" field.
I have tried selecting Context Object = Filename http://sap.com/xi/XI/System/File and entering this code in the Right Operand: "contains(substring('_4000_'))"   and an "=" in the as I am looking for a filename, that contains the substring "_4000_".
I would like to avoid using an extra map and using Dynamic Configuration, as I thing this would be the most elegant way of fixing it
Is there a way of referencing the context object if I chose xpath in stead of context object?
MIkael

Hi Mikael,
I have the same scenario like you , could you please tell me about the condition how to you use XPath for Context Object
I need to check the file name and according to that I have to put the file in the different directory.
Source File: XXXX_IN_xxxx
                   XXXX_PH_xxxx
I have to check the 7th and 8th Char of the file and according to that I have to place the file in the folder
Target: DGE008\IN\Inbound
            DGE008PH\Inbound
I don't know how to used the XPATH for file and specially how to use the substring in that.
Could you please help.
Thanks,

Problem in testing SOAP receiver adapter using SOAP UI

Dear Experts,
I'm trying to test my SOAP receiver adapter as mentioned in the blog http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/21844. [original link is broken] [original link is broken] [original link is broken] But, my request from ECC proxy keeps failing in XI communcation channel monitor. I've configured my receiver adapter http://ip:8080/mockSoapHTTPBinding and kept the authentication as NONE. Can any of you suggest?
ip - is my system ip shown in ipconfig.
mockSoapHTTPBinding - is the path.
Thanks.

What is the error of the messages? Are the messages leaving the SOAP adapter?
Please try both:
1. Go to Runtime Workbench -> Component Monitoring -> Adapter Engine -> Test message. Then, execute the message directly without the intermediate of the Proxy sender. This will allow you to check only the receiver SOAP.
2. Please use the TCPGateway tool attached from the note below. It will be a "man-in-the-middle" between the target WS and the Receiver SOAP channel, tracking the whole HTTP/SOAP message. Check if the message is well-formed.
[Note 856597 - FAQ: XI 3.0 / PI 7.0 / PI 7.1 SOAP Adapter|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=856597]
under question "Q: How can I trace the whole message?"

Dynamic Interface Determination Using the same Business System

Folks...
Does anyone have any good ideas on how to build a scenario where the same business system is used, but the interface mapping needs to be dynamic? I have a single JMS sender and 40 different message types on one side, and 40 ABAP Proxies on the other. The two solutions I see are as follows:
1. Create 40 separate JMS Senders with 40 different sender agreements
2. Create 40 Business Services for the same ECC system and utilize XPath expressions to support conditionally selecting an interface mapping
Neither of these in my mind is a great solution, does anyone have any others?
Mahalo,
Jonathan

Hi, I came cross the same problem on my current project, now I have following solution:
Create a number of JMS sender adapters, they all connect to same queue, but each JMS sender adapter only pick up particular type of message based on one JMS message property value. The message provider will be responsible to set the property value when they send message into the queue.
In JMS sender adapter, Parameter Tab -> Advanced Tab ->check Set Adapter-Specific message Attributes ->check Specify Additional JMS Message Properties (Maxmum of 10) -> Add Property name, e.g. "MsgType"
->Processing Tab -> Input Value in "JMS Message Selector", e.g. MsgType='WorkOrder'
after above setup, this adapter will only pick up messages that with "MsgType" Property value "WorkOrder"
For each type of adapter, you will create a JMS sender adapter and repeat the steps above, just put on the different Property value.
This approach will have number of Integration Scenarios, hence will have number of Sender Agreement.
I have tested the approach and it works.
Liang

Use of range in case of XPATH for receiver determination.

Hi Experts,
I need to achieve the following using standard receiver determination.
The material number in the source message structure has to lie within a perticular range and that should decide the receiver of the message.
For example:
MT_SRC
|---- Ele1
|----
MaterialNo.
If MaterialNo is between 100000100 and 100001000 then it should be sent to BS_TGT1 else it should be sent to BS_TGT2.
Is it possible to achieve this using the standard conditional receiver determination using XPATH and if yes, how exactly?
Regards,
Amol

Hi Amol,
I think its possible. Never tried though for a range.
Go through this link and check out what is described under the section "Notes Regarding the Use of XPath Expressions"
http://help.sap.com/saphelp_nw04/helpdata/en/43/a513f2632c332ce10000000a11466f/frameset.htm
I am not sure whether it will work for two conditions though, i.e. for a range( Greater than 100000100, less than 100001000).
Just try and let us know.
Regards,
Sanjeev.

Reading custom SOAP header with XHeaderName1

Hello Experts,
I have a SOAP to File scenario and I am trying to do dynamic receiver determination by looking at the SOAP request header info. I am adding a custom field (System_ID) that I want rules to run against in Receiver Determination..
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:*******************">
<soapenv:Header>
<System_ID>100</System_ID>
</soapenv:Header>
<soapenv:Body>
</soapenv:Body>
</soapenv:Envelope>
In the Receiver Determination I have multiple rules using SOAP context object to XHeaderName1 = the System_ID (100) to pass the message to the right system at runtime according to the System_ID.
In the SOAP sender channel I have Set Adapter-Specific Message Attributes and Variable Transport Binding checked. I also have the variable name System_ID in the first Variable Header (XHeaderName1).
In the SOAP sender Conversion Parameters I have Do Not Use SOAP Envelope and Keep Headers checked, as well as nosoap=true in the SOAP request URL.
I'm getting the System ID to show in XI in sxmb_moni in the Header but no where do I see it being used with XHeaderName1.
Am I using XHeaderName1 right? If not could you advise as to how XHeaderName1 should be used?
My requirement is to read system ID from Header, not payload.
Thank you!
Tim

I was able to find a solution to my problem.
I created a basic senario below to test:
1.A basic Asynchronous scenario is created using a SOAP sender adapter to 2 possible flat file receivers.
2.The SOAP sender channel will have the option u201CDo Not Use SOAP envelopeu201D checked and SOAPUI URL will have u201C&nosoap=trueu201D added to the end.
3.The receiver system name will be stored in the WS-Addressing u201CActionu201D field sent from SOAPUI.
4.Two ABAP mappings are created. One mapping will extract the system number from the WS-Addressing u201CActionu201D field. The other mapping will extract just the body of the SOAP message to send along. Using regex and string manipulation in the ABAP mappings we can reuse the mappings for any SOAP message.
5.Enhanced (Extended) Receiver Determination is selected and interface mapping using system/XI ReceiverDetermination service interface is used to capture the receiver system.
While this is a solution is not the best, it is a solution. Upon research I found a recent SAP Note 1385579 talking about implementing a SAP delivered generic SOAP Sender AXIS handler com.sap.aii.axis.soap.HeaderExtractionHandler to extract SOAP Header elements and place in message attributes. I will be trying this out.

Handling Dynamic pay loads using a Single URL

Hi All,
I need to integrate SAP R/3 to a Third party web portal using SAP XI. Portal will communicate with 15+ messages. The third party portal is asking me to provide a single URL to send tje XML Messages. the problem is each message is having different structure from other. We have to recognize the message by seeing the header. The header (root node) will contain message number (like Msg01, Msg02, Msg03 and so on...) , . They have provided us a XSD file, which contains all the messages as complex type , which i can able to upload as External Definitaion. But in the message interface only one message i can use at a time as output message. i,e msg01 or msg03 or msg03 etc... . But the third part portal will send any of message out of 15 messages. So how can i generate single URL to accept dynamically any of 15 message. Also i am getting a confusion which sender adapter to use . Can anybody guide me how to handle this situation?

Hi,
you can use one java mapping in the advanced receiver determination as I mentioned. Which does not need to have a unified message format.
Enhanced Receiver Determination
Use
You use an enhanced receiver determination to have a mapping program determine the receivers of the message dynamically at runtime. Instead of creating the receivers in the receiver determination manually, you assign a mapping to the receiver determination and this returns a list of receivers at runtime.
A typical usage case is if you do not yet know the names of the receivers at configuration time. In this case, you can define a mapping program, for example, which reads a list of receivers from a table or from the payload of the message at runtime.
After Java Mapping you have already assigned the 15+ different messages to the right receiver you intend to send the request. You can just carry on with normal configuration from here, perform mapping if you need in the interface determination step. etc. Since you don't have one unified Message format for the 15 different messages, you probably need implemented all mappings in Java. Because message mapping does not work, since you have only one outbound interface from Portal (15 different requests are labeld with same interface name). Nevertheless, with java mapping it is not a problem to check the root node at first and carry out the wished mapping.
Summarize here a bit:
1. defined ONE Message Outbound interface e.g. MI_OUT_Portal for different Portal request (you could define this interface based on some random MT, does not matter at this point)
2. define one Interface mapping which map the MI_OUT_Portal to Receivers, Receivers is located in SAP BASIS (standard XI content from SAP)
In this interface you should have to refer one java mapping which read the XML payload from portal request and find out who is the receiver. This should be quite easy. You could even configure it in one external Database which msg goes to which receiver and find out it in the runtime.
3. You need mapping from different message typ to the wished receiver, these 15 request messages will probably has 15 different inbound interfaces, you will need 15 different interface mapping if every request message has to be mapped before it can pass through to the receiver application. These mappings could be done in one java mapping again.
4. configure Receiver Determination with advanced RD in Configuration with the Interface mapping which implemented in step2
5. configure Interface determination and receiver agreement
regards,
Hai

Dynamic receiver file name C1.yyMMdd.C2

PI Experts,
Is it so difficult to acheive in SAP PI? I hope I made the requirement clear.
Scenario: Sender AS2 adapter --> PI --> Receiver File (NFS) Adapter. Just a file pass through, no mapping
Requirement: Irrespective of sender adapter in a file pass through scenatio where we wont read the file (payload just contains the flat file), I want to delivery the same file with the naming convention C1.yyMMdd.C2 where C1, C2 are constants and yyMMdd is cuurent date. So sum up, need to have current date in a file name on receiver side with out reading the payload.
1) Variable substituation works on if we are are receiving the variable value from the payload.
2) Looks like ASMP works only same filename from a sender to a receiver file adapter, because if you are not using sender adapter or using sender adapter without selecting ASMP - File Name, there no way you can receive DynamicConfiguration under SOAP Header. Please correct me if I am worng.
3) Running the OS command after file processing to re-name the file, may be its the last resort, but I would expect and would like to do in PI.
What is the best possible solution?
- Riya Patil

Hi Shabarish
Please find below the my UDF code:
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
String SourceFileName = "C1." + a + ".C2";
String TargetFileName = SourceFileName;
conf.put(key, TargetFileName);
return TargetFileName;
And mapping trace:
<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 54, 45, 53(:main:, row:1, col:3) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:187) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:174) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:118) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.GeneratedMethodAccessor1102.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy182.processFunction(Unknown Source) at sun.reflect.GeneratedMethodAccessor12384.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:254) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 54, 45, 53(:main:, row:1, col:3) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:157) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 54, 45, 53(:main:, row:1, col:3)(:main:, row=1, col=3) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 54, 45, 53(:main:, row:1, col:3) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2787) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2832) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) -
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 54, 45, 53(:main:, row:1, col:3) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2787) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2832) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) ... 4 more</Trace>
<Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_MM_Lockbox_Filename_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 54, 45, 53(:main:, row:1, col:3)</Trace>
<Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_MM_Lockbox_Filename_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 54, 45, 53(:main:, row:1, col:3) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:73) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.GeneratedMethodAccessor1102.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy182.processFunction(Unknown Source) at sun.reflect.GeneratedMethodAccessor12384.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:254) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 54, 45, 53(:main:, row:1, col:3) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:187) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:174) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:118) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.GeneratedMethodAccessor1102.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy182.processFunction(Unknown Source) at sun.reflect.GeneratedMethodAccessor12384.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:254) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 54, 45, 53(:main:, row:1, col:3) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:157) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 54, 45, 53(:main:, row:1, col:3)(:main:, row=1, col=3) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 54, 45, 53(:main:, row:1, col:3) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2787) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2832) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) -
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 54, 45, 53(:main:, row:1, col:3) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2787) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2832) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) ... 4 more</Trace>
<Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>
</Trace>
Thanks for helping me on this.
- Riya Patil

Requirement in receiver determination

Hi
We are on XI 3.0 SP18 and have the following requirement -
I have two receivers - A and B for a message - asynchronous mode . I want the message to reach receiver B only if it has successfully reached A - ( technically successful - as in any async scenario ) .
How can this be achieved ? Can enhanced/dynamic receiver determination solve my requirement ? Please elaborate .
Thanks in advance for your answers/solutions.

You have to use a BPM model to control to check the response from Receiver A and make a decision to send the message to receiver B.
Also keep in mind a BPM model will additional concerns around the performance of integration scenario, so please make sure these requirement is completly necessary.
In other way you can accomplish the same by using an intermediate sotrage such as JMS storage and JDBC storage etc.
Thanks

Dynamic Receiver Determination using Soap header

Similar Messages

Maybe you are looking for