cancel
Showing results for 
Search instead for 
Did you mean: 

Query on Company Code and Time Slice Reduction in TDMS

Former Member
0 Kudos

Hi Experts,

We have a requirement wherein we have to use TDMS to extract the data for only one company code and the landscape is as below :

TDMS (Control+Central)-Separate Box.

Sender and Receiver-2 Clients on the Same box

I understand that we can configure Sender and Receiver on the same box (with some performance issues because of reading and writing on the same database).

1) The question is what is the best option for data transfer, should we do a full client transfer or to use Shell Creation. Shell creation is used when the sender and receiver repositories are not synchronized and in this case, since both the sender and receiver are on the same box, repositories are synchronized.

2) We would like to extract a subset of the data for one company code by ‘Company Code and Time Reduction’ approach and we should not transfer
any config data for other company codes which are not selected. What will happen to the cross client configuration data for the company codes that
are not selected for transfer, will those get copied over? Do we need to delete them later in the receiver system?

Thanks very much,

Best Regards,

Savitha

Accepted Solutions (1)

Accepted Solutions (1)

bxiv
Active Contributor
0 Kudos

For question 1, I don't think you want to attempt a shell creation as the end result is an empty system; its intention is to create a new system based on the repository of the sender system.  I would think if you attempted this while using the same box you would wipe out all of your transactional/master data/customizing data.

For question 2, TDMS is a client specific tool if you TS and CC filter the data this is for transactional/master data/customizing.  An example of this would be printers.

What is the purpose of moving data from one client to another within the same system?

Something to consider, leverage TDMS for a client deletion scenario and then do a local client copy.

Former Member
0 Kudos

Hi Billy,

Thanks very much for your reply.

Question-2-There is a Test System,TES/300 for ex., created with the copy of production data (System refresh) which contains 50 Company Codes. The requirement is to have another client, TES/400  with the data pertaining to only two company codes out of 50 CCs. To achieve this, we can use TDMS CC (and TS) to select only two Company Codes in TES/300 (their respective master data/transactional/customizing) scramble the data and transfer the data of these 2 Company Codes to TES/400. This client will contain only subset of the production data that is required for testing. We would not want the configuration of the other 48 company codes that haven't been selected to be copied to the new client, although I'm thinking some of the data like intercompany vendors will be copied over.

You have mentioned we could leverage TDMS for a client deletion scenario. We would like to keep TES/300 intact. Can we do a full client copy of TES/300 to TES/400 and then use TDMS delete function in TES/400 to delete the not required company codes data? Is the Company Code reduction solution available for the deletion scenario?

Best Regards,

Savitha

bxiv
Active Contributor
0 Kudos

Client deletion scenarios are no different than deleting a client the old fashion way (except faster) so no there is no way to save 2 company codes.

Why are you doing a system refresh for one client to then duplicate another client with only 2 company codes?  If you are going to use TDMS, let it bring over the 2 company codes you need on the Test system and save time not worrying about another client?

Answers (0)