Ansicht
Dokumentation

VC_TCCAVRG - Define Automated Transactions

PERFORM Short Reference   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

In this activity you can determine that specific transactions for setting a system status are executed automatically.

For the change header, this setting is defined per change type. You can set automatic execution for the following transactions:

• Check

• Checked

• Approve

• Convert

• Complete

• Release

For the objects, this setting is defined per object type. You can set automatic execution for the following transactions:

• Change Possible

• Complete Change

• Release Change

The system first reads the Customizing entry with the most specific data:

• If you enter an entry without an object type at object level, this entry applies to all object types.

• If an entry for the same change type exists with reference to a specific object type, the system reads the settings for this object type. Exactly the transactions that were selected specifically for this object type are executed automatically.

The check logic in the automated check process is identical to the logic in the manual process. The transactions are checked in the following sequence:

• Change header: Check

• Object: Change Possible

• Change header: Checked

• Change header: Approve

• Change header: Convert

• Object: Complete Change

• Change header: Complete

• Object: Release Change

• Change header: Release

The system executes the automated transactions in this sequence until it finds a transaction that cannot be executed. This is the case in the following processing situations:

• The transaction is not defined as an automated transaction.

• The transaction cannot be executed due to the program logic.
  In this case you see an error message, as in the manual process.

rdisp/max_wprun_time - Maximum work process run time   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 3109 Date: 20240523 Time: 165021     sap01-206 ( 36 ms )