This chapter provides an overview of Compensation Strategy and discusses how to:
Set up a workforce simulation rule
Set up a compensation planning scenario
Review and analyze a compensation planning scenario
Alter compensation planning scenario results with Analytic Calculation Engine
Approve compensation planning scenario output

 Understanding Compensation Strategy
Understanding Compensation Strategy
This section provides an overview of the Workforce Rewards Compensation Strategy and discusses:
Compensation strategy definition
Compensation Strategy business process
Market compensation rates

 Overview
Overview
The Compensation Strategy module provides tools to review and analyze the total compensation costs and strategies for your workforce. With Compensation Strategy you can automate and streamline the performance of these compensation strategy tasks:
Use data extracted from multiple sources.
Define compensation rules for any type of compensation, such as base pay, variable compensation, or benefits compensation.
Create scenarios of your organization's job growth and reduction, or headcount plans.
Create and analyze multiple compensation scenarios involving combinations of compensation types, such as base pay, variable compensation, and benefits compensation.
Evaluate the impacts of these scenarios on compensation distribution, costs, and value.
Once you've identified the scenarios with the desired results, approve the results of your efforts.
You also utilize a wealth of data in the process. Compensation Strategy integrates data from a variety of sources, such as:
Workforce compensation data from internal transactional database systems, such as HRMS.
Market rates developed with the Market Compensation module.
Base pay structures developed with the Base Pay Structure module.
Employee retention and reduction data from the Retention Strategy module.
Key performance indicators (KPIs) from Scorecard and Workforce Scorecard.
You use the Compensation Strategy module to generate differing scenarios of base and variable compensation plans, as well as any other cost-related plans (such as benefits). We designed the module around two main Application Engine processes, Workforce Simulation (WA_WFS) and Compensation Planning & Simulation (WA_CPS).

Conceptual relationship between Workforce Simulation and Compensation Planning and Simulation

 Compensation Strategy Definition
Compensation Strategy DefinitionBefore you begin using the Compensation Strategy module, take some time to formulate the questions that you want to answer. The types of questions to consider fall into two broad categories:
What is your organization's overall compensation strategy? What changes in the existing compensation system would you like to model, to assess their effects?
How can you best use Compensation Strategy to generate scenarios to evaluate and answer these questions?
One part of understanding your organization's compensation strategy involves knowing what pay components, target pay rates, and pay ranges to apply to various jobs. It also involves understanding your organization's ongoing efforts to attract and retain the right people with the necessary skill levels. Once you have this background you are ready to use Compensation Strategy to perform tasks such as:
Model the changes from a proposed salary or compensation reorganization, based on market values, to evaluate the cost of moving your workforce up to market levels.
Create new types of variable compensation to help motivate your workforce, and evaluate the cost impact.
Target special compensation plans for specific groups of employees, such as executives, salespeople, or workers with mission-critical job skills.
A second part of understanding your organization's compensation strategy involves knowing how the overall compensation strategy cycle is executed, and knowing at what point in the cycle your organization is at a any given time. Equipped with this knowledge, you can use Compensation Strategy to perform these types of tasks:
Model compensation cost changes based on forecasted workforce growth and reduction.
Establish a merit matrix or other rules for pay out of annual base pay increases.
Determine what types of performance goals or related pay out rules you need for any base compensation or variable compensation types in the compensation plan.
Examine the compensation cost effects based on organizational performance indicators, for periodic bonuses and so on.
Set proposed compensation budgets for departments or business units.
Allocate compensation pools across organizations, special classifications, groups, and individuals.
Another part of your strategy involves understanding how to best use Compensation Strategy. You have these options:
Set up and run Compensation Planning and Simulation (CPS) as a Historical process, using your existing workforce. This means having no inputs from Workforce Simulation.
Set up and run CPS as a Forecast process, using input from Workforce Simulation, or Retention Strategy, or both, to include simulated changes to your workforce in the scenarios. Follow the retention or workforce simulation results through the completion of the CPS process, and evaluate the cost impacts of your retention, growth, and reduction decisions.
Set up and run CPS with or without including existing base salary in the compensation rules. This means you can either evaluate the total compensation impact of a scenario, or focus only on the change introduced by new rules.

 Compensation Strategy Business Process
Compensation Strategy Business ProcessThe following diagram outlines the main steps in the Compensation Strategy business process.

Compensation Strategy business process

 Market Compensation Rates
Market Compensation RatesIf you plan to use market rates to help you develop and evaluate compensation scenarios for your workforce, make sure you have completed the steps needed to import compensation survey data, and define market compensation rates.
If you plan to use new base pay structures to help you develop and evaluate compensation scenarios for your workforce, make sure you have completed the steps needed to develop new base pay structures.
See Also

 Setting Up Workforce Simulation
Setting Up Workforce SimulationTo set up workforce simulation, use the WA_CP_WFSIM_DFN.GBL and WA_WFS_MODL_TBL.GBL components.
This section provides an overview of workforce simulation and discusses how to:
Set up workforce groups.
Enter workforce simulation growth and reduction rules.
Set up model IDs for workforce simulation.
Define a workforce simulation model.
Set up a workforce simulation scenario definition.
Set up the process run control for the Workforce Simulation process.
Run the Workforce Simulation process.
Review your workforce simulation scenario setup.

 Understanding Workforce Simulation Setup
Understanding Workforce Simulation Setup
The Workforce Simulation process serves as a basis for input to the Compensation Planning and Simulation process. The inputs for the Workforce Simulation process are workforce growth and reduction rules, which define your workforce strategy. Run the Workforce Simulation process to generate a simulated workforce, consisting of your existing employees plus any new simulated employees and reduced employees (employees to be removed from your workforce). In the end, the result is a simulated workforce based on assumptions for growth and reductions for a given time period. The output is stored in the WA_JOB_S00 table. WA_JOB_S00 is identical to the JOB_F00 table, with SCENARIO_ID added as a key field. Use this simulated workforce in forecast scenarios in Compensation Strategy.
Before you begin working with Workforce Simulation, think about the questions that you want to answer. The questions you ask dictate your strategy for the workforce simulation and compensation rules you create. They also dictate your strategy for which modules and processes to run, and in what sequence to run them. For example, do you want to run the Retention Strategy module first, to generate lists of employees to reduce and retain, and use them in the Workforce Simulation? If you do, then you can follow the retention results right on through to the completion of the Compensation Planning and Simulation process, and evaluate the cost impacts of your retention decisions.
To set up your workforce simulation strategy complete the following steps:
Set up workforce groups.
Enter growth and reduction rules.
Set up a Model ID.
Use the rules to define a workforce simulation model.
Set up a scenario ID.
Run the Workforce Simulation process.
Review the workforce simulation scenario

 Pages Used to Set Up and Run Workforce Simulation
Pages Used to Set Up and Run Workforce Simulation
| Page Name | Object Name | Navigation | Usage | 
| Workforce Simulation Rule | WA_CP_WFSIM_DFN | Workforce Analytics, Compensation Strategy, Setup WF Simulation Rules | Enter growth and reduction assumptions for your workforce, which you can use to run a workforce simulation scenario. | 
| Workforce Simulation Model | WA_WFS_MODL_TBL | Workforce Analytics, Compensation Strategy, Setup WF Simulation Model | Define a workforce simulation model by associating a set of simulation rules with a model ID. | 
| Run Workforce Simulation | RUN_PF_JOBSTREAM | Workforce Analytics, Compensation Strategy, Run Workforce Simulation | Generate a workforce simulation scenario. | 
| Workforce Simulation Rules report | RUN_RWA_0019 | Workforce Analytics, Workforce Reports, Compensation Strategy Reports, Workforce Simulation Rules | Run the Workforce Simulation Rules Crystal report (WAC0019), summarizing the simulation rules for a given setID and model ID. | 

 Setting Up Workforce Groups for Workforce Simulation
Setting Up Workforce Groups for Workforce SimulationYou use workforce groups to set up workforce reduction rules. You set up workforce groups using the Workforce Group component by selecting Workforce Analytics, Workforce Analytics Setup, Setup Groups. This component is documented in the PeopleSoft Enterprise Workforce Analytic Applications 8.9 PeopleBook.
See Also
Setting Up Workforce Groups and Group Sets

 Entering Workforce Simulation Growth and Reduction Rules
Entering Workforce Simulation Growth and Reduction Rules
Access the Workforce Simulation Rule page.
Selecting a Simulation Type
| Simulation Type | Enter a Simulation Type from the list of translate table values. Valid values are Workforce Growth, Requisition Growth and Workforce Reduction. | 
You enter your requisition growth, workforce growth, and workforce reduction assumptions in the corresponding group boxes below. Later, when you run the workforce simulation process, the system uses these rules to create a simulated workforce output. The system uses your existing workforce as a starting point. The processing is as follows:
New Simulated Workforce = Existing Employees + Employees Reduced + New Simulated Employees.
Note. Set up one Simulation Type per rule. When you save the page or change the field for the rule type, the system hides the fields that do not apply to the Simulation Type you select.
Defining a Workforce Growth Simulation
| Job Code | Enter a new headcount for your organization by specifying the Job Code for the new jobs or positions. Job Codes prompt from the JOBCODE_D00 table. | 
| Department | Specify the Department to which the jobs are to be added. Departments prompt from the DEPARTMENT_SRCH table. Always specify both a Job Code and a Department for a workforce growth rule. | 
| Number to Simulate | Enter the number of new jobs or positions to add to your workforce. | 
| Base Compensation | Indicate the Base Compensation type you want the system to use to simulate the compensation cost of the new workers. Valid translate table values are: 
 | 
| Measure ID | Select a Measure ID. Valid values for the Measure ID prompt from the WA_MKT_PCT_VW table. You developed these measure values and their associated measure amounts using the functionality in the Market Compensation module. | 
Defining a Requisition Growth Simulation
| Constraint Code | Select a Constraint Code to indicate the constraint to use in determining which job openings to use for simulation. Valid values for the Constraint Code prompt from the WA_WFSCONSTR_VW table. Note. DataSets for Requisition Growth simulations must be based on TableMaps having STAFFING_F00 as the primary table. | 
| Base Compensation | Indicate the Base Compensation type you want the system to use to simulate the compensation cost of the requisitions. The valid translate table values are listed above. | 
| Measure ID | Select a Measure ID. Valid values for the Measure ID prompt from the WA_MKT_PCT_VW table. You developed these measure values and their associated measure amounts using the functionality in the Market Compensation module. This field is only required if you pick Market Rate in the Base Compensation field. | 
Defining a Workforce Reduction Simulation
| Group ID | To define the group of employees you want to reduce, select a Group ID from the prompt list values, which are from the WA_CP_GROUP_DFN table. For example, you may choose to reference a workforce group based upon the workforce reduction decisions you made in the Retention Strategy module. | 

 Setting Up Model IDs for Workforce Simulation
Setting Up Model IDs for Workforce SimulationBefore you use the Compensation Strategy Workforce Simulation Model page, you must have set up model IDs in the Performance Management Warehouse. You do this using the EPM Foundation, Business Metadata, Business Framework, Models page. This page is documented in the PeopleSoft Enterprise Performance Management Foundation for Analytical Applications and Performance Management Warehouse 8.9 PeopleBook.
See Also

 Defining a Workforce Simulation Model
Defining a Workforce Simulation Model
Access the Workforce Simulation Model page.
Listing the Rules
Use the grid at the bottom of the page to list the workforce simulation rules you want to include in this model. Add rows to list multiple rules.
| SeqNum (sequence number) and Simulation Rule ID | For each rule enter the SeqNum (sequence number) and Simulation Rule ID. The system displays the simulation rule description. | 

 Setting Up a Scenario Definition for Workforce Simulation
Setting Up a Scenario Definition for Workforce SimulationBefore you run the Workforce Simulation process, you must set up a Scenario ID and definition using the EPM Foundation, Business Metadata, Business Framework, Scenarios page. This component is documented in the PeopleSoft Enterprise Performance Management Foundation for Analytical Applications and Performance Management Warehouse 8.9 PeopleBook.
Note. The scenario type for a Workforce Simulation must be a Forecast Scenario.
See Also

 Setting Up the Process Run Control for Workforce Simulation
Setting Up the Process Run Control for Workforce SimulationAccess the Run Workforce Simulation page.
The run control definition includes these basic elements:
Business unit
Scenario ID
Fiscal year and accounting period
Jobstream ID
Scenario ID
The scenario ID you select using this page must be for a Forecast scenario.
Fiscal Year and Accounting Period
Run Simulation scenarios for a fiscal year and accounting period. Do not run them based on an as of dated jobstream.
These are the basic jobstreams and engines delivered for Workforce Simulation:
| Jobstream ID | Job ID | Application Engine ID | 
| WA_WFS | WA_WFS | WA_WFS | 

 Running the Workforce Simulation Process
Running the Workforce Simulation ProcessTo generate a workforce simulation scenario, you run a PeopleTools Application Engine (AE) process called Workforce Simulation (WA_WFS).
Workforce Simulation Process Output Tables
The main Workforce Simulation process output table is WA_JOB_S00. It is a clone of JOB_F00 with the addition of the PF_SCENARIO_ID field. This table stores the simulated workforce, which includes the current workforce (based on the date of the simulation scenario) from JOB_F00. This table can also include new simulated employees based on the rules defined in the workforce simulation pages (growth rules), as well as simulated terminated employees (reduction rules). This table is a basis for input into the Compensation Planning and Simulation process. If a reduction rule is specified in a simulation, the WA_GROUP_F00 table is also populated with the employees that are to be reduced from the workforce.
Identifying Reduced and New Simulated Employees
The WA_WFS AE process calculations use the groups and rules that apply to the selected business unit, setID, model ID and scenario ID. The process uses the existing employees from JOB_F00 as a starting point, and puts them in the WA_JOB_S00 table, but only in the first accounting period specified in the scenario. Then the system performs actions for the reduced employees in WA_JOB_S00, if any, and then adds new simulated employees to WA_JOB_S00, if any, to create the new simulated workforce. The process flow is:
New Simulated Workforce = Existing Employees + Employees Reduced + New Simulated Employees.
For each reduced employee, the row is assigned a personnel Action of TER, and a Reason of WFS.
For each simulated new employee, the row is assigned a personnel Action of HIR, and a Reason of WFG. The system assigns them an employee identification number based on the structure $YYPPRRR###, where:
| $ | Indicates this is a simulated employee. | 
| YY | Indicates the last two digits of the fiscal year. | 
| PP | Indicates the accounting period. | 
| RRR | Indicates a unique number attached to a WFS rule. Values can range from 001 to 999. | 
| ### | Indicates a unique number generated for an employee within a rule. The system first uses all numeric values ranging from 001 to 999. Then the system uses a combination of both alphabetic and numeric, such as A01, A02 and so on, ultimately up through ZZZ. | 
Note. Based on this formatting, for a given fiscal year, accounting period, and workforce simulation scenario, you can add a maximum of 46,656 unique, simulated employees.
When the system creates simulated employees using existing job requisition information, from STAFFING_F00, it distinguishes these simulated employees from those created by workforce growth rules. Simulated employees from job requisitions are assigned a personnel action of HIR, and a reason of WFJ.
Effective Dating of Models and Rules in Workforce Simulation
The effective date of the model and rules used in the workforce simulation must be less than or equal to the effective date of the accounting period for the process run. For example, when you run the process for the fiscal year 2000, and accounting period 1, then the system uses all rules that are valid as of the beginning of that fiscal year/accounting period. If you have a rule that has an effective date of 02/01/2000, then it won't be used until you run the process for fiscal year 2000, accounting period 2.
Currency Codes and Currency Conversion in Workforce Simulation
When you run the Workforce Simulation process the system assigns new employees (in WA_JOB_S00) a currency code that is the same as the existing employees for that same scenario.
If your implementation of Workforce Rewards includes working with multiple currencies, you must run the Currency Conversion Application Engine process (PF_MULT_CURR) to populate the annual BCE rate field for employees in the JOB_F00 table. The timing of this step is important. You run this process after you have used the delivered ETL tool to import your source data to the data warehouse tables, and before running the Workforce Simulation process. If you don't run the Currency Conversion process prior to running Workforce Simulation, certain annual BCE rates are populated as zero throughout the JOB_F00 table, and these zero rates can be carried through the Workforce Simulation and Compensation Planning and Simulation processes. Employees' annual BCE rates should always be greater that zero.
Note. Check your Application Engine process messages after running the Workforce Simulation process. The process checks for any rows in WA_JOB_S00 with an annual rate of zero. If it finds such rows an error message is generated stating: "Warning: Annual BCE Rate=0. Must run Processing Multiple Currency or CPS results will be incorrect."
ChartFields in Workforce Simulation
When you run the Workforce Simulation process the system automatically retrieves the ChartFields for employees and stores the data in the WA_EE_FUND_F00 table (Employee Funding Defaults). ChartFields for simulated employees are taken from the DEPT_BUDGET_ERN table. ChartFields for existing employees are taken from the JOB_EARNS_DIST, JOB_F00, or DEPT_BUDGET_ERN tables, depending upon the source. The system can carry this ChartField data over to the Compensation Planning and Simulation process.
Synchronizing Workforce Simulation Data with the Workforce Rewards Data Mart
When you run the Workforce Simulation process, the system also calls the Data Mart Dimension process (WA_UPG_DIM), which updates the Workforce Rewards Data Mart dimensions. Workforce Simulation does not call any fact processes, but it does call the dimension build process:
For the first period the scenario is run for, all Workforce Rewards dimensions are populated.
If the scenario is run for additional periods, then only the employee specific dimensions such as WFI_PERSON_DIM and WFI_JOB_DIM are populated. The system does this because Workforce Simulation is creating new employee records in WA_JOB_S00, so the dimensions need to contain a complete list of all employees. Other dimensions do not need to be repopulated as they've already been populated for the first period.
See Also

 Reviewing Your Workforce Simulation Scenario Setup
Reviewing Your Workforce Simulation Scenario SetupReview your workforce simulation rules setup using the following Crystal reports:
Workforce Simulation Rules report (WAC0019), summarizing the simulation rules for a given setID and model ID.
Workforce Groups report (WAC0018), summarizing the workforce group setup.
Note. Samples of these reports are provided with your documentation.
See Also

 Setting Up a Compensation Scenario
Setting Up a Compensation ScenarioTo set up a compensation scenario, use the WA_CP_ELEM_DFN.GBL, WA_CP_GOALMTRX_DFN.GBL, WA_CP_MERIT_DFN.GBL, WA_CP_PYOUT_DFN.GBL, WA_CP_BASE_PAY.GBL, WA_CP_RULE_DFN.GBL, WA_CP_OTHER_DFN.GBL, and WA_CP_MODEL_DFN.GBL components.
This section discusses how to:
Link employee information to a compensation scenario.
Define performance-based calculation rules with a goals matrix.
Define base compensation increase rules with a merit matrix.
Control compensation distribution payout rules.
Define base pay rules.
Define variable pay rules.
Specify other pay rules.
Define frequency details for compensation models.
Set up workforce groups for compensation models.
Set up model IDs for compensation models.
Define a compensation planning and simulation model.
Set up compensation scenario IDs.
Set up the Compensation Planning and Simulation process run control.
Run the Compensation Planning and Simulation process.
Review compensation planning scenario data with the Workforce Rewards data mart.

 Pages Used to Set Up and Run a Compensation Scenario
Pages Used to Set Up and Run a Compensation Scenario
| Page Name | Object Name | Navigation | Usage | 
| Data Element | WA_CP_ELEM_DFN | Workforce Analytics, Compensation Strategy, Setup Data Elements | Create data elements that link employee-based information in the system to compensation planning rules. | 
| Goals Matrix | WA_CP_GOALMTRX_DFN | Workforce Analytics, Compensation Strategy, Setup Goals Matrix | Define performance-based calculation rules for group or employee performance based on a goals matrix. | 
| Merit Matrix | WA_CP_MERIT_DFN | Workforce Analytics, Compensation Strategy, Setup Merit Matrix | Create a merit matrix which defines the amount rules for base compensation increases for your workers. | 
| Payout Rule | WA_CP_PYOUT_DFN | Workforce Analytics, Compensation Strategy, Setup Payout Rules | Establish the amount rules for how to pay out compensation based on a flat amount, percentage of base pay, or criteria in a data element. | 
| Base Pay Compensation Rule | WA_CP_BASE_PAY | Workforce Analytics, Compensation Strategy, Setup Base Pay Rules | Create a base pay compensation rule. | 
| Variable Pay Rule | WA_CP_VC_PAY | Workforce Analytics, Compensation Strategy, Setup Variable Pay Rules | Create a variable pay compensation rule, for bonuses for example. | 
| Other Pay Rule | WA_CP_OTHER_PAY | Workforce Analytics, Compensation Strategy, Setup Other Pay Rules | Create other pay rules, for benefits for example. | 
| Compensation Model | WA_CP_MODEL_DFN | Workforce Analytics, Compensation Strategy, Setup Compensation Model | Set up a model to bring together the workforce groups and compensation rules needed to run a scenario. | 
| Workforce Group Description | WA_CP_MODEL_SEC1 | Click the Workforce Group Info (information) button alongside the group ID field on the Compensation Model page. | View a description of the workforce group. | 
| Compensation Rule Description | WA_CP_MODEL_SEC2 | Select the Compensation Rule Info (information) button alongside the rule ID field on the Compensation Model page. | View a description of the compensation rule. | 
| Run Compensation Scenario | RUN_PF_JOBSTREAM | Workforce Analytics, Compensation Strategy, Run Compensation Scenario | Run the compensation planning and simulation process. | 

 Linking Employee Information to a Compensation Scenario
Linking Employee Information to a Compensation Scenario
Access the Data Elements page.
Data elements, at their most simple level, define information that you link to an employee. At a more complex level, you use data elements when you build compensation rules, to tell the system what data to retrieve about your workforce groups, and what performance measures to apply to your compensation scenario.
Selecting a Data Element Type
Select a Data Element Type from the list of translate table values:
| DataSet | A calculation amount resolved for each employee subject to this rule. DataSets are data pointers from DataMaps. They point to measurable data about an employee, in the data warehouse tables. DataSets provide you a means of defining a set of information to use in Application Engine processes. When you select the DataSet option the Constraint Code field displays. Once you select the Constraint Code, the Dimension and Measure ID fields also display. The DataSet definition you specify with these fields determines the type of measure used in the Compensation Planning and Simulation process (WA_CPS). | 
| Goals Matrix Score | When you select this option, the Goals Matrix ID field appears. Prompt values for this field are from the WA_CP_GOAL_DFN table. You create goals matrices using the Goals Matrix page. | 
| KPI Assessment Value | The KPI Assessment Value is a numeric value for the assessment, or scoring, of a KPI (Key Performance Indicator). You create KPIs in Scorecard. The KPI is scored when the KPI Resolved Value is compared to a target value. When you select KPI Assessment Value the KPI ID field displays. Prompt values for this field are from the WA_KPI_DFN_VW table. | 
| KPI Resolved Value | The KPI Resolved Value is the calculated value of the KPI. You define them using the KPI Manager, in Scorecard. When it is compared, or scored, against a target value, the result is a numeric KPI Assessment Value. When you select KPI Resolved Value, the KPI ID field displays. Prompt values for this field are from the WA_KPI_DFN_VW table. | 
DataSet Data Element Type
| Constraint Code | For a Data Element Type of DataSet select the Constraint Code for the system to use for every compensation rule to which the data element is applied. Constraints are collections of filters you use to define business rules for processing, and return desired data from a given DataMap. This field prompts values from constraints you define in Performance Management Warehouse with the Constraint component. The prompt values are from the PF_CONSTR_DFN table. Note. When you build Constraints for use with Workforce Rewards, you must base them on DataMaps where the primary table in the TableMap is the simulated workforce job table WA_JOB_S00. | 
| Dimension | Select a dimension from the prompt list values, which are from the WA_DM_DIM_VW table. The most common dimensions for Workforce Analytics that repeatedly appear in the DataMaps are business unit, employee identification, department identification, location code, and job code. | 
| Measure ID | Specify the Measure ID for the Dimension. The prompt values are from the WA_DM_MEAS_VW table. | 
| Compile Rule | For a Data Element Type of DataSet, click the Compile Rule button. This triggers the system to build the underlying SQL. Otherwise the system builds it automatically on saving the page. After building the SQL the system displays the SQL Object ID Prefix, a system-generated number identifying the location of the SQL in the SQL Repository. | 
Goals Matrix Score Data Element Type
For a Data Element Type of Goals Matrix Score, first create the Goals Matrix on the Goals Matrix page. Then, while still on that page, choose to have the system automatically create a corresponding Data Element with the same name. If you already have a Goals Matrix built, and you want to define a Data Element with a different name, then create the Data Element using this page. In either case, each Goals Matrix ID must be linked to a corresponding Data Element ID.
Some Important Points about Creating KPIs for Use with Workforce Rewards
When you use Scorecard to create KPIs for use in Workforce Rewards, remember the following important points:
The Enterprise Scorecard pages you use to create KPIs are located by navigating to Key Performance Indicators, Define KPI's. They are as follows:
Data Element Definition (if you are using data elements in your KPI.)
Calculation Definition.
Assessment Definition (if you are using a target rule, then specify the assessment usage as Workforce Analytics to ensure required values are populated.)
KPI Definition.
KPI Calculation Rule.
KPI Object.
KPI Target Rule (if you are using assessed values then specify the target rule type as Workforce Analytics.)
Specify the model IDs for your KPIs in the KPI Model column, on the EPM Foundation, Business Metadata, Business Framework, Scenarios - Forecast Business Rules page.
Processing is done by using the Workforce Rewards jobstreams (either WA_CPS or WA_RETENT). None of the KPI jobstreams need to be run if the KPI is only used in Workforce Rewards.)
Workforce-specific KPIs are delivered with Workforce Scorecard. If your implementation includes Workforce Scorecard, you can use those KPIs on the Data Element page in Workforce Rewards.
Note. You can only use the KPI-related options if your implementation includes Scorecard or Workforce Scorecard.

 Defining Performance-Based Calculation Rules with a Goals Matrix
Defining Performance-Based Calculation Rules with a Goals Matrix
Indicating the Number of Award Levels in the Scale
| Number of Levels | Select the number of pay out, or performance measure, levels you want to include in your Goals Matrix. Valid values from the translate table are Three Levels, Five Levels and Seven Levels. | 
| Scale and Scale Values | Based on the number of levels you select, the corresponding number of level fields display in the Scale group box, and the same number of performance measure columns display on the Scale Values tab at the bottom of the page. | 
Using the Scale Group Box
The system labels the lowest, middle, and highest levels of the scale the Threshold, Target and Stretch, respectively:
| Threshold | This is the performance level for minimum adequate performance, the designated level of performance below which it is inappropriate to pay incentives. | 
| Target | This is the performance level your organization establishes as the norm for performance and pay out. | 
| Stretch | This is the performance level for which an employee achieves maximum pay out. Performance above this level receives no greater pay out. | 
Scale Group Box
| Scale | If you are using the Goals Matrix in a Formula Plan, you enter the exact pay out amounts you want to apply to each level in this group box. The amounts you enter in these fields are paid out based on the pay out scores calculated for the performance goals in the grid at the bottom of the page. If you use the Goals Matrix in a Target Plan, then you use this group box as a standardizing scale, to standardize data elements to a common scale of measurement. The values you enter in the levels are used by the system to standardize the pay out scores for the performance goals in the grid at the bottom of the page. There are different approaches you can take depending on how diverse your performance goals are: 
 | 
Using the Matrix Group Box
Your goals matrix is made up of performance goals (which are the rows), and performance measures (which are the columns). Individual performance goals are defined using data elements. You create data elements using the Data Element page. On the average, a goals matrix may have from three to five goals, but some may have as many as ten. To list multiple goals in the Goals Matrix, place the cursor in the Data Element ID field and insert additional data rows.
For each individual goal follow these steps:
On the Matrix Elements tab, define the goal by selecting a Data Element ID from the prompt list values from the WA_CP_ELEM_VW table.
Enter a weight value for the goal in the Weight% (weight percentage) field. The system totals the weight percentages for all of the goals and displays the figure in the Total Weight field at the bottom of the page. You must ensure that the cumulative weights for all of your goals adds up to 100.00.
In each of the performance measure columns on the Scale Values tab, enter the Threshold, Target and Stretch values for this specific goal. For example, if the goal is Quarterly Billable Hours, and there are three levels, the performance measure values might be 200, 300, and 400 hours respectively.
Performing Goals Matrix Calculations for a Target Plan
Create a goals matrix with this page for use in conjunction with a compensation plan type called a target plan. The system uses the Goals Matrix to calculate a total score for an employee. The system compares the employee's total score to the scoring criteria defined in the target matrix in the Compensation Rules component, and determines the monetary value of the pay out the employee receives based upon their performance. Here's an example of how this calculation process works:
For this example let's take a goals matrix for employees who are off-site consultants, that calculates their quarterly bonus. We have three goals: billable hours (with values of 200, 300, and 400), customer satisfaction rating (with values of 1,2, and 3), and customer courses taught (with values of 2, 4, and 6). Because the goals are so different, we standardize them using a three level scale of 0, 50, and 100. Our Scale and goals look like this:
| Scale or Goal | Weight | Threshold | Target | Stretch | 
| Scale | 
 | 0 | 50 | 100 | 
| Billable Hours | 50% | 200 | 300 | 400 | 
| Customer Satisfaction Rating | 25% | 1 | 2 | 3 | 
| Courses Taught | 25% | 2 | 4 | 6 | 
An employee, William Avery, has 350 billable hours, a customer satisfaction rating of 3, and he has taught 3 customer courses. Here's what happens when the system uses this goals matrix to evaluate his performance.
The system looks at his 350 billable hours, and interpolates this against the scale. (Interpolation means using an equation to calculate the value in between two known values.) The system does the same for his customer rating of 3, and his 3 courses. The results of the interpolation are as follows:
| Goal | Employee's Performance | Interpolated Scale Value | Explanation | 
| Billable Hours | 350 | 75 | Because 350 is midway between 300 and 400, the system interpolates that 75 is midway between the standardized scale values of 50 and 100. | 
| Customer Satisfaction Rating | 3 | 100 | 3 corresponds exactly to 100 on the scale. | 
| Courses Taught | 3 | 25 | Because 3 is midway between 2 and 4, the system interpolates that 25 is midway between the standardized scale values of 0 and 50. | 
The interpolated scale value is the employee's actual performance standardized against the scale. Then, for each goal, the system multiplies the interpolated scale value by the weighting, to create a weighted rating for the goal. Then the system adds up the weighted ratings for all of the goals to get a total score.
The calculation process looks like this:
| Goal | Weight | Employee's Performance | Interpolated Scale Value | Weighted Rating | 
| Billable Hours | 50% | 350 | 75 | .5 x 75 = 37.5 | 
| Customer Satisfaction Rating | 25% | 3 | 100 | .25 x 100 = 25 | 
| Courses Taught | 25% | 3 | 25 | .25 x 25 = 6.25 | 
| Total Score | 37.5 + 25+ 6.25 = 68.75 | 
The system then compares the employee's total score against the scoring criteria defined in the target matrix in the Compensation Rules component, and determines the monetary value of the pay out the employee receives based upon their performance. For example, if the target matrix indicates that all employees with a goals matrix score between 50 and 75 should receive a bonus pay out equal to 2 percent of their base pay, then the system calculates a 2 percent bonus for William Avery.
Performing Goals Matrix Calculations for a Formula Plan
Create a goals matrix with this page for use in conjunction with a compensation plan type called a formula plan. In the formula plan, the pay out score is calculated in association with a payout rule. The payout rule must have a payout type of data element, where the data element is a goals matrix such as the one in the previous example. The pay out score is calculated from the goals matrix, as in the prior example, and interpolated against the monetary amounts in the scale to determine the actual pay out amount.
Creating a Data Element From the Goals Matrix
| Create Data Element on Save | You already created the individual data elements used in this goals matrix using the Data Element page. Once the goals matrix is complete, make it into a data element as well. You can do this in two ways. The system creates the data element for you. If this is a new goals matrix ID, and you want the corresponding data element ID to have the same name, select this check box and save the page. This is the default setting for the check box . If you want the data element to have a different name to the goals matrix, clear the Create Data Element on Save check box. | 

 Defining Base Compensation Increase Rules with a Merit Matrix
Defining Base Compensation Increase Rules with a Merit Matrix
| Rating Model | Select a Rating Model from the prompt list values, which are from the WA_RTGMDL_R00 table. | 
Completing and Using the Merit Matrix
| Review Rating | As in HRMS, a merit matrix provides the salary increase parameters for each review rating in a rating model. To complete the merit matrix, you begin with the Review Rating column. Place the cursor in the Review Rating column, and select a rating from the prompt list values, which are from the WA_REVWRTG_R00 table. | 
Insert an additional row of data for each Review Rating in the Rating Model. Then, for each Review Rating, enter the recommended percentage pay increase for each of the employee pay range values as follows:
| Default | In the Default column, select a single review rating that you want the system to use as a default pay increase guideline, if an employee (or simulated employee) has no review rating. | 
| Below Min % (below minimum percentage) | This is the lowest allowable increase for an employee, if the employee's current base compensation is below their salary grade minimum. | 
| Below Max % (below maximum percentage) | This is the highest allowable increase for an employee, if the employee's current base compensation is below their salary grade minimum. Together with the Below Min % figure, this provides an allowable salary increase range for the employee. | 
| 1st Qt Min % (first quartile minimum percentage) | This is the lowest allowable increase for an employee, if the employee's current base compensation falls within the first quartile of their salary grade range. | 
| 1st Qt Max % (first quartile maximum percentage) | This is the highest allowable increase for an employee, if the employee's current base compensation falls within the first quartile of their salary grade range. Together with the 1st Qt Min % figure, this provides an allowable salary increase range for the employee. | 
| 2nd Qt Min % (second quartile minimum percentage) | This is the lowest allowable increase for an employee, if the employee's current base compensation falls within the second quartile of their salary grade range. | 
| 2nd Qt Max % (second quartile maximum percentage) | This is the highest allowable increase for an employee, if the employee's current base compensation falls within the second quartile of their salary grade range. Together with the 2nd Qt Min % figure, this provides an allowable salary increase range for the employee. | 
| 3rd Qt Min % (third quartile minimum percentage) | This is the lowest allowable increase for an employee, if the employee's current base compensation falls within the third quartile of their salary grade range. | 
| 3rd Qt Max % (third quartile maximum percentage) | This is the highest allowable increase for an employee, if the employee's current base compensation falls within the third quartile of their salary grade range. Together with the 3rd Qt Min % figure, this provides an allowable salary increase range for the employee. | 
| 4th Qt Min % (fourth quartile minimum percentage) | This is the lowest allowable increase for an employee, if the employee's current base compensation falls within the fourth quartile of their salary grade range. | 
| 4th Qt Max % (fourth quartile maximum percentage) | This is the highest allowable increase for an employee, if the employee's current base compensation falls within the fourth quartile of their salary grade range. Together with the 4th Qt Min % figure, this provides an allowable salary increase range for the employee. | 
When you run the Compensation Planning and Simulation process (WA_CPS) to generate a compensation scenario, the system looks at an employees review rating, and determines where their current grade and pay fits on this matrix. The system then uses the averaged percentage increase recommendations to calculate the simulated percentage pay increase for the employee.
When you enter the recommended pay increase percentages into the merit matrix, take into account your organization's pay strategy, or the pay strategy that you want to model in a scenario. You may want to create multiple merit matrices to test the costs and benefits of changing your pay strategy. For example, you might create one merit matrix that provides higher pay increase percentages for employees who are at the low end of their salary ranges, but keeps pay increases at a minimum for employees who are currently at the top of their salary range. Or you may want to create a merit matrix that rewards high performers with higher recommended pay increases, and provides poor performers with lower recommended pay increases.

 Controlling Compensation Distribution with Payout Rules
Controlling Compensation Distribution with Payout Rules
| Compensation Type | Select a Compensation Type for the payout rule. Valid values are Currency Amount and Unit of Measure. | 
| Description | Enter a description. | 
| Notes | Enter associated notes. | 
Selecting the Amount Type
| Payout Rule ID | For each Payout Rule ID, select one or more amount types from the list of translate table values. Valid values are Employee Expense, Employee Val and Employer Exp (employee value and employer expense), Employee Value, and Employer Expense. For example, in the case of a benefit plan such as an Employee Stock Purchase Plan (ESPP), the cost to the employer might be zero, but the value to the employee might be large. | 
Entering the Payout Type
For each Amount Type, select a Payout Type from the list of translate table values, which are as follows:
| Data Element | Define the pay out rule using a data element that you have created on the Data Element page, by selecting a Data Element ID from the prompt list values, which are from the WA_CP_ELEM_VW table. You also have the option of specifying the payout be based on a percentage of the data element. | 
| Flat Amount | Define the pay out rule as a monetary flat amount. | 
| Percent of Base Pay | Define the pay out rule using the % of Base Pay (percentage of base pay) field, basing the pay out rule on a percentage of an employee's base pay. | 
You can also base the payout type on a Unit of Measure. Valid values include: Days, Dollars, Each, Man Hours, Number, Percent, Seconds, Stock Units and Time. If this is the case, then enter the Units and Value Per Unit.

 Defining Base Pay Rules
Defining Base Pay Rules
Access the Base Pay Compensation Rule page.
Your next step is to use the setup data you have entered to define compensation rules. Building compensation rules is a little like creating a compensation plan. Except, rather than just specifying the compensation types that go into a compensation plan, you define rules for calculating the predicted pay out for a population of employees who participate in the compensation plan. You define rules for base pay, variable pay, and other pay (for example benefits), either individually or in any given mix that you specify.
| Actionand Reason Code | Enter an Action and Reason Code for the base compensation rule. The purpose of this step is to make the base compensation rules actionable by associating them with personnel actions. | 
Entering a Rule Type
Enter a Rule Type by selecting from the list of translate table values:
| Amount Increase | Select this option if your scenario involves an amount increase to an employee's base pay. Use Amount to enter the increase. | 
| Equity Increase | Select this option if your scenario involves an equity increase to an employee's base pay. Equity increases are pay increases granted to bring an employee's pay up to some internally specified standard. Select the type of equity in the Equity group box. For example, you might want to bring the base pay of all your software developers up to at least the market rate midpoint. To do this, grant an equity increase to those developers whose current pay is below that level. | 
| Merit Matrix Increase | Select this option if your scenario involves a merit increase to an employee's base pay. A merit increase is calculated using a merit matrix created on the Merit Matrix page. Select a Merit Matrix Code from the prompt list values, which are from the WA_CP_MERIT_DFN table. The system uses the amount rules defined in the merit matrix, and an employee's salary review ratings, to determine the level of merit increase to grant the employee. | 
| Percentage Increase | Select this option if you want to grant a pay increase to an employee or group based upon a percentage of their current base pay. Enter the desired increase percentage in Percent of Base Pay field. | 
| Step Progression | Select this option if you want to grant a step progression increase to an employee or group, as long as their salary plan includes steps within grades. When you select this option, the system advances each affected employee one step up their pay scale. | 
Specifying the Equity Type
For a Rule Type of Equity Increase, specify the type of equity in the Equity group box from the following options:
| Internal Pay Structure | This option gives you the ability to define an equity increase based upon an employee's salary Range Penetration. Range Penetration is the degree to which an employee's actual pay has progressed through their salary grade, and is usually expressed as a percentage. For example, if you enter a value of 20% in the field, the system will not grant an equity increase to any employee in the affected group whose salary has already penetrated to this level. For any employee whose degree of range penetration is below this level, the system grants them an equity increase equal to the monetary amount needed to bring them up to this range penetration level. The calculation is: Range penetration = (Employee Base Pay Range Minimum/(Range Maximum Range Minimum) For example: If an employee's pay is 70,000 in a pay range with a minimum and maximum of 40,000 and 80,000, then the calculation is (70,000/ 40,000) / (80,000 / 40,000) = 30/40 = 75% range penetration. | 
| Market Rate | Select this option if you want the equity increase to be based upon the market rate values for the employee's job code and salary grade. Select the Measure ID (the percentile of the market rate) that you want to use as the control point. In this case, for any employee whose current salary is at or above this level, the system grants them no equity increase. For any employee below this level, the system grants them an equity increase equal to the monetary amount needed to bring them up to this level. | 

 Defining Variable Pay Rules
Defining Variable Pay Rules
Access the Variable Pay Rule page.
Using this Page
To complete this page follow these three basic steps:
Specify the Compensation Code, Compensation Type, and VC Plan ID (variable compensation plan identification code).
Specify the compensation distribution Plan Type.
Define the compensation rules in one of the three plan type group boxes.
Identifying the Variable Compensation Code and Type
| Compensation Code | Select the Compensation Code for the variable compensation for which you are defining a rule. This may be any compensation code except regular base pay (600). Prompt list values are from the WA_COMP_TREE_VW table. | 
| Compensation Type. | Select a Compensation Type. Valid values are Currency Amount and Unit of Measure. | 
| VC Plan ID | Associate the variable compensation rule with a VC Plan ID (variable compensation plan identification) from HRMS. | 
Identifying the Compensation Distribution Plan Type
Enter a compensation distribution Plan Type by selecting from the list of Translate values.
| This plan type provides managers ultimate discretion over a pool of money, which is either funded based on organization, group, or employee performance, or is budgeted. The discretionary award determination is sometimes guided by a pre-determined percent of the participant's salary, expressed as an opportunity. This figure can then be modified based upon management's perception of actual value created by the group or employee. For example, each participant in an annual bonus plan may have the opportunity to earn 10 percent of base salary, but that amount may be changed based on manager discretion. Some employees may receive less than 10 percent, others may receive more. | |
| Formula Plan | This compensation distribution plan type is based on a payout rule. The payout rule can be based on a flat amount, a percentage, or a data element. Whereas a target plan distributes payout based on a comparison of a performance measure against a target, in a formula plan the payout is based just on the payout rule. | 
| With this distribution plan type the level of award is linked directly to a predetermined level of performance. For example, a target plan for a group might be as follows: A group, increase the business units, net income by 10% and each member of the group is eligible for an award equal to 5% of base pay. | 
Specifying Discretionary Plan Details
For a Plan Type of Discretionary Plan, select the Distribution Type from the list of translate table values: Business Unit, Department, Group, Job Code, and Location. You can choose to vary the distribution, or compensation pay out, to employees using any one of these dimensions. For any of these options select a Payout Rule ID from the list of prompt values, which are from the WA_CP_PYOUT_DFN table.
The discretionary plan takes the results of a payout rule, but distributes it based on the Distribution Type field. For example, if the Distribution Type is Department, the payout is distributed as a fraction of how many employees belong to a particular department. That is, if person X belongs in a department of 10 people and the payout to be distributed is 1000 units, each employee in that department receives 100 units as a pay out.
Specifying Formula Plan Details
The formula plan calculation process takes the results of a payout rule and distributes it to each employee in a workforce group who has that compensation rule assigned to it, without prorating or otherwise diluting the payout.
Select a Payout Rule ID for the formula plan from the list of prompt values, which are from the WA_CP_PYOUT_DFN table.
Specifying Target Plan Details
For a Plan Type of Target Plan, select the Data Element ID from the prompt list values, which are from the WA_CP_ELEM_VW table. The target plan applies a case or evaluation method for determining what payout is paid to an employee. The level of award for an employee is linked directly to a predetermined level of performance.
Note. Remember, if you are using a goals matrix with a target plan, you create a goals matrix on the Goals Matrix page. Then you tie the goals matrix to a data element on the Data Element page. The data element that you select using this page is the one that references the goals matrix you want to use with this target plan.
In the Compare Type field specify whether you want the first Data Element compared against a Static Value or against another Data Element. If you select Static Value, then complete the following fields:
| Seq Nbr (sequence number) | Enter a number to indicate the sequence in which you want the rules processed. To enter multiple rules insert additional data rows. | 
| Operator | Select an arithmetic operand from the list of values. Valid values include Less Than, Less Than or Equal To, Not Equal To, Equal To, Greater Than, and Greater Than or Equal To. | 
| Value | Enter the comparison value as a numeric value. | 
| Payout Rule ID | Indicate the Payout Rule ID you want to associate this condition with. Prompt list values are from the WA_CP_PYOUT_DFN table. | 
If you select Data Element, then complete the following fields:
| Seq Nbr (sequence number) | Enter a number to indicate the sequence in which you want the rules processed. To enter multiple rules insert additional data rows. | 
| Operator | Select an arithmetic operand from the list values. Valid values include Less Than, Less Than or Equal To, Not Equal To, Equal To, Greater Than, and Greater Than or Equal To. | 
| Data Element ID | Select a Data Element ID from the prompt list values, which are from the WA_CP_ELEM_VW table. | 
| Payout Rule ID | Indicate the Payout Rule ID you want to associate this condition with. Prompt list values are from the WA_CP_PYOUT_DFN table. | 

 Specifying Other Pay Rules
Specifying Other Pay RulesAccess the Other Pay Rule page entering a setID and compensation Rule ID.
This page is essentially the same as the Variable Pay Rule page, with the following exceptions:
It does not have the variable compensation plan ID field.
Its intended use is for benefits-related compensation.

 Setting Up Frequency Details for Compensation Models
Setting Up Frequency Details for Compensation ModelsYou use Frequency ID Codes on the Compensation Model page. You set up these codes on the EPM Foundation, EPM Setup, Common Definitions, Calendars, Frequency and Frequency Details pages. You can also access the Frequency Details page directly from the Workforce Analytics, Compensation Strategy menu, enabling you to review the frequency IDs in the system. These pages are documented in the PeopleSoft Enterprise Performance Management Foundation for Analytical Applications and Performance Management Warehouse 8.9 PeopleBook.
See Also

 Setting Up Workforce Groups for Compensation Models
Setting Up Workforce Groups for Compensation ModelsYou use workforce groups on the Compensation Model page. You set up workforce groups using the Workforce Analytics, Workforce Analytics Setup, Workforce Groups component. These pages are documented in the PeopleSoft Enterprise Workforce Analytic Applications 8.9 PeopleBook.
See Also
Setting Up Workforce Groups and Group Sets

 Setting Up Model IDs for Compensation Models
Setting Up Model IDs for Compensation ModelsBefore you use the Compensation Model page, you must set up a model ID on the EPM Foundation, Business Metadata, Business Framework, Models page. This page is documented in the PeopleSoft Enterprise Performance Management Foundation for Analytical Applications and Performance Management Warehouse 8.9 PeopleBook.
See Also

 Defining a Compensation Planning and Simulation Model
Defining a Compensation Planning and Simulation Model
Access the Compensation Model page.
Understanding the Purpose of this Page
The purpose of this page is to tie together the setID, model ID, workforce groups, compensation rules, and calculation frequencies needed to use the model in a scenario. The model definition tells the Compensation Planning and Simulation process (WA_CPS) what compensation data to calculate for what group of employees, and on what frequency.
Two Methods for Beginning the Model Definition
You have option of cloning your model and rules from an existing one. To do this select a model ID in the Clone Model ID field. Prompt values are from the WA_CP_MODL_TBL table. If you choose to do this, edit the model setup and rules to create your new model.
You also have the option of creating your new model manually. To do this bypass the Clone Model ID field and proceed to complete the fields on the remainder of the page.
In the Group ID field, select the overall workforce group which encompasses all of the workers you want to include in the model. Prompt values are from the WA_CP_GROUP_DFN table.
Select the Include Current Pay check box if you want the system to automatically include employees' current base salary in their compensation calculations. This is useful when you want to model the total compensation impact of compensation changes. Leave it cleared if you want the system to omit current pay from the compensation calculations. This is useful when you want to model only the change in compensation.
Defining the Rule Sequence
Use the Rule Sequence group box to specify the sequence of groups and compensation rules you want to include in the model.
| Sequence | When you specify multiple compensation rules for your compensation model, you must specify the sequence in which you want them processed. The system inserts default sequence numbers, but the field is editable, so you can change the sequence. | 
| Group ID | Select a workforce group ID from the prompt list values, which are from the WA_CP_GROUP_DFN table. The workers in this group must be a subset of the overall group specified above, in the model definition. | 
| Rule ID | Select a compensation rule ID from the prompt list values, which are from the WA_CP_RULE_VW3 table. | 
| Frequency ID | Select a calculation frequency ID from the prompt list values, which are from the PF_FREQ_DTL table. | 
| Workforce Group Info and Compensation Rule Info | Click the Workforce Group Info or Compensation Rule Info button to the right of the Group ID and Rule ID fields to access the Workforce Group Description and Compensation Rule Description pages, and view the descriptions of the groups or rules. | 

 Setting Up Compensation Scenario IDs
Setting Up Compensation Scenario IDsBefore you run the Compensation Planning and Simulation process in Compensation Strategy, you must have set up a scenario ID using the EPM Foundation, Business Metadata, Business Framework, Scenarios page. These pages are documented in the PeopleSoft Enterprise Performance Management Foundation for Analytical Applications and Performance Management Warehouse 8.9 PeopleBook.
See Also

 Setting Up the Compensation Planning and Simulation Process Run Control
Setting Up the Compensation Planning and Simulation Process Run ControlAccess the Run Compensation Scenario page.
The run control definition includes these basic elements:
Business unit
Scenario ID
Fiscal year and accounting period
Jobstream ID
Scenario ID
The scenario ID you select using this page can be for either a Forecast or a Historical scenario.
When you use the Run Jobstream run control you can access and run other jobstreams, but these are the basic jobstreams and engines delivered for Compensation Planning and Simulation:
| Jobstream ID | Job ID | Application Engine ID | 
| WA_CPS | WA_CPS, WA_CPS_MRG | WA_CPS | 

 Running the Compensation Planning and Simulation (CPS) Process
Running the Compensation Planning and Simulation (CPS) ProcessTo generate a Compensation Planning scenario, you run a PeopleTools Application Engine (AE) process called Compensation Planning and Simulation (WA_CPS).
Running CPS as a Forecast versus Historical Process
The Retention Assignment and Workforce Simulation processes can serve as a basis for input to the CPS process, when it is run for Forecast scenarios. You can use constraints to integrate the results of the Retention Assignment engine into your compensation rules, or use the reduced employees in WA_GROUP_F00 as a workforce group. You can also use the Workforce Simulation process to generate a simulated workforce in WA_JOB_S00, consisting of your existing employees in a business unit, plus any new simulated employees and reduced employees (employees to be removed from your workforce). The CPS process can take the simulated workforce generated by the Workforce Simulation process, and use it as input for calculating compensation costs and values. CPS can simulate several varieties of base compensation rules, as well as an infinite number of changes to variable and benefits compensation rules.
If you run CPS as a Historical scenario the system uses the existing workforce from JOB_F00 to populate WA_JOB_S00. In this case you do not use inputs from either retention strategy or workforce simulation.
CPS Process
The CPS process performs calculations using the groups and rules that apply to the business unit, setID, model ID and scenario ID defined on the run control, if the process is not already approved. The process performs calculations using the annual rate and annual amount base currency equivalent fields in the tables. The process does not convert rates and amounts back to hourly or monthly. For each job with changed compensation data, new rows of data are added to the WA_JOB_S00 table. Each row of data is associated with a personnel action of PAY and a reason of CPS.
The high-level sequence of tasks performed by the CPS process is as follows:
Resolves the model rules.
Prepares input from the WA_JOB_S00 table.
Flattens trees (for Job Code, Organization, and Compensation Code).
Calls the subprograms stored in the application libraries in the following order:
| Group Builder (WA_GRPBUILD) | Resolves the constraints associated to the workforce group definition. After resolving the constraints, the data from the constraints (primarily employees) is copied over to the WA_GROUP_F00 temporary table so the CPS process can utilize it to process affected employees. | 
| Base Pay Calculator (WA_BP_CALC) | Calculates the base pay for employees in a scenario based on the compensation rules specified in the model. | 
| Data Element Resolver (WA_DATA_ELEM) | Resolves the data elements used in the scenario and resolves the accompanying data in the WA_DATAEE_F00 temporary table. The data elements resolved by this process can be used in the Variable Pay Calculator or the Payout Resolver processes. | 
| Payout Resolver (WA_PAYOUT) | Determines all of the pay out possibilities for a given scenario. After the payouts are determined, the results of a payout are then accessed by the Variable Pay Calculation program to determine which pay out to use for the final results in the CPS process. | 
| Variable Pay Calculator (WA_VP_CALC) | Is similar to the Base Pay Calculator, however, it differs in that it uses the results from the last three sub-programs to calculate the variable compensation to pay out to the employee. | 
CPS Process Output Tables
When you run CPS the process populates these final output tables:
| Table | Purpose | 
| WA_CALC_F00 | Stores all final calculation results of the CPS process. This includes the appropriate costs or value per employee based on the rules specified in the scenario. The system only performs calculations for, and updates, the annual rate and annual amount base currency equivalent fields in the table. The system does not convert rates and amounts back to hourly or monthly. If part of the scenario process run includes a workforce simulation where simulated employees are added to the workforce, the new employees are assigned a currency code (in WA_JOB_S00) that is the same as the existing employees for that same scenario. | 
| WA_JOB_S00 | A clone of JOB_F00 with the addition of PF_SCENARIO_ID in it. For each job with changed base compensation data, new rows of data are added to the table. Each row of data is associated with a personnel action of PAY and a reason of CPS. | 
| WA_GROUP_F00 | Contains the list of employees in a workforce group specified in the scenario. WA_GROUP_F00 is populated by both WFS and CPS. If a reduction rule is specified in the scenario, the WA_GROUP_F00 table is populated with the employees that are to be reduced from the workforce during the WFS run. A reduction rule points to a workforce group to be reduced, this forces the WFS process to call the Group Builder process to run and create the group in WA_GROUP_F00. | 
| WA_DATAEE_F00 | Contains the resolved values for all data elements specified in the scenario. The table is populated by the WA_DATA_ELEM AE library that is called by CPS. | 
| WA_JOBPAY_F00 | Contains base pay compensation data for employees in the scenario calculations. Provides you the ability to direct the CPS process to either include or exclude current base pay from the process calculations. | 
ChartFields in Compensation Planning and Simulation
When you run the Workforce Simulation process the system automatically retrieves the ChartFields for employees and stores the data in the WA_EE_FUND_F00 table (Employee Funding Defaults). The CPS process populates the ChartFields in the WA_CALC_FUND_F00 table (CPS Funding Output) using the data from WFS, but replaces the ChartField account field data with data from CPS.

 Reviewing Compensation Planning Scenario Data with Workforce Rewards Data Mart
Reviewing Compensation Planning Scenario Data with Workforce Rewards Data MartWhen you run the CPS process, the system also calls the CPS Data Mart process (WA_CPS_FACT), which updates the Workforce Rewards Data Mart. This keeps the data in the Data Mart and the Workforce Rewards tables synchronized. You can also run the CPS Data Mart process alone, to populate the fact tables for prior periods without having to run the WA_CPS process.
| Reporting Area | Input Table (D00, R00, and F00) | Output Table (Fact) | 
| CPS | WA_JOB_S00, WA_CALC_F00, WA_COMP_HST_F00, JOBCODE_D00, LOCATION_D00, PERSONAL_D00, SAL_GRADE_D00, WA_MKT_RATE_TBL | WA_CPS_FACT: The final output table of the engine. Contains all the facts required from the CPS engine. | 
In Compensation Strategy the fact table data is accessed by delivered inquiry pages in the Compensation Scenario inquiry component. You also have the option of selecting a business intelligence application of your own choice, and developing analysis templates for use with Compensation Strategy.
See Also

 Reviewing and Analyzing a Compensation Scenario
Reviewing and Analyzing a Compensation ScenarioThis section provides an overview of compensation scenario review and analysis and discusses how to:
Run Crystal reports to review your scenario.
Review results of data elements applied to a scenario.
Review merit matrix table setup.
Review pay rules setup.
Review a high-level compensation scenario summary.
Review compensation scenario rule details.
Review compensation scenario group details.
Review compensation scenario employee details.

 Understanding Compensation Scenario Review and Analysis
Understanding Compensation Scenario Review and Analysis
Once you have run the Compensation Planning and Simulation Application Engine process (WA_CPS), the next step is to review your work and analyze the results of your scenario. To assist you we provide the following analysis tools:
Six Crystal reports to review the setup for your calculation, payout rules, and compensation rules, and compensation models.
Three inquiry pages to review the data for your data elements, merit matrixes, and payout rules.
The Compensation Scenario inquiry component, to review and analyze compensation scenario output.
The Compensation Scenario inquiry component allows you to review data in the WA_CPS_FACT Data Mart. The 12 pages in this component provide multidimensional access to the data.
Analyzing and reviewing your compensation scenario is an iterative process. If you don't think the data output from your scenario is satisfactory, then go back to the various setup steps outlined in this chapter and change the groups and rules as needed. Then run the Compensation Scenario process over again, and analyze and review the results. Keep doing this until you are satisfied you have identified the scenario with the desired results.

 Pages Used to Review and Analyze Your Compensation Scenario
Pages Used to Review and Analyze Your Compensation Scenario
| Page Name | Object Name | Navigation | Usage | 
| Data Elements report | RUN_RWA_0016 | Workforce Analytics, Workforce Reports, Compensation Strategy Reports, Data Elements | Run the Data Elements Crystal report (WAC0016). | 
| Goals Matrix report | RUN_RWA_0015 | Workforce Analytics, Workforce Reports, Compensation Strategy Reports, Goals Matrix | Run the Goals Matrix Crystal report (WAC0015). | 
| Merit Matrix report | RUN_RWA_0017 | Workforce Analytics, Workforce Reports, Compensation Strategy Reports, Merit Matrix | Run the Merit Matrix Crystal report (WAC0017). | 
| Payout Rules report | RUN_RWA_0014 | Workforce Analytics, Workforce Reports, Compensation Strategy Reports, Payout Rules | Run the Payout Rules Crystal report (WAC0014). | 
| Compensation Rules report | RUN_RWA_0013 | Workforce Analytics, Workforce Reports, Compensation Strategy Reports, Compensation Rules | Run the Compensation Rules Crystal report (WAC0013). | 
| Compensation Model report | RUN_RWA_0012 | Workforce Analytics, Workforce Reports, Compensation Strategy Reports, Compensation Model | Run the Compensation Model Crystal report (WAC0012). | 
| Data Elements Inquiry | WA_ELEM_INQ | Workforce Analytics, Compensation Strategy, Review Data Elements | Review the results of the data elements included in a scenario. | 
| Data Element Description | WA_ELEM_INQ_SEC | Click the Data Element Info (information) button alongside the data element ID on the Data Elements inquiry page | View a description of a data element. | 
| Merit Matrix inquiry | WA_CP_MERIT_INQ | Workforce Analytics, Compensation Strategy, Review Merit Matrix | Review the merit matrix setup. | 
| Pay Rules inquiry (base pay) | WA_CP_BP_INQ | Workforce Analytics, Compensation Strategy, Review Pay Rules | Review the compensation rules setup for base pay. | 
| Pay Rules inquiry (variable and other pay) | WA_CP_VC_INQ | Workforce Analytics, Compensation Strategy, Review Pay Rules | Review the compensation rules setup for variable pay and other (benefits) compensation. | 
| Compensation Scenario - Scenario Summary | WA_CP_SUMMARY | Workforce Analytics, Compensation Strategy, Review Compensation Scenario Additionally, by clicking the Scenario Summary link from the other pages in the Compensation Scenario inquiry component. | Review a high-level summary of the employer expenses versus employee values for a compensation planning scenario, and to gain access to the other 11 pages in the component, which further detail the scenario results. | 
| Compensation Scenario - Rule Summary | WA_CP_RULE_SUM | Click the Rule Summary link from other pages in the Compensation Scenario inquiry component. | Review a list of compensation rules included in the compensation planning scenario. | 
| Compensation Scenario - Rule Summary Detail | WA_CP_BP_RUL_EE | Click any pay rule listed in the Pay Rule column on the Rule Summary page. | Review a list of the employees included in a compensation rule in a compensation planning scenario. | 
| Compensation Scenario - Rules By Period | WA_CP_RULE_PER | Click the Rules by Period link from the other pages in the Compensation Scenario inquiry component. | Review a list of the compensation rules included in a compensation planning scenario by accounting period. | 
| Compensation Scenario - Rule By Period Detail | WA_CP_BP_RUL_EE_P | Click any pay rule listed in the Pay Rule column on the Rules by Period page. | Review a list of the employees included in a compensation planning scenario, by accounting period. | 
| Compensation Scenario - Group Summary | WA_CP_GROUP_SUM | Click the Group Summary link from the other pages in the Compensation Scenario inquiry component. | Review a list of the workforce groups included in a compensation scenario. | 
| Compensation Scenario - Group Summary Detail | WA_CP_GRP_EE | Click any value listed in the Group ID column on the Group Summary page. | Review a list of the employees in a workforce group included in a compensation planning scenario. | 
| Compensation Scenario - Groups By Period | WA_CP_GROUP_PER | Click the Groups By Period link from the other pages in the Compensation Scenario inquiry component. | Review a list of the workforce groups included in a compensation planning scenario by accounting period. | 
| Compensation Scenario - Group By Period Detail | WA_CP_GRP_EE_P | Click any value listed in the Group ID column on the Groups by Period page. | Review a list of the employees included in a workforce group for a given accounting period in a compensation planning scenario. | 
| Compensation Scenario - Employee Summary | WA_CP_EE_SUM | Click the Employee Summary link from the other pages in the Compensation Scenario inquiry component. | View a list of the employees included in a compensation planning scenario. | 
| Compensation Scenario - Employees By Period | WA_CP_EE_PER | Click the Employees By Period link from the other pages in the Compensation Scenario inquiry component. | Review a list of employees included in a compensation planning scenario by accounting period. | 
| Compensation Scenario - Employee Detail | WA_CP_EE_DET | Click any employee ID listed in the Employee ID column on various pages in the Compensation Scenario inquiry component. | Review personal, group, rule, value and expense information for an individual employee included in a compensation planning scenario. | 

 Running Crystal Reports to Review your Scenario
Running Crystal Reports to Review your ScenarioUse the following Crystal reports to review the data setup for your Compensation Strategy system:
Data Elements Crystal report (WAC0016) for reviewing your data elements.
Goals Matrix Crystal report (WAC0015) for reviewing your goal matrixes.
Merit Matrix Crystal report (WAC0017) for reviewing your merit matrixes.
Payout Rules Crystal report (WAC0014) for reviewing your payout rules.
Compensation Rules Crystal report (WAC0013) for reviewing your compensation rules.
Compensation Model Crystal report (WAC0012) for reviewing your compensation models.
Note. Samples of these reports are provided with your documentation.
See Also

 Reviewing the Results of Data Elements Applied to a Scenario
Reviewing the Results of Data Elements Applied to a Scenario
Access the Data Element Inquiry page.
Entering Search Criteria
Use the active fields at the top of the screen to indicate search criteria for the rows of data you want to see displayed in the grid on the bottom of the page.
| Business Unit and Scenario ID | Business Unit and Scenario ID are the only required fields on this page. Enter a Business Unit and a Scenario ID from the prompt list values, which are from the SP_BU_PF_NONVW and SCENARIO_SRCH tables, respectively. | 
| Fiscal Year, Accounting Period, Data Element ID and EmplID | You have the option of using the Fiscal Year, Accounting Period, Data Element ID or EmplID (employee identification) as search criteria. The Data Element ID and EmplID prompt values are from the WA_CP_ELEM_DFN and PERSONAL_SRCH tables, respectively. | 
| Search | Once you have entered your search criteria, click the Search button. | 
| Data Elements | After the search is performed the system retrieves the requested rows of data and displays them in the Data Elements grid on the bottom of the page. | 
Reviewing the Data Elements Data
Based on your search criteria, the system displays a row of data for each employee in the scenario whose compensation calculations were based on a data element. You use the display to view the results of the data elements after the Compensation Planning and Simulation process is run. For example, if you want to view the results of an employee's goals matrix score, do that here.
For each row of data displayed, the system provides the Fiscal Year, accounting Period, EmplID , and:
| Empl Rcd# (employment record number) | The Employment Record Number is used for employees with multiple jobs. | 
| Data Element ID | The Data Element ID that was used in a compensation rule for this employee in this scenario. | 
| Measure Amount | The value associated with the data element. For example, if the data element you are looking at is for a goals matrix score, the measure amount is the actual score. | 
| Data Element Info | Click the Data Element Info button to access the Data Element Description page and view a description of the data element. | 
Note. On inquiry pages such as this one, row-level security can go down to the employee level. This means, if your implementation has row-level security, and you don't have security to see an employee, you won't. The employees you see in the grid, on this page, can vary depending upon your level of security access.

 Reviewing the Merit Matrix Table Setup
Reviewing the Merit Matrix Table SetupAccess the Merit Matrix inquiry page. Enter a SetID, Merit Matrix Code, and Rating Model. Prompt list values for the Merit Matrix Code and Rating Model are from the WA_CP_MERIT_DFN table and WA_RTGMDL_R00 table, respectively.
This page is a display-only copy of the Merit Matrix setup page. Refer to that page discussion for a description of the fields.
See Also
Defining Base Compensation Increase Rules with a Merit Matrix

 Reviewing Pay Rules Setup
Reviewing Pay Rules SetupAccess the Pay Rules inquiry page.
| SetID and Rule ID | Enter a SetID, and Rule ID. | 
| Compensation Rule Type | The page displays varying fields depending upon the Compensation Rule Type selected: Base Pay Rule, Variable Pay Rule or Other Pay Rule. The system displays the setup for the selected compensation rule, from the WA_CP_RULE_DFN table. This is the data you entered using the Base Pay Rules, Variable Pay Rules, and Other Pay Rules setup pages. Refer to those page discussions for a description of the fields. | 
See Also

 Reviewing the Compensation Scenario Summary Page
Reviewing the Compensation Scenario Summary Page
Access the Compensation Scenario component.
From this page you can access all the other pages in the component.
As you navigate between the pages in the Compensation Scenario component, the system displays summary, group, employee and compensation rule level data about the scenario compensation costs. The compensation costs are categorized as either Employer Expenses or Employee Values.
At the top of each page in this component, the system displays links to the other pages in the component. Click these links to navigate from one page to another.
At the top of each page the system also displays the Business Unit, Scenario ID, scenario Description, Fiscal Year, Currency and Approval Status for the scenario.
Note. This component contains confidential information at both the scenario and employee level. Depending upon your implementation of row-level security, the scenarios and employees an operator sees in the Compensation Scenario inquiry pages can vary depending upon their level of security access. If you implement row-level scenario security, and an operator doesn't have security access for a given scenario, they cannot see it. If you implement row-level employee security, and an operator doesn't have security access to see an employee, they won't.
On the Scenario Summary page the system displays a bar chart comparing the total Employer Expense to the total Employee Value, for the scenario, and by Accounting Period.
The system also displays the monetary amounts for Total Employer Expense and Total Employee Value, for the scenario.
For each accounting Period, the system displays the monetary amounts for the Average Value, total Employee Value, and total Employer Expense.

 Reviewing the Compensation Scenario Rules Pages
Reviewing the Compensation Scenario Rules Pages
Access the Compensation Scenario inquiry component rules pages.
Note. Since the Compensation Scenario inquiry component rules pages are similar in their layout and content, we show this one example for the Rule Summary page, but not all of the others. We discuss the content and fields for each of the rules pages in the subtopic headings that follow.
Rule Summary Page
When you access the Rule Summary page, the system displays a bar chart comparing the Employer Expense to the Employee Value, for the scenario, and by compensation Pay Rule.
The system also displays a list of the pay rules included in the scenario. For each Pay Rule, the system also displays the monetary amounts for the Average Value, total Employee Value, and total Employer Expense.
Click any value listed in the Pay Rule column to open the Rule Summary Detail page for that pay rule.
Rule Summary Detail Page
When you access the Rule Summary Detail page, the system displays a bar chart comparing the total Employer Expense to the total Employee Value, for a single compensation Pay Rule, and by Accounting Period.
The system also displays the monetary amounts for Total Employer Expense and Total Employee Value, for the Pay Rule.
The system also displays a list of the employees included in the pay rule calculations. For each EmplID (employee identification number), the system displays the employees' Department, Job Code, and monetary amounts for the Employee Value and Employer Expense.
Click any employee listed in the EmplID column to open the Employee Detail page for that employee.
Rules by Period Page
When you access the Rules by Period page, the system displays a bar chart comparing the Employer Expense to the Employee Value, for the scenario, by compensation Pay Rule, and for each Accounting Period.
The system also displays a list of the pay rules, by accounting period, included in the scenario. For each accounting Period and Pay Rule, the system also displays the monetary amounts for the Average Value, total Employee Value, and total Employer Expense.
Click any value listed in the Pay Rule column to open the Rules by Period Detail page for that pay rule.
Rules by Period Detail Page
When you access the Rules by Period Detail page, the system displays a bar chart comparing the Employer Expense to the Employee Value, for a single compensation Pay Rule, and by Accounting Period.
The system also displays the monetary amounts for the Average Employee Value, Total Employee Value and Total Employer Expense, for the Pay Rule, for each accounting Period.
The system also displays a list of the employees included in the pay rule calculations for the accounting period. For each EmplID (employee identification number), the system displays the employees Group ID, Department, Job Code, and monetary amounts for the Employee Value and Employer Expense.
Click any employee listed in the EmplID column to open the Employee Detail page for that employee.

 Reviewing the Compensation Scenario Groups Pages
Reviewing the Compensation Scenario Groups Pages
Access the Compensation Scenario inquiry component groups pages.
Note. Since the Compensation Scenario inquiry component groups pages are similar in their layout and content, we show this one example for the Group Summary page, but not all of the others. We discuss the content and fields for each of the groups pages in the subtopic headings that follow.
Group Summary Page
When you access the Group Summary page, the system displays a bar chart comparing the Employer Expense to the Employee Value, for the scenario, and by workforce Group.
The system also displays a list of the groups included in the scenario. For each Group ID, the system also displays the monetary amounts for the Average Value, total Employee Value, and total Employer Expense.
Click any value listed in the Group ID column to open the Group Summary Detail page for that group.
Group Summary Detail Page
When you access the Group Summary Detail page, the system displays a bar chart comparing the total Employer Expense to the total Employee Value, for each employee within a Group ID.
The system also displays the monetary amounts for Total Employer Expense and Total Employee Value, for the group.
The system also displays a list of the employees included in the group calculations. For each EmplID (employee identification number), the system displays the employees Department, Job Code, and monetary amounts for the Employee Value and Employer Expense.
Click any employee listed in the EmplID column to open the Employee Detail page for that employee.
Groups by Period Page
When you access the Groups by Period page, the system displays a bar chart comparing the Employer Expense to the Employee Value, for each workforce Group ID in the scenario, and by accounting Period.
The system also displays a list of the groups, by accounting period, included in the scenario. For each accounting Period and Group ID, the system also displays the monetary amounts for the Average Value, total Employee Value, and total Employer Expense.
Click any value listed in the Group ID column to open the Group by Period Detail page for that group.
Group by Period Detail Page
When you access the Group by Period Detail page, the system displays a bar chart comparing the Employer Expense to the Employee Value, for the employees within a single workforce Group ID, and by Accounting Period.
The system also displays the monetary amounts for the Average Employee Value, Total Employee Value and Total Employer Expense, for the Group ID, and for each accounting Period.
The system also displays a list of the employees included in the group for the accounting period. For each EmplID (employee identification number), the system displays the employees Department, Job Code, and monetary amounts for the Employee Value and Employer Expense.
Click any employee listed in the EmplID column to open the Employee Detail page for that employee.

 Reviewing the Compensation Scenario Employee Pages
Reviewing the Compensation Scenario Employee Pages
Access the Compensation Scenario inquiry component employee pages.
Note. Since the Compensation Scenario inquiry component employee pages are similar in their layout and content, we show this one example for the Employee Summary page, but not all of the others. We discuss the content and fields for each of the employee pages in the subtopic headings that follow.
Employee Summary Page
When you access the Employee Summary page, the system displays a bar chart comparing the Employer Expense to the Employee Value, for each Employee included in the scenario.
The system also displays a list of the employees included in the scenario. For each Employee ID, the system also displays employee Name, and the monetary amounts for the Employee Value and Employer Expense.
Click any employee listed in the Employee ID column to open the Employee Detail page for that employee.
Employees by Period Page
When you access the Employees by Period page, the system displays a bar chart comparing the Employer Expense to the Employee Value, for each Employee in the scenario, and by accounting Period.
The system also displays a list of the employees, by accounting period, included in the scenario. For each accounting Period and Employee ID, the system also displays the employee Name, and monetary amounts for the Employee Value, and Employer Expense.
Click any employee listed in the Employee ID column to open the Employee Detail page for that employee.
Employee Detail Page
When you access the Employee Detail page, the system displays a bar chart comparing the Employer Expense to the Employee Value, for the selected Employee, and by accounting Period.
The system also displays the employee's Gender, Ethnicity, Total Employee Value and Total Employer Expense.
The system also displays a list, by accounting Period, of each Group ID and Rule ID the employee is included in, for the scenario. For each period, group and rule combination (that is, for each row of data) the system displays the employee's Employee Value and Employer Expense.

 Altering Scenario Results with Analytic Calculation Engine
Altering Scenario Results with Analytic Calculation EngineBy generating a Compensation Planning and Simulation (CPS) scenario you produce results that define a compensation strategy and budget. The Compensation Strategy module provides functionality to enable a compensation analyst to review and alter the results of a CPS scenario online using ACE (Analytic Calculation Engine). ACE is a decision support tool that provides real-time, multidimensional modeling. With ACE the compensation analyst can review, analyze and alter CPS scenario results, to make sure they are within the constraints of the organization's overall compensation strategy and budget; the analyst can analyze and alter scenario results without having to change the model and rules, and rerun the process.
This section provides an overview of how to use ACE with CPS and discusses how to:
Load the CPS scenario results into an ACE model.
Alter the compensation scenario.
Review the compensation ACE model results.

 Understanding How to Use ACE With Compensation Strategy
Understanding How to Use ACE With Compensation Strategy
To use ACE to alter a CPS scenario follow these steps:
Create an ACE model ID by going to EPM Foundation, Business Metadata, Business Framework, Models.
You can load a scenario into different models. However you cannot load multiple scenarios into a single model—loading a scenario into a model will overwrite any preexisting scenario. Also reloading the same scenario into the same analytic model will reset any adjustments made to this scenario. It is therefore advisable to create multiple model IDs for different users or different sets of assumptions.
Note. Due to the analytic server's limited resources, it is recommended that you reuse the same model ID, whenever possible.
Select a CPS scenario.
Load the ACE model with the selected scenario results .
Use the Alter Compensation Scenario page to review, analyze and alter the ACE model containing the scenario results.
Use the Review Compensation ACE model page to review and analyze the altered scenario results.
Run the CPS scenario approval process to approve the altered scenario data . The process performs these functions:
Reloads the Data Mart with the new information.
Loads WA_CALC_TGT with the new information.
Note. You can limit access to the Alter Compensation Scenario component using PeopleTools security (permission list) so that only
certain users can alter scenarios, while the rest can still review and analyze scenarios within the Review Compensation ACE
Model component.
In addition to PeopleTools page security, you can strictly limit access to scenarios using scenario-level security.  This
means, if a user doesn't have security access for a given scenario, they cannot access it.  If you grant users access to a
scenario, they have access to all scenario data within that scenario approval page, so that they can view all the data they
are approving.  Therefore, for those operators you have granted such security, you may also want to grant them employee-level
security for all employees within their scenarios.  This allows them to review all the employees on other pages with employee-level
security, such as the inquiry pages.

 Pages Used to Alter Scenario Results with ACE
Pages Used to Alter Scenario Results with ACE
| Page Name | Object Name | Navigation | Usage | 
| Load Compensation ACE Model | RUN_WA_CP_BAM_LOAD | Workforce Analytics, Compensation Strategy, Load Compensation ACE Model | Load the results of a compensation scenario into an ACE model. | 
| Alter Compensation Scenario | WA_CP_ALTER_SCEN | Workforce Analytics, Compensation Strategy, Alter Compensation Scenario | Load the ACE model into an analytic (stateful) server to Review, analyze and alter the CPS scenario results.. | 
| Review Compensation ACE Model | WA_CP_VIEW_SCEN | Workforce Analytics, Compensation Strategy, Review Compensation ACE Model | Load the ACE model into an analytic (stateful) server to review and analyze the altered CPS scenario results. | 

 Loading the CPS Scenario Results into an ACE Model
Loading the CPS Scenario Results into an ACE Model
Access the Load Compensation ACE Model page.
On this page you define the parameters for loading CPS scenario results into an ACE model. The application engine process you run is (WA_CP_BAM_LD).
| Process Frequency | Set up a process run by selecting a Process Frequency and entering a Description. | 
| Analytic Model ID | Select a model from the prompt list values. | 
| Scenario ID | Select a Scenario ID from the prompt list values. Only non-approved scenarios can be selected. | 

 Altering the Scenario Results in the CPS ACE Model
Altering the Scenario Results in the CPS ACE Model
Access the Alter Compensation Scenario page.
The page looks like a worksheet containing the results of the selected CPS scenario, and it provides you with an interface to ACE. It enables you to review, analyze and alter your scenario data. The following is an example of a loaded ACE model page.
You can view and alter the scenario data using the following versions of the Alter Compensation Scenario page. Note that only non-approved scenarios can be selected in this component.
| Compensation Scenario | Use this page to view and alter the compensation scenario at the highest level, by Budget Plan or Compensation Rule, and Period. | 
| Eligibility Group | Use this page to view and alter the compensation scenario by Eligibility Group, | 
| Department | Use this page to view and alter the compensation scenario by Department, and Budget Plans within a Department. You can also see the department data by departmental roll-up totals, or for the one department only. Note that you can only select and review departments for which you are authorized and the departments that roll up to those departments. | 
| Employee | Use this page to view and alter the compensation scenario by Employee. You can see the employee data by departmental roll up, or for the one department only. You can also see simulated employees. Note that the employees listed are only those belonging to the selected department(s). You can only select and review employees which belong to departments for which you are authorized and the departments that roll up to those departments. To select individual employee you can drag the employee dimension to the slicer. | 
We won't show examples of each of the pages, or go into each of them in any detail, since the layout and use of these pages are so similar. Although the intersections of data, or dimensions, presented on each page are different, the basic page functions are the same. With these pages you can:
Review the compensation allocations in the scenario across a given set of dimensions.
Determine if the allocations are in alignment with your organization's compensation strategy and budgeting constraints.
Manipulate the scenario output at the department, group, employee and compensation rule level.
Each one of these page, in turn, is presented in two versions: by Budget Plan, and by Compensation Rule:
| Budget Plan | For base pay rules a budget plan is the roll up of values for like Action Reasons. For Variable pay rules a budget plan is the roll up of the values for like Variable Compensation Plan IDs. In this view the budget plan roll-ups are displayed, but not the breakdown of data for individual compensation rules. | 
| Compensation Rule | In this view the breakdown of data for individual compensation rules is displayed. | 
For each page, use the Go To link to toggle between two modes: Alter mode or View Only mode. In the View Only mode you can further slice the data by periods.
| Alter | In this mode the page view includes two columns near the center of the page which are active. Use these columns to select an Alter Method, and an Alter Amount or %. The fields in these columns are the ones you use to change the results of the scenario. | 
| View Only | In this mode the page view does not include any active columns or fields, and you cannot change the scenario results. | 
Using Page Functions
The ACE pages have three distinct sections: analysis action links, dimensions, and the grid.
| Save button | Recalculates the values on the grid and saves to the database. | 
To use an analysis action, click the appropriate link at the top of the page. To alter the data use the Alter Method and Alter Amount columns. To recalculate the data after you have made changes and to save to database, use the Save button.
When you are finished with your analysis, you can use the Unload and Return to Search link to unload the model from the analytic server. This is to free up memory, in consideration of the limited resources of the analytic server. All your saved entries will show in the grid the next time you load the model. Note that the model will time out and unload after one hour of inactivity.
The ACE grid allows you to drag and slice the data elements as needed for your analysis, thus allowing you to work with the data in different dimensions. You can drag any dimension from the row axis to the slicer bar or column axis, and you can drag cubes from the column axis to the slicer bar or row axis. You can also expand or collapse each dimension as well as change the order of the dimension. Please refer to the Enterprise PeopleTools PeopleBook: PeopleSoft Analytic Calculation Engine book for instructions.
Alter Version of the Compensation Scenario Page
You can alter the Employee Value, Employer Expense or the Allocated Stock Units by entering an amount or percentage in the Alter Method and Amount columns. After you enter your changes, click Save to recalculate.
The Current Altered Amount and Altered Stock Units will automatically reflect the result of this change. The system also prorates this change across all rows that roll up to this level.
Any changes to the Stock Units are reflected in the Employee Value column.
The Total Altered Expense and Total Altered Value reflect the aggregated results of all the changes you make in other pages when altering the data by different dimensions.
Note. The system does not allow you to alter a value of '0'. For example, if a row in the Stock Units column displays '0', you cannot
adjust it in the Alter Method and Amount columns.
All prorated amounts are rounded to the nearest cent and stock units are rounded to whole number. This may result in some
discrepancy between target amounts and total altered amounts, which is expected due to rounding and aggregation. 
 If multiple users are altering the same model simultaneously, they may override each other yielding unpredictable results
and error messages. In particular, the department and employee totals may be wrong. In this case, ignore the totals or re-select
the department. It is thus not recommended that multiple users access the same model simultaneously.
View Version of the Compensation Scenario Page
You cannot make alterations in this page which further slices the data by period. Here the system displays three variance columns to reflect the results of your changes in the Alter version of the page described above. These variance columns are: Expense Variance, Value Variance, Stock Units Variance. The variances indicate the difference between the original scenario budgeted amounts and your alterations.

 Reviewing the Compensation ACE Model
Reviewing the Compensation ACE Model
Access the Review Compensation ACE Model page.
You can use this page to view only the scenario data, but you may not alter it. You can view and analyze all scenarios for which you are authorized, including approved scenarios. You can also access these pages from the go to links in the alter Compensation Scenario component.
For a description of the page, its versions, and how to use it, please refer to the section above, 'Altering the Scenario Results in the CPS ACE Model.'

 Approving Compensation Planning Scenario Output
Approving Compensation Planning Scenario OutputOnce you have analyzed your scenario output, and made a decision that the scenario has the desired results, your next step is to approve the results.
In the Market Compensation and Base Pay Structure modules you approve the results of your scenarios by clicking buttons which initiate PeopleCode processes. In this module, approval is done using an application engine process (WA_CPS_APPRV). Due to the large number of rows of data that need to be moved to the target tables, it is more efficient to use application engine batch processing.

 Page Used to Approve Scenario Output
Page Used to Approve Scenario Output
| Page Name | Object Name | Navigation | Usage | 
| Compensation Scenario Approval | RUN_WA_CPS_APPROVE | Workforce Analytics, Compensation Strategy, Run Scenario Approval | Run the Compensation Scenario Approval (WA_CPS_APPRV) application engine process. | 

 Running the Compensation Scenario Approval Process
Running the Compensation Scenario Approval Process
Access the Compensation Scenario Approval page.
Specify the parameters for running the Compensation Scenario Approval (WA_CPS_APPRV) Application Engine process.
| SetID and Scenario ID | Approval for CPS scenarios is done by SetID and Scenario ID, and the prompt list values are from the WA_CP_APPROV_TBL table. All business units for a scenario are approved and published at the same time. This means you can only run the scenario approval process from this page. You cannot run the scenario approval process from the Performance Management Warehouse Run Jobstreams page. Note. In addition to PeopleTools page security, you can strictly limit access to scenarios for approval using scenario-level security. This means, if a user doesn't have security access for a given scenario, they cannot approve it. If you grant a user access to a scenario approval page and a scenario, they have access to all scenario data within that scenario approval page, to allow them to view all the data they are approving. Therefore, for those operators you have granted such security, you may also want to grant them employee-level security for all employees within their scenarios. This allows them to review all the employees on other pages with employee-level security, such as the inquiry pages. Note. Only non-approved scenarios can be selected for approval. | 
| Analytic Model ID | Select from the list which displays all the analytic models with altered scenario data for this scenario. Leave blank if you didn't use ACE to alter a scenario, or if you wish to approve the original scenario results. | 
Running the WA_CPS_APPRV Process
When you run the Compensation Scenario Approval application engine process (WA_CPS_APPRV) the system updates the scenario status to Approved. This prevents the Workforce Simulation (WA_WFS), Compensation Planning and Simulation (WA_CPS) processes from reprocessing the scenario.
Bringing Altered Scenario Data Back from ACE
When you have worked with an ACE model, and run the scenario approval process, the system performs these functions:
Reloads the CPS final output tables, including WA_CALC_TGT, with the new information from the ACE Model.
Reloads the CPS Scenario dimension (WFR_CPSC_DIM) so that the status is updated to Approved .
Reloads the CPS fact (WA_CPS_FACT). This will sync up the results in the Review Compensation Scenario component with the results from ACE
Note. Once you approve the scenario you cannot alter it through ACE again, but you can review it using the Review Compensation ACE Model and the Review Compensation Scenario components.