Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Executing custom SAP transactions

You can use the following custom SAP transactions to automate time-consuming SAP activitites. These custom transactions are typically required prior to executing the post-deployment actions available from the BMC Cloud Lifecycle Management console:

Custom SAP transaction

Automated SAP activity

Maintain the logical system pairs.

This custom transaction automates the execution of the SAP transaction BDLS, which is used to convert logical system names following SAP system refresh, system copy and system rename.

Control the scope of the post-system refresh.

Once the database is recovered and opened, several SAP transactions and programs have to be executed in the SAP system to adjust the database and SAP configuration to the new host and <SAPSID>. For a specific system refresh, you may not want to execute all the post refresh transactions. The the SAP transaction ZBMCVARIANT enables you to control the scope of the post-refresh SAP transactions and programs that are executed.

Reprocess the SAP transactions or programs that do not complete or do not produce the desired result.

The post-refresh SAP transactions and programs are executed by BMC Cloud Lifecycle Management at the end of the service offering’s execution. This execution of the SAP transactions and programs cannot be interrupted even if one of them is in error. If an SAP transactions or program does not complete or does not produce the desired result, execute the custom developer SAP transaction ZBMCPOSTPROCESSING to reprocess the transaction.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*