This chapter provides an overview of Model Generator and Ledger Mapper Generator, lists prerequisites, and discusses how to:
Load source data.
Set up Model Generator.
Set up Ledger Mapper Generator.
Assign generation IDs to your Activity-Based Management (Activity-Based Management) model.
Run Model Generator and Ledger Mapper Generator.
Review model objects and ledger mapping rules.
In addition to defining Activity-Based Management models and setting up resources, activities, cost objects, drivers, and pointers for sustainable models, Activity-Based Management also features two engines that let you create reusable, sustainable models. The following table lists the engines that automate model creation to streamline the model building process:
Engine |
Usage |
Model Generator |
Automates the process of setting up your Activity-Based Management model by generating resources, activities, cost objects, and drivers. |
Ledger Mapper Generator |
Creates your ledger-to-resource mappings. |
Once you run these engines and create resources, activities, cost objects, drivers, and ledger-to-resource mappings for your model, you can process your Activity-Based Management model.
You can run Model Generator, Ledger Mapper Generator, or both engines. If you run both, run Model Generator before Ledger Mapper Generator. If you are only running Ledger Mapper Generator, first complete resource setup for the model.
See Also
Running Model Generator and Ledger Mapper Generator
Before you can run Model Generator or Ledger Mapper Generator, you must:
Create your business model in Enterprise Warehouse.
Set up the scenario for the model in Enterprise Warehouse.
Set up the performance (PF) unit scenario definition in Enterprise Warehouse.
Identify whether you are using trees for ledger mapping on the Ledger Mapping Tree Usage page.
Set up ledger mapping defaults for all general ledger business units from which you want to map expense data to the Activity-Based Management resources.
Set up the Ledger Mapping Rule for the setID of your PF business unit.
Load the source data into a data warehouse table.
Set up data warehouse metadata for the source data.
For Model Generator, you can use a spreadsheet containing your source and target information to load your source data into the system. To load this spreadsheet into the system, you can use your ETL tool.
For Ledger Mapper Generator, you can either use a spreadsheet to load the data into the system or use and adapt your existing general ledger data.
Review the following Ledger Mapper Generator and Model Generator sample spreadsheets:
This section discusses how to set up the model generation definition.
Activity-Based Management Model Generator automates the process of setting up the data warehouse metadata for filters and constraints as well as setting up Activity-Based Management objects, drivers, and the pointers for driver quantities.
Model Generator generates:
Activity-Based Management resources, activities, and cost objects.
Drivers, interunit drivers, and constraints and filters for driver quantities.
To accomplish this, Model Generator requires source data that can be loaded into the system from a spreadsheet.
To run Model Generator, set up a model generation ID to specify:
The location of the source data.
Source and target setup.
Driver quantities and rates.
Any interunit drivers.
Page Name |
Object Name |
Navigation |
Usage |
AB_MODELGEN_TBL1 |
Activity Based Management, Setup, Model Generator, Model Generation Definition |
Set up the model generation definition by defining the model generation ID and parameters. This page lets you build your model one step at a time by defining multiple generator sequences. |
Access the Model Generation Definition page.
Sequence |
Enter the sequence of each source and target type mapping that you add. Note. Sequence 1 specifies that this is the first step in driving monetary amounts from a source to a target. |
Constraint Code |
Enter a constraint code to identify the location of the source data. |
Source Field Seq(source field sequence) |
Select a source field sequence to specify the DataMap column sequence number that you want to use for the source. This is the location of the source information for your model. Specify whether this source is a resource, activity, or cost object. |
Source Desc Field Seq (source description field sequence) |
Select the location of the description for your source. |
Target Field Seq (target field sequence) and Target Desc Field Seq (target description field sequence) |
Select the location of your target information on the source data table. Specify whether this target is a resource, activity, or cost object. |
Actual Driver Quantity, Budgeted Driver Quantity, Capacity Driver Quantity, and Frozen Rate |
Select the location of the actual, budgeted, and capacity driver quantity information as well as the frozen rate. |
IBU Business Unit and IBU Model ID |
If this is an interunit model, select the location of the IBU business unit and IBU model ID. |
This section discusses how to set up the ledger mapping generation definition.
Activity-Based Management Ledger Mapper Generator lets you create ledger mapping rules automatically by using information loaded into Enterprise Warehouse from a spreadsheet or by adapting existing system data from a general ledger. Ledger Mapper Generator generates the mapping rules that determine how general ledger accounts are assigned to existing Activity-Based Management resources. This is an alternate method to manually setting up mapping rules using the Ledger Mapping Rule page.
You can use Ledger Mapper Generator to identify which columns—business unit, general ledger business unit, department, and so on—in the DataMap are for resources. Ledger Mapper Generator contains the same flexible mapping capabilities as manually entered maps. As with manually entered maps, you can define whether you are mapping a tree node or a percentage value. Ledger Mapper Generator also accommodates actual and budget maps.
In addition, Ledger Mapper Generator is scalable and sustainable. You can use it on an ongoing basis to update previously generated maps or for adding and deleting maps that you no longer use.
To run Ledger Mapper Generator, first set up a ledger mapping generation definition.
Page Name |
Object Name |
Navigation |
Usage |
AB_LDMPGEN_TBL1 |
Activity Based Management, Setup, Model Generator, Ledger Mapping Creation |
Set up the ledger mapping generation definition by defining the parameters for Ledger Mapper Generator. This page lets you generate mapping rules one step at a time by defining multiple generator sequences. |
Access the Ledger Mapping Creation page.
Sequence |
Enter the sequence of each mapping rule that you add. Note. Sequence 1 specifies that this is the first ledger mapping rule. |
Constraint Code |
Enter a constraint code to identify the location of the source data. This data can be a table generated from spreadsheet data or existing general ledger data in the system. |
Resource Field Seq (resource field sequence) |
Enter a resource field sequence to specify the DataMap column sequence number that you want to use for the resource. |
Ledger Map Desc Field Sequence (ledger map description field sequence) |
Enter the ledger map DataMap column sequence number for the ledger map description. |
Mapper Type |
Select a mapper type. Values are: Actuals or Budgeted. |
Business Unit Field Seq (business unit field sequence), Percentage Allocation Seq, and Map Chartfield 1 through 8 |
Enter the DataMap column sequence number to use. |
Once you set up your model generation and ledger map generation IDs, you must assign them to the model. To assign the generation ID, you must first select the model ID that you want to use, and then select the Run Control Information tab. Define the appropriate model generation ID, ledger maps generation ID, or both, and then save the page.
See Defining an Activity-Based Management Model.
Note. You do not have to run both engines. You can run Model Generator, Ledger Mapper Generator, or both.
See Also
Setting Up Activity-Based Management Models
This section provides an overview of delivered engines and discusses how to:
Specify run control parameters.
Inquire about engine messages.
As with all Activity-Based Management engines, you can run these engines in a job stream from Enterprise Warehouse.
Page Name |
Object Name |
Navigation |
Usage |
Run Jobstream |
RUN_PF_JOBSTREAM |
Activity Based Management, Setup, Processing, Run Jobstream. |
Use to run model generator and ledge mapper generator. |
Message Header |
PF_ENGMSG_HEAD |
Activity Based Management, Setup, Processing, Error Messages, Message Header |
Use to view error messages. |
Message Detail |
PF_ENGMSG_LOG |
Activity Based Management, Setup, Processing, Error Messages, Message Detail |
Use to view error messages. |
The following table lists the delivered engines for building models:
Engine Name |
Job ID |
Usage |
Activity-Based Management Model Generator (AB_MODEL_GEN) |
AB_MDLGEN |
Generates the objects and drivers for a model. |
Activity-Based Management Ledger Mapper Generator (AB_LDMPGEN) |
AB_LDMPGEN |
Generates the ledger-to-resource mappings. |
Access the Run Jobstream page.
You can review messages generated by these jobs by opening the Application Engine message log.
See Enterprise PeopleTools PeopleBook: PeopleSoft Process Scheduler
Once you run Model Generator and Ledger Mapper Generator, you can use the following pages to review the objects and mapping rules that you created as well as make any appropriate adjustments:
Page Name |
Navigation |
Resources |
Activity Based Management, Setup, Resources, Resources |
Activities |
Activity Based Management, Setup, Activities, Activities |
Cost Objects |
Activity Based Management, Setup, Cost Objects, Cost Objects |
Implicit Pointers |
Activity Based Management, Setup, Pointers to Drivers, Implicit Pointers |
Drivers |
Activity Based Management, Setup, Drivers, Driver |
Inter Unit Drivers |
Activity Based Management, Setup, Drivers, IBU Driver |
Ledger Mapper Rule |
Activity Based Management, Setup, Resources, Ledger Map Rule |
You can also use the Model Navigator component to review your generated model.
See Also