SWCV for Non SAP products

[Former Member]

Hi Experts,

While dealing with different systems, suppose I am dealing with WS to RFC scenario. Do I need to create SWCV for WS??

Generally, we use SWCV of SAP only.Even if we create SWCV of Non SAP products, will it work??

Please suggest.

Regards,

Sushama

[former_member200962]

We do not create SWCV for a protocol...it is created in accordance with the business unit of your client...for more information do refer page 6 of this document:

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40a66d0e-fe5e-2c10-8a85-e418b59ab...

Similar document is available for lower versions.

Regards,

Abhishek.

[Former Member]

There's no hard and fast rule for creating a SWCV for WS or for that matter any other service.

Have a look at this blog.

/people/thorsten.nordholmsbirk/blog/2006/07/25/structuring-integration-repository-content--part-1-software-component-versions

But whats important is the mapping part and for that you import the WSDL of the WS and use it. Doesn't really matter if the SWCV is dedicated for sender,receiver or transformation. But yeah recommended way is to go with this approach.

Regards

Soumen...

[Former Member]

Hi ,

Normally it is recommended to have three different SWC ..which represents the sender,receiver and the transformation one..

so that all the sender and receiver systems related interfaces will be in one SWC...and also very helpful for maintenacne and extendability....

so in your case you can create for one SWC for the receiver (WS)...if neeeded....

there is no point like not working if one or different SWC...all need is to have the existing mapping name in interface mapping and the same in interface determination...only these things will be checked by runtime...

HTH

Rajesh