Advantages of a shell system

[Former Member]

Hi,

We have had TDMS running for a while, DMIS 2006_1_700. We primarily use it to refresh QA and a dev client from production. In the past we have taken a flash of production and used the results as the source system. We run a TDTIM for 3 months and it takes several days. For development we push the results into a new client that has had a client copy with SAP_UCSV.

Our management has gone to Tech Ed and talked with unspecified other customers who have assured them that this can all happen much quicker. Apparently they pull directly from production, possibly devoting an application server in production to the effort. I've been told that using a shell system will speed the process up dramatically.

Would creating a shell speed things up? I assume we whack an existing client, create a shell client with TDMS, and then run TDTIM. Is that the process?

Does anyone have suggestions on running TDMS against a live production system, other than avoid high activity (since it takes days to run, it isn't clear how that is possible)?

Best regards,

Russ

[Former Member · Accepted solution]

Hi Russell,

Yes system shell has advantages as it is a speedy process than normal TDMS run.

A system shell is an SAP system that contains only cross-client data and the required client specific user and address data (client 000), but virtually no other client-dependent data. From a technical perspective, it contains only the basis tables and the table structures of the other tables (which can then be filled in a SAP TDMS run). Consequently, system shells are mainly meant to be used as receiver systems for TDMS runs. Depending on your specific requirements, it may also be possible for you to use a system shell as a development system.

Depending on your requirements, you can use one of the following types of shells:

Save shell: A save shell is a simple backup of the system shell created in preparation to an SAP TDMS implementation. When a new system is built up using a save shell, all transports that have gone into the related sender system after creation of the backup must be imported to the shell.

Master shell: A master shell is also created as a copy of the original system shell. However it is included in the transport chain and receives all transports that go into the production system. As a consequence, it always reflects the current status of the DDIC and cross-client information in the production system, and no additional transports are required when a new system is to be created based on the master shell.

Steps in creating system shell :

• 
  Preparing for a System Copy
• Creating a Control File
• Defining Environment Parameters and Excluding Tables
• Carrying Out the Database Export
• Determining the Initial Size for Tables and for the Database
• Updating the Control Files with a Modified Size for Tables and the Database
• Carrying Out the System Copy
• Creating a Reference Client and Installing SAP TDMS
• Deleting Non-Relevant User and Address Data in the Receiver System

Thanks,

Ravi