Copy Standard ABAP Server Proxy-Re use?

[Former Member]

Hi:

I have copied the sap standard server proxy "PurchaseOrderConfirmation_In" from the name space http://sap.com/xi/SRM/Procurement/Global to my own name space and created a Interface ZConfirm_in.

The sap standard proxy PurchaseOrderConfirmation_In uses the code as below in method

CALL FUNCTION 'BBP_SAPXML1_PCO_CREATE_IN'

EXPORTING

is_pco = input.

So I copied the above code in my above Z interface of my method .

Now the Z proxy is not working when I do the proxy--test interface with the payload .

The payload works for sap standard proxy and goes inside the call 'BBP_SAPXML1_PCO_CREATE_IN'

and so on and process the payload.

The payload is not working for z proxy,it goes inside the call 'BBP_SAPXML1_PCO_CREATE_IN'

and then to the method XI_PROCESS_CALL_APPLICATION and then to the error CATCH cx_root INTO l_error..

Any clues on how to copy the sap standard server proxy and re use it.

Thanks in Advance..

[turmoll · Accepted solution]

> I have copied the sap standard server proxy "PurchaseOrderConfirmation_In" from the name space http://sap.com/xi/SRM/Procurement/Global to my own name space and created a Interface ZConfirm_in.

I assume that you have copied it in XI IR, haven't you? If yes, that's fine.

> The sap standard proxy PurchaseOrderConfirmation_In uses the code as below in method

> CALL FUNCTION 'BBP_SAPXML1_PCO_CREATE_IN'

> EXPORTING

> is_pco = input.

>

> So I copied the above code in my above Z interface of my method .

> The payload works for sap standard proxy and goes inside the call 'BBP_SAPXML1_PCO_CREATE_IN'

> and so on and process the payload.

> The payload is not working for z proxy,it goes inside the call 'BBP_SAPXML1_PCO_CREATE_IN'

> and then to the method XI_PROCESS_CALL_APPLICATION and then to the error CATCH cx_root INTO l_error..

>

> Any clues on how to copy the sap standard server proxy and re use it.

> Now the Z proxy is not working when I do the proxy--test interface with the payload .

In my view, first you should generate the proxy for ZConfirm_in message interface by tcode: SPROXY. Then you should make a copy of implementing class of PurchaseOrderConfirmation_In to your Z-class. Next, change implementing class in your ZConfirm_in proxy from empty (just generated) to Z-class (copy of sap standard).

It should work.

Regards,

Jakub

[turmoll]

Hi,

BTW: have you considered to use enhancements ...? If you don't change the message interface then it might be enough to implement your modifications ...

Regards,

Jakub

[Former Member]

I have awarded points .The solution you suggested was one way of going around but it did not work.

I am closing the thread now

[former_member189387]

Hi Kumar ,

Hope you have done the following

1. First you have added the Dependency to the SRM SWCV ( Delivered content ) to your SWCV in SLD with context as meta-data request ? Now you can see the delivered content with all namespace under your SWCV

2. Then you can use the Message interface ( Which already proxy generated one ) as your source interface in Interface mapping then target interface might be your own interface .

Here the point is we are using the standard predelivered, pre generated proxy class . For Eg , BP updated in applicatiion system it will call the proxy class of standard content which we have used as source in our interface mapping . IS push the data to you target structure as per your mapping .

Hence you no need to change/copy untill unless you do some enhancement .

3. Refer the michal's blog for enhancement [/people/michal.krawczyk2/blog/2006/11/14/xipi-data-type-enhancements-standard-business-partner|/people/michal.krawczyk2/blog/2006/11/14/xipi-data-type-enhancements-standard-business-partner]

Hope this clarifies .

Thanks.,

V.Rangarajan