Problem solve Get help with specific problems with your technologies, process and projects.

Taking instances out of the TMS landscape

An instance cannot be taken out of the TMS landscape if it has been copied over by another instance. Here is how to do it after the fact.

An instance cannot be taken out of the TMS landscape if it has been copied over by another instance. Here is how to do it after the fact.

Let's say you need to refresh a sandbox (TEC) with your Quality Assurance (QA) instance but forgot to take TEC out of the TMS Landscape before the refresh and consequently were unable to afterwards. The Domain Controller for TEC is PRE. This is a two-system landscape but will work with three system landscapes.

The problem is that PRE will not be able to add TEC back into the landscape once post-processing is finished because it never knew it was deleted from the landscape.

This was done on a 4.6C system using Extended Transport Control.

Solution:

Delete the contents from the following tables:

TMSACTDAT
TMSALOG
TMSALRTSYS
TMSBUFCNT
TMSCDES
TMSCDES_S
TMSCDOM
TMSCDOMT
TMSCNFS
TMSCNFST
TMSCSYS
TMSCSYST
TMSMCONF
TMSPCONF
TMSPVERS

Now the Domain Controller can accept TEC as a new system and you can use the TMS landscape versioning to retrieve the version of the landscape that you desire.
This was last published in September 2003

Dig Deeper on SAP Basis administration and NetWeaver administration

PRO+

Content

Find more PRO+ content and other member only offers, here.

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

-ADS BY GOOGLE

SearchManufacturingERP

SearchOracle

SearchDataManagement

SearchAWS

SearchBusinessAnalytics

SearchCRM

SearchContentManagement

SearchFinancialApplications

Close