cancel
Showing results for 
Search instead for 
Did you mean: 

How to Handle ABAP parsing error in Server Proxy .

Former Member
0 Kudos

Hi Experts,

     In server proxy (async), PI makes the call to ECC, Proxy would be invoked then abap code execution work continues.

Once the soap/xi adapter makes a call to ecc, message status would be set to 'successful'.

Suppose 'data type' is changed in PI and regeneration of Proxy is not done at ECC.

if we execute this scenario, it will leads to an exception.

How to handle these kind of exception in pi 7.31?

waiting for your inputs.

BR,

Avinash M

Accepted Solutions (0)

Answers (4)

Answers (4)

baskar_gopalakrishnan2
Active Contributor
0 Kudos

PI structure should match with proxy (stub) objects.  So if there is a change in Pi structure you have to explicitly regenerate proxy objects to reflect the latest changes for sure.  Remember these proxy objects are simple mediator pattern classes to call the exact abap objects in ECC.

ambrish_mishra
Active Contributor
0 Kudos

Avinash,

This will fail in ECC and PI (whatever version it is on) has no say.

You cannot handle this exception since it will fail because of inconsistent structure. If I am not wrong, if you transport the object in ECC to another environment, it will show error return code.

Hope it helps!

Ambrish

naveen_chichili
Active Contributor
0 Kudos

Hi Avinash,

>>Suppose 'data type' is changed in PI and regeneration of Proxy is not done at ECC.

It will throw error in MONI . You need to regenerate the proxy also if you change the Datatype.

Thanks and Regards,

Naveen

Dimitri
Active Contributor
0 Kudos

Dear Avinash,

In that case, you will get an error on the back end side. Normally to be seen in transaction SXMB_MONI as a red flag.

For SAP PI, all is fine and you will get status finished successfully.

You can create a small ABAP program to alert these kinds of errors and produce an alert e-mail.

Kind regards,

Dimitri