XSL Interface Mapping - Recover name of file

Good evening,
I am using XSL interface mapping to convert a file to idoc and I need to recover the name of the file to insert it in the idoc.
I have been looking for in XSL manuals for an answer and I haven't find it.
How can I recover the name of the file that I'm trying to map to idoc?
Best Regards,
Nuria

hi,
right after you create an IDOC in your XSLT mapping
create another mapping - message mapping (this time IDOC to IDOC)
and put it into your interface determination
put the code from my blog:
/people/michal.krawczyk2/blog/2005/11/10/xi-the-same-filename-from-a-sender-to-a-receiver-file-adapter--sp14
and you will have the name
Regards,
michal

Similar Messages

  • File-soap-file : problem in getting Interface Mapping

    Hi
    I am doing file to Soap to file scenario by using BPM. But I have several methods in Web Service.I am using one method for my requir in that I have to trigger by using CharSoapIn and CharSoapout interfaces .
    I have created
    <i>Message mappings</i> 1 Sen_File_MT to CharSoapIn and 2. CharSoapout to Rec_File_MT.
    <i>Interface Mapping</i> 1. File to Soap and 2. Soap to File respectively.
    I know I have to create 3 receiver determinations.
    Problem is I am not finding out the Interface Mapping where I am configuring from BPM to Business Service.
    I am using Business Service I feel that I am going wrong some where  in adding the "Services".
    Anyone help me out..what would be the problem
    Thanks
    Shankar.

    Yes I am using Abs interfaces and I am following below block
    /people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
    Fig 13 I am using separatly FileRequest_MT to CharSoapIn and FileResponse_MT to CharSoapOut.
    But here instead of RFC I am using SOAP also I am using Business Service intead of Business System.
    I am unable to fine the Interface Mapping from BPM to Soap or BMP to File
    Thanks
    Shankar

  • Error in interface mapping  when calling a xsl file

    Hi,
    Using XSLT I am calling another XSL file  into my main xsl file.I have added both the zip files into  a single zip file and imported in my imported archive.But when i do the interface mapping testing i get an error 'Transformer configuration exception occurred when loading XSLT xslt1.xsl'.
    What should i do?

    Dear Sidhvin,
    First test your XSLT in the editor (for example STYLUS STUDIO). In Editor run your mapping and have a look whether you are getting the required result.
    if you are  getting the required result of XSLT then use it in the scenario and after importing this activate it and then run the interface.
    hope this time you will not get any error
    Thanks
    Sandeep
    PS: if helpful Reward points

  • Use of Orders05 Interface mapping & XSLT mapping file for Orders03 IDOC

    Hello Experts,
    In a scenario we are sending Purchase orders and Purhase Order change from SAP to SNC through XI.
    Currently Orders03 IDoc is used and standard mapping for Orders03 XSLT is used.
    Now the requirement is to use the same IDOC (Orders03) but
    - XSLT mapping (OrdersOrders05_ReplenishmentOrderNotification) and
    - Interface Mapping (OrdersOrders05_ReplenishmentOrderNotification_01) of Orders05.
    What changes would be necessary
    - On SAP side,
    - in the XSLT mapping, and
    - On XI side.
    Thanks in advance,
    Suraj

    Hi Suraj,
    First compare ORDERS03 IDOC and ORDERS05 IDoc structures,if both structures are same then u no ned to chnage the XSL it will work fine.
    If any chnages in ORDERS05 Idoc then u have to adjust XSLT as per ORDERS05 IDOC.
    test interface mapping first and let me know if any error.
    Regards,
    Raj

  • How to get  the name of Interface Mapping ?

    Beside the information given by setParameter() i like to know the name of the "Interface Mapping". Does somebody know how to get this information ?

    Hi Frank,
    not really there are a lot of information in there but <b>not the name of the interfacemapping</b>. By iterating through the xiContext given by setParameter() i got the following output:
    <u>As defined in StreamTransformationConstants:</u>
    MessageClass = RQ
    VersionMajor = 003
    VersionMinor = 000
    ProcessingMode = A
    MessageId = B9EFFFC05A7411D9CA2F00306E5DA806
    RefToMessageId = 00000000000000000000000000000000
    ConversationId = null
    TimeSent = 20041230150856
    Interface = ORDERS.ORDERS05
    InterfaceNamespace = urn:sap-com:document:sap:idoc:messages
    SenderParty = null
    SenderPartyAgency = null
    SenderPartyScheme = null
    SenderService = BS_QGDBW
    ReceiverName = msgIF_ORDERS_DATARIVER
    ReceiverNamespace = http://prototype.com/xi/test
    ReceiverParty = null
    ReceiverPartyAgency = null
    ReceiverPartyScheme = null
    ReceiverService = BS_QGDBW
    MappingTrace =
    <u>Additional Information found:</u>
    Direction = 0
    MessageID = B9EFFFC05A7411D9CA2F00306E5DA806
    BusinessSystemSender = BS_QGDBW
    BusinessSystemReceiver = BS_QGDBW
    SenderNamespace = urn:sap-com:document:sap:idoc:messages
    SenderName = ORDERS.ORDERS05
    QueueID = null
    SenderSystem = BS_QGDBW
    ReceiverSystem = BS_QGDBW
    These are interresting informations but nothing to find out which interface-mapping-name has called the execute-method....
    Regards,
    Urs

  • Creating Map IDs using HTM File Name

    Is it possible to create Map IDs using the File name of the HTM, instead of its Topic Title?

    While Generating Map IDs, we get an ID along with a Map # for each HTM in the CSH.
    For Example, I have a HTM in my CSH with the following Details:
    Topic Title - Access Masks
    File Name - admpr00001.htm
    Now when I create a Map ID for this page. I can customise the Map ID by setting any/all of the three options: - 'Prefix Map IDs with', 'Make Uppercase' and 'Start Numbering with'. But the Map ID is generated only based on the Topic Title.
    Like - ebACCESS_MASKS 1000   where, eb is the set prefix.
    Is it possible for me to create a MAP ID using the File Name. In this case, as ebadmpr00001 1000?
    Hope I am clear .

  • XSTL is not displaying in interface mapping

    I've created a XSLT transformation, next I've zipped *.xslt file into *.zip and imported (it is visible in Imported Archives). When I click "Display program" icon, I see popup with valid code.
    In message mapping I want to use this imported transformation. When I'm selecting XSL and then when I'm trying to select any XSLT I'm not able because nothing is displayed. When I tried to use drag and drop technique to paste my imported xslt I got an message:
    "IA_XSLT_PROXY_req has no program", where IA_XSLT_PROXY_req is a name of imported archieve.
    Any idea what is going on?

    Hi,
    Did you selected the option of XSL Mapping in Interface Mapping. Please select it from drop down list from where you select the ABAP MApping / Java Mapping. It will be in left side of lower window in Interface mapping. Please check it out.
    For more info about it you can refer to this weblog.
    /people/aashish.sinha/blog/2008/01/17/step-150-by-150-step-simple-approach-for-xslt-mapping
    Regards
    Aashish Sinha
    PS : reward points if helpful

  • ERROR WHILE USING XSLT MAPPING IN INTERFACE MAPPING

    Hi,
      We are using an xslt mapping in our scenario but while i load the XSLT mapping in the interface mapping i get a message :
    Transformer configuration exception occurred when loading XSLT
    sorce interface :outbound and asyncronous.
    mapping : XSLT mapping (imported as a zip file)
    target interface: abstract,asyncronous.
    The xslt runs well in standalone and its well formed and there is no name space issue.
    please help if any one has faced such a situation while using XSLT mapping.
    regards,
    Anirban.

    Hi Anirban
    When you say it runs well <i>standalone</i> what exactly do you mean? Which XSLT processor are you using to run it? There are subtle difference between XSTL processors that can sometimes result in incompatibilities. For instance, I have seen XSLTs run correctly in XMLSpy but incorrectly (or at least slightly differently) in XI.
    Regards,
    Thorsten

  • XSLT Interface Mapping Not Found For HTTP Response

    NW 04's SR 10, RFC => XSL => HTML
    The scenario transforms data from R/3 into XML using XSLT and sends it to a 3rd party vendor wrapped inside a field of an HTML form via the HTTPS adapter.  XSL was used for this instead of standard MessageMapping to meet the customer's needed for the XML data to be delivered in an untransformed structure, including their DTD declaration, so they could parse it upon receipt.
    The outbound process is successful and the data is posted to the customer's database.  Upon receipt, they send back a simple HTML form containing the success/failure in an H1 tag and our submitted XML data in the Body tag.
    The problem is that due to the use of an XSL as the outbound mapping XI does not have a cached message structure to which it can map the response and thus throws the <b>Interface mapping .... does not exist in runtime cache</b> message.  I do not feel this is a cache problem since I've cleared the XI cache, CPACache and anything else I've read as well as verified that the outbound mapping exists in the XI Cache list.  I honestly feel I'm just missing a necessary piece to tell XI how to map the HTML response message back to the RFC Sender.
    I have attempted numerous ideas, one of which included the use of the same RFC structure as the inbound and outbound MessageType so that a Response mapping could be specified but a NullPointerException was thrown in the mapping step since the response was of a completely different structure.
    My question is how to handle the return data when using XSLT to create the outbound structure dynamically to prevent runtime errors in XI?
    Thanks in advance,
    Lane

    Thanks for the quick response Bhavesh.
    I figured out the response mapping option after I posted the question and also thought of using XSL to handle the response but I ran into a few other issues relating to my limited experience with XSLT that is preventing me from completely solving this.
    The response is a plain HTML file structured as:
    < html >
      < body >
        < h1 >Success/FailureMessage< /h1 >
        < br >
        Record Created
        < br >< br > XML Data: <?xml version="1.0" encoding="utf-8"?><!DOCTYPE ....
      < /body >
    < /html >
    where the actual XML data posted to the client system is embedded in the HTML body.  Therefore the response is not well-formed XML and fails on parsing but also contains another XML message within the HTML structure that throws off parsing as well.  Do you know XSLT well enough to get around this?
    What about writing a Java function that just reads the incoming information but in doing this how do I go about mapping back to the RFC?  Can I get ahold of the XI API somewhere to instantiate the RFC Objects dynamically?
    Thanks again,
    Lane

  • About interface mapping

    what are there case about interface mapping?
    i knew that the following:
    outbound to inbound
    abstract to abstract.
    what else the case?

    Hi joy zheng  ,
    These r the details about interface mapping :
    Interface Mappings
    You can define mappings for an interface pair (source and target interface) by using message interfaces and message types in the Integration Repository.You can also define the corresponding mappings when the source or target interface is an IDoc, an RFC, or another interface connected by an adapter.
    When defining mapping programs for request, response, or fault messages, the definition is first separated from the interfaces that reference the corresponding message types. Furthermore, you can reuse a message type for multiple interfaces. This means that the simple definition of a mapping program is not sufficient to establish a connection (that is based on the assignment of outbound and inbound interfaces).
    This role is undertaken by the interface mapping:
    &#9679;     An interface mapping specifies the corresponding mapping programs for request, response, or fault messages for a selected interface pair. You use an interface mapping to register mappings for an interface pair.
    &#9679;     You can also specify multiple mapping programs to be executed one after the other in the case of requests and responses for an interface mapping.
    You can also define multiple interface mappings for the same interface pair, to provide multiple variants in the Integration Repository. At configuration time, the customer can select the appropriate mapping in an interface determination and save it in the Integration Directory
    Use :
    Interface mappings register your mapping program for an interface pair in the Integration Repository. If you require a mapping at runtime, it is sufficient to select the interface mapping for the interface pair at configuration time . The Integration Server uses the interface mapping to identify associated mapping programs for request messages, response messages, fault messages, or all three.
    Features
    Executing Multiple Mapping Programs for One Direction
    By using an interface mapping you can execute multiple mapping programs consecutively for the transformation of a request or response message. In such cases, an interface mapping comprises multiple steps for which the following applies:
    &#9679;     The steps are executed in the sequence specified (from top to bottom). The result of the mapping program from the previous step is forwarded to the mapping program of the subsequent step.
    &#9679;     Each step can reference a mapping program that executes a 1:1, 1:n, n:1, or an m:n transformation. In the case of multi-mappings (1:n, n:1, or m:n), the previous step must create the same number of messages that the subsequent step expects.
    &#9679;     Multi-mappings use one envelope to put all messages in one structure. If one of the steps references a multi-mapping program, all subsequent steps must use the same envelope.
    The mapping for a request message comprises two message mapping programs: one 1:1 transformation and one 1:n transformation. Since the latter message mapping uses the multi-mapping envelope for both the target message and the source message, the message mapping for the 1:1 transformation must also create a transformation result with a multi-mapping envelope.
    You do not strictly need to divide up one direction of the whole mapping into different steps. However, this enables all the message formats in one system landscape to be mapped to a central message format, for example. This results in less mapping programs being required because you no longer need to be able to map all the different message formats to each other.
    Activities
           1.      Create your interface mapping on the design maintenance screen of the Integration Builder (see also: Creating an Object).
    You can also create multiple interface mappings for the same interface pair.
           2.      Enter the source and target interfaces that require a mapping of the request message, the response message, the fault message, or all three, in the table of the same name. The following restrictions apply:
    &#9675;     If you want to use the interface mapping in a transformation step in an integration process, you must only specify abstract message interfaces. Furthermore, all objects (integration process, interface mapping, and all objects referenced by the interface mapping) must be in the same software component version. If you want to reference objects from underlying software component versions, you must access the objects from the Basis Objects branch (in the navigation tree or using an input help) (see also: Underlying Software Component Versions).
    &#9675;     If you want to map multiple messages to each other by using a multi-mapping, you can only specify asynchronous interfaces (for further restrictions, see: Multi-Mappings). If any message interfaces are missing, you can also create them by using the functionCreate New Object ().
    If the interface cannot be imported or cannot be created in the Integration Repository (in the case of an external adapter, for example), you must enter the interface names manually. However, it is not possible to check the technical name in this case.
           3.      To import the properties of the interfaces, choose Read Interfaces. The table in the lower area displays tab pages for the request message, response message, and if available, for the fault message, for each mode of the interfaces (either synchronous or asynchronous).
           4.      To develop an external mapping program, export the XSD schema of the respective request or response message as a zip file after you have imported the interfaces. The zip file can contain multiple schema files that reference each other, for example in a multi-mapping. In this case, the schema with the global message element has the name MainSchema.
           5.      To reference a mapping program for the respective message, you have the following options:
    &#9675;     Select an existing mapping program from the Integration Repository by using the input help (). If this is a message mapping, the default setting of the input help only displays those message mappings that are found using the source and target message in the Integration Repository (in multi-mappings, the first source and target messages are used as the search criteria). However, you can also display any number of message mappings, for example, because you are constructing a mapping from several mapping programs with intermediate instances which have no message types.
    &#9675;     You can create message mappings directly from the interface mapping. To do this, select the mapping type Message Mapping in the Type column. Position the cursor in the Name column and choose the function Create New Message Mapping () in the Mapping Program frame. The Integration Builder copies the specifications of the messages and their occurrence directly from the interface mapping.
    An interface mapping can only reference mapping programs that belong to the same or an underlying software component version of the interface mapping. This ensures that the mapping program can be shipped together with the interface mapping (see: Software Logistics).
           6.      If you are not using a mapping for a fault message, you can execute multiple mapping programs in succession for request and response messages:
    &#9675;     To insert an additional line for a mapping program, choose .
    &#9675;     To delete the registration for a mapping program, choose .
    At runtime, the mapping programs are executed from top to bottom.
           7.      Save the interface mapping.
    The following web-site gives complete details about interface mapping :
    http://help.sap.com/saphelp_nw2004s/helpdata/en/12/05731a10264057badc32d3d3957015/content.htm
    **********Please reward points if u find this useful
    cheers,
    gyanaraj

  • Without BPM:Call RFC using JCO in interface mapping using java mapping

    Hi all
    I have a very small scenario where REQUEST from the customer comes via Web Service all i have to do is to read the request using SOAP adapter and call an interface mapping(lets say the name is IM_TEST) inside which there is a JAVA MAPPING program written which will call an RFC in CRM using JCO.
    Now this was really simple and i cud test the Interface mapping successfully, but the problem is when loading the scenario in integration directory i have certain things to do
    1. to set the SENDER AGREEMENT which i did correctly
    2. set the RECEIVER DETERMINATION, INTERFACE DETERMINATION AND RECEIVER AGREEMENT now here i am stuck because there is no receiver in my case as the RFC is called inside the mapping only.
    can i call one more message mapping in IM_TEST which will write file onto the XI directory and then in RECEIVER DETERMINATION, INTERFACE DETERMINATION AND RECEIVER AGREEMENT i can mention the reciever as FTP.
    I tried it but i gives the following error
    Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_MM_TEST_WRITE_FILE: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Parsing an empty source. Root element expected!
    Please help me how to complete the scenario so that customer can run it end to end.
    <REMOVED BY MODERATOR>
    Edited by: Prateek Raj Srivastava on May 12, 2010 1:44 PM

    Stefen
    What do i do then...actually this is the project requirement. They want a very fast response from PI and thats why they wnt us to omit BPM and the Graphical mapping from the scenario.
    I am able to test the interface mapping which calls the the Java mapping inside which there is an RFC call, but i cannot implement it end - to - end as there is no receiver business system in this case. The only business system i have is the SOAP sender.
    I am really troubled now, please help me with a solution.
    Is there any other possible way through which the process can become very fast whic hcan meet their requirement.
    Regards
    Naina

  • How to use rfcnormalizer.jar  in interface mapping

    Hi
    Iam getting one error while doing xml file to RFC scenario.
    the error is like this
    Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null>: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null>
    As a solution for this i got SAP Note 730870.
    here i have to download rfcnormalizer.jar 
    i have uploaded in integration repository under imported object.
    but iam not able to see this in interface mapping
    now i have to use this in interface mapping .
    Please give me step by step how to use this in interface mapping
    how the interface mapping should be like
    Regards
    veena

    Hi,
    The RfcAdapter trys to find a Sender Agreement for this RFC call but the lookup failes. The values used for this lookup are:
    Sender Party/Sender Service: The values from Party and Service belonging to the sender channel.
    Sender Interface: The name of the RFC function module.
    Sender Namespace: The fix RFC namespace urn:sap-com:document:sap:rfc:functions
    Receiver Party/Receiver Service: These fields are empty. This will match the wildcard
    Regards,
    Suryanarayana

  • Unale to get XSLT object in interface mapping

    Hi
    i had imported the zip file contaning xslt file for mapping in Import Archives .But during interface mapping, integration builder is not able to show me the created import archive object.
    Please Help me out.

    Hai Mitesh,
    After u r importing a <b>Zip</b> file ( which the zip file contains (<b>.xsl</b> extension...)),  make sure in the interface mapping to select xsl type and clik F4 to Select the zip file in the mapping program... and if u doesnt see ...
    try by clicking Environment --> Cache notifications and click refresh for some secs... then proceed with above steps u will <b>definitely</b> get...
    Regards,
    sridhar reddy . k

  • Getting Java mapping errors when testing my Interface mapping

    Hi,
    I'm trying to test my interface mapping from IR, I keep getting these exceptions. All I'm doing in my interface mapping is I have two mapping programs a XSLT mapping with java helper functions with the XSL and a message mapping. In the test it pass thru the XSLT mapping but fails at Message mapping and throws the following exception. Any help on this is really appreciated.
    10:03:26 Start of test
    Call XSLT processor with stylsheet com/earthlink/xi/mapping/xmlc_to_crm_resp.xsl.
    START APPLICATION TRACE ***
    Response:
    0
    END APPLICATION TRACE ***
    Returned form XSLT processor.
    Call method execute of the application Java mapping com.sap.xi.tf._MM_XMLC_RESP_
    Error during appliction Java mapping com/sap/xi/tf/_MM_XMLC_RESP_
    java.lang.NullPointerException at com.sap.aii.mappingtool.tf3.AMappingProgram.exceptionCaught$(AMappingProgram.java:59) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:182) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:149) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrep.server.mapping.ibrun.RepJavaMapping.execute(RepJavaMapping.java:73) at com.sap.aii.ibrep.server.mapping.ibrun.RepSequenceMapping.execute(RepSequenceMapping.java:54) at com.sap.aii.ibrep.server.mapping.ibrun.RepMappingHandler.run(RepMappingHandler.java:80) at com.sap.aii.ibrep.server.mapping.rt.MappingHandlerAdapter.run(MappingHandlerAdapter.java:107) at com.sap.aii.ibrep.server.mapping.ServerMapService.transformInterfaceMapping(ServerMapService.java:127) at com.sap.aii.ibrep.server.mapping.ServerMapService.transform(ServerMapService.java:104) at com.sap.aii.ibrep.sbeans.mapping.MapServiceBean.transform(MapServiceBean.java:40) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0.transform(MapServiceRemoteObjectImpl0.java:167) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0p4_Skel.dispatch(MapServiceRemoteObjectImpl0p4_Skel.java:104) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320) at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198) at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) 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:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    10:03:26 End of test

    Joe,
    most likely your XSLT is outputting a not well-formed XML message.
    Remove message mapping from the mapping list and execute it again, to check output.
    Also, for mapping debugging in java enhanced function inside XSLT mappings, use the following:
    1st, you need to pass the "inputparam" parameter from the XSLT runtime to the Java function (it needs to be one of the input parameters for the executed java function).
    In the Java code itself, implement the following code:
    AbstractTrace trace = (AbstractTrace) param.get(StreamTransformationConstants.MAPPING_TRACE);
    trace.addInfo("Log your message here!");
    where <i>param</i> is the input parameter refering to the <i>inputparam</i> from XSLT.
    The AbstractTrace and StreamTransformationConstants classes can be found in the aii_map_api.jar file (used in Java mappings).
    Regards,
    Henrique.

  • BPM Error in Transformation Step: Interface Mapping not found

    Hi,
    Can you help me on this? I have a tranformation step in my BPM that combines a request and response message of a previous Send step to create a Source message for the next Send step. However, on my transformation step, I got the mapping error in workflow log: Interface mapping http://gl.euhreka.com/learning/skillsoft/catalogSy.YGLXI_OM_MergeRequestAndHandleResponseAB_To_PollFo (SWCV=DF8549309ECE11DFB58DF3570A341E0F) not found
    Do you have any idea about this error? My mapping program is working fine. I also checked if the container elements assigned to the transformation steps are correct. 
    Can you suggest of other way on how can I achieve on merging 2 messages (request and response) and set it to the Request for another send step?
    Thanks,
    Jenny

    Hello,
    I already solved the problem. The namespace and Operation mapping name is too long that's why it cannot be located at runtime.
    After the rename, another error appeared.
    "Incorrect XML format after mapping: Root-Tag expected instead of Messages"
    There are no useful information on the trace:
      <?xml version="1.0" encoding="utf-8" ?>
    - <MappingTrace>
      <Trace level="1" type="T">Mapping http://test YGLXI_OM_Merge , Software Component Version DF8549309ECE11DFB58DF3570A341E0F</Trace>
      <Trace level="1" type="T">Mapping Step 1 , Type XSLT , Program PollForReport_Merge</Trace>
      <Trace level="2" type="T">Call XSLT processor with stylsheet PollForReport_Merge.xsl.</Trace>
      <Trace level="2" type="T">Returned form XSLT processor.</Trace>
      </MappingTrace>
    Here is myXSLT program:
    <?xml version='1.0' encoding='utf-8' ?>
    <xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"  >
         <xsl:template match="/">
              <YGLXI_MT_PollForReportRequest>
                   <customerID>
                        <xsl:value-of select="//customerID"/>
                   </customerID>
                   <customerPassword>
                        <xsl:value-of select="//customerPassword"/>
                   </customerPassword>
                   <reportIDHandle>
                        <xsl:value-of select="//reportHandle"/>
                   </reportIDHandle>
              </YGLXI_MT_PollForReportRequest>
         </xsl:template>
    Here is my source message:
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
       <ns0:Message1>
          <ns1:YGLXI_MT_InitiateFullCourseListingRequest xmlns:ns1="http://gl.euhreka.com/learning/skillsoft/catalogSynchronization">
             <customerID>ZZZ</customerID>
             <customerPassword>XXX</customerPassword>
             <reportFormat>VVV</reportFormat>
             <mode>VCC</mode>
             <userName>CC</userName>
          </ns1:YGLXI_MT_InitiateFullCourseListingRequest>
       </ns0:Message1>
       <ns0:Message2>
          <ns1:YGLXI_MT_InitiateFullCourseListingResponse xmlns:ns1="http://gl.euhreka.com/learning/skillsoft/catalogSynchronization">
             <reportHandle>SADA</reportHandle>
          </ns1:YGLXI_MT_InitiateFullCourseListingResponse>
       </ns0:Message2>
    </ns0:Messages>
    I tested my program in Operation mapping and it is working. How come it is not in BPM?
    Thanks,
    Jenny

Maybe you are looking for