Control-M for SAP can automate the following Business Warehouse process jobs:
After you create a Process Chain in SAP, you can create a Control-M job that is used to run it. Running this Control-M job starts the Process Chain in SAP and enables you to monitor it.
The monitoring procedure in Control-M does not monitor a specific CCMS job in SAP-BW, since a Process Chain in SAP-BW includes several CCMS jobs. Instead, it uses BAPIs to start and monitor the Process Chain as a logical unit, not limited to a specific process or CCMS job. This means that the entire Process Chain, the details of which can be displayed in SAP GUI as many processes, are represented in Control-M as one job.
The Output of the Control-M job includes information about the updated status of each process in the chain and the number of records transferred and requested. You can define post-processing rules in Control-M based on this information.
The output file for Process Chain prints a summary before each section that describes a step. This summary can then be used in On Statement processing. Format: <step_type>_<status>_<variant>.
TRIGGER_FINISHED_START
After creating an InfoPackage in SAP, you can create a Control-M job to run it. Running this Control-M job starts the Info Package in SAP and enables you to monitor it.
The monitoring procedure in Control-M does not monitor a specific CCMS job, since an Info Package run in SAP-BW usually includes several CCMS jobs and other operations. Instead, it uses SAP BAPIs to start and monitor the Info Package as a logical unit that is not limited to one specific CCMS job. The SAP XT process should be started in order to perform the monitoring.
The Output of the Control-M job includes information similar to that displayed on the SAP-BW status panel of the monitoring screen of an Info Package specific run (transaction RSA1), including error messages. You can define post-processing rules in Control-M based on this information.
Parent Topic |