CL_DMC_ACT_REC - List class of activity records
CPI1466 during Backup SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3upThis documentation is copyright by SAP AG.
Activity records are used to
- document the execution of MWB activities
- facilitate the return of status information of activities that have been started
One or more application logs can be linked to an activity execution.
Objects that want to create an activity record need to provide a unique identifier for the activity.This identifier (called session ID or external ID) is stored as part of the activity record and allows for retrieving the status information of the respective activity.
In case of parallel-running batch jobs that execute the same activity but with different conversionobjects, a specific activity record exists for each of these batch jobs. These activity records sharethe same external ID but are distinguished by their specific job names, job counts and work processIDs. So for each of these jobs, it can be seen when it was started, ended, which status was assignedto it (error, success, aborted, still running, etc.). As each of these records have the same external identifier, it is easy to retrieve the overall status of the activity.
Activity records can also be used to cancel running batch jobs. They contain a field ABORT_BATCH_JOBwhich can be set and then checked by the respective report. Thus the report gets the information that the job should be canceled, and can stop processing at a point where no inconsistencies can occur.
Two database tables are used:
- DMC_ACT_REC for the activity records
- DMC_ACT_REC_LOG to link the application log numbers to the activity records
TXBHW - Original Tax Base Amount in Local Currency PERFORM Short Reference
This documentation is copyright by SAP AG.
Length: 1728 Date: 20120526 Time: 135423 triton ( 119 ms )
