Thursday, August 11, 2016

STMS issues after a system refresh

So the other weekend we carried out a system refresh of the QAS system with Production.

Apart from the standard reconfiguration of RFC's , re-importing of transport request and other post refresh activities we encountered an issue where users could not release transports to test using Solution Manager , and also in transaction STMS queues users were being prompted for a username and password when trying to refresh the transport queue.

After alot of checking on and resetting the TMSADMIN password due to user failed log in errors, RFC generation and all we discovered it is easier to recreate the whole transport management system from scratch and redistributing the setting from the domain controller.

This saves you time from groping around trying to pin point the problem!

Tuesday, August 9, 2016

Locked objects in transport request

While doing an upgrade of our ST/PI component (service tools for applications 0 from SP09 to the new SP13 using SPAM i encountered and error that some objects were locked in a transport request.

The issue is the owner of the request was a Solman Admin user in a different client and i could not release the transport request because it was for implementation of a SAP note and its status was inconsistent !

However i managed to log in to client 001 and using transaction SE03 I was able to unlock the objects in that transport.

Very powerful tool SE03 but be very careful what you use it for as you could cause major system inconsistencies !!!


Monday, August 8, 2016

A QUESTION !!!

Today I am seeking some information..Does anyone know what it takes to switch from extended classic SRM deployment scenario to classic scenario?