SAP BASIS TMS Issues n Resolution

TMS Issues and resolution ..

TMS ISSUES

Q. I installed the kernel patch 6.40 level 098 and now the transport system is not working properly. The job RDDIMPDP is not starting, although I start it manually. I keep receiving error messages. How should I solve this problem?

A: First go into SE38 in both client 000 and your working client. Run program RDDNEWPP. This will schedule program RDDIMPDP with proper parameters. Then, check if any "TP" programs are running . If this is the case, check in /usr/sap/trans/log and look for the most recent files contents. - See more at: http://www.saptechies.org/transport-problems/#sthash.mmIHit3k.dpuf

 

q.2     SAP-TMS Transport issue with DOM_CTL error message

You may face issue while performing transport request forward or import stage with error DOM_CTL with module "CALL_FUNCTION_CONNECT_ERROR".

The error mostly occur in QA systems after performing DB refresh or after performing system copy.

This error occur because of the wrong / non relevant entries of the current system in secure store of SAP.

If searched in google for this error, you may end up in executing SECSTORE_CLEANUP report to clean the secure store and refresh it.

This solution may not help in all kinds of scenario's, the below  mentioned were the best solution

Solution is by migrating the invalid SECSTORE entry HMAC_INDEP/RFC_EXTERNAL_TICKET_4_TRUSTED_SYSTEM, provided that SAP Note 1491645 was implemented.         

The validity check and the migration of an SECSTORE entry are described in SAP Note 816861.

1) Solution 1:- (Manually correct the SECSTORE)

Call transaction SECSTORE

Choose "Execute" (F8).

In the entries that are displayed, delete the entry /HMAC_INDEP/RFC_INTERNAL_TICKET_4_TRUSTED_SYSTEM if it is marked with a red traffic light. 

In the entries that are shown, delete the entry /HMAC_INDEP/RFC_EXTERNAL_TICKET_4_TRUSTED_SYSTEM if it is marked with a red traffic light.

After the deletion of this entry, all the trust relationships to trusted systems (systems that are trusted by the current system) are invalid and, if required, have to be deleted in the current system using transaction SMT1 and then have to be recreated.

In transaction SE37, execute the function module RFC_PING with the destination NONE. If the system displays an error message, execute the function module RFC_PING again; the error message cannot appear a second time in this case.

2) Solution 2:- (Automatic SECSTORE cleanup)

As of SAP Basis Release 620:

Execute the report RS_TT_CLEANUP_SECSTORE.

If you cannot implement this report using transaction SNOTE if the report not available in the system Note 1532825 (due to the RFC problem), copy the source code of the report for the relevant release from the attachment of the Note 1532825.

This report deletes invalid secstore entries /HMAC_INDEP/RFC_INTERNAL_TICKET_4_TRUSTED_SYSTEM and /HMAC_INDEP/RFC_EXTERNAL_TICKET_4_TRUSTED_SYSTEM.

After the deletion of the entry for  /HMAC_INDEP/RFC_EXTERNAL_TICKET_4_TRUSTED_SYSTEM, all the trust relationships to trusted systems (systems that are trusted by the current system) are invalid and, if required, have to be deleted in the current system using transaction SMT1 and then have to be recreated.

How to Import SAP Transport Request at OS Level

1. Make sure the transport request is released from the source system. Log onto the target systemas <SID>adm.

2. To add the transport request to the buffer (Single command line).

tp addtobuffer <TRANSPORT-REQUEST> <SID> Client=<CLIENT-NUMBER>

pf=/usr/sap/trans/bin/TP_DOMAIN_<DOMAIN_SID>.PFL

Example:

tp addtobuffer DEV12345 QAS Client=000

pf=/usr/sap/trans/bin/TP_DOMAIN_DEV.PFL

3. To import the transport request (Single command line).

tp pf=/usr/sap/trans/bin/TP_DOMAIN_<DOMAIN_SID>.PFL

import <TRANSPORT-REQUEST> <SID> U128 client=<CLIENT-NUMBER>

Example:

tp pf=/usr/sap/trans/bin/TP_DOMAIN_DEV.PFL

import DEV12345 QAS U128 client=000