Regarding Operational Specific

[Former Member]

Hi,

Could any one please give more information on Operational Specific concept in SAP PI

Regards,

Anusha Penneru.

[iaki_vila]

Hi Anusha,

First of all, thank you Mark for comment the restriction, i didnt know them.

My few cents, the operation-specific check in the receiver determination is only a way to make the configuration available to the webservices operations concept, this concept  technically allows to add more bindings inside a WSDL. Functionally means that with a same functional object like for example ("Customer") you can add some opertation to it, like add, remove, insert, etc all inside the same WSDL or the same webservice.

You can check Aashish Sinha's blog http://scn.sap.com/community/pi-and-soa-middleware/blog/2013/04/03/setup-multiple-operations-scenari... where you can find an easy example and good explanations.

Regards.

[markangelo_dihiansan]

Hello Anusha,

The operation-specific service interface validates/reads the root of the message type for that operation. This is useful if you have many operations/message types, if you will be sending binary messages (e.g pass-through) disable this option.

There are some limitations:

1. You cannot have the same message type as the root message for the request unless you create it in a different namespace

2. It is not possible to generate an ABAP Proxy when using different types, e.g when one of your operation is a message type, the other is an external definition. All of them has to have the same type.

Hope this helps,

Mark

[Former Member]

Hi Anshu

When your service interface has multiple oprations then you go for operation specfic option in the receiver determination.By this way you can define multiple receiver for multiple oprations of your service interface.

Otherwise we go for non-opration specific option.