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

Similar Messages

ABAP Mapping Programm error Urgent

I am getting mapping error in ABAP Mapping programm. plz help me how to solve
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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">APPLICATION_PROGRAM_ERROR</SAP:Code>
<SAP:P1>Z_HBS_PAYROLL_MAPPING</SAP:P1>
<SAP:P2>SAP-ABAP</SAP:P2>
<SAP:P3>UNCAUGHT_EXCEPTION</SAP:P3>
<SAP:P4>Program Z_HBS_PAYROLL_MAPPING=========CP Include Z_HBS_PAYROLL_MAPPING=========CM001 Line 1</SAP:P4>
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error in mapping program Z_HBS_PAYROLL_MAPPING (type SAP-ABAP, kernel error ID UNCAUGHT_EXCEPTION) An exception with the type CX_SY_REF_IS_INITIAL occurred, but was neither handled locally, nor declared in a RAISING clause Dereferencing of the NULL reference</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Hi,
I think this exception you need to catch it in the ABAP..
This may help u- http://help.sap.com/saphelp_47x200/helpdata/en/55/bff20efe8c11d4b54a006094b9456f/content.htm
just cross verify with this guide-
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e3ead790-0201-0010-64bb-9e4d67a466b4
Regards,
moorthy

Mapping error MAPPING_DURING_EXECUTE

HI
I am getting a mapping error in sxmb_moni.
My mapping object in IR is
Source structure
MT_INPUT_GL dt_gl
doctype    o to unound
docdate    o to unbound
Destination structure
MT_OUTPUT_GL DT_GL_OUTPUT 1 to 1
doctype    o to unound
docdate    o to unbound
I mapped MT_INPUT_GL to MT_GL_OUTPUT
and all the fields thereafter
My file conversion parameters are
document name MT_GL_INPUT
document namespace http://FCE/FTM/GLInbound
recordsetname DT_GL_INPUT
recordsetnamspace http://FCE/FTM/GLInbound
recordsetstructure DT_GL_INPUT,1
recordsetsequence varible
recordset per message *
DT_GL_INPUT.fieldFixedLengths 2,10,10
DT_GL_INPUT.fieldSeparator ,
DT_GL_INPUT.fieldNames      DocType,DocDate,PostingDate
can anybody help me by providing me sugesstion
Debraj

HI
Thanks for the so early reply.
I have checked the xml which has been generated in SXM_MONI it is different from the source one.How can i change the xml of input structure so that it matches.
My actual xml file of the input structure in IR design enviroment is
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_GL_INPUT xmlns:ns0="http://FCE/FTM/GLInbound">
   <DocType>ccc</DocType>
   <DocDate>cc</DocDate>
   <PostingDate>tt</PostingDate>
   <Currency>y</Currency>
   <CompanyCode>yyu</CompanyCode>
   <Reference>u</Reference>
   <HeaderText/>
   <UserName/>
   <LedgerGroup/>
   <CDFlag/>
   <GLAcct/>
   <Amount/>
   <Text/>
   <ProfitCenter/>
   <CostCenter/>
   <WBS/>
   <InternalOrder/>
   <TPartner/>
   <Network/>
   <TranType/>
   <Class/>
   <ID/>
   <SUB/>
</ns0:MT_GL_INPUT>
but in sxmb_moni it is
<?xml version="1.0" encoding="utf-8" ?>
- <ns:MT_GL_INPUT xmlns:ns="http://FCE/FTM/GLInbound">
- <ns:DT_GL_INPUT xmlns:ns="http://FCE/FTM/GLInbound">
- <DT_GL_INPUT>
<DocType>KR</DocType>
<DocDate>12 12 2005</DocDate>
<PostingDate>12 12 2005</PostingDate>
</DT_GL_INPUT>
</ns:DT_GL_INPUT>
- <ns:DT_GL_INPUT xmlns:ns="http://FCE/FTM/GLInbound">
- <DT_GL_INPUT>
<DocType>KR</DocType>
<DocDate>12 12 2005</DocDate>
<PostingDate>12 12 2005</PostingDate>
</DT_GL_INPUT>
</ns:DT_GL_INPUT>
- <ns:DT_GL_INPUT xmlns:ns="http://FCE/FTM/GLInbound">
- <DT_GL_INPUT>
<DocType>KR</DocType>
<DocDate>12 12 2005</DocDate>
<PostingDate>12 12 2005</PostingDate>
</DT_GL_INPUT>
</ns:DT_GL_INPUT>
- <ns:DT_GL_INPUT xmlns:ns="http://FCE/FTM/GLInbound">
- <DT_GL_INPUT>
<DocType>KR</DocType>
<DocDate>12 12 2005</DocDate>
<PostingDate>12 12 2005</PostingDate>
</DT_GL_INPUT>
</ns:DT_GL_INPUT>
</ns:MT_GL_INPUT>
Please let me know the solution it is a bit urgent.
Thanks
Debraj

Mapping error in PI 7.1

Hi All,
When i am trying to create a new mapping or coyping the existing mapping(which is already activated) , i am not able to activate the mapping . I am getting the following error :
Source text of object Message Mapping: new |
urn:abc:MessageOut has syntax errors: Source code has syntax error:
Source strcuture and everything is perfect as i had created previous mapping using the same source structure.
Please advice as to what might be the issue here and what is the solution.
Regards
Vinay P.

In each and every mapping which is already avialble in IR and the new ones that i am trying to create ...i am getting the followin exception throughout if press F7 in the mapping ...as a result u cant actiavte any changes in the existing mapping nor in the new mapping
Error:
Source text of object Message Mapping:
Mapping name| urn:abc:namespace:SI_Interface has syntax errors: Source code has syntax error:
Regards
Vinay P.

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

Java.util.EmptyStackException Mapping error

Hi All,
I am integrating SAP ECC 6.0 system with SAP SNC.
For these i am using standard content of SAP SNC
I am getting following mapping error :
TransformerConfigurationException occurred when loading XSLT InvoiceRequest_InvoicInvoic01_01.xsl; details: Could not load stylesheet.com.sap.engine.lib.xml.util.NestedException: Error parsing query. -> java.util.EmptyStackException
Plz help me out
Regards Milan

hi,
check the interaface mapping which is used in your flow
inside integration repository - is it working over there?
do you see the XSL file in the external archives in repository?
Regards,
Michal Krawczyk
http://mypigenie.com XI/PI FAQ

Multi-Mapping Error after copying into new namespace

Hi everybody,
we got a BPM running using a multi-mapping.
We decided to design new namespaces. After copying every IR object (datatype, message-type, mappings etc.) --> SXMB_MONI shows a mapping-error.
But when I take the payload and test the mapping, everything is fine?
Any ideas?
Regards Mario

Hi,
If your payload has Messages tab remove that..and test the payload.
Payload doesn't have any Messages tab.
Just i have given example payload..this payload two strucures it will split into twofiles..and compare your payload should be like same
<?xml version="1.0" encoding="UTF-8"?>
<STRUCTURE>
<EMP_DETAILS>
   <EMPNO>123<EMPNO>
   <EMPNAME>XYZ<EMPNAME>
<EMP_DETAILS>
<STUDENT_DET>
   <STUO>123<STUNO>
   <STUNAME>XYZ<STUNAME>
</STUDENT_DET>
<STRUCTURE>
Regards,
Venu.

Catch Mapping Error in File to IDoc scenario

Configured BPM and now learning Error Handling. I know that through BPM we can handle system Errors, but I doubt whether Mapping error is a system error.
I am interested to know the classification of errors with examples, preferably listing out all types of errors.
Please provide some weblogs or explain briefly how to handle system and application errors through BPM.
Thanks,
Raja

Hi Raja,
You will need CCMS if you want to send the Alerts to external system or you want to access the ALerts from the transaction. You can capture your alerts without this also.
When you go to Alert Configuration in the Runtime Workbench you can see Create Alert Rules. These rules are pertaining to the error generated in your AF,AE or IE.
Once you have completed the whole config. The error happening in the AE, IE or AF would trigger the alert. you can see this in your Alert Inbox.
The best would be if you go through the URL I have mentioned below.
http://help.sap.com/saphelp_nw04/helpdata/en/80/942f3ffed33d67e10000000a114084/content.htm
You have to use BPM only if you want to do an activity after the alerts are raised.
Regards
Vijaya
Message was edited by: vijaya kumari

Mapping Error in XI Configuration for MM-SUS Scenario

Dear Experts,
I am working on MM-SUS Classic Scenario,
We have done all basic setting in SRM, ECC and SUS.
Now we are configuring XI Scenario(Working on ESOA Architecture), while configuring XI Scenario, I follow the mention steps :
I have started from Integration Builder in XI (using T-code SXMB_IFR)
1. I have assigned two Business System( for ECC and SUS) In integration Builder (Creates Communication Channels Automatically) .
2. Modify IDOC and XI Communication in ERP and SUS Business system respectively.
3. Now select Tools -> Transer Integration Scenario from Inegration Repository and Create Scenario in it properly
(Included Assign Services, Configure Connections, Generate etc).
4. In last, save scenario.
After configuration XI I am not getting Scenario Data (Objects and Configuration Overview data) in it.
When i click to Check Configurability under Model Configurator of mine Scenario, I found following Errors ( I am Mentioning only some errors) :
Component View SE_Services_Procurement: Connection from Send Z_CREMAS_SUSMM to Business Partner empfangen has no mapping
Component View SE_Services_Procurement: Connection from Send_PO_From_MM to Receive_Purchase_Order has no mapping
Component View SE_Services_Procurement: Connection from ServiceAcknowledgementConfirmationRequest to ServiceAcknowledgementConfirmationCreate has no mapping
Component View SE_Services_Procurement: Connection from InvoiceRequest senden to Receive INVOIC has no mapping
Kindly correct me if am missing some, and help me out, what should have been done to remove this mapping errors.
Thanks in advance,
Regards,
Pawan Keshwani

If you are on >= SP9 you do not need to perform that action at all.
Go to SU01 transaction assign SAP_XI_DEVELOPER role for the desired users and try it.
regards
Shravan

Mapping Error in AAE in PI 7.1

Dear Team,
If we use message mapping along with AAE concept , What are the objects we need to create in ESR and ID .
How can we monitor the messages - messages failed with Mapping Error.Is there any new option available in RWB?
Thanks&Regards
Drumi

Hi,
ESR Objects are same but in ID we need to create Integrated configuration
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/700058f0-b1a1-2a10-39a8-ab2627b87cfa
If we are using AAE then we don't get any status in SXMB_MONI.
Regards,
Venkata Ramesh

Mapping error in PI 7.4 dual stack

Dear Experts,
Recently we upgraded our system from PI 7.1 to PI 7.4 dual stack.
Scenerio is ECC->PI->SOAP(Webservice) synchronous
Issue in detail:
We are creating a invoice in ECC system through PI its updating in third party site using SOAP webservice and will get a reference number from that site and then updating in ECC as in synchronous way.
Invoice data's are reached PI sucessfully from ECC but it not updating in the site and getting below mapping error after upgarded to PI 7.4.
Your points will be highly appreciable.
Kindly help to sort out this issue.
Best Regards,
Monikandan

Hi Monikandan,
It seems you are trying the sign the payload in your java mapping. So, looking at the attached error, there could be 2 possibilities:
1) Either there is no certificate with alias: *_PRD
2) This certificate is stored in some "System" type keystore view which is not accessible from you mapping code. Try to move your certificate to some "User" keystore view.
Thanks & regards,
Piyush

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

Mapping error for file scenario.

Hi ,
I am working with the help of this scenario to pick only selected files.
/people/mickael.huchet/blog/2006/09/18/xipi-how-to-exclude-files-in-a-sender-file-adapter
I am getting error in mapping . Everything i have checked its correct . Mapping is correct . but still its giving error . how can i solve it .
Error : RuntimeException in Message-Mapping transformatio~
Thanks ,
Syed.

Dear Syed Kumar
Based on the blog you are executing the scenario I guess. The scenario is clearly focusing on the picking up the files using the mask attribute in File Access Parameters.
As you mentioned clearly, that you are getting mapping error plz concentrate on how to rectify the mapping errors.
will guide to do so.
1. Go to SXMB_MONI and in the integration server and check for the message you are trying send.( I hope you did this)
2. As it is giving you mapping error, Double click onthe message Flag showing red.
3.Plz check the Payload XML content copy that content and paste in the message mapping Test section of IR.
4. Execute the Test. If you get the message at the receiver side there shouldn't be any error.
If you still get the error let me know.
Best of Luck
Reward Points If found use ful.
Edited by: Praveen Kurni on Jun 13, 2008 7:43 AM
Do the Interface mapping test as well if you are successful in message mapping.

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.

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

Similar Messages

Maybe you are looking for