cancel
Showing results for 
Search instead for 
Did you mean: 

TDMS 3.0 for ERP 6.0: step by step procedure for TDSH6 Shell creation

Former Member
0 Kudos

Dear All,

I need to perform shell creation. I have never done this and need help with step by step instructions.

I need to refresh my my development system with a TDMS shell creation from production client in production system.

I am familiar with TDTIM and performed many TDTIM copies. I have gone throught the master and operational guides for TDMS also.

I would try to list down my understanding so far after reading the guides.

Please correct me if I am wrong ang also suggest correct steps.

1. All my three systems (central, sender and receiver) are ready from installation point of with with authorizations and latest SPs.

2. I log into Central/Control system and start a new package "ERP Shell creation package for AP Release higher 4.6 "

3. AS I have never executed this option I do not know what are the stps inside it.

But I assume I should be asked for the source client details from which shell needs to be creates. (000 or pruduction client)

What type of shell : slave or master?

4. During the shell creation from sender system client, is there a downtime for sender system.

5. Once the shell creation is done an export dump will created.

6. I perform all the preprocessing steps of a homogenous system copy on the receiver systems.

7. Stop receiver system, start sapinst database instance installation with homogenous system copy with R3load option.

8. Provide the export dump location to sapinst.

9. After database instance is installed, perform system copy specific post processing steps.

10. Afte the system is ready it has only one client 000 now available in development system and i need to create a new cleint from 000 which will act as my new development cleint.

I request all you experts to please provide your comments at the earliest as activity would be starting from 5th of this month.

Regards,

Prateek.

Accepted Solutions (0)

Answers (1)

Answers (1)

0 Kudos

Hello,

Your steps (as mentioned) are almost correct.

- You need to create the package ""ERP Shell creation package for AP Release higher 4.6 ".

It will not ask you anything like source client details and about the type of shell.

Once the package is created , it will show you the process tree (similar to the TDTIM package) with the list of the activities.

Some of the activities are information activities and some are executable activities.

Please go through all the activities and their documentation. it will lead you to , what steps to be done and in what order.

Also if you are on SP16, please apply the note 1553433.

Thanks and Regards

Isha

Former Member
0 Kudos

Hello Isha,

Many thanks for the answers

Some queries

1. Is there a downtime for Production system (sender system).

2. Shell creation works on both Production and 000 client or only Production client,

3. when I import the the dump using sapinst, how many clients are available in receiver systems.

4. Soem where in the guide it is mentioned that downtime depends on the type of shell I create.

Kindly suggest should I create a master shell or slave.

5. Once I execute this activity of shell creation for lets say receiver system A, then can I use the same export dump for second receiver system B.

6. Lastly please suggest the activity execution time as customer has provided us 2 days to execute this activity.

Many thanks in advance and awaiting your reply.

Regards,

PRateek Khare.

Former Member
0 Kudos

Hi,

Let me answer your questions.

Some queries

1. Is there a downtime for Production system (sender system).

SAP recommends that nothing much should be going on during the export of the Sender(PRoduction) system, but so far i have never encountered an issue doing the export in online mode.

2. Shell creation works on both Production and 000 client or only Production client,

Be carefull!!! - A Shellcreation is a normal Homogenous Systemcopy using R3load. You will create a 'new' system with the DDIC and clientindependent customization of the Sender system. ALL former data of the target system will be deleted.

You mention that you will refresh a development system that way. Please be aware of the implications that a development refresh contains. That said. After the refresh you will have the 000 client and parts (users ... authorizations of sonder) of the other clients on the new system.

3. when I import the the dump using sapinst, how many clients are available in receiver systems.

See above. All client configuration will be available, but nearly no data will be in these clients except 000. A manual part of the Shellcreation is to clean up the target system (delete the clients that are not needed) This is a fast process.

4. Soem where in the guide it is mentioned that downtime depends on the type of shell I create.

Kindly suggest should I create a master shell or slave.

Hm. The master shell is just a concept that you create a complete new system and put that system into your transport landscape without filling it with data. You can then use that system as the source for a normal (database dependent) systemcopy without impacting your prod system. The result is a very small copy that can be repeated very often without an impact to prod/QA...

Downtime is as described in point1 not required

5. Once I execute this activity of shell creation for lets say receiver system A, then can I use the same export dump for second receiver system B.

Yes

6. Lastly please suggest the activity execution time as customer has provided us 2 days to execute this activity.

This depends on your knowledge of homogenuous systemcopies and the preparation + some items like size of stxl and other tables that will be exported/imported. If you are very familiar with the systemcopy process using R3Load 2 days are feasable.

I have seen shellcreations done within 1-2 days but also much longer ones!

As a prerequisite i would always recommedn to have the latest R3* + migmon exe available on sender + target.

I hope i have clarified some of your items.

Best Regards

Joerg

Former Member
0 Kudos

Hello Joerg,

Many thanks for clearing my doubts.

Now it is much more clear.

For point 2:

Problem:

WE were using our development system. THen while applying support packages, client 790 was deleted and hence several objects were not imported in 790 client.

solution by SAP:

SAP then suggested us to do a copy from production system using TDMS shell creation.

THus we need to create our development system again using shell creation.

After the developments system is created we would then do a local client copy to 790, so that development system is as before.

Could you please provide your opinion on this?

And any steps that needs to be considered.

Many thanks again.

Regards,

Prateek Khare.

Former Member
0 Kudos

Hi,

For point 2:

Problem:

WE were using our development system. THen while applying support packages, client 790 was deleted and hence several objects were not imported in 790 client.

solution by SAP:

SAP then suggested us to do a copy from production system using TDMS shell creation.

THus we need to create our development system again using shell creation.

After the developments system is created we would then do a local client copy to 790, so that development system is as before.

Could you please provide your opinion on this?

And any steps that needs to be considered.

#####

So is your development system itself still ok and only one client is missing (i do not know what your 790 client is used for!)

and what other clients are available on the current dev system.

If you only need a new client with some testdata you do not need to run a Shellcreation but you can do a tdms erp run with time slice. If your whole dev system is broken due to the import issue then you can do a shellcreation to create a new system.

So i cannot really provide an option based on the current information. Sorry

Former Member
0 Kudos

Hello Joerg,

Your second option is right. DEv system is broken hence using shell creation to create the dev system again. 790 is the development client.

@Isha: Many thanks.

Many thanks guys.

Regards,

Prateek Khare