BPM message mapping error

Hi all,
I am using BPM for sending idoc to mq through XI.
In the transformation step, an error is throwing up in the workflow.
But I am using the same kind of mapping in other scenario. I am getting success message for mapping.
Any idea why its throwing up error?
Thanks,
Deno

Hi Deno,
There should be a <b>invalid operation</b> in your BPM itself. This problem cannot be viewed while design and configuration times. When you perfom a check (F7) your BPM, it will not show any errors and gets activated giving you a feel that your BPM is perfect. which is not true.
So check ur BPM once again and see if there are any invalid operations. <b>Try doing this and u will get an error (99 code) in sxi_cache.</b>
RUN1: Have a BPM with a simple rx and send steps. Save and active the same. Import it into Configuration and actiave it. Go to sxi_cache and u will find that the BPM has ret code 0.
RUN2: Insert a container operation ( assign a simple variable to your MESSAGEID > usign ur condition editor>interface variables>context objects> MESSAGEID). Try importing the same into your Configuration time and Active the same. When u go to Sxi_cache, u will find that the ret code is 99.
So the Design and configuration times dosen't show any  invalid operations in BPM.
Cheers,
Siva Maranani.

Similar Messages

  • Message Mapping Error in Text File to XML file Scenario

    Hi Gurus,
    This is Sudheer...I am New to SAP-PI......
    Below link is File to File Scenario(Text File to XML File)...
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/basicFileAdapterContentConversion
    I am facing Message Mapping Error....I am not able to map the fileds...
    Please help me.
    -Sudheer

    Thanks Shabarish & Manisha for your reply....
    Ya I am getting error while I am testing in IR....
    I dont know how to map the fields that shown given below...
           Message Type         ---         Message Type
                 Record                              Employee
                     Header                                 EmployeeID
                         Key                              Name
                         EmpID                          Company
                         Name                            Phone
                         Company                       Prior_Employer
                         Phone                               Company         
                      Detail                                   Location
                          Key
                          Company
                          Location

  • Message Mapping Error in BPM

    when message mapping, if the length of source field is longer than specified length, I need to output these kinds of messages. what is the solution?

    Hi,
            try using a user defined function written in java where u can check for the condition and raise a exception.
               if(sourcefield.length()>16)
    S.O.P("The Invoice Number is greater than 16 characters");
    or
       using a BPM where u can check whether Invoice number is greater than 16 characters and if it is true then raise an exception and send the message through BPM.
    regards
    jithesh

  • 1: N multi mapping -----Message Mapping Error

    Hi,
    I am doing this scenario
    Various multi-mappings and Optimizing their Implementation in Integration Processes (BPM) in XI.
    In the design part of the mapping.
    How can I perform the message mapping
    Step 1. We are controlling occurrence of Output Piyush_msg_out_3 by mapping it with element2 with message context.
    Step 2.
    We are using u201CUseOneAsManyu201D under category node functions (SP14). It has three inputs ;
       1. Element which is going to be used for multiple times. In our case it is Element1 with message context.
       2. The element which is going to define how many times it will be replicated. Important thing, context should be same.
       3. Same as second input but with its own context in our case it is Element2.
    For Step 1,
    I have mapped piyush_msg_out_3 with Element2 (context is root)
    For Step 2,
    I have mapped
    Element1(context root)----
    |
    Element2(context root)----
    |   useOneAsMany -
    >Element1
    Element2(context root)----
    |
    subelement------> subelement
    I did not do root mapping.
    when do the test I am getting the following error
    Start of test
    Compilation of MM_multimappingandoptimizing successful Cannot produce target element
    /ns0:Messages/ns0:Message1/ns1:piyush_msg_out_3[2]/root/Element1. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd Cannot produce target element
    /ns0:Messages/ns0:Message1/ns1:piyush_msg_out_3[2]/root/Element1. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
    End of test
    I thought error generated due to Parent Node condition fails, How do I map the Top node,
    even though I mapped root------->root, I am  getting the same error in the instance test
    Please give me some suggestions
    my message mapping is correct or do I need to change the context of the node  or what should I have to do ?
    thanks
    manian

    Hi Praveen,
    I have checked the XSD tab of Source and Target message types. I can see the complete XSD.
    Source Message Type XSD:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:mlr:multimappingandoptimizing" targetNamespace="urn:mlr:multimappingandoptimizing">
         <xsd:element name="piyush_msg_in_1" type="piyush_msg_in_1" />
         <xsd:complexType name="piyush_msg_in_1">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   f1fd03a0cddd11ddc1c4001cc01cef0d
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="root">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             99ffb9e0cd1a11ddc6b0001cc01cef0d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:complexType>
                             <xsd:sequence>
                                  <xsd:element name="Element1" type="xsd:string">
                                       <xsd:annotation>
                                            <xsd:appinfo source="http://sap.com/xi/TextID">
                                            99ffb9e1cd1a11dd8843001cc01cef0d
                                            </xsd:appinfo>
                                       </xsd:annotation>
                                  </xsd:element>
                                  <xsd:element name="Element2" maxOccurs="unbounded">
                                       <xsd:annotation>
                                            <xsd:appinfo source="http://sap.com/xi/TextID">
                                            99ffb9e2cd1a11dd8f7a001cc01cef0d
                                            </xsd:appinfo>
                                       </xsd:annotation>
                                       <xsd:complexType>
                                            <xsd:sequence>
                                                 <xsd:element name="subelement" type="xsd:string">
                                                      <xsd:annotation>
                                                           <xsd:appinfo source="http://sap.com/xi/TextID">
                                                           99ffb9e3cd1a11dd8ff2001cc01cef0d
                                                           </xsd:appinfo>
                                                      </xsd:annotation>
                                                 </xsd:element>
                                            </xsd:sequence>
                                       </xsd:complexType>
                                  </xsd:element>
                             </xsd:sequence>
                        </xsd:complexType>
                   </xsd:element>
              </xsd:sequence>
         </xsd:complexType>
    </xsd:schema>
    Target Message Type XSD:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:mlr:multimappingandoptimizing" targetNamespace="urn:mlr:multimappingandoptimizing">
         <xsd:element name="piyush_msg_out_3" type="piyush_msg_out_3" />
         <xsd:complexType name="piyush_msg_out_3">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   058e2b60cdde11ddaffd001cc01cef0d
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="root">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7fb0d7d0cd1b11dd99ae001cc01cef0d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:complexType>
                             <xsd:sequence>
                                  <xsd:element name="Element1" type="xsd:string">
                                       <xsd:annotation>
                                            <xsd:appinfo source="http://sap.com/xi/TextID">
                                            7fb0d7d1cd1b11ddc07e001cc01cef0d
                                            </xsd:appinfo>
                                       </xsd:annotation>
                                  </xsd:element>
                                  <xsd:element name="Element2">
                                       <xsd:annotation>
                                            <xsd:appinfo source="http://sap.com/xi/TextID">
                                            7fb0d7d2cd1b11dd9385001cc01cef0d
                                            </xsd:appinfo>
                                       </xsd:annotation>
                                       <xsd:complexType>
                                            <xsd:sequence>
                                                 <xsd:element name="subelement" type="xsd:string">
                                                      <xsd:annotation>
                                                           <xsd:appinfo source="http://sap.com/xi/TextID">
                                                           7fb0d7d3cd1b11dda9d7001cc01cef0d
                                                           </xsd:appinfo>
                                                      </xsd:annotation>
                                                 </xsd:element>
                                            </xsd:sequence>
                                       </xsd:complexType>
                                  </xsd:element>
                             </xsd:sequence>
                        </xsd:complexType>
                   </xsd:element>
              </xsd:sequence>
         </xsd:complexType>
    </xsd:schema>
    thanks
    manian

  • Cancel or Reprocess BPM message with error on outbound state

    I have a BPM scenario, IDOC comes from R3 and triggers a BPM. The BPM has a fork step which sends the message across 4 branches. Each branch has its own steps. Now, the problem is the IDOC has come and has trigerred the BPM but has errored on outbound side. The first step in each branch is a mapping step and the BPM has failed at this due to Jco communication failure. This has been fixed now. Now I need to reprocess this message, but can not restart as it shows succes message in inbound side.
    I have to re process this message, but how?
    Regards,
    Jaishankar

    Jai,
    I dont know whether it is the correct appraoch.
    Have a look at the transaction SWWERRE_DEBUG
    Regards,
    Sudharshan N A

  • BPM Message Mapping: "Cannot produce target element /ns1:BAPI...."

    Hi,
    A scenario File - BPM - BAPI call was developed, as described in blog 'RFC scenario using BPM' cfr. link
    /people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
    The Mapping is as follows:
    MT_EDB_MATERIAL_REQ (1:1) --> BAPI_MATERIAL_EXISTENCE_CHECK (1:1)
    MATNR (1:1) -
    > MATERIAL (1:1)
    When executing the scenario, an error appears in the trace of SXMB_MONI, step 'Request Message Mapping'
    Cannot produce target element /ns1:BAPI_MATERIAL_EXISTENCECHECK. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd....
    I tried the following:
    1) import the XML-file into the testmapping: executed successfully
    File:
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:MT_EDB_MATERIAL_REQ xmlns:ns0="http://agfa.com/SD_EDB">
    <MATNR>15P6X</MATNR>
    </ns0:MT_EDB_MATERIAL_REQ>
    2) Removed the mapping on node level and left mapping only on element level (material): same error
    3) Activated the message mapping, interface mapping, determinations, etc again...:same error
    4) Removed the Interface Mapping and created it again: same error
    5) Compared the version ID of the Interface Mapping/message mapping in the Monitor trace with the version ID of the IR and saw that there was a difference.
    After the CPA full cache, SXI_CACHE full refresh and object refresh in the IB Administration, the differences remain, and also the error....
    Anybody an idea ?

    Hi
    >>>Cannot produce target element /ns1:BAPI_MATERIAL_EXISTENCECHECK. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd....
    The error clearly says that one of the occurrence value  for the target node mentioned is not coming from the source during mapping. The easiest way to solve the problem is as follows
    <b>
    First Execute the mapping as pointed out by "Raj" and the following steps.
    </b>
    1. Goto the Mapping Editor
    2. Double click on the target node that is causing the problem here BAPI_MATERIAL_EXISTENCECHECK.
    3.  Right click on the same node and select "DisplayQueue".
    4. View the Queue.
    5. YOu will find "Suppress" entries, which means a value is expected but no value is coming in.
    6.Go from right to left and check each node in the mapping and you will be able to trace where the suppress node comes from and take appropriate action
    regards
    krishna

  • BPM - Message has error on the outbound side

    I get this error 'Message has error on the outbound side" . I am using IDOC - BPM - JDBC. I checked SXI_CACHE and I see ret code 99 for this Integration Process. I tried to activate it. I see an error saying that ZCUST_NUMBER is not a component object of PAYLOAD. I have this context object defined on the Abstract Message Interface built to store the IDOC.
    Any ideas are helpful

    Michael,
    <i>The program outputs a returncode = 99 during the cache refresh of an integration process (ccBPM), with an error message that says that 'xxxx' is not a component of the 'PAYLOAD' data object.</i>
    If you are getting the above error, check OSS NOte 890760

  • Message Mapping error in UDF

    I am receiving errors when trying to activate my MM.  I believe the issues are in one of two UDF's.  These UDF's do work in another MM without error.  Below are the error's and UDF's.
    ERRORS:
    Activation of the change list canceled Check result for Message Mapping MM_WPDBBY_WPDBBY01_TO_POS_WAWAFILE | http://wawa.com/xi/erp/pos:  Starting compilation  Source code has syntax error:  /usr/sap/XID/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map5420e070cabe11dcab4b00306ef38da9/source/com/sap/xi/tf/_MM_WPDBBY_WPDBBY01_TO_POS_WAWAFILE_.java:3291: cannot resolve symbol symbol : variable container location: class com.sap.xi.tf._MM_WPDBBY_WPDBBY01_TO_POS_WAWAFILE_ map = container.getTransformationParameters(); ^ /usr/sap/XID/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map5420e070cabe11dcab4b00306ef38da9/source/com/sap/xi/tf/_MM_WPDBBY_WPDBBY01_TO_POS_WAWAFILE_.java:3293: cannot return a value from method whose result type is void return constant; ^ 2 errors
    UDF's:
    public String getSender(Container container){
    String constant;
    java.util.Map map;
    // get constant map
    map = container.getTransformationParameters();
    constant = (String) map.get (StreamTransformationConstants.SENDER_SERVICE);
    return constant;
    IMPORTS:  com.sap.xi.mapping.parse.dom.;javax.xml.parsers.;java.io.;com.sap.aii.mapping.lookup.;org.w3c.dom.*;
    public String getSeqNum(String fileType,String objNum,String Sender,Container container){
    String request = "<ns0:ZRFC_NUMBER_GET_NEXT xmlns:ns0=\"urn:sap-com:document:sap:rfc:functions\"><NR_RANGE_NR>" + fileType + "</NR_RANGE_NR><OBJECT>" + objNum + "</OBJECT><QUANTITY/></ns0:ZRFC_NUMBER_GET_NEXT>";
    InputStream isRequest = new ByteArrayInputStream(request.getBytes());
    SystemAccessor accessor = null;
    String num  = null;
    try{
         // 1. Determine a channel.
         Channel channel = LookupService.getChannel(Sender, "R_RFC_ERP");
         // 2. Get a system accessor for the channel.
         accessor = LookupService.getSystemAccessor(channel);
         // 3. Create a payload according to the data type which the adapter expects.
         //    Use service.getBinaryPayload() for binary payload,
         //    and service.getTextPayload() for text payloads.
         Payload payload = LookupService.getXmlPayload(isRequest);
         // 4. Execute lookup.
         Payload response = accessor.call(payload);
         //Parse response
         DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
         DocumentBuilder builder = factory.newDocumentBuilder();
         InputStream resStream = response.getContent();
         Document doc = builder.parse(resStream);
         Element sequence = doc.getDocumentElement();
         NodeList number = sequence.getElementsByTagName("NUMBER");
         //Extract Number
         num = DOMUtil.getSimpleElementText((Element) number.item(0));
    } catch (Exception e) {
         return e.getMessage();
    } finally {
         try {
              if (accessor != null) accessor.close();
         } catch (Exception e) {
              return e.getMessage();
    GlobalContainer gc = container.getGlobalContainer();
    gc.setParameter("Num", num);
    return num;
    Any help is appreciated.
    Regards,
    Darrell

    Fauver,
    Just to narrow down the problem first remove the first udf and only use the 2nd user defined function. Also in the 2nd udf you have to change this line:
    try{
    // 1. Determine a channel.
    Channel channel = LookupService.getChannel(Sender, "R_RFC_ERP");
    In the above line instead of Sender you use the business service or business system where R_RFC_ERP RFC communication channel is created in Integration Directory. So you are hardcoding it first.
    Once you have done this changes do save and test it once again. If this works then you can change back to original and your first udf needs to be checked.
    Regards,
    ---Satish

  • While Activating  Message mapping, error.

    Hi
    While activating my message mapping  i am getting this error "JMS server failed"
    How to resolve this and whats the cause of it?
    Please do not post links.
    Thanks in advance
    Saiyog
    Points will be awarded
    Edited by: Saiyog Gonsalves on Jun 13, 2008 6:09 PM

    Hi,
    There seems to be problem with J2EE Server. Please follow the following steps and it will resolve your error.
    login to J2EE Visual aadmin ->cluster ->services ->.JMS connector ->runtime(Right side tab) ->check the factories / destinations (if anything is in red color X mark).
    Fix it and restart the server.
    Pls reward points if answer is useful
    Thanks
    Amit

  • Message Mapping error:  RuntimeException in Message-Mapping transformation

    Hi,
    Being new to XI, I am struglling to sort out a basic mapping error. Appreciate if you could help out.
    Its an File->XI->R/3 scenario.
    My FCC successfully reads the File and creates an XML. However this XML is not transferred to the target XML structure which is exactly same except the root element name is different at top.
    I tried various forum tips but I still am getting the error.
    ( When I Test the Message mapping in test mode..it seems fine, however if I copy the XML from SXMB_MONI, it then throws the above error)
    I looked at the MM in text mode: below is the extract
    /ns0:MT_REQUEST_TO_SAP/REQUEST_DETAILS/MSG_HEADER=/ns0:MT_REQUEST/REQUEST_DETAILS/MSG_HEADER=
    /ns0:MT_REQUEST_TO_SAP/REQUEST_DETAILS/MSG_HEADER/SOURCE=/ns0:MT_REQUEST/REQUEST_DETAILS/MSG_HEADER/SOURCE=
    /ns0:MT_REQUEST_TO_SAP/REQUEST_DETAILS/MSG_HEADER/DESTINATION=/ns0:MT_REQUEST/REQUEST_DETAILS/MSG_HEADER/DESTINATION=
    /ns0:MT_REQUEST_TO_SAP/REQUEST_DETAILS/MSG_HEADER/MESSAGE_ID=/ns0:MT_REQUEST/REQUEST_DETAILS/MSG_HEADER/MESSAGE_ID=
    As seen the name space in both starts with nS0 and end of each line has '=' sign. Is that ok.
    I have run out of options and dont know , whats the problem. Please help.
    The target and Source XML structures are exactly same as shown below
    MT_REQUEST                                 MT_REQUEST_TO_SAP
       |__MSG_HEADER                            |__MSG_HEADER  
         |__SOURCE                                |__SOURCE
         |__DESTINATION                           |__DESTINATION
         |__MESSAGE_ID                            |__MESSAGE_ID
    And the SXMB_MONI Trace shows the following error
    <Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation:
    Cannot produce target element /ns0:MT_REQUEST_TO_SAP.
    Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at ..
    Thanks
    Shirin
    Edited by: Shirin K on May 29, 2008 10:29 AM

    Hi Prakasu,
    As structure are exactly same, I have done 1:1 mapping. So all the fields in target structure are mapped, so no field has beeen left.
    In this structure, I do not have any 1:n relation. So 1:1 mapping should be fine.
    Apart from this could teher be any other reason.
    Regards
    Rajiv

  • Message Mapping Error - Runtime

    Hi,
    I am able to execute message mapping in graphical mapping editor succesfully. But when i include mapping in interface determination  throws as error.. In sxmb_moni as shown below
    i<SAP:Error xmlns:SAP=throws as error.. In sxmb_moni as shown below"http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>Application</SAP:Category>
      <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
      <SAP:P1>com/sap/xi/tf/_MM_DEMO1_</SAP:P1>
      <SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>
      <SAP:P3>on: Cannot create target element /ns0:MT_Demo. Val</SAP:P3>
      <SAP:P4>ues missing in queue context. Target XSD requires~</SAP:P4>
      <SAP:AdditionalText />
      <SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_DEMO1_; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns0:MT_Demo. Values missing in queue context. Target XSD requires~</SAP:Stackt
    Please share your thoughts..

    Hi Guys,
    I have done a one to one mapping, it runs fine in the editor but fails at run time.
    I took the payload from moni put it in messagemapping test tab, it shows red...
    I compared the payload with the payload i get after successfulll message mapping...it is the same..
    yet i get red signal...
    im on PI 7.1..have ne of u faced ne thign similiar?

  • Retrive message mapping error from java class

    Hi,
    I'm trying to create a scenario that if exist an error in the message mapping step this error will be inserted in a Ztable. I'm thinking in to call to the message mapping from a java class to catch the exception and this java class will be used in the interface mapping.
    Is it possible? If yes, How to call the message mapping from java code?
    Exists other possible solution?
    I need to do it because we want store all mapping errors in a Ztable. (Customer requeriment)
    Thanks, in advance
    Jose Manuel

    you can throw generic exceptions from the message mapping like this - /people/michal.krawczyk2/blog/2007/04/26/xipi-throwing-generic-exceptions-from-any-type-of-mapping
    you can then decide how to handle these exceptions

  • Message Mapping errors in Integration Builders

    Hi
    Our Developer   trying to make changes to a message mapping in  Integration Builder and when we try to compile the mapping to test it I'm getting the following error:
    11:34:42 Start of test
    Compilation process error : CreateProcess: javac @G:/usr/sap/XID/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Mapccbaf1a0532211ddcdd4001b7835a092/O1216204482525.txt @G:/usr/sap/XID/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Mapccbaf1a0532211ddcdd4001b7835a092/S1216204482540.txt error=2
    11:34:43 End of test
    Any ideas?
    Regards
    Chandu

    Hi
    I checked for read, write and modify permissions for that folder and SAPSERVICExxx user has full writes to that folder.
    The error we are getting is :
    #6 11:15:57 [AWT-EventQueue-0] ERROR com.sap.aii.utilxi.swing.toolkit.ExceptionDialog: Throwable
    Thrown:
    MESSAGE ID: com.sap.aii.ib.server.cmpl.CompilerException
    com.sap.aii.ib.core.mapping.exec.ExecuteException: Compilation process error : CreateProcess: javac @G:/usr/sap/XID/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map555c4a6053e911ddb1d1001b7835a092/O1216289752214.txt @G:/usr/sap/XID/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Map555c4a6053e911ddb1d1001b7835a092/S1216289752246.txt error=2
         at com.sap.aii.ib.server.mapping.exec.ServiceUtil.compileSourceCode(ServiceUtil.java:207)
         at com.sap.aii.ib.server.mapping.exec.ServiceUtil.compile(ServiceUtil.java:156)
         at com.sap.aii.ibrep.server.mapping.ServerMapService.compileSourceCode(ServerMapService.java:361)
         at com.sap.aii.ibrep.server.mapping.ServerMapService.compileSourceCodeWithoutAndWithArchives(ServerMapService.java:301)
         at com.sap.aii.ibrep.server.mapping.ServerMapService.execute(ServerMapService.java:153)
         at com.sap.aii.ibrep.sbeans.mapping.MapServiceBean.execute(MapServiceBean.java:52)
         at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0.execute(MapServiceRemoteObjectImpl0.java:259)
         at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0p4_Skel.dispatch(MapServiceRemoteObjectImpl0p4_Skel.java:146)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
         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)
    Serialized server exceptions:
    Regards
    Chandu

  • Message Mapping Error : "already dropped from buffer"

    Hi,
    today we have a new strange error in a simple message mapping File2IDoc thats results in SYSFAIL.
    Maybe a buffer or memory error?
    In short:
    +/ARTMAS05/IDOC/E1BPE1MARART[2]/DELN_DATE(suppressed field); root message: Index 2147483647 is already dropped from buffer. Cur offset is 2147483636+
    In detail:
    #2.#2010 08 18 10:49:51:619#+0200#Error#/Applications/ExchangeInfrastructure#
    #BC-XI#com.sap.xi.util.misc#0026557C6A4004B6000000000000120D#229073650000000872#sap.com/com.sap.xi.services#com.sap.aii.ib.server.mapping.execution.JavaMapping#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : #0A1BAF81AA0111DF82D40026557C6A40#0a1baf81aa0111df82d40026557c6a40#0a1baf81aa0111df82d40026557c6a40#0#output#Java##
    RuntimeException during appliction Java mapping com/sap/xi/tf/_xxxxx_Out_To_ARTMAS_ARTMAS05_A1_
    Thrown:
    com.sap.aii.mappingtool.tf7.MessageMappingException: Runtime exception when processing target-field mapping /ARTMAS05/IDOC/E1BPE1MARART[2]/DELN_DATE(suppressed field); root message: Index 2147483647 is already dropped from buffer. Cur offset is 2147483636
    #2.#2010 08 18 10:52:45:149#+0200#Error#/Applications/ExchangeInfrastructure#
    #BC-XI#com.sap.xi.util.misc#0026557C6A4004BA000000000000120D#229073650000000872#sap.com/com.sap.xi.services#com.sap.aii.ib.server.mapping.execution.JavaMapping#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : #0A1BAF81AA0111DF82D40026557C6A40#0a1baf81aa0111df82d40026557c6a40#0a1baf81aa0111df82d40026557c6a40#0#output#Java##
    RuntimeException during appliction Java mapping com/sap/xi/tf/_xxxxx_Out_To_ARTMAS_ARTMAS05_A1_
    Thrown:
    com.sap.aii.mappingtool.tf7.MessageMappingException: Runtime exception when processing target-field mapping /ARTMAS05/IDOC/E1BPE1MARART[2]/DELN_DATE(suppressed field); root message: Index 2147483647 is already dropped from buffer. Cur offset is 2147483636
    Thanks in advance,
    André

    Hi André, did you try to re-create de Message Mapping with the same source/target structures?
    Regards,
    Juan.

  • Request Message Mapping - error

    Hello,
    Scenario :
    Flat file => File adapter => XI 2.0 => IDoc => SAP
    The adapter picks up the file, sends it to Integration Engine. In the Monitoring tool, the following are fine : Inbound Message, Receiver determination, Interface determination, Technical routing, Receiver grouping, Message split.
    We are getting error in Request Message Mapping. The error is below :
    ===========
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
      <SAP:Context />
      <SAP:Code p1="Error during mapping" p2="--- Creating Java mapping com.sap.xi.tf._zMsgMap_ --- Using MappingResolver with context URL /sapmnt/XID/global/xi/mapping/http%3A%2F%2FABCxyz%2Ecom%2Fxi%2FTest%2F/bc52cef0be3411d8b277cade640701c6/ --- Loaded class com.sap.xi.tf._zMsgMap_ --- com.sap.aii.util.misc.api.BaseRuntimeException: Fatal Error: com.inqmy.lib.xml.parser.ParserException: XMLParser: No data allowed here:BLO (:main:, row:1, col:3) at com.sap.aii.mappingtool.tf.Transformer.start(Transformer.java:60) at com.sap.aii.mappingtool.tf.AMappingProgram.execute(AMappingProgram.java:100) at com.sap.aii.ibrun.server.map.RUMappingJava.execute(RUMappingJava.java:47) at com.sap.aii.ibrun.server.map.RURunner.run(RURunner.java:58) at com.sap.aii.ibrun.server.map.RUManager.run(RUManager.java:66) at com.sap.aii.ibrun.sbeans.map.MappingRequestHandler.handleRequest(MappingRequestHandler.java:62) at com.sap.aii.ibrun.sbeans.map.MappingServiceImpl.processFunction(MappingServiceImpl.java:72) at com.sap.aii.ibrun.sbeans.map.XMappingServiceObjectImpl0.processFunction(XMappingServiceObjectImpl0.java:24) at com.sap.aii.ibrun.sbeans.map.MappingServiceKey.processFunction(MappingServiceKey.java:10) at java.lang.reflect.Method.invoke(Native Method) at com.inqmy.services.rfcengine.RFCDefaultRequestHandler.invokeBean(RFCDefaultRequestHandler.java:73) at com.inqmy.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:47) at com.inqmy.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:69) at com.sap.mw.jco.JCO$Server.dispatchRequest(Unknown Source) at com.sap.mw.jco.rfc.MiddlewareRFC$Server.nativeListen(Native Method) at com.sap.mw.jco.rfc.MiddlewareRFC$Server.listen(Unknown Source) at com.sap.mw.jco.JCO$Server.listen(Unknown Source) at com.sap.mw.jco.JCO$Server.run(Unknown Source) at java.lang.Thread.run(Thread.java:479) --- An error occured during the execution of the Java mapping com.sap.xi.tf._zMsgMap_ . Fatal Error: com.inqmy.lib.xml.parser.ParserException: XMLParser: No data allowed here:BLO (:main:, row:1, col:3) ---" p3="" p4="">MAPPING.GENERIC</SAP:Code>
      <SAP:Text language="EN">Error during mapping</SAP:Text>
      </SAP:ErrorHeader>
    ===========
    For same scenario, another interface, we get the below error :
    ===========
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
      <SAP:Context />
      <SAP:Code p1="Error during mapping" p2="--- Creating Java mapping com.sap.xi.tf._xMsg_mapping_ --- Using MappingResolver with context URL /sapmnt/XID/global/xi/mapping/http%3A%2F%2FABCxyz%2Ecom%2Fxi%2FTest%2F/bc52cef0be3411d8b277cade640701c6/ --- Load of com/sap/xi/tf/_xMsg_mapping_.class from /sapmnt/XID/global/xi/mapping/http%3A%2F%2FOwensCorning%2Ecom%2Fxi%2Ftest%2F/bc52cef0be3411d8b277cade640701c6 failed. --- Class not found: com.sap.xi.tf._xMsg_mapping_ --- java.lang.ClassNotFoundException at RUMappingJava.load(): Could not load class: com.sap.xi.tf._xMsg_mapping_ Class not found: com.sap.xi.tf._xMsg_mapping_ --- com.sap.aii.ibrun.server.map.MappingRuntimeException: at com.sap.aii.ibrun.server.map.MappingRuntimeException.code_STYLESHEET_OR_CLASS_NOT_FOUND(MappingRuntimeException.java:91) at com.sap.aii.ibrun.server.map.RUMappingJava.load(RUMappingJava.java:119) at com.sap.aii.ibrun.server.map.RUMappingJava.execute(RUMappingJava.java:40) at com.sap.aii.ibrun.server.map.RURunner.run(RURunner.java:58) at com.sap.aii.ibrun.server.map.RUManager.run(RUManager.java:66) at com.sap.aii.ibrun.sbeans.map.MappingRequestHandler.handleRequest(MappingRequestHandler.java:62) at com.sap.aii.ibrun.sbeans.map.MappingServiceImpl.processFunction(MappingServiceImpl.java:72) at com.sap.aii.ibrun.sbeans.map.XMappingServiceObjectImpl0.processFunction(XMappingServiceObjectImpl0.java:24) at com.sap.aii.ibrun.sbeans.map.MappingServiceKey.processFunction(MappingServiceKey.java:10) at java.lang.reflect.Method.invoke(Native Method) at com.inqmy.services.rfcengine.RFCDefaultRequestHandler.invokeBean(RFCDefaultRequestHandler.java:73) at com.inqmy.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:47) at com.inqmy.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:69) at com.sap.mw.jco.JCO$Server.dispatchRequest(Unknown Source) at com.sap.mw.jco.rfc.MiddlewareRFC$Server.nativeListen(Native Method) at com.sap.mw.jco.rfc.MiddlewareRFC$Server.listen(Unknown Source) at com.sap.mw.jco.JCO$Server.listen(Unknown Source) at com.sap.mw.jco.JCO$Server.run(Unknown Source) at java.lang.Thread.run(Thread.java:479) ---" p3="" p4="">MAPPING.GENERIC</SAP:Code>
      <SAP:Text language="EN">Error during mapping</SAP:Text>
      </SAP:ErrorHeader>
    ===========
    Any help in resolving these issues is greatly appreciated.
    Thanx,
    Homiar.

    Hallo Homiar,
    to the first problem:
    Do you get the same error, if you test the mapping in the Integration Builder:Design? I mean, you can download the XML instance which is entered into the Message
    Mapping  zMsgMap in the Integration Engine Monitor (R/3 Transaction SXMB_MONI) and use this XML in the test environment of the Message Mapping in the Integration Builder:Design.
    to the second problem:
    It looks like that the  Message Mapping xMsg_mapping could not be found by the Integration Engine. You can try to reactivate the Message Mapping in the Integration Builder. This is done for example by changing the description of the corresponding Message Mapping object and saving and activating the object.
    Regards Franz

Maybe you are looking for

  • Email Client Missing Issue in Reader XI

    Whenever I open a document in Reader (both X and XI) I get the email client missing error message window which I have to then close.  I googled this error and have looked in the Adobe questions for this.  What little I found was of no help.  I don't

  • Problem in bdc for adding another inspection type in mm01

    Hi, i had made a code in which it will maintain the quality view and there it will going to insert twi insoection type ZSTAGE and 03 . Te problem is when it uploads the value of 1 inspection type it works fine but when it is going to insert another i

  • Making dynamic selection parameter an onscreen parameter

    Dear Experts, I am search on threads regarding defining new fields and adding fields to dynamic selection options, however I have not found an answer to my issue. I need to add a field XBLNR (Reference) currently in the dynamic selections of FBL1N an

  • Can Grid Control on Windows monitor databases on UNIX?

    If I install Grid Control on a Windows pc can I use it to monitor databases on UNIX?

  • Spacing Between Elements

    How can I reduce the space between the two elements below (h2 & p)? There is a significant gap between the two lines which cannot be reduced with padding / margin. The gap does reduce with font size  but not as much as I would like. <header>     <h2