Understanding Data Manager and Allocation Manager
This topic discusses:
Data Manager.
Allocation Manager.
Mathematical model for Data Manager and Allocation Manager rules.
Data Manager
The Data Manager is a flexible tool that enables you to:
Move data into the performance journal table (PF_JRNL_F00).
Organize the output from any PeopleSoft EPM engine to create rows of data with multiple dimensions.
Create reporting categories (dimensions) that represent groups of information for reports, such as business units, customers, products, channels, accounts (revenue, expense, and so on), and departments.
Note these key features of Data Manager:
You can use Data Manager to consolidate or aggregate data and eliminate redundant rows.
You can run Data Manager using different rules to organize and create multiple dimensions for direct costs and revenue data.
Data Manager supports the following methods for moving data:
|
Method |
Description |
|---|---|
|
Copy |
Moves data from the source to the target. This method typically uses multiple-dimension data as the source. |
|
Arithmetic |
Applies an arithmetic operation using the amounts in both sources. |
|
GL Mapper |
Takes data from the general ledger tables and maps it to performance data. This method populates the temporary GLSTG table . From here, you can use the copy method to move data directly to the performance journal. |
|
Prorata |
Adds an additional dimension to your data and divides the amount across the dimension based on the percentage of the total amount. |
|
Spread Even |
Adds an additional dimension to your data and spreads the fact amount evenly across the dimension. |
|
Tree Aggregation |
Aggregates measures based on a tree hierarchy. The node names act as dimensions. |
Data Manager and the Profit Manager
Data Manager works with the Profit Manager tools by moving data to the performance journal table (PF_JRNL_F00). The Profit Manager tools verify this data (PF_EDIT engine) and post the data to the performance ledger (PF_POST engine). They also unpost data, if necessary (PF_UNPOST engine) and can clean up the performance journal table ( PF Journal Cleanup engine). The Profit Manager includes tools for balancing and reconciling your data.
The performance ledger, PF_LEDGER_F00, is a useful table for reporting because it contains all of the performance fact data. The facts have been allocated across several dimensions of your choice (typically channel, product, customer, and department). Having all of this information organized in a single table makes it easier for you to query and create reports.
The Profit Manager tool is described in the Understanding Profit Manager Tools topic.
Data Manager Setup
To set up the Data Manager, you need to:
Define the necessary metadata (including tablemaps, datamaps, constraints, and filters).
The system uses datamaps and constraints to point to the appropriate tables.
Define Data Manager rules, including the method by which you want to move, aggregate, or create multidimensional data, as well as the sources and target of the process.
Create a Data Manager rule set that contains one or more rules.
Set up job metadata and jobstreams.
Associate the Data Manager rule set with a job.
Run the Data Manager engine.
Allocation Manager
Allocation Manager is an EPM tool that enables you to distribute revenue, expense, and statistical amounts across business units, departments, and other dimensions. For example, you can allocate budget planning to detail levels to perform detailed budgeting.
The Allocation Manager tool can also be used to create offset and residual rows, capture source, basis, and target data, and create, process, and post journals to a ledger.
Allocation Manager consists of several PIA components and an application engine. You create the rules and rule sets that define your processing with PIA pages, while the application engine is executed using a jobstream and a run control PIA page.
Each allocation output is determined by the type of allocation method that you select. The following table lists the types of allocations that are supported by the Allocation Manager and describes each allocation type:
|
Allocation Type |
Description |
|---|---|
|
Arithmetic Operation |
Defines a mathematical calculation using the source and basis, such as source + basis. |
|
Prorata |
Divides the source amount proportionately among the targets based on basis measures. |
|
Spread Even |
Distributes the source amounts equally by the specified basis fields. For instance, if expenses were spread evenly across four business units, each would have 25 percent of the expense. |
|
Copy |
Copies the source amounts to the targets. |
Allocation Manager can use any source dimension within the OWE and provide output to any target. As a result, you can use sources from Global Consolidations and ABM results to further manipulate the output for analysis based on business rules specific to your organization.
Allocation Manager Dimensions
Due to platform limitation issues on DB2 UDB for OS / 390 and z/OS (the index size is limited to 255 characters) and Oracle (which requires 30 columns in an index) the predelivered index is on the first 10 dimensions. However, based on your requirements and the database platform, you can increase the maximum number of dimensions in the Allocation Manager to 28. The records that need to be modified for index changes include PF_AL_CALC_T, PF_AL_DIFF_T, PF_AL_DIV_T, PF_AL_SRC01_T, PF_AL_BAS02_T, and PF_AL_TOTAL_T.
To increase the number of dimensions:
Open each of the above records in the Application Designer.
Open the relevant subrecord.
The delivered unique index is shown on the fields PF_AL_DIM1 to PF_AL_DIM10.
Depending on the number of dimensions you are adding, modify the index by adding the extra dimensions as keys.
For example, if you want to use 15 dimensions then modify the index to include PF_AL_DIM11 through PF_AL_DIM15 and build the record. Alternatively, you can add a custom index on the table, using the Add Index feature.
Note: You can also apply these steps to Data Manager.
Mathematical Model for Data Manager and Allocation Manager Rules
The rules for Allocation Manager and Data Manager represent mathematical operations to be performed on the data you specify. Although Allocation Manger and Data Manager use different terminology, they perform similar calculations. For Allocation Manager, you must specify a source, basis, and target for the operation. For Data Manager you must specify two sources (source 1 and source 2) and the target.
The following table lists the Data Manager and Allocation Manager terms and how they relate.
|
Allocation Manager |
Data Manager |
|---|---|
|
Source |
Source 1 |
|
Basis |
Source 2 |
|
Target |
Target |
The sources of a rule use constraints to tell the Data Manager what is to be assigned and what basis to use. Use constraints to apply business rules to limit row selection. The target of a rule uses a datamap to tell the Data Manager where the rule should be located. The method that is applied to the rule determines the calculation that is performed.
Note: The explanation of the mathematical operations uses only Allocation Manger terms. Use the previous table to apply the Data Manager terms.
Understanding the Calculations Behind the Prorata and Spread Even Methods
The prorata and spread even methods perform the same calculation with the following exception: the prorata method uses measures from the basis table in the calculation, whereas the spread even method uses row counts from the basis to determine the ratio that is defined by basis measure รท basis total.
The prorata method performs the following calculation:
Source Measure * Basis Measure / Basis Total
Source Measure = Sum(Measures in source grouped by common dimensions and source mapped dimensions)
Basis Measure = Sum(Measures in basis grouped by common dimensions and basis mapped dimensions)
Basis Total = Sum(Measures in basis grouped by common dimensions only)
The spread even method performs the following calculation:
Source Measure * Basis Measure / Basis Total
Source Measure = Sum(Measures in source grouped by common dimensions and source mapped dimensions)
Basis Measure = Sum(Count of basis rows grouped by common dimensions and basis mapped dimensions)
Basis Total = Sum(Count of basis rows grouped by common dimensions only)
The following tables provide an example of the prorata method with one common dimension (unique dimension combinations).
Source:
|
Source Product |
Source Amount |
|---|---|
|
A |
10 |
|
B |
20 |
Basis:
|
Basis Product |
Basis Channel |
Basis Measure |
|---|---|---|
|
A |
X |
10 |
|
A |
Y |
20 |
|
B |
V |
10 |
|
B |
W |
40 |
Target:
|
Target Product |
Target Channel |
Target Amount |
|---|---|---|
|
A |
X |
3.33 (10 * 10/30) |
|
A |
Y |
6.66 (10 * 20/30) |
|
B |
V |
4 (10 * 10/50) |
|
B |
W |
16 (20 * 40/50) |
This table illustrates an example of the spread even method with one common dimension (unique dimension combinations).
Source
|
Source Product |
Source Amount |
|---|---|
|
A |
10 |
|
B |
20 |
Basis:
|
Basis Product |
Basis Channel |
|---|---|
|
A |
X |
|
A |
Y |
|
B |
V |
|
B |
W |
Target:
|
Target Product |
Target Channel |
Target Amount |
|---|---|---|
|
A |
X |
5 (10 * 1/2) |
|
A |
Y |
5 (10* 1/2) |
|
B |
V |
10 (20 * 1/2) |
|
B |
W |
10 (20 * 1/2) |
Understanding the Calculations Behind the Arithmetic Method
The arithmetic method performs the following calculation:
Source Measure [Operator] Basis Measure
Source Measure = Sum(Measures in source grouped by common dimensions and source mapped dimensions)
Basis Measure = Sum(Measures in basis grouped by common dimensions and basis mapped Dimensions)
Operator = [Addition (+), Subtraction (-), Multiplication (*), Division (/)]
Allocation Using Fixed Percentages
In Allocation Manager, you can divide a quantity by predetermined percentages and allocate those amounts by using the prorata method in combination with the fixed basis option.
In the calculation that is performed by the prorata method, the basis determines the ratio by which the source is divided. A ratio is another way to specify a percentage. By controlling the ratio, you can allocate the source amounts by specified percentages, or a fixed percentage.
Source Measure * (Basis Measure / Basis Total)
or
Source Measure * (%Percentage)
Warning! The prorata method always allocates 100 percent of the source. You must use the correct percentages when defining the fixed basis.
Setting Up Allocations
To set up allocations:
Complete your metadata setup, including datamap setups for the source, basis, and target definitions.
This step is required.
Note: PeopleSoft provides the Datamap Wizard to greatly simplify the creation of datamaps.
The Datamap Wizard can be found using either of these navigation paths:
EPM Foundation, Foundation Metadata, Metadata Wizards, Datamap Wizard
EPM Foundation, Data Enrichment Tools, Allocation Manager, Datamap Wizard
See Datamap Wizard Page.
Define value objects.
This step is optional.
Create indices on Allocation Manager temporary tables.
This step is optional.
Define fixed dimensions.
This step is optional if you do not use a fixed source or basis in your allocations.
Define allocation rules, including the method, source, basis, and target definitions.
This step is required.
Create an Allocation Manager rule set that contains one or more allocation rules.
This step is required.
Associate Allocation Manager rule set with a job.
This step is required.
Process allocations using Run Allocations engine.
This step is required.