In SAP, many transactions are called internally by another transaction. For example, when a user execute transaction OB52 to open or close an accounting period, OB52 internally calls transaction SM30 to update the corresponding tables. This ensures that the end user does not explicitly require access to SM30.
Lots of people ask me if there are ways to check such internal transaction calls in SAP. The answer - through the tables TSTCP or TCDCOUPLES. Table TCDCOUPLES is more user friendly and I will recommend use of this table if you are trying to identify internal transaction calls in SAP.
Lots of people ask me if there are ways to check such internal transaction calls in SAP. The answer - through the tables TSTCP or TCDCOUPLES. Table TCDCOUPLES is more user friendly and I will recommend use of this table if you are trying to identify internal transaction calls in SAP.
The question is how do we manage SOD issues for incompatibilities existing with calling or called transactions and other transactions. How do we know if a user performed an SOD violation?
ReplyDelete