cancel
Showing results for 
Search instead for 
Did you mean: 

SWCV SAP BASIS use for customer namespaces - OK?

Former Member
0 Kudos


Hi,

another interesting question for me.

The customer used a number of SAP defined SWCVs to add lots of namespaces and interface development.

Thinking about content update I am in doubt if there is a risk with that doing regarding later SLD and SWCV content updates from marketplace.

Any idea if content updates could delete all these customer developed namespaces?

SLD content update is no issue as you will not import this SWCV again to the ESR.

What could be the reason for a SWCV update (as I know there are some for business specific purpose like provided for tax interfaces )

Probably I am thinking too much ABAP where changing SAP original reports/FMs could have this effect.

Any ideas?

Best regards

Dirk

Accepted Solutions (1)

Accepted Solutions (1)

marksmyth
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Dirk,

The SAP delivered SWCV's are not designed for custom developments. The reason for this is that any new content update e.g. if you move from SAP Basis Content SP12 to SAP Basis Content SP14, the custom developments will be lost during the import of the SP14 content.

SAP constantly provide updates to the various SWCV's and this will usually contain new configuration objects e.g. new sender/receiver interfaces etc.

What we recommend is that if you wish to use any of the configuration objects provided in the SAP SWCV's, they should be copied into your own custom SWCV/namespace etc. This way, you will not run the risk of losing any of your custom developments with any subsequent update provided by SAP.

Regards

Mark

Former Member
0 Kudos

Hello Dirk,

I can only add to Mark's statement that migrating the namespaces to other SWCV should be no operative problem. The SWCV is not needed at runtime, and as long as you don't change namespaces migration can be done without any other changes. You can use the "Release Takeover" feature for that.

Regards,

Jörg

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

found the issue that gives the answer.

The customer added all his SAP Proxies to a SAP SWCV and namespace. From 7.31 (expect from 7.1) ECC systems will no longer import the SAP SWCVs to SPROXY. So you cannot use them here.

You need to create a customer SWCV and recreate all methods in there for the Proxies.

Regards

Dirk