Issues with n:1 Operation Mapping execution in NW BPM

[Former Member]

Dear Experts,

We are facing issues with n:1 operation mapping execution in NWBPM. Details of the same is given below.

We are using SAP PO 7.4 SP 11

All the multi mappings (n:1 and m:n) in NW BPM are failing with the below error.

'Could not invoke service reference name d5a5a8f7-745f-4109-bb69-4fd9996f76c3, component name xxxxxx.com~nwpo~fore_syn~BPMcomponent, application name xxxxxx.com/nwpo~fore_syn.'. Further information: root exception Message 'EXCEPTION_DURING_EXECUTE: Error during operations mapping execution because of wrong payload{}. Check if input payload matches the actual operations mapping. '; message ID 'n/a'; log ID 'C000AC1AF90C7F2F0000000200004932'

We tried 2 options in input mapping as listed below but both gave the same error.

1. Had separate data objects in the input mapping step
2. Had a mapping step before the Operation mapping execution to combine all the input data objects to a single one. We have used the mapping input data type (under namespace http://sap.com/xi/XI/SplitAndMerge ) which gets created when import the Operation mapping to BPM.

In context data (under Manage Processes: Process Instances) we could see that all the data objects has proper values.

Also in SOA -> Logs and Traces -> Connectivity Logging & Tracing we could see that webservice call is failing but its payload contains proper values. We have tested the Operation mapping in ESR with same values and it is giving proper output.

We have also tried to test the webservice through the wsnavigator and it is giving the below error

Error during deserialization of SOAP re-response on the client: XML Deserialization Error. XML Node [Message1] is not allowed to be null. This is restricted by schema description.

Any pointers on the same will be really helpful.

Regards,

Manish Antony

[Former Member · Accepted solution]

Hi All,

We have checked with SAP on this. This is a product level issue and SAP is working on the same.

We observed that multi-mapping is working in lover SPs but it doesn't work on PO 7.4 SP11.

I will update once we have a solution from SAP.

[DaiQuach]

Manish,

This is not related n:m OM, it's all from restriction of the schema such as your input payload is missing some data that is required.

Your input data should be from External Message, look careful at the data structure.

[Former Member]

Hi Dai,

When I execute the OM in ESR with the same data, I am getting the proper output so it should not be an issue with missing data in the payload

[DaiQuach]

Hi Manish,

It's totally different. When you import OM to BPM then you will see the WSDL of that OM, after that when you create a Service Reference for the OM it'll actually create a WS hosted on BPM. So all data restriction is from the WSDL now.

Now do compare the schema structure in WSDL file with your input payload data.

[Snavi]

Hi Manish,

Can you put screenshot of your input and output mapping from your mapping step where you used operation mapping in BPM

and screenshot of the operation mapping in ESR

[Former Member]

Hi Navdeep,

PFB the screenshots

[Snavi]

Hi Manish,

your input/output message type in the operation mapping is not matching with the messages that are in the mapping of your automated activity in BPM.

if your operation mapping has been changed you have re-import it to BPM