Moving Your Solution From Test to Production – The Copying Process and Duplicate Work Required

When the test solution profile is copied over, only certain configurations are copied to a new (fresh) production tenant.

Many customisations have to be either imported or manually redone in the production tenant.

I have highlighted below the copying processes and additional work that is required in the production tenant.

The lists below are in no way exhaustive but will serve to provide a guide as to the work required during the move from the test C4C solution to the new production system.

Initial test system copying by SAP to the new production system will only include:

The scope

All the fine tuning entries

KUT adaptations, extension fields,    (as long as non previously exist in Production)

Page layouts & code list restrictions  (as long as non previously exist in Production)

Level 0 master data objects:

These will be copied over to the staging area of the migration workbench but will need to be manually committed to the new production tenant:

BANK_DIRECTORY (bank directories)

ORG_CENTER (organizational structure)

JOB (jobs)

PRODUCT_CATEGORY (product categories)

L0_TRANSPORT_LANE (transport lanes)

L0_TRANSPORT_ZONE (transport zones)

Level O master data is automatically transferred to migration templates which then sit in the staging area as prepopulated templates awaiting import by the user into the production tenant.

Customisations Requiring Export from Test and Import into Production System

Many configurations that have been created in the test tenant will require exporting out of the test system, saving on to your desktop and then importing into the new production system via the import function in each of the respective business objects or workcentres.

The non exhaustive list below gives you an idea of the type of customisations requiring export from Test then import into Production:

Code list mapping

ID mapping

Customised and New Reports

KPIs & Dashboards


Custom objects

Language Adaptations

OData service

Organisation chart (if not accepted via Level 0 data transfer)

Lead routing

Realignment runs

Customisations which have to be manually redone in the Production tenant.

There are some customisations which cannot be copied or imported into the Production tenant.

Below are some of the customisations which have to be manually redone in the production system.

Business roles

Workflow rules

Work Distribution

Email and fax settings

Service Level Agreements

Mashup authoring

Report assignment to workcenters

The extent and nature of the replication work required will of course depend on the scope of the solution being implemented.

I hope this helps to guide fellow SCN users during their project implementations.



New NetWeaver Information at

Very Helpfull



User Rating: Be the first one !