Mapping runtime Exception

I have tested my mapping in IR, it is working good. Problem comes it is receving data from sender system.
I have checked the sender side data type and Iam receving the data properly, once the data reaches XI, it could not map it to target structure.
In Moni, it showing
<?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">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_msgMap_R3_clarity_res_</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>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_msgMap_R3_clarity_res_: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
Root Cause: com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /NikuDataBus/Resources/Resource[6]/OBSAssocs/OBSAssoc/unitPath. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:286) at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:312) at
Iam getting the below message in Runtime Work bench
The XML page cannot be displayed
Cannot view XML input using style sheet. Please correct the error and then click the Refresh <javascript:location.reload()> button, or try again later.
XML document must have a top level element. Error processing resource

Hi,
This error occurs due to erroneous XML formatting. Check your mapping program and ensure that you supply valid input data.
Your XML should have a top level element. i.e. all elements must be under a single parent node, say the node with the name of your message type. XML should have a structure as per below -
<Message_type>
   <Node1>
      <Subnode1>
      </Submode1>
   </Node1>
   <Node2>
   </Node2>
</Message_type>
Hope this helps.
Regards,
Riyaz

Similar Messages

Mapping Runtime Exception - How to see complete error message?

Hello,
we have a mapping runtime exception in SXMB_MONI. However only the first 4 lines are displayed are shown in <SAP:Stack>, the rest of the error message is needed however for trouble shooting.
Is there any way to display the full error message? Executing a unit-test in ESR is not possible as there are some functions executed which just work during runtime.
Thank you.

Resolved: The full error is visible in the trace section of the header.

Runtime Exception in Message mapping

Hi Experts,
I have a scenario of IDoc to <third party adapter> cXML.
The message caught the below error
RuntimeException in Message-Mapping transformation : Runtime exception during processing target field mapping ......./ShipTo[2]/Address/PostalAddress/DeliverTo (suppressed field). The message is: Exception:[java.lang.ArrayIndexOutOfBoundsException: 7] in class com.sap.xi.tf._M_IDOC_to_cXML_ method getShipToContact$[, , com.sap.aii.mappingtool.tf3.rt.Q2QFunctionWrapper@253fdd8a]
Please suggest on what went wrong, as everything is working fine before.
Thanks in advance.
MK

Mk:
Please check if the source fields which are mapped to the target are all generated by the SAP Script and make sure that they have data so that when they are mapped to the target. If they are mapped and source fields don't have data then it may error out. Sometimes SAP Script might not generate a node if there is not data for it, make sure you handle that condition also.
RuntimeException in Message-Mapping transformation is
due to the missing TEXT_LINE element in the segment Z1VOBTH for the TEXT_ID 'INVOICE_TO_LOCATION'
I am not able to understand this. is Text_ID subelement of Text_Line?? Could you please post the complete error message as it is.

RuntimeException in Message-Mapping transformation: Runtime exception durin

Hi Friends,
Iam going test Message Mapping, i got the error like
RuntimeException in Message-Mapping transformation: Runtime exception during processing target field mapping /ns0:LeapIndent_R3_MT/Recordset/RowData/QTY_TNS. The message is: Exception:[java.lang.NumberFormatException: empty String] in class com.sap.aii.mappingtool.flib3.Arithm method formatNumber[, com.sap.aii.mappingtool.tf3.rt.Context@27f972cf]
Pls help me ..
Thanks & Regards,
Nvr

Hi Ravi,
Thanks for ur reply, the problem is solved, the Date field is Mandaratory, they are not mention the data field, so that way the problem is coming.
Thanks & Regards,
NVR

Runtime exception occurred during execution of application mapping program

Hi all
while testing intergase mapping i am getting this error----->
com/sap/xi/tf/_XI_FI_BAPI_CC_DOCUMENT_POST_REQ_MM:
com.sap.aii.utilxi.misc.api.BaseRuntimeException;RuntimeException in Message-Mapping transgormation:Runtime exception during processing target field mapping
/ns1:BAPI_ACC_DOCUMENT_POST/DOCUMENTHEADER/HEADER_TXT. THE message is:Exception:[java.lang.NullPointerException] in class com.sap.aii.mappingtool.flib3.TextFunction s method substring [null,com.sap.aii.mappingtool.tf3.rt.Context@2388897239]
I had used in the message mapping two user defined function scan you please look into the user defined functions, getPriviousMounthLastDate and FileName in the mapping for the target DocDate field
ihave used even this getPriviousMounthLastDate user defined function before using FileName
this is the code of userdefined function getPriviousMounthLastDate
Calendar cal = Calendar.getInstance();
SimpleDateFormat output = new SimpleDateFormat("yyyyMMdd");
cal.add(Calendar.MONTH,1);
cal.set(Calendar.DAY_OF_MONTH,1);
cal.add(Calendar.MONTH,-1);
cal.add(Calendar.DATE,-1);
StringBuffer dateBuffer = new StringBuffer();
output.format(cal.getTime(),dateBuffer,new FieldPosition(0));
return dateBuffer;
this is the code of userdefined function FileName
DynamicConfiguration conf = (DynamicConfiguration) container
.getTransformationParameters()
.get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create(
"http://sap.com/xi/XI/System/File",
"FileName");
String valueOld = conf.get(key);
return valueOld;
thanks sandep
Edited by: sandeep pendyala on Feb 6, 2008 6:52 AM

Hi Sandeep,
                 please check the trace file in SXMB_MONI,
                 which is avialble in response node.
                  if you analyze the trace, u can find-out....
                 error happend because of ehich field.
                first copy the inbound xml from MONI and test it at message mapping.
                 then also, u can find-out the error.
regards
mahesh.

Multi Mapping Base Runtime Exception

Hi all
Im getting a Base Runtime Excecption in Multi mapping. My scenario is File to IDocs.
when i test the message is IR its successful. However while testing End to end im getting Base Runtime excception.
Any pointers to this
--Keerthi

Hi Abhishek,
I tested from ID-Tools-Test configuration
Its stopping at the Interface Detarmination&Mapping step. Now the Base Runtime exception is gone. Geeting a new error"Messages in multi-message format can only be sent to one Adapter Engine".
According to the forum i've removed the Messages and Message 1 tag and tested.. But still the same error.
My scenario is File to IDOCs using multi -mapping. I've changes the occurece to unbounded.. Used Enhanced Receiver determination..All my configuration seems perfect Also in SXMB_MONI multiple messages as desired are present under 'Message Branch According to Receiver List'
But the error "Messages in multi-message format can only be sent to one Adapter Engine" is still there
--Keerthi

Reg: Runtime exception occurred during application mapping

Dear SAP Gurus,
This is Amar Srinivas Eli working currently on SOAP to SOAP Scenario on PI 7.1 Server.
I Would like to inform you that I have done all steps regarding DESIGN and CONFIG and also regarding SERVICE REGISTRY part successfully.
While Testing the data in the WS Navigator by giving the input parameters I am getting an error that
*<?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="1">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_HRS_LISTReferral_Response_MM_</SAP:P1>
<SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>
<SAP:P3>on: Cannot create target element /ns1:PI_ListRefer</SAP:P3>
<SAP:P4>ral_Response_MT. Values missing in queue context.~</SAP:P4>
<SAP:AdditionalText />
<SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_HRS_LISTReferral_Response_MM_; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns1:PI_ListReferral_Response_MT. Values missing in queue context.~</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
These are the steps I did while implementing..
1. Importing the XSD's successfully
2. Developed the design and config part and also checked nearly 3-4 times regarding both REQ and
    RESPONSE Mappings.
3. I already checked the link of WSDL once again...
4. Even I found REsponse Interface once again...
Still I am not getting where the error was ? Please guide me in detail in a right way in this issue.
Regards:
Amar Srinivas Eli
Edited by: Amar Srinivas Eli on Jan 13, 2009 7:53 AM

Hello,
I already checked all those queues and context fields////
Based on my Observation I found
1) As I am unable to view the SOAP BODY I increased the RUN TIME Trace Level to 3 and LOG_VAlue to 3
2) ANother most Important that I found later doing these settings are....
    I found Receiver Pay LOAD and I copied that entire pay load and pasted it in
    REceiver Message Mapping> Test Tab and Code->PASTED...and compared all those parameters
    in the TEST TAB and DEFINITION TAB in Tree View whether all the mandatory receiver mapped
    elements are coming I mean passing from source or not...
OBSERVATION::
I found that for nearly 3 fields there is a difference when I compared on Tree View in DEFINITION TAB and also parallely in the TEST TAB Tree View which I got by copied from MONI,,,,
see for example ::
CENTRE <----
> DISCHARGE DATE..
For going to CENTRE..here I found that in DEfiniition TAB...
Control Act Event-->Subject->document-->Component>Structured body> component> Section>Component>PatientCareProvisionEvent->EffectiveTime-->CENTRE
But immediately I have gone to TEST TAB and TREE VIEW and I found that respective field CENTRE is posting I mean passing any value or parameter to Discharged Date or not...
But I found that...
Control Act Event-->Subject->document-->Component>Structured body> component> Section>Component-->_PatientCareProvisionEvent_
This Implies that Effective Time and Centre are missing in the XML and I mean no values are passing to receiver right..
In PI XSD 's it is there but in I think after Compiling REQUEST MAPPING and while in returning to RESPONSE MAPPING I mean whenever the Response is posting to SOAP WEBSERVICE it is unable to found those target elements and I think due to this...
Am I Correct ?
If that is the case...Let me know where the issue is whether in the data present in the WEBSERVICE created on target side or in PI Side..any issue...
Regards:
Amar Srinivas Eli
Edited by: Amar Srinivas Eli on Jan 13, 2009 10:00 AM

Runtime exception occurred during application mapping

Hi All,
Please find the error message which we are getting:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_CRM_COD_ProductCategoryHierarchy_R~</SAP:P1>
<SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>
<SAP:P3>on: Cannot create target element /ns0:ProductCateg</SAP:P3>
<SAP:P4>oryHierarchyMassReplicationRequest/ProductCategor~</SAP:P4>
<SAP:AdditionalText />
<SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_CRM_COD_ProductCategoryHierarchy_R~; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns0:ProductCategoryHierarchyMassReplicationRequest/ProductCategor~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please give your expert Advice on the same.
Regards
RK

Dear Rableen,
As Muniyappan and peter told about the mandatory field value is missing for the target element
"/ns0:ProductCategoryHierarchyMassReplicationRequest/ProductCategor", I am able to see other fields are also not getting input data.
as below
"Cannot create target element /ns0:ProductCateg"
Request you to test with the payload in message mapping and activate the message mapping first and then edit your operation mapping and call the same message mapping in your operation mapping and activate all your objects.
Thank you!
Regards
Hanumantha Rao

Runtime exception occurred during application mapping in SAP PI

Hi Team,
Please help me regarding this issue is very urgent:
Runtime Error in configuration part:
Here i test the XML message in Receiver Determintion:
Below i am getting error:
Runtime exception occurred during application mapping com/sap/xi/tf/_MaterialStockUpdate_Multi_AllPlant~; com.sap.aii.utilxi.misc.api.BaseRuntimeException:The processing instruction target matching "[xX][mM][lL]" is not allowed
SXMB_MONI:
I am getting below error:
Runtime exception occurred during application mapping

Hi,
Actually my problem is what i am getting,I am trying to test the data in runtime workbench and configuration part copied from inbound payload XML structure .
I already sent the screenshots of above errors,
Configuartion:
Runtime workbench:
This the error i am getting below in "Runtime Workbench"
Error While Sending Message: Additional error text from response: com.sap.engine.interfaces.messaging.api.exception.ConfigException: ConfigException in XI protocol handler. Failed to determine a receiver agreement for the given message. Root cause: com.sap.aii.af.service.cpa.CPAObjectNotFoundException: Couldn't retrieve outbound binding for the given P/S/A values: FP=;TP=;FS=MHEPL_Sandbox_100;TS=;AN=MaterialStockUpdate_Multi_AllPlants_N;ANS=http://www.manipalhospitals.com/his/mm; in the current context [Unknown].

Runtime exception occurred during application mapping "EXCEPTION_DURING_EX"

Hi Gurus,
I am getting following error in MONI:
SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_MDM_CMS_Backfeed_Group_</SAP:P1>
<SAP:P2>com.sap.aii.mappingtool.tf7.MessageMappingExceptio</SAP:P2>
<SAP:P3>n: Runtime exception when processing target-field</SAP:P3>
<SAP:P4>mapping /ns0:BackfeedGroup/group/MasterId; root m~</SAP:P4>
<SAP:AdditionalText />
<SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_MDM_CMS_Backfeed_Group_; com.sap.aii.mappingtool.tf7.MessageMappingException: Runtime exception when processing target-fieldmapping /ns0:BackfeedGroup/group/MasterId; root m~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have tried to refresh the mapping cache and restart the message but stil this message persists.
For me it seems an issue with a wrong mapping or some wrong value in the inbound scenario.
Please suggest if any one of you had come across this error before.
With Reg,
Vikash

Hi Vikash
Whenever you have a problem in your mapping you will get this kind of error in monitoring
According to your log the problem is in parameter /ns0:BackfeedGroup/group/MasterId
First of all check your mapping. If it is fine than check the value of this parameter from your payload.
Also try to copy your xml and test the mapping in IR. Check wether you are getting same error there .
If same error comes than try to manipulate the value of that field and try the same test again
Regards,
Shradha

Message mapping tab works fine ,runtime exception

Hi ,
Need some advice... I get a runtime messge mapping error ( system error) failing the substring logic although when i download the same payload and run in test tab it works fine. Has anyone encountered similar issue ?
Thank you.

objects are active.Your second point is good ,but this error only happens when a load test is done , partciular messages throw runtime exception and fail in mapping on substring logic but when the same payload is downloaded and run via message mapping tabl it runs through. i will try disabling the substring logic nodes.
Secondly when i get a runtime exception ,i try to restart the same message and it goes thorugh successfully. So restarting in moni helps.... but does not explain why....
Thanks
Edited by: xi project on May 18, 2010 12:28 AM

About runtime exception in the mapping

Just i am trying to solve the blog http://weblogs.sdn.sap.com/pub/web/3228
in the sxbm_moni it is showing that runtime exception in massage mapping trasformation. But in that scinario i am not using any mapping program? Whithout using any mapping program how we will get exception in massage mapping?

Dear Rama Krishna,
I'm unable to open the link to web blog. plz provide the correct path so that I can help.
Regards
Praveen

Runtime exception for Date format

Hi,
Scenario : RFC to IDOC
found the error in my payload :
RuntimeException in Message-Mapping transformation: Runtime exception during processing target field mapping /ZORDERS06/IDOC/E1EDK03/DATUM. The message is: Unparseable date: "2008-05-19" at com.sap.aii.mappingtool.tf3.AMappingProgram.start
Here i has used DateTransformation from the Date Function.
How can i give the format for Target side here.
Regards,
yeswanth.

Hello Yeshwanth,
RuntimeException in Message-Mapping transformation: Runtime exception during processing target field mapping /ZORDERS06/IDOC/E1EDK03/DATUM. The message is: Unparseable date: "2008-05-19" at com.sap.aii.mappingtool.tf3.AMappingProgram.start
Here i has used DateTransformation from the Date Function.
In Date Trans Properties:
In Format Source date u select : yyyy-mm-dd
In Target Format u select: yyyy/mm/dd
Thanks,
Satya

Mapping runtime error

Hi Everyone ,
My scenario gives me an error in moni .
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM2SUSOrderCreate_</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>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_MM2SUSOrderCreate_: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
The root cause of the error is :
RuntimeException in Message-Mapping transformation: Runtime exception during processing target field mapping /ns0:PurchaseOrderRequest/PurchaseOrder/Item/ScheduleLine/Quantity/unitCode. The message is: Exception:[com.sap.aii.mappingtool.tf3.IllegalInstanceException: Too many values in first queue in function useOneAsMany. It must have the same number of contexts as second queue.] in class com.sap.aii.mappingtool.flib3.NodeFunctions method useOneAsMany[, , ]
Please do guide me where I am possibily wrong and what needs to be done

Hi Tom,
The Error shows you are using a standard function 'useOneAsMany', in which one of the input is 'unit code'
you have two provide 3 inputs to this standard function, where in the number of instances of the first two inputs should be the same. the instance of the third input may differ.
Please make the necessary changes, and test it.
Thanks,
Varun

Runtime Exception

Hi All,
I am getting following runtime exception in mapping,unable to trace. Plz advice :
<SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_Select_Material_to_AddMaterial_: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>

Hi Ravi,
I have copied the payload from SXMB_MONI and tested it in the test tab of the message mapping and its working fine here. But still throwing runtime excpetion error. Below is the my content of payload :
<?xml version="1.0" encoding="utf-8" ?>
- <Select_Material>
- <row>
<OAOC_PRID_CSID_ID>1212164</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1212164</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1212182</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1212182</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1212722</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1235161</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1235161</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1235161</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1235161</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1235161</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1235161</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1235207</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1235207</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1235207</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1235207</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1235207</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1235207</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1235207</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1235207</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1235207</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1235207</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1235207</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1235207</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1235207</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1335641</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1335641</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1335641</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1335641</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1357046</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1357046</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1357046</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1360599</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1367323</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1367336</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1367336</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1367336</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1367336</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1367336</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1399230</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426426</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426426</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426426</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426426</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426426</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426426</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426444</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426444</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426444</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426444</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426444</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426444</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426462</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426494</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426494</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426494</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426494</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426494</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426494</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426494</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426512</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426512</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426512</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426512</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426512</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426512</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426530</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426530</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426530</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426530</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426530</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426530</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426544</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426544</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426544</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426544</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426544</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1426544</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1428104</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1428104</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1428104</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1428104</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1428104</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1428134</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1428134</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1428134</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1428134</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1428134</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1428134</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1428134</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1428134</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1428134</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1428134</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1428152</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1428152</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1428152</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1428152</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1428152</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1428170</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1428186</OAOC_PRID_CSID_ID>
</row>
- <row>
<OAOC_PRID_CSID_ID>1428198</OAOC_PRID_CSID_ID>
</row>
</Select_Material>

Mapping runtime Exception

Similar Messages

Maybe you are looking for