Skip to Content
Author's profile photo A Prasad Rao

Transaction aborted; switch for SAP TM resource master is inactive.

Installed ADD-ON SAP TM 9.3 on SAP Netweaver 740 SPS 13. ADD-ON SAP TM 9.3 must not be installed on existing SAP SCM 7.0.

When executing  transaction code  /n/scmtms/res01 and  then press enter  key, immediately  error message  appeared ” Transaction aborted;  switch for SAP TM resource  master is inactive”.




Transaction code SPAM




As shown in the  above Kernel patch  number is  300.  This is  the  latest  SAP kernel  patch.

But the  error is  nothing  to do  with   kernel patch.

root cause of this issue was due to program error.

The main program is “/SCMB/TMS_RESOURCE”. ENter tx code se38  as shown in the figure below


Click Display

Scroll down till you find the lince code as shown in the figure below


As shown in the above figure, it should be corrected as “EQ abap_true.”

This is because  after double click on “scmb/cl_tmsres_switch”  another screen appeared as shown in the figure below


Then click on button just below Overwrite-Ext (highlighted in small red circle as shown in the above figure) ,

Another screen appeared. there you can see as shown in the figure below.


As shown in the above it is Active and aslo abp_true. hence change th coding as shown in the figure below


Make changes the correction by clicking from display to change. It ask for SSCR object key.  Request the key in SAP MArket Place .

Save after making correction as shown in the figurer above (highlighted in yellow colour). Pop-up screen displayed for  transport request number.

close the screen.

Re-execute transaction code again as shown in the figure below


Now the output of the transaction is displayed as shown in the figure below.


Finally  issue  resolved.  No OSS  note  is  available for the above issue.

Assigned Tags

      1 Comment
      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      Hi, Prasad

      Also please consider that the business function SCM_SAPTM_SCMB_FND is active in your system in order to be able to access master data properly.

      We had similar issue and was resolved by simply activating the BF