Skip to Main Content
Return to Navigation

Using the Activity-Based Management Drillback Engine

In addition to using OLAP cubes to get a three-dimensional view of you Activity-Based Management data, you can use the Activity-Based Management Drillback engine to get a multidimensional view for reporting purposes.

To use the Activity-Based Management Drillback engine, you must:

Note: If you are using the Activity-Based Management Drillback engine you also must select the Get Drill Level 2 Information check box on the Models - Run Control Information page before running the Activity-Based Management engine.

See Run Control Information Page.

Page Used to Specify Drillback Levels

Page Name

Definition Name

Navigation

Usage

Drillback Levels

AB_SEC_LEVEL_TBL1

select Activity Based Management, then select Analysis, then select Drillback Levels

Name the drillback levels that will display in reports generated after you run the Activity-Based Management Drillback engine.

Drillback Levels Page

Use the Drillback Levels page (AB_SEC_LEVEL_TBL1) to name the drillback levels that will display in reports generated after you run the Activity-Based Management Drillback engine.

To name the drillback levels for multidimensional reporting, enter a Drillback Level Name and Description. The description will appear in any reports you generate after running the Activity-Based Management Drillback engine.

Running the Activity-Based Management Drillback Engine

As with all Activity-Based Management engines, you can run the Activity-Based Management Drillback engine in a jobstream. You can also run it separately from the Activity-Based Management Drillback page by selecting select Activity Based Management, then select Analysis, then select Drillback.

The Activity-Based Management Drillback engine first populates temporary tables. After running this engine, you need to run the Merge engine to transfer the data from the temporary tables to the final table, the Drillback table (AB_DRILL_F00) used to drill back data. You can do this by creating a jobstream for both engines, or you can run the engines separately.

You can review messages generated when you run these jobs, by accessing the Application Engine message log for the specific process instance and engine ID. This component is described in detail in the PeopleSoft Enterprise Performance Management Fundamentals 9.1 documentation.