Problem to analyse mapping error

Hi all,
I have a problem to analyse a BPM mapping error on PI7.1. The szenario is as follows: I have 3 different containers (Abstract Interfaces) which data is used to determine the content of a  result container.
E.g:
ABSTRACT_INTERFACE_1
ABSTRACT_INTERFACE_2 -> Mapping -> ABSTRACT_RESULT_INTERFACE
ABSTRACT_INTERFACE_3
If have quouted the source interfaces (cardinality 1 for each interface)  in my operation mapping and configured the transformation step accordingly. The operation mapping alone works in the integration builder test environment. When I execute the BPM process, the mapping fails. Unfortunately the is no information in the trace leaf of the respective container information. Writing data to the mapping trace doesn't work neither.
Has got anybody an idea what might be the problem?
Kind regards,
Heiko

Hi Heiko,
Pls, do the following:
1. Build a java mapping which is going to write the payload content before the message mapping.
import com.sap.aii.mapping.api.StreamTransformation;
import com.sap.aii.mapping.api.StreamTransformationException;
import java.io.File;
import java.io.FileOutputStream;
import java.io.InputStream;
import java.io.OutputStream;
import java.util.Map;
public class InputFileWriter implements StreamTransformation {
    public void setParameter(Map map) {
    public void execute(InputStream in, OutputStream out)
    throws StreamTransformationException {
        try{
            File f=new File("C:\PayloadContent.xml");
            FileOutputStream fosPayload = new FileOutputStream(f);
            byte[] content= new byte[in.available()];
            int c;
            int i=0;
            String sb =  "";
            while ((c = in.read()) != -1){
                content<i>=(byte)c;
                sb += (char)content<i>;
                i++;
            fosPayload.write(sb.getBytes());
            fosPayload.close();
            out.write(sb.getBytes());
            out.close();
        }catch(Exception ex){
            ex.printStackTrace();
2. Add the javamapping to your interface mapping putting before of message mapping.
3. Run your scenario.
4. Check the file
C:\PayloadContent.xml
5. Test your message mapping in with PayloadContent.xml
And tell me what happened.
Regards
Ivan
Edited by: Jose Iván Reyes Arteaga on Jul 16, 2009 6:05 PM

Similar Messages

  • Mapping error : strange problem

    Hi all,
                I am getting the mapping error in runtime.
    I have tested in message mapping. It is successful there.
    But I got the strange thing. When I change from design to test page and upload my XML file(from SXMB_MONI),  all nodes in my structure are red! Now If I test the message mapping , I am getting the mapping error in SXMB_MONI.
    May someone has a idea what's going wrong...
    Thanks & Regards,
    Sekhar.

    Hi Sekhar,
    If you test using an XML message saved from the sxmb_moni, you have to add 2 namespace tags around the content of the message. Something like this:
    <ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
      <ns0:Message1>
    ...message...
      </ns0:Message1>
    </ns0:Messages>
    This is usually done internally by SAP XI, but in the test tool it is not..
    Hope this helps!
    (additional hint: First click "create instance" in the test tool. Check out the first two namespaces, usually messages and message1, and copy these in your test file. That should do the trick.:-) )
    Regards,
    Yordy
    Message was edited by: Yordy Minderhoud

  • Strange Data Mapping Errors after SEM 6 Upgrade. Please assist.

    Hi All, I encountered these sudden Mapping errors after I tried to do Testing in Post Upgrade Sand Box. Here I am trying to to perform Collected Reported Financial Data under Data Collection Method for a particular Company Code 3040. Kindly help me with some quick responses as this is kind of high priority. The errors and the Diagnosis Notes I am unable to follow as I do not where I shall write those Mapping Rules they are referring to. I do not even know if that need to apply any SAP Notes as such. Once again Highly appreciate your quick response and Many Thanks in Advance.
    Regards, BIP
    Input conversion for field Period Value LC has invalid format Message no. UCT8210 Diagnosis The mapping rule for target field Period Value LC contains a move with a selected Input Conversion indicator. Therefore, the system performs an input conversion prior to creating the target data. However, an error in the input conversion occurred while moving the source key figure to the target key figure Period Value LC. This means that the format used for the input conversion is incompatible with the target data. System Response The system will not perform the move. Procedure Examine the mapping rule for field Period Value LC. Either select the Conversion Exit indicator or deselect the Input Conversion indicator. Execute the method again. -
    3040 is incompatible with input format for field /1FB/COMPANY Message no. UCT8258 Diagnosis During execution, the method derives the source selection for source field /1FB/COMPANY from the mapping rule for the target field. 3040 is one of the values that were derived for the source selection. The system requires that this value is in the correct SAP-internal format because the Conversion Exit indicator has been selected in the move operator for field /1FB/COMPANY. However, the value 3040 is incompatible with the SAP-internal format. System Response The system attempts to interpret value 3040 as an external format and convert it to the internal format. If this fails, the system is unable to restrict the source selection using source field /1FB/COMPANY. In this case, the system may read more source data than was originally intended, which can affect performance. Procedure In the log, choose the Source button to display the source selections that are used to read the source data. When this appears, examine values selected for field /1FB/COMPANY. If the correct values were selected, you can ignore this message. To prevent this message from being issued, you can select the indicator in the mapping rule used by source field /1FB/COMPANY. If incorrect values were selected, make sure that the mapping rule used by source field /1FB/COMPANY has been defined correctly. If the mapping rule is correct and value (3040) derived for the source selection does not affect the overall result, you can ignore this message. If the source selection does not contain the value 3040 for field /1FB/COMPANY and, because of this, source data that is supposed to be read is not being read, make sure that the mapping rule has been defined correctly. If the source selection does not contain any value for field /1FB/COMPANY, make an estimation as to how much excess source data is being read and whether this might affect system performance. If you do not expect any performance problems, you can ignore this message. In any event, you have the following alternatives if the mapping rule is defined correctly, but the source selection on field /1FB/COMPANY is unsatisfactory: You can define a source selection for field /1FB/COMPANY in the Customizing settings for the method on the Selection tab page. Then the method uses this source selection instead of the source selection derived from inverse interpretation of the mapping rule. You can implement the Business Add-In (BAdI) UC_DATATRANSFER and use the method INVERT to determine the source selection on field /1FB/COMPANY. Then the method uses the result of the INVERT method for the source selection instead of the source selection derived from inverse interpretation of the mapping rule. -
    Cannot derive the source selection from target field Version Message no. UCT8252 Diagnosis Field Version has one of the following roles: Consolidation unit Group currency key Fiscal year Posting period Version To delimit the volume of the source data to be read, the system usually derives the source selection from the target selection of such a field. However, the system cannot derive a source selection from field Version. System Response It is possible that a greater volume of source data is being read than is necessary. This can lead to performance issues. Procedure Check whether a mapping rule is defined for field Version. If a mapping rule is defined, you can disregard this warning message. However, if you discover after method execution that the system did not process a large amount of data, and that system performance was not satisfactory, you may want to examine the source selection by choosing the Source button in the log. If the reason for the disregarded data is that too much source data was read because of the unrestricted selection on the source field (which is linked with target field Versionthrough mapping), choose one of the alternatives below: Change the mapping rule for field Version so that the system can derive a delimiting source selection. Implement the Business Add-In (BAdI) UC_DATATRANSFER with the method INVERT to delimit the selection for the source field that is linked via mapping to the target field Version. -
    Cannot derive the source selection from target field Group Currency Message no. UCT8252 Diagnosis Field Group Currency has one of the following roles: Consolidation unit Group currency key Fiscal year Posting period Version To delimit the volume of the source data to be read, the system usually derives the source selection from the target selection of such a field. However, the system cannot derive a source selection from field Group Currency. System Response It is possible that a greater volume of source data is being read than is necessary. This can lead to performance issues. Procedure Check whether a mapping rule is defined for field Group Currency. If a mapping rule is defined, you can disregard this warning message. However, if you discover after method execution that the system did not process a large amount of data, and that system performance was not satisfactory, you may want to examine the source selection by choosing the Source button in the log. If the reason for the disregarded data is that too much source data was read because of the unrestricted selection on the source field (which is linked with target field Group Currency through mapping), choose one of the alternatives below: Change the mapping rule for field Group Currency so that the system can derive a delimiting source selection. Implement the Business Add-In (BAdI) UC_DATATRANSFER with the method INVERT to delimit the selection for the source field that is linked via mapping to the target field Group Currency
    1 is incompatible with input format for field FISCPERIOD Message no. UCT8258 Diagnosis During execution, the method derives the source selection for source field FISCPERIOD from the mapping rule for the target field. 1 is one of the values that were derived for the source selection. The system requires that this value is in the correct SAP-internal format because the Conversion Exit indicator has been selected in the move operator for field FISCPERIOD. However, the value 1 is incompatible with the SAP-internal format. System Response The system attempts to interpret value 1 as an external format and convert it to the internal format. If this fails, the system is unable to restrict the source selection using source field FISCPERIOD. In this case, the system may read more source data than was originally intended, which can affect performance. Procedure In the log, choose the Source button to display the source selections that are used to read the source data. When this appears, examine values selected for field FISCPERIOD. If the correct values were selected, you can ignore this message. To prevent this message from being issued, you can select the indicator in the mapping rule used by source field FISCPERIOD. If incorrect values were selected, make sure that the mapping rule used by source field FISCPERIOD has been defined correctly. If the mapping rule is correct and value (1) derived for the source selection does not affect the overall result, you can ignore this message. If the source selection does not contain the value 1 for field FISCPERIOD and, because of this, source data that is supposed to be read is not being read, make sure that the mapping rule has been defined correctly. If the source selection does not contain any value for field FISCPERIOD, make an estimation as to how much excess source data is being read and whether this might affect system performance. If you do not expect any performance problems, you can ignore this message. In any event, you have the following alternatives if the mapping rule is defined correctly, but the source selection on field FISCPERIOD is unsatisfactory: You can define a source selection for field FISCPERIOD in the Customizing settings for the method on the Selection tab page. Then the method uses this source selection instead of the source selection derived from inverse interpretation of the mapping rule. You can implement the Business Add-In (BAdI) UC_DATATRANSFER and use the method INVERT to determine the source selection on field FISCPERIOD. Then the method uses the result of the INVERT method for the source selection instead of the source selection derived from inverse interpretation of the mapping rule
    Input must be in the format ___,___,__~ Message no. 00088 Diagnosis Your entry does not match the specified input format. System Response The entry in this field was rejected. Procedure The entry must comply with the edit format. The following edit format characters have a special meaning: "_" (underscore) There should be an input character at this point; this should be a number for numeric fields. "." (decimal point) (applies to numeric fields) The decimal point occurs here (setting in the user master record). "," (thousands separator) (applies to numeric fields) This separator occurs (optionally) for more than three figures. Depending on the setting in the user master record, it can be a period or a comma. "V" (applies to numeric fields) The operational sign appears here. If used, it must by at the right margin of the field. The sign is either "-" or " "(space). "~" (tilde) (applies to numeric fields) As of and including this character, leading zeros must also be entered. Otherwise, this character has the same meaning as an underscore. Leading zeros need not be entered on the left of the tilde. They are not output at this position. All other characters have their normal meanings and must be entered in the same position as in the edit format.

    Hi Dan,
    Could you Kiindly advise me where we need to write the Mapping Rules in Consolidation Monitor? All he time the errors refering to Mapping Rules. The only Tab I seen "Mapping" is in Data Basis But as per my Understanding Iwe do not have much to do there as it is system generated Mapping Tab.
    Where we actually go and select/deselct those Input Conversion Indicator/ Conversion exit Indicator.
    Highly appreciate your advise.
    Thanks and Regards,
    BIP

  • RFC Lookup mapping error in PI 7.1

    Hi Experts,
    I´m getting mapping error when executing interface SOAP -> WS (SAP ECC) . The message mapping call RFC Lookup to SAP ECC.
    When test the message mapping in Integration Builder the interface calls communication channel by RFC Lookup and works fine.
    That interface was imported from QAS environment and was working fine, but in PRD it doesn´t works.
    I checked the Interface Determination and the parameter is filled correctly with communication channel. The same communication channel was used on message mapping test.
    The Interface Determination in SXI_CACHE has no value assigned to parameter in PRD environment, otherwise, the same interface determination in SXI_CACHE in QAS environment there is value (CC ID).
    The problem persists after Cache Refresh in SXI_CACHE and CPA Cache.
    Can anyone help me ?
    Thanks in advance,
    Regis Ferrato
    Bellow the trace of error ocurred:

    Hi Regis,
    Please check my reply in your other thread:
    Re: RFC Lookup error cache in PI 7.1
    Regards,
    ---Satish

  • Mapping error in XI

    Hi Gurus,
    I am getting mapping error at runtime. Im getiing this error message'com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:1, col:301)'. When i testing in the design level its executed successfully. That is i have copied the entire xml message and paste it in the test tap of the integration directory. when i execute it , it run successfully. Pl help out to resolve this problem.
    Regards,
    Ramalakshmi.G

    Hi,
    This s the audit log ..
    2008-07-28 16:29:15 Success
    The message was successfully retrieved from the receive queue.
    2008-07-28 16:29:15 Success
    The message status set to DLNG.
    2008-07-28 16:29:15 Success
    Delivering to channel: CC_WARRANTY_receiver
    2008-07-28 16:29:15 Success
    MP: Entering module processor
    2008-07-28 16:29:15 Success
    MP: Processing local module localejbs/CallSapAdapter
    2008-07-28 16:29:15 Success
    Receiver JDBC adapter: processing started; QoS required: ExactlyOnce
    2008-07-28 16:29:21 Error
    JDBC message processing failed; reason Channel has reached maximum concurrency (5,000 concurrent messages) and no free resource found within 5,000 milliseconds; increase the maximum concurrency level
    2008-07-28 16:29:21 Error
    MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Channel has reached maximum concurrency (5,000 concurrent messages) and no free resource found within 5,000 milliseconds; increase the maximum concurrency level
    2008-07-28 16:29:21 Error
    Exception caught by adapter framework: Channel has reached maximum concurrency (5,000 concurrent messages) and no free resource found within 5,000 milliseconds; increase the maximum concurrency level
    2008-07-28 16:29:21 Error
    Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Channel has reached maximum concurrency (5,000 concurrent messages) and no free resource found within 5,000 milliseconds; increase the maximum concurrency level.
    Last four lines descripes the error
    Regards,
    Ramalakshmi.G

  • XSLT Mapping Error - Split-MappingRoot-Tag missing

    Hi,
    I am getting "Split-MappingRoot-Tag missing" Error while using XSLT mapping. I am using 3 mappings in one Operation Mapping.
    1)  Java Mapping 2) Message Mapping 3) XSLT Mapping.
    When I have these mappings in a BPM one after another it is working fine.
    But ,if I put these mappings one after another in one Operation mapping it is giving problem after message mapping is complete.
    I tried to remove XSLT mapping and Msg Mapping is producing correct output which can be used as input for XSLT mapping.
    Any idea what could be the reason. Any hep is appreciated.
    ERROR
      <SAP:Code area="MAPPING">GENERIC</SAP:Code>
      <SAP:P1>Split-Mapping</SAP:P1>
      <SAP:P2>Root-Tag missing</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Split-MappingRoot-Tag missing</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
    Is there any chance XSLT mapping starting before message mapping is complete
    Regards,
    Ramesh

    Thank you for your response.
    I tried to put XSL in the following format by adding that namespace. but it still giving same error.
    <?xml version="1.0"?>
    <xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
    Code ---
    </xsl:stylesheet>
    Also I itried to put Java mapping before XSLT mapping to see what payload is coming to XSLT.
    I am getting payload as:
    <?xml version="1.0" encoding="UTF-8"?> <ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge"><ns0:Message1>
    XML Payload Data --
    </ns0:Message1></ns0:Messages>
    Any one knows how to fix this issue? appreciate your inputs
    Regards,
    Ramesh

  • Catch mapping error message in BPM Exception branch

    Hi dudes,
    Does anyone know how to catch the mapping runtime error message into a BPM exception branch? I know how to create an exception branch and how to trigger it, but I wonder whether it's possible to pass the mapping error message as shown in SXI_MONITOR (i.e. 'Cannot create target element XXXXX. Values missing in queue context').
    Otherwise, everytime my BPM fails I will have to take the payload and run the mapping test in order to find out the reason of the error.
    Many thanks in advance!
    Paco

    Thanks,
    My problem is not about handling exception in BPM, but getting the mapping error description and then passing it to the exception branch.
    I can see in the workflow log that this info is contained into the Exception container EXCEPTIONS[2] / T100MSG:
    Message Class: SAI_MAPPING
    Message Number: 217
    Message Type: E
    Message Variable: com/sap/xi/tf/_<MM name>
    Message Variable: com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti
    Message Variable: on: Cannot create target element /ns1:<path/field>.Message Variable: Values~
    The text in bold is the one I am interested in to be get and mapped into the exception branch.

  • 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

  • Serious mapping error in OWB 9.2.0.2.8

    Hi,
    I was updating a fairly simple mapping, with a single source and a single target table when I came across a problem that seemingly "destroyed" the entire mapping.
    This is what I did:
    - I added two key lookups to the mapping in series (i.e using the output from first lookup as input to the second).
    - After I had added the lookups I pressed "Validate".
    - Validation completed successfully, but after the validation was completed, the new lookups were gone from the mapping.
    - I then tried to add the first of the two lookups again. But this time I got a JAVA error stack. (unfortunately, I didn't save the error message)
    - Finally I tried to restart OWB, but now when I try to open the mapping I get a "java.lang.NullPointerException"
    and the mapping i blank.
    Has anybody had a similar problem?
    I have also tried to export the mapping, the following is the error stack from the export:
    MDL1254: Error occurred exporting mappings. See below for more details:
    Detailed Error Message:
    java.lang.NullPointerException
         at oracle.wh.repos.impl.mapping.WBStageImpl.&lt;init&gt;(WBStageImpl.java:98)
         at oracle.wh.service.impl.ContextServiceImpl.getBusinessObject(ContextServiceImpl.java:33)
         at oracle.wh.service.impl.metadataloader.WBExportMapping.exportMappings(WBExportMapping.java:1502)
         at oracle.wh.service.impl.metadataloader.WBExport.exportProjectMappings(WBExport.java:964)
         at oracle.wh.service.impl.metadataloader.WBExport.exportProjectAndFCOs(WBExport.java:1688)
         at oracle.wh.service.impl.metadataloader.WBExport.exportSingleProject(WBExport.java:1655)
         at oracle.wh.service.impl.metadataloader.WBExport.process(WBExport.java:2049)
         at oracle.wh.ui.metadataloader.WBMetaDataExportTransaction.run(WBMetaDataExportTransaction.java:1112)
    And the following is the last three lines of the .mdl.err file that was generated:
    CONFIGPARAM|8i.ORACLE8.1.DEFAULT_STORAGETABLESPACE|8i.ORACLE8.1.DEFAULT_INDEXTABLESPACE|null|Y|04CB64C498DA4FBB870D4FA4BB33E8DF
    CONFIGPARAM|8i.ORACLE8.1.DEFAULT_STORAGETABLESPACE|8i.ORACLE8.1.DEFAULT_OBJECTTABLESPACE|null|Y|A448D883E39845B99BCF61CB87D2FE95
    INCOMPLETE FILE

    Hi Igor,
    Did you ever manage to reproduce the problem?
    We have now had the same problem with another mapping. It occured in simmilar circumstances to last time, only this time the error occured after adding an expression. This expression dissapeared when pressing Validate, and the mapping now gives a null pointer exception when we try to open it:
    java.lang.NullPointerException
    java.lang.NullPointerException
         at oracle.wh.repos.impl.mapping.WBStageImpl.<init>(WBStageImpl.java:98)
         at oracle.wh.service.impl.ContextServiceImpl.getBusinessObject(ContextServiceImpl.java:33)
         at oracle.wh.ui.mapping.MappingEditorCanvas.refresh(MappingEditorCanvas.java:280)
         at oracle.wh.ui.common.WhFolderEditor.refreshCanvas(WhFolderEditor.java:951)
         at oracle.wh.ui.common.WhFolderEditor.refresh(WhFolderEditor.java:604)
         at oracle.wh.ui.common.WhFolderEditor$1$MyRefresh.run(WhFolderEditor.java:424)
         at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:154)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:337)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:131)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:98)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
         at java.awt.EventDispatchThread.run(EventDispatchThread.java:85)
    I hope you manage to track this bug down, because it has the potential to ruin many hours of work

  • Mapping error in FCC to XML conversion

    hiii friends,
    im donig a simple fcc to xml conversion
    my Sender msg type is like
    TXT_mt
          records                             1.1   
                row                             1.n
                    id                             1
                    Name                       1
                    address                   1
    My receiver msg type like
    Xml_mt
          records                             1.1   
                row                             1.n
                    id                             1
                    Name                       1
                    address                   1
    msg mapping like
    records--->records
    id--->id
    Name-->Name
    address-->address
    **Im getting a mapping error like**
    <SAP:Error xmlns:SAP="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/_pepsi_fcc_file_mm_</SAP:P1>
      <SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
      <SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>During the application mapping com/sap/xi/tf/_pepsi_fcc_file_mm_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    I ve checked my adapeters they r green.
    Could u tell me the problem here and how to solve it???
    Regards
    Balaji

    Hii Volker,
    I have tried to understand the trace msg,. i got one interesting error message i hope it will tell the exact problem im facing,,,
    <Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_pepsi_fcc_file_mm_</Trace>
      <Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns:xml_mt/record/row. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram
    My Sender CC  contains the following FCC parameters
    Document Name -
    > txt_mt
    Recordset Name -
    > records
    recordset Structure -
    >  row, *
    row.fieldNames -
    > id, Names,address
    row.fieldSeparator -
    > , (comma)
    row.endSeparator--- >  'nl'
    row.processConfiguration  -
    > FromConfiguration
    my TXT_in.txt contain
    100,balaji,chennai
    200,raj,orissa
    300,charakrat,bangalore
    Regards,
    Balaji
    Edited by: Balaji Pichaimuthu on Jul 1, 2009 3:44 PM

  • Mapping error in File to File Scenario.

    In a file to file scenario some times sender communication channel picked the file, before the file is completely copied to the directory Though the poling intervals is 300 seconds. To my assumption, assume that the sender communication channel lastly polled on 10:10:10 and i am coping a file after 285 sec that is 10:14:55 and file size is 20 mb that takes 50 sec to copy. but the next sender communication channel poling is 10:15:10. here the file is partially copied but the communication channel picked the file and process. The scenarios throws mapping error because of in correct input file. This rarely accords but how to handle this. i want the cc to wait until the file is completely copied to the dir and then poll.

    Hi ,
    But there is some problem with system i guess. Adapter engine first load the whole file and then send it to Integration engine where after receiver and interface determination , mapping is excuted. So the fact that adapter picked up half of the file and tried to process does not seem correct.
    Ideally this behaviour should not occurs.
    If you are observing similar with all the adapter , you should also cross check with SAP support team.
    Ranjeet Singh.

  • MAPPING ERROR...................URGENT

    Hi Experts,
    I have a File to File (FTP) scenario,
    The source structure.....................Mapping.......................................target structure
    PO ...................................................................................PO
    |........Header...1.1.................................................................|.....Header.....1.1
    |........Line........1.unbounded..................................................|....Line...........1.unbounded
    |.........sno.........1.unbounded
    |........Inst...........1.unbounded................................................|.....Inst............1.999
    It caught an Mapping error, when i send a messge with below srtucture
    PO
    |........Header
    |........Line
    |........Line
    |........Line
    Error details:
    RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:PO/Inst.
    Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
    Please suggest to resolve the error.
    Thanks in advance.

    Hi,
    In you source structure all fields are with occurance 1 -1 or 1- Unbounded.
    But in source XML, if the filed <Inst> is missing its creating this kind of error. As the decided Source XML structure is not getting matched up.
    Probably you could do one thing here either pass the blank space or any value such as 00 etc to Inst field. That will make this Inst available in source XML structure.
    Or change the occurance of Inst to 0 - Unbounded. This will solve the problem.
    Just for confirmation you could add </Inst> tag in your source XML while testing it in Test Tab of mapping.
    (Make sure to add this tag in proper sequece only)
    Thanks
    Swarup

  • IDOC Serialization(EOIO) using IDOC Adapter throwing Mapping error

    Hello SDN Gurus,
    The scenario I am working on is IDOC(PAYEXT & EUPEXR) --> XI (ABAP Mapping) --> Flat File (IDOC Structure).
    The IDOCS produced in Appl system may be in the following order
    PAYEXT
    PAYEXT
    EUPEXR
    PAYEXT
    PAYEXT
    PAYEXT
    EUPEXR
    I need them to be processed in the same order into flat file.
    The scenario is working good except for the serialization. So I did the following
    Created two entries in IDXQUEUE one for each message type with the same Queue name in XI system.
    Created a new rule for the queue and an associated function module. Used this rule in partner profile for both the message types.  I used the following link to create the above two steps.
    /people/community.user/blog/2006/11/04/how-to-serialize-idoc-xml-messages-fed-into-xi
    The SAP system in based on WAS 6.4.
    I can see the queue name & EOIO in the inbound message header.
    I am getting a mapping error in ABAP program. If I inactivate the queue(in Appl system SAP ECC), I don't get any error.
    Does anybody had this problem earlier? Please advice.
    Thanks
    Srini Vaidyam

    I found an OSS note to resolve my issue. The note number is 1057573.
    Whenever the queue is activated, the sender system will not send the <TABNAM> field value in EDI_DC40 structure. This note addresses this problem.
    I found out this by comparing the results from SXI_MAPPING_TEST individually for the message that failed after queue is activated and the message that was successful if the queue is inactivated.
    Only thing I noticed now is even if you selected the radio button "Trasfer Immediately" in Partner profile of Appl. system, the messages are not sent. They are getting collected. So we need to manually push them out using WE14.
    This forum Rocks.
    Thanks. 
    Srini Vaidyam

  • Mapping Errors

    Hi All:
    What types of Mapping Errors we can get in XI also how can we Test it. Suppose I need to raise an ALERT if Mapping fails. So how can I raise it. I am testing with SOAP client, now when I am destructuring the source message I am not able to test it because SOAP does not parse it. What mistake I will do in MM so that I can get an Mapping ALERT??
    Regards,
    Praveen

    Praveen,
    Give Incorrect XML.
    Take any of your scenarios and the source XML should be invalid XML and the mapping will error out in the Message Mapping stage.
    Regards
    Bhavesh
    PS: Basic point is to make an error happen in XI. You can create an Error in XI in thousands of ways
    Please close your earlier threads and if they are not answered please do update on what the problem in the answers is.

  • Non-build-in-data type mapping error

    Hi,
    I started a new web service design using a pre-defined Schema. I created a schema project and use XML bean as my web service method parameter.
    It works fine in workshop test IDE. But when I deployed it and tried to generate client jar, it gave me Failed to do type mapping error.
    What steps I should do to fix this non-build-in data type problem?
    thanks
    May

    Hi,
    I started a new web service design using a pre-defined Schema. I created a schema project and use XML bean as my web service method parameter.
    It works fine in workshop test IDE. But when I deployed it and tried to generate client jar, it gave me Failed to do type mapping error.
    What steps I should do to fix this non-build-in data type problem?
    thanks
    May

Maybe you are looking for