cancel
Showing results for 
Search instead for 
Did you mean: 

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

Former Member
0 Kudos

Hi,

A scenario File - BPM - BAPI call was developed, as described in blog 'RFC scenario using BPM' cfr. link

/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit

The Mapping is as follows:

MT_EDB_MATERIAL_REQ (1:1) --> BAPI_MATERIAL_EXISTENCE_CHECK (1:1)

MATNR (1:1) -


> MATERIAL (1:1)

When executing the scenario, an error appears in the trace of SXMB_MONI, step 'Request Message Mapping'

Cannot produce target element /ns1:BAPI_MATERIAL_EXISTENCECHECK. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd....

I tried the following:

1) import the XML-file into the testmapping: executed successfully

File:

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

<ns0:MT_EDB_MATERIAL_REQ xmlns:ns0="http://agfa.com/SD_EDB">

<MATNR>15P6X</MATNR>

</ns0:MT_EDB_MATERIAL_REQ>

2) Removed the mapping on node level and left mapping only on element level (material): same error

3) Activated the message mapping, interface mapping, determinations, etc again...:same error

4) Removed the Interface Mapping and created it again: same error

5) Compared the version ID of the Interface Mapping/message mapping in the Monitor trace with the version ID of the IR and saw that there was a difference.

After the CPA full cache, SXI_CACHE full refresh and object refresh in the IB Administration, the differences remain, and also the error....

Anybody an idea ?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi

>>>Cannot produce target element /ns1:BAPI_MATERIAL_EXISTENCECHECK. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd....

The error clearly says that one of the occurrence value for the target node mentioned is not coming from the source during mapping. The easiest way to solve the problem is as follows

<b>

First Execute the mapping as pointed out by "Raj" and the following steps.

</b>

1. Goto the Mapping Editor

2. Double click on the target node that is causing the problem here BAPI_MATERIAL_EXISTENCECHECK.

3. Right click on the same node and select "DisplayQueue".

4. View the Queue.

5. YOu will find "Suppress" entries, which means a value is expected but no value is coming in.

6.Go from right to left and check each node in the mapping and you will be able to trace where the suppress node comes from and take appropriate action

regards

krishna

Former Member
0 Kudos

Hi Krihnamoorthy (and previous),

After some changes and activations, the problem was solved, but in the end I don't understand what was the possible cause. Now I know were to look for these kind of problems. Thanks (I granted points).

Regards. Jan Macken.

Former Member
0 Kudos

Hi

Glad you were able to find the fix .

regards

krishna

Answers (2)

Answers (2)

justin_santhanam
Active Contributor
0 Kudos

Jan,

First execute the mapping in test editor and check the results. Please let us know ur proceedings.

Best regards,

raj.

Former Member
0 Kudos

Check the input data that is coming...check for the mandatory fields....check the mapping you are using.