Understanding Batch Processing
Once you complete the necessary setup, you can process your model using engines that validate metadata (or model setup) or that process data for single or multiple dimensions (or ensure that the model is configured correctly within the system).
This section provides overviews of:
Jobstreams and engines.
Activity-Based Management tables.
Batch processing process flow.
Jobstreams and Engines
Jobstreams let multiple users run their own jobs using instances of the same engines at the same time. By sharing temporary tables passed between jobs, jobstreams also speed up processing.
This section discusses:
Jobstreams.
Delivered engines.
Jobstreams
Instead of locking up the primary input (fact) tables in the operation warehouse - enriched (OWE), jobstreams use temporary tables for intermediate processing. A set of delivered temporary tables, which are called record suites, use only the relevant data from the main OWE fact tables to run the engines and process the data. This lets the engines in the jobstream run faster while keeping the fact tables open and accessible to other users so they can run the same engines simultaneously. The system assigns the record suites when the first engine runs and releases them when the last engine finishes.
Note: PeopleSoft Enterprise Performance Management (EPM) has predefined engines, engine metadata, jobs, job metadata, jobstreams, and record suites. You can also set up your own jobstreams. To do so, associate each engine with a job ID using the Job Metadata page, and then associate jobs with a jobstream using the Jobstream Setup page. A job must be unique across all jobstreams.
Delivered Engines
PeopleSoft EPM applications use engines to run processes. PeopleSoft delivers engine metadata with the system. This metadata stores information about the various PeopleSoft Application Engine programs used within an engine. The following table lists the delivered PeopleSoft engines and the associated job IDs that you use when processing Activity-Based Management:
Engine Name |
Job ID |
Description |
Usage |
---|---|---|---|
RUN_PF_JOBSTREAM |
RUN_PF_JOBSTREAM |
Activity-Based Management Model and Activity-Based Management Ledger Mapper |
Generates the objects and drivers for a model and the ledger-to-resource mapping for a model. |
PF_EMP_SURV |
EMP |
Employee Profile |
Generates resources and drivers based on the employee profile information. |
AB_RTG |
RTG |
Routing Information engine |
Creates relationships (drivers) for activities and cost objects for manufacturing purposes. |
PF_Activity-Based Management_CUBE |
AB_CUBE |
Activity-Based Management Cube engine |
Creates online analytical processing cubes. |
AB_DRILLBACK |
AB_DRILL |
Activity-Based Management Drillback engine |
Processes data for multidimensional reporting using a third-party reporting tool. |
PF_ABPS |
ABPS |
ABPS engine |
Processes ABPS models. |
PF_OBJ_TBL |
OBJ_TBL |
Populate Activity-Based Management Object Table |
Combines the separate object tables into a single table for modeling and reporting. Run this engine any time that you make changes to any objects. |
AB_VALIDATE |
ABMD |
Activity-Based Management Model Validation |
Validates resources, activities, cost objects, business rules, and tree structures for the model. You can run it any time after creating the model. |
PF_ABC |
Activity-Based Management |
Activity-Based Management engine |
Calculates single dimensional costs for resources, activities, and cost objects. |
PF_MERGE |
MERGE |
Merge engine |
Moves engine output from the temporary processing tables to the appropriate final table. This engine is part of EPM Foundation and should be run after all other engines. |
ABM_RT_MAP |
ABM_RT_MAP |
Activity-Based Management mapping |
Assign costs and amounts to resources based on the resource-to-ledger mapping rules and saves the output in ABM_LEDMAP_F00. This engine is used when preparing the ledger to resource mapping/amounts from the Real-Time ABM model. |
Note: This list does not include any Data Manager activities discussed in the Enterprise Warehouse Tools and Administration documentation.
This document discusses the following engines:
Model Generator
Ledger Mapper Generator
Employee Profile
Routing Information
Activity-Based Management Cube
Activity-Based Management Drillback
Employee Profile
ABPS
You can only run the Activity-Based Management Objects engine in a jobstream. It does not have a separate run control page.
Activity-Based Management Tables
Activity-Based Management has input tables that enable you to enter information into the system for processing and output tables that store processing results.
Image: Key Activity-Based Management tables
The following flow chart illustrates key tables that the system uses during Activity-Based Management, Data Manager, and Profit Manager processing.
You can select any of the following input tables for ledger mapping information; however, you may choose to use the first two tables more frequently:
Amounts (LEDGER_F00)
Optional Budget Amounts (LEDGER_BUDG)
Resources (RES_TBL)
Activities (ACT_TBL)
Cost Objects (CST_TBL)
Driver (DRIVER_TBL, DRIVER_SRC_SEQ, and DRIVER_TAR_SEQ)
The output tables contain calculation tables. Metadata defines the types of data that the calculation tables store, which affects the calculation tables' output and how Data Manager uses the output for processing. The calculation tables store the output of the Activity-Based Management engine until it is used by other system processes. The system performs calculations in stages, and then stores these calculations in temporary tables; however, the system copies all of the results to the final tables.
The following table lists Activity-Based Management calculation tables:
Table Name |
Object ID |
Contents |
---|---|---|
Calculation Objects |
CALC_OBJ_F00 |
Contains calculated cost values for resource, activity, and cost object amount information as processed by the Activity-Based Management engine. Use this table to query amount results for an object. |
Calculation Detail |
CALC_DETAIL_F00 |
Contains drillback or direct assignment information. The Drill Level field within the table denotes the type of calculation assignment. Use this table to drill back to the previous object (direct calculation) and obtain information for drilling back to all objects that contribute indirectly to the object (drillback calculation). |
Calculation Bucket |
CALC_BUCKET_F00 |
Contains temporary calculation results for resources, activities, and cost objects; therefore, it contains the most amount of detail. The system stores all finalized values in the Calculation Detail table (to be used for other processes). |
Calculation Rate |
CALC_RATE_F00 |
Contains driver rates. |
Calculation Object Rate |
CALC_OBJ_RATE_F00 |
Contains object rates such as object costs or object-calculated amounts. |
Calculation Object Quantity |
CALC_OBJ_QTY_F00 |
Contains object volume and quantity. |
Calculation Fragmentation |
CALC_FRAG_F00 |
Contains activity fragmentation data for employee resources. |
Calculation Inter-Business Unit |
CALC_IBU_F00 |
Contains cost data from inter-unit drivers. |
Calculation Transaction |
CALC_TRN_F00 |
Contains transaction rates. |
Inter-Unit Rate |
BU_RATE_F00 |
Contains inter-business unit driver rates. |