CL_BCM_CONTROLLER - Business shift quota of the controller

CPI1466 during Backup   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Functionality

The class CL_BCM_CONTROLLER (short: BCM-Controller) is the central control unit for the business shift (that means the application logic) of the Configuration Management application. In particular:

• Flags for the ABAP/OO-Framework are set,

• Transactions are started by:

• MODIFY_FOLDER: a product folder is generated, its status is read from the database and the object reference is transferred to the caller. Changes to this folder can be saved.

• CREATE_FOLDER_SUCCESSOR: a successor folder is created for a product folder. This can be saved.

• CREATE_PRODUCT: a new product and an initial product folder are created and can be saved.

• Transactions are completed by:

• SAVE: all open transactions (see below) are completed, the changes that were logged during the transaction are updated. A system flag determines whether the update is carried out synchronously or asynchronously.

• SAVE_SINGLE: the last transaction opened (and not closed) is closed and the changes updated.

• UNDO: all open transactions are completed but the changes are not updated.

• UNDO_SINGLE: the last transaction opened is closed but the changes are not updated.

• The return of Configuration Management data is started (by GET_FOLDER_AND_PRODUCT),

• Tables are locked and unlocked.

Relationships

The BCM controller has relationships to system services such as:

• Persistence manager (if_os_persistency_manager),

• Transaction manager (if_os_transaction_manager),

as well as to an individual object of his own class and to an individual object of the class CL_BCM_WORKLIST. There are no inheritance relationships

Example

Notes

For methods that open a transaction, there have to follow methods that can close it again. The closureof a transaction does not have to be carried out immediately after it is opened. The methods SAVE andUNDO close all open transactions. With the methods SAVE_SINGLE and UNDO_SINGLE individual transactions are closed. Therefore a *_SINGLE method operates on the last opened but not reclosed transaction.

The class is transient and implemented to the Singleton-Pattern accordingly that means that at most, one object of the class exists. The only way to obtain an object reference is to call up the method GET_CLASS_AGENT.

Further information

To persistence and transaction service:

CPI1466 during Backup   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.


Length: 2970 Date: 20120526 Time: 090231     triton ( 124 ms )