File To IDoc Scenario

[Former Member]

Hi all,

my scenario is that file having multiple records will mapped in to segment of the idoc.

i already desinged and tested in test map area, working fine,

but getting error message in real testing end to end.

error message is:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Request Message Mapping

-->

- <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/_MP_L_NL_IM_RFGNInternalMovementToS~</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/_MP_L_NL_IM_RFGNInternalMovementToS_{: RuntimeException in Message-Mapping transformatio}</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error

and in trace i got message as

Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_MP_L_NL_IM_RFGNInternalMovementToSAP_13_</Trace>

<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /Z_L_NL_OPS_BAS_RFGEN_SAP/IDOC. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at

regards

somu

[Former Member]

There is a problem with the field /Z_L_NL_OPS_BAS_RFGEN_SAP/IDOC. Just check that this IDOC element is mapped or not otherwise do the map. Becase this is the top most element in the IDoc structure.

Your problem will solved.

Best Regards,

Vijay

[Former Member]

hi.. do the testing of the mapping with the runtime XML.. check this for same

/people/michal.krawczyk2/blog/2005/09/16/xi-how-to-test-your-mapping-in-real-life-scenarios

[Former Member]

can u provide the mapping that u have used. i mean the multiple node from source structure to the target node in the IDOC with the source n target structure

[Former Member]

the structure of the sender structure:

<?xml version="1.0" encoding="utf-8"?>

<ns:MT_L_NL_InternalMovement xmlns:ns="urn:pepsico:ops:internalMovement">

<Movement_Seg>

<TRDID>0000382121</TRDID>

<TRDTY>PSPL</TRDTY>

<TRDDT>20070731</TRDDT>

<WERKS>4100</WERKS>

<WERKS_R></WERKS_R>

<LGORT>5001</LGORT>

<LGORT_R></LGORT_R>

<LGPLA>F011L</LGPLA>

<LGPLA_R>F011L</LGPLA_R>

<EXIDV>187103980000014457</EXIDV>

<MATNR>000000000300000059</MATNR>

</Movement_Seg>

</ns:MT_L_NL_InternalMovement>

and in idoc side:

z*********

idoc

begin

z********* item segment

[Former Member]

i already mapped the idoc segments

still getting same error onlyy

[prasanthi_chavala]

Hi Somu,

Check once again the message mapping. In trace it is clearly telling that there is problem in producing target element. Also check the source xml message and context levels also.

Regards,

Prasanthi.

[Shabarish_Nair]

try to take the XML from SXMB_MONI and test the mapping - /people/michal.krawczyk2/blog/2005/09/16/xi-how-to-test-your-mapping-in-real-life-scenarios

I feel there is a conflict in the XML structure expected in the mapping.