STMS Configuration after system refersh

Workbench Organizer Reconfiguration

1. Logon on to client 000 of new refreshed system with DDIC.
2. Validate that user TMSADM is a system user type. If not, change it
to system user.
SE06
1. Select the Database Copy or migration option
2. Press the Post-installation Processing button.
3. When prompted Do you want to re-install the CTS?, press the Yes
button
4. When prompted for the Source System of Database Copy?, make sure
that the of the source system is selected. Press the checkmark button
to continue.
5. When prompted Change originals from PRD to QUA?, press the Yes
button
6. When prompted Delete TMS Configuration?, press the Yes button
7. When prompted Delete old TMS configuration?, press the Yes button
8. When prompted Delete Old Versions of transport routes?, press the No
button

TMS Configuration

1. Logon on to client 000 of the newly refreshed system.
STMS
1. Upon starting STMS, a window with the title TMS: Include System in
Transport Domain should be displayed
2. The information on this screen is automatically filled out from
information provided during the SAP installation and should be correct.
If it is correct, then enter a description for the system and press +S
to save.
Otherwise, press the Other configuration button and manually configure.
1. From the Overview menu, select Transport Routes
2. From the Configuration menu, select Adjust with Controller
3. Press the Yes button when prompted if you want copy the transport
routes from the controller.

Each time you do a change and save it, a versions of your STMS configuration is saved.

You can go back directly to a previous version that wroked fine by doing this:

STMS – -> Transport_Routes

Get_Other_Version

Then you can choose the version it worked fine before. (you can get there by activation date).

STMS – slog, alog and ulog

These files are one the important log files, to check the heart beat of the SAP server. We can understand by reading this logs files, Why the error has come and we can get an idea to overcome with the error. While doing the version upgrade, we have to check this log files. This will help you to understand the background processing.

SLOG: This log file provides the information on steps started by tp which have already run or in the process of running. SLOG is updated by tp.

ALOG: This log file provides the information what actions have performed when tp has started. ALOG also updated by tp.  You can find out the tp action in Transport phase log (tp log).

ULOG: All tp calls executed by the system while doing the transports or patching are contained in ULOG with the relevant call parameters.

Configure & Activate SAP TMS Backup Domain Controller

Prerequisites
In your transport domain, the SAP System that is configured as the domain controller is of special significance. If this SAP System fails, you cannot make changes to the TMS configuration during this time. Therefore if your transport domain contains more than three SAP Systems, we recommend configuring a backup domain controller. If your domain controller fails, the backup controller can assume the function of the domain controller.

Procedure
To configure a backup domain controller:

1. Log onto the SAP System functioning as the transport domain controller.
2. Enter Transaction STMS.
3. Choose Overview > Systems. The system overview appears.
4. Position the cursor on the domain controller.
5. Choose SAP System > Change. The brings you to the screen Change TMS Configuration: System <SID>.
6. In the field Backup, enter the SAP System you want to use as the backup controller of your transport domain.
7. Save your entries and distribute the configuration change.

Note:
• The SAP System that you want to use as the backup controller must have the same release version as the domain controller. Otherwise, configuration information may be lost when changing the transport domain controller.

Activating the Backup Domain Controller

Prerequisites
If your domain controller failed and you have to make changes to the TMS configuration, you can activate the backup controller.

Procedure
To activate the backup domain controller:

1. Log on to the SAP System functioning as the backup domain controller.
2. Enter Transaction STMS.
3. Choose Overview > Systems. The system overview appears.
4. Choose Extras > Activate backup controller.
5. Confirm the prompt.

Result
The backup domain controller is activated as the transport domain controller. The configuration change is distributed to all SAP Systems in the transport domain. The status bar indicates SAP System in which the configuration is being adjusted.

Note:
• When you have activated the backup domain controller, the “old” domain controller is automatically made the “new” backup controller, if it can be accessed.
• As long as the information that the domain controller has changed cannot be distributed to all the SAP Systems of the transport domain, the system overview of the new controller shows that the backup controller activation is still incomplete. You can only change the transport domain configuration if the backup controller is completely activated.

Syncmark left in STMS buffer after support package upgrade

Symptom

Support packages are applied successfully, but there is a transport request named “syncmark” left in the STMS import queue.

Environment

Release independent

Cause

SYNCMARK, which is present on the system buffer, consists of the entries that divide the number of packages that can be imported at same time by the upgrade/update tools.
These entries are only needed when TP is allowed to import several transport requests (or packages) in parallel, and it’s used to avoid that two transport requests that contain the same object are imported in parallel.
So only transport requests not separated by a “SYNCMARK” will be imported in parallel.

For more details, please see SAP Note 1616401.

Resolution

 Before removing SYNCMARK, please check first to see if either of the two situations below applies:

A. There are active import actions defined in transactions SPAM or SAINT.
Generally speaking, SYNCMARK should be automatically removed after implementation or deletion of the queues.

B. Enhancement packages are going to be installed via SUM or you are preparing an upgrade or the upgrade is in an unfinished state.

If either of the situations above is true, please wait until the import finishes to see if SYNCMARK can be deleted automatically.
If neither of the situations above applies or if SYNCMARK isn’t deleted automatically after import, you may remove it manually by following the steps below:

1. Save a copy of the buffer file.
(DIR_TRANS/buffer/<SID>)

2. Run the “tp delsyncmark” command to delete SYNCMARK.
tp delsyncmark ALL <SID> pf=/usr/sap/trans/bin/<Profile>.PFL

3. If step2 doesn’t work, delete the whole line of “SYNCMARK” from buffer file (DIR_TRANS/buffer/<SID>) directly.

After that,  you can run “tp cleanbuffer” command to delete all imported transports from the buffer file.
(eg: tp cleanbuffer <SID> pf=/usr/sap/trans/bin/<Profile>.PFL)

 

Source:2051448 – Syncmark left in STMS buffer after support package upgrade

SAP Unconditional tp Modes

Unconditional tp modes are intended for special requirements when you want to ignore certain rules of the Transport Organizer and Transport Management System. An unconditional mode is represented by a digit between 0 and 9. To use the unconditional mode when you call the tp program, enter a U in the command line and then add the required digits.

tp import transportrequest <sid> clientxxx U1
tp import transportrequest <sid> clientxxx U126
tp import transportrequest <sid> clientxxx U148

The u stands for unconditional force ( how hard you want to force the request into the system – do you want to overwrite without warnings, or softly try to load the objects).

0: Called a overtaker; change request can be imported from buffer without deleting it and then uncoditional mode 1 is used to allow another import in the correct location.

1: If U1 is used with the export then it ignores the correct status of the command file; and if it is used with import then it lets the user import the same change request again.

2: When used with tp export, it dictates the program to not to expand the selection with TRDIR brackets. If used in tp import phase, it overwrites the originals.

3: When used with tp import, it overwrites the system-dependant objects.

5: During the import to the consolidation system it permits the source systems other than the integration system.

6: When used in import phase, it helps to overwrite objects in unconfirmed repairs.

8: During import phase it ignores the limitations caused by the table classification.

9: During import it ignores that the system is locked for this kind of transport.

u128 is combination of 128 OF THE above points.

Eg:tp pf=/usr/sap/trans/bin/TP_DOMAIN_<SID>.PFL import XXXXXXX S4P U128 client=500

SAP Routes & Layers: Step by Step Configuration

Some content on this page was disabled on June 28, 2023 as a result of a DMCA takedown notice from Guru99 Tech Pvt Ltd. You can learn more about the DMCA here:

https://wordpress.com/support/copyright-and-the-dmca/

STMS Status of Importing Queue: (Requests do not match the component version of target system)

With Version SAP_BASIS 702 a new feature was added to the TMS system, tp was checking thecomponent version of the transport which was released and the component version of the system where the transport was going to be imported. If there was a difference, this difference was highlighted in the import queue (transaction stms_import) and if you tried to import the transport, the import would stop with a warning message about the difference in the SAPCOMPONENT versions.
You have error import status “Request does not match component version”.

Solution:
Set STMS  profile parameter : SP_TRANS_SYNC = OFF
This can be added via transaction STMS of the domain controller.
Call transaction STMS
Goto ‘Systems Overview’
Double click you wish to add the parameter to
Goto ‘Transport Tool’ tab
Goto ‘change mode’
Add SP_TRANS_SYNC to parameter column and OFF to value column
Save, activate and distribute

Related SAP Notes
1581638 SAP component checks no longer working in TMS
1577714 Transport requests in Check requirements phase

Symptom

The versions of the software components in the source and target systems for 1 transport requests do not match. At the time of the export, the release or SP level of 1 software components (ST-PI) were different in the export system from those in the target system.

Solution

Import for request *9xxxxx* already running in TP

Stop the tp process on the system (kill -9), but apparently it was always restarted. All the same I deleted the request from the queue and re-added it but I still got the little truck.

In the meanwhile however I also created a customer message at the SAP Service Marketplace and I got the following reply:

Kindly perform the following steps to resolve the issue:

1. Ensure that tp.exe process is not running at the OS level before proceeding with next steps.

2. STMS -> Import queue -> remove the requests with the status “RUNNING” (Truck Icon) manually.

3. STMS -> Import Monitor -> remove the obsolete entries “RUNNING” or error messages ( Select the entry, right click -> Delete option )

4. Ensure that there exists no clogged entries in TRBAT & TRJOB table entries. If exists remove them ( Ensure that tp is not running )

5. Run the TCode SE16 –> Enter the table name “TPSTAT” –> In the second field “TRKORR” enter the transport request number “D01K900481” –>Execute.

You will find an entry of transport request #*<SID>9xxxxx* in the table TPSTAT and now you need to delete transport request entry from this table as you can’t edit this table from R/3 level you need to delete this directly from the database level.

6. After deleting the transport request from TPSTAT table add the requests to the import queue and re-import them.

How to Modify SAP Transport Number Range

To achieve this we can follow 3 options since it’s a SAP standard table and it will not allow you to update it directly using table maintenance option tcodes like SE16, SE16N & SM30

1.  Get help from a ABAP programmer to help out on this to update the table value via program
2. Update the table filed value at OS level by small SQL query like how do you lock and unlock SAP* password reset activities
3. This is something backdoor method and its not recommended by sap, to do it go to SE16N tcode and enter E070L table and hit enter then you need to execute &SAP_EDIT in the tcode command box then it will enable edit option directly on table level, but you may face some security audit issues and this option is removed in EHP series

Above steps I performed in SAP 4.7 and used OS level SQL queries

SQL query for ORACLE DB:

update SAPR47.E070L set TRKORR=’LEDK901012′ where LASTNUM=’TRKORR’;

SAP Transport Management System (TMS) Overview Part-2

ADDING NEW SYSTEMS TO EXISTING TRANSPORT DOMAIN

1) After completely configuring an SAP system as Transport Domain Controller, you can add all additional systems in your transport domain. Adding systems in domain is performed in two steps:

• Sending a request from the new SAP system that is to be included in transport domain.
• Confirming the request of the new system in the transport domain controller.

For example: System QAS- System to be included in Transport Domain DOMAIN_DEV

System DEV- this system is Domain Controller

2) To include an SAP system in transport domain:

• Login to client 000 in SAP system that you want to include in the transport domain (QAS).
• After performing the Post installation Activities (SE06), Call Transaction STMS.
• Dialog box “TMS: configure Transport Domain appears”
• From the Dialog Box click on other configuration -> Include system in Domain      Provide the required details Target Host, System Number of transport domain controller.
• After saving the details SAP system performs the following actions:
  • Creates user TMSADM
  • Generates RFC destination required for TMS
  • Sends address data to Domain Controller
  • Sends profile parameters for configuring transport control program to domain controller
  • Configures SAP systems as single system
• Now after sending request from new system to TMS Domain controller. Log into client “000” of the Domain controller. Execute Transaction STMS, where it shows that system is waiting for inclusion in the transport domain
• The request must be accepted by the Domain controller in order to confirm the inclusion of the new system in transport domain.
• To do so, navigate to overview -> systems from the Domain controller Initial Screen, In the System overview, it appears as system is waiting to be included in transport domain.
• Highlight the SAP system and choose SAP system -> Approve from the main menu and confirm the prompt later distribute the updated configuration.

Initial screen of TMS

From TMS main screen overview->systems, Provides you the list of systems that were added to your

TRANSPORT – DOMAIN (DOMAIN_)

You can create various types of systems

In Communication Tab, you can add Backup Domain Controller, Workflow Engine and also can run RFC Connection Test

We can modify the Transport Tool Parameters (TP_DOMAIN_.PFL)

Transport group provides you with list of all the R/3 systems that come under same DOMAIN-GROUP (GROUP_)

Import Overview

Displays list of opened requests in all the systems in Transport Domain and can also monitor imports, check import logs.

Enter Import Queue from Import Overview screen, this provides list of imports that are released in development,

(Once change request are released in DEV, they are visible in the import queue of the target system)

Change Request  K9(5-Digit serial)  ——  DS1K900025

All the imports can be monitored and Import History, as below

Import Monitor show you complete list of Import activities for each request along with the TP command

Checking consistency

SAP Systems->Check->Transport Tool->provides you the result of check with RFC, TP interface, TP call, TP Interface.

SAP Systems->Check->Transport Directory-> provides you with usr/sap/trans consistency check

Transport Routes:

Consolidation Route (DEV – QAS)

Delivery Route (QAS – PRD)

RFC

TMSADM is automatically generated when TMS is configured.

TMSSUP:

This is temporarily used by R/3 systems by domain controller while distribution and activation.

Transport Domain

This maintains all R/3 systems in a domain that have same transport group and common Domain controller “DOMAIN_”

Workflow Engine is configured in some cases when there is a need of transporting change requests directly from DEV to PRD

The QA approval config is done after the workflow Engine setup. This helps the admin to finalize the change request and approve while transporting change request from DEV to PRD