How to copy ESS/MSS DC to new DC for custom changes

[Former Member]

Hi, all.

Our env is like the following.

NW2004s SP11 + ESS/MSS(ERP 2005)

We are developing some copy add-ons(copy original ESS/MSS

DC and create new one). We don't want a direct modification

of ESS/MSS because it needs too much admistrative tasks whenever

we have to apply new SPs.

So, in order to copy the original DC and create new one with

new package name and object name, we are considering using the

steps which is describe in the following helpful weblog.

How to migrate a DC to a new SC by Helmut Tammen

/people/helmut.tammen2/blog/2006/01/30/how-to-migrate-a-dc-to-a-new-sc

It seems that it works right now

Is there anyone who used this steps for ESS/MSS? Any know-hows

or problems when applying to ESS/MSS?

Or is there any other easy way to copy ESS/MSS DC to new DC?

Best Regards.

Sejoon

[Former Member · Accepted solution]

Hi Sejoon,

Why do you want to copy the DC's to a custom SC. It gives you a lot of problems with references in the WebDynpro's and in the backend customizing.

The ESS/MSS applications are in a separate business package which you don't need to upgrade whenever you apply a patch to your portal, so there is no administrative effort.

Also, if you copy the DC's to a custom SC, and you do want to upgrade the package, then you still have to copy the DC again, and redo all your changes.

Anyway, SAP's recommended approach is described in the NWDI cookbook; it says not to copy the DC's, but change directly in the original.

Johan