on 08-14-2014 10:23 AM
Hi,
I have searched already online but i am unable to find anything relevant.
The scenario is that I have an Inbound proxy for processing the incoming payload and in this code the call is made to the oubound proxy method and i am gettin the MAPPING.TRANSFORMER_EXCEPTION Exception occurred during XSLT mapping of the application
CALL METHOD outbound_obj->shipment_status_notification_o
EXPORTING
output = wa_orders_request_out
IMPORTING
input = wa_orders_response_out.
We just updated the orders_request_out with a single field and activated and regnerated the proxy in ECC and i can now see the updated structure.
However, if i take the payload from production and just pass the payload in debug to the above method call in both Dev and QA with the added field, I am getting the above error.
I cannot do the proxy debug in production unfortunately so i cannot see if this is happening only in Dev and QA.
Can anyone please help me as this is urgent and If i can get past this error i can actually test if processing is working as expected?
Regards,
Archana
check field type and max length.
To check if this is cache issue: Try some dummy change in Service Interface in PI and then save & activate. Once done, run SPROXY to re-generate the proxy.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Can you check if the field you have added is mandatory (1..1)? That could explain why the call is failing.
Regards,
Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mark,
I have checked the data type and the field occurrence is 0.1
The change was made only to the request structure as based on this field value some selection needs to be made. The Response structure was not changed at all.
I have regenerated the outbound proxy as well and surprisingly even though it was not modified it still did not give me a message that the proxy object has not changed. I had to activate it as changed to inactive.
I am also not sure why that happened.
Regards,
Archana
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.