This chapter provides overviews of salary forecasting and technical details, lists common elements, and discusses how to:
Define periods.
Set up events.
Define scenarios.
Forecast compensation.
Purge scenario history.
View scenario history.
Use Salary Forecasting, a French-specific business process, as an analysis tool or as a forecasting tool. Either analyze the changes in compensation for a group of workers in past periods or simulate how hypothetical events occurring in the future will affect compensation. Because you can see how various events affect your compensation package, this business process is useful for human resources managers or executives wanting to build compensation budgets.
Salary Forecasting is compliant with the rules of the French Analysis Method for compensation variations, called La Masse Salariale. The analysis method that the business process employs enables you to calculate independently the effects of any compensation decisions for a group of workers for a future time period. The reports provided are also in accordance with La Masse Salariale.
The steps for using the Salary Forecasting business process are:
Set up your data.
Run the calculations.
Run and view the reports.
See Also
PeopleSoft HCM Reports: Selected Reports
If you use the Salary Forecasting business process for forecasting purposes, then set up events for modeling the future compensation.
If you use the business process for comparison of two past periods, then do not set up any events. Note that the calculation process ignores events defined in past periods.
Complete these steps to set up salary forecasting:
Define, one at a time, two like periods of time.
These time periods can be past, current, or future. Usually, you compare two equivalent periods of time, referred to as the reference and the analysis periods.
Associate the periods for comparison or forecasting.
Define groups, if they are not already created.
Define worker groups using the Group Build module. Each person defined in a group used in the Salary Forecasting business process must have, in his or her compensation package, rate codes attached to a rate code class. Use the rate codes without rate code class report to verify.
Define the various events that you want to apply to the worker groups whose compensation you want to analyze and forecast.
The events can be of various types, as described in the next section. You might also define additional setup data such as proration rules or specific hours rate.
Ensure all events for one scenario have the same elementary period.
(Optional) Define your proration rules.
(Optional) Define your rates for hours worked.
Group events into a scenario.
At the scenario level, define a set of events to apply to groups of workers for a given time period.
See Also
Understanding Technical Details
This section discusses technical details for:
Compensation effects.
Categorization of events.
The following topics describe the effects in La Masse Salariale method of analysis.
Any compensation measure that increases the level of compensation as of a certain date has a level effect. Any compensation increase of the elements of base pay has a level effect.
Any compensation increase, either an increase in base compensation or any type of variable compensation, has a mass effect. It affects the average compensation for the period and population being considered.
Considering any given period of time and any compensation measure that has a level effect, the sooner in the period the measure is applied, the greater the mass effect for that measure.
The carry over effect represents the effect on a given period of all the measures taken during the previous period. For any compensation measure that has a level effect, the later this measure is applied in a given time period, the bigger the carry over effect on the next time period.
Average Compensation for Employees in Place
The overall compensation for an organization could change between two consecutive periods for several reasons:
Compensation increases given to a subgroup or to the entire organization.
Seniority changes due to the overall aging of the population.
Hires and departures within the organization.
Moves within the organization that trigger changes in compensation, such as promotions.
Average compensation for employees in place (ACEP) is the average compensation for the subset of people within the organization during two consecutive time periods.
The headcount effect is the variance of the headcount multiplied by the variance of the average compensation.
The structure effect is the variance in the overall compensation due to internal moves within the organization.
The Noria effect is defined as the consequence of changes in compensation due to hiring and departures. Often, the salaries of the newly hired are below those of workers who have been at the same job longer. The Noria effect tracks the differences.
Overall Variance of Compensation Between Two Time Periods
The calculation is as follows:
ACEP variance + Headcount effect + Structure Effect + Noria Effect
All variances and effects are expressed in percentages (refer to Report LMS001).
All events are classified in predefined categories by the Forecast Compensation module calculation process. Those categories are the ones commonly used for La Masse Salariale analysis. The category codes and descriptions are delivered as system data.
This table displays La Masse Salariale categorization and the corresponding category codes that are used by the calculation process to map the events defined at the scenario level with the categories:
Category |
Category Code |
General Increases |
C20 |
General Increases given as a percentage |
C21 |
General Increases given as a Amount or Points changes |
C22 |
Measures by Category |
C30 |
Bonus |
C40 |
Regular Bonus |
C41 |
Exceptional Bonus |
C42 |
Individual Measures |
C50 |
Seniority |
C51 |
Shift-Technicality |
C52 |
Activity |
C53 |
The following matrix displays which events affect which categories.
Event |
Category/ Rate Code Class |
C 20 |
C 21 |
C 22 |
C 30 |
C 40 |
C 41 |
C 42 |
C 50 |
C 51 |
C 52 |
C 53 |
Leave |
|
N/A |
N/A |
N/A |
N/A |
N/A |
N/A |
N/A |
N/A |
N/A |
N/A |
N/A |
Promotion |
Base Pay |
|
|
|
|
|
|
|
* |
|
* |
|
|
Reg Bonus |
|
|
|
|
* |
* |
|
|
|
|
|
|
Seniority Bonus |
|
|
|
|
|
|
|
* |
* |
|
|
Salary Increase |
Base Pay |
* |
* |
* |
* |
|
|
|
* |
|
* |
|
|
Reg Bonus |
|
|
|
|
* |
* |
|
|
|
|
|
|
Seniority Bonus |
|
|
|
|
|
|
|
* |
* |
|
|
Seniority |
Seniority Bonus |
|
|
|
|
|
|
|
* |
* |
|
|
Working Schedule |
Base Pay |
|
|
|
|
|
|
|
* |
|
|
* |
|
Reg Bonus |
|
|
|
|
* |
* |
|
|
|
|
|
|
Seniority Bonus |
|
|
|
|
|
|
|
* |
* |
|
|
Entry |
|
N/A |
N/A |
N/A |
N/A |
N/A |
N/A |
N/A |
N/A |
N/A |
N/A |
N/A |
Incentive |
N/A |
|
|
|
|
* |
|
* |
|
|
|
|
Period Types |
Four period types define the periods of comparison:
|
Periods or Periods of Comparison |
Periods, or periods of comparison, are the periods being compared. Use salary forecasting in two ways: to analyze two past periods or to forecast a future period, using the current period as a base. |
Reference Period |
For forecasting, this period is likely to contain the current date. For comparing past periods, use any period as a basis for comparison |
Analysis Period |
For forecasting, this is a future period contiguous with the reference period. For comparing past periods, this period must be contiguous with and prior to the reference period. |
Type of Elementary Period |
How often the module processes its calculations. These elementary period types coincide with your possible payroll dates:
Suppose that you select Year as the period type and semi-monthly as the elementary period type. The module makes 24 calculations. If you select Monthly as the elementary period type, the module makes 12 calculations. Select the elementary period type when you define events. |
The monthly or semi-monthly segments of a comparison period. Whether the segments are monthly or semi-monthly is determined by the selected elementary period type.
The process manages the current elementary period exactly the same way it manages any past elementary period. The process manages future elementary periods by copying the data calculated for the current elementary period. |
|
The date the event is to occur (or trigger) within the analysis period. |
|
Working Periods |
The two periods (always one analysis and one reference) that you associate for either comparing or forecasting. They are defined by a Working Period ID. These rules apply to the two periods associated as working periods:
When using the Salary Forecasting module to analyze the future, use the present as the reference period. This rule is true for all period types: analyze this year against next year, this month against next month, and so on. |
Working Periods ID |
A value that must be the same for all events in a scenario. |
Event ID |
Identifies a compensation event in the system. You enter one for each event that you define. |
Event Type |
Select one of the following: Headcount Increase, Headcount Decrease, Compensation Increase, Promotion, Seniority Increase, Incentives, and Working Schedule. |
To set up periods, use the Period Setup panel (LMS_PERIOD_PNLGP_GBL) and Working period setup panel (LMS_WRK_PD_PNLGP_GBL) components.
This section discusses how to associate contiguous working periods.
Page Name |
Definition Name |
Navigation |
Usage |
LMS_PERIOD_DEFN |
Set Up HRMS, Product Related, Compensation, Forecast Compensation FRA, Period Setup panel, Period Setup panel |
Define the time periods to compare and analyze compensation. Each time period is a Time Period ID. |
|
LMS_WRK_PD_DEFN |
Set Up HRMS, Product Related, Compensation, Forecast Compensation FRA, Working period setup panel, Working Periods |
Associate two contiguous time periods. If you analyze two past periods, do not include the current period. If you forecast for the future, the reference period is the current period. |
Access the Working Periods page (Set Up HRMS, Product Related, Compensation, Forecast Compensation FRA, Working period setup panel, Working Periods).
Reference Period |
For forecasting, select the current period—Month, Quarter, Semester or Year—depending on what period type you selected on the Period Setup panel page. For comparing past periods, select any past period. |
Analysis Period |
For forecasting, this value must be a future period contiguous with the reference period, and of the proper length for the period type. For comparing past periods, select any past period contiguous with the reference period. The system ensures that the reference and analysis periods do not overlap, that they are contiguous, and that they are of the same type. |
To set up events, use the Headcount increase setup panel (LMS_ENTRIES_EVENT_GBL), Incentive event setup panel (LMS_INCENT_EVENT_GBL), Salary Increase event setup (LMS_INCREASE_EVENT_GBL), Headcount decrease event setup (LMS_LEAVES_EVENT_GBL), Promotion event setup panel (LMS_PROMO_EVENT_GBL), Seniority Setup panel (LMS_SENIOR_EVENT_GBL), Working Schedule event setup (LMS_SCHEDULE_EVENT_GBL), Proration setup panel (LMS_PRORATION_GBL), and Hours rate setup panel (LMS_HOURS_RATE_GBL) components.
An event is an action (or a set of actions) applied to a group of workers. Events are the building blocks of your scenarios. You define and reuse events in many scenarios as long as the scenarios apply to the same set of time periods. This section discusses how to:
Simulate a headcount increase.
Add workers to any group (by job code or position) to simulate hiring or to study the effects of proposed organizational changes.
Simulate future awards.
This simulation enables you to see the effect of awarding a lump sum amount at a specific point in time. The incentive event is simplistic here because the Variable Compensation module offers a more complex simulation. The Variable Compensation module enables you to perform different scenarios to determine the maximum, target, and minimum awards for a group of workers based on a given plan of specific business rules.
Simulate a compensation increase event.
Simulate a headcount decrease.
Simulate a promotion.
A promotion is defined as a move from one Job Code to another Job Code.
Simulate seniority.
This simulation shows the effect of seniority increases.
Define a working schedule.
A working schedules event determines the effect of changing the working schedule for a group of workers.
Define proration rules.
Define hours rates.
See Also
Understanding Variable Compensation
Page Name |
Definition Name |
Navigation |
Usage |
LMS_ENTRIES |
|
Define a Headcount Increase event. |
|
LMS_ENTRIES_SEC |
Click Simulation Parameters link on the Headcount Increases page |
Define additional parameters if the selected job code or position has compensation packages containing pay components expressed either in points or in a weekly frequency. Define the standard hours per standard work period or the points value and currency required by the calculation process for correctly handling the conversion of those pay components. |
|
LMS_INCENTIVES |
|
Set up a future award for a group. |
|
LMS_INCREASE |
|
Define a compensation increase event. |
|
LMS_LEAVES |
|
Define a headcount decrease event. |
|
LMS_PROMOTION |
|
Simulate promotions for all people in a group. |
|
LMS_SENIORITY |
|
Define a seniority event. |
|
LMS_WRK_SCHEDULE |
|
Define work weeks for the calculations. |
|
LMS_PRORATION |
Set Up HRMS, Product Related, Compensation, Forecast Compensation FRA, Proration setup panel, Proration setup panel |
Define the proration schemes. |
|
LMS_HOURS_RATE |
Set Up HRMS, Product Related, Compensation, Forecast Compensation FRA, Hours rate setup panel, Hours rate setup panel |
Define the overtime rates used for simulating the working schedules event. Use this page only for the Salary Forecasting calculation process. |
Access the Headcount Increases page (Set Up HRMS, Product Related, Compensation, Forecast Compensation FRA, Headcount increase setup panel, Headcount Increases).
Headcount Increase Type |
Select how you want the calculations to consider the increase: Avg Amnt (average amount): When you select Avg Amnt, these fields appear: Average Amount, Currency, Frequency. Enter a free compensation amount, which is multiplied by the number of people selected. Use this type of headcount increase to perform an estimated simulation. JobCode: Select this option and the SetID and Forecasted Job fields appear. Use this option to add many people with the same job code. The calculation uses the compensation package defined for the specified job code and multiplies it by the number of people selected for the simulation. Note. Only those job codes that are not associated with a matrix are available. Position: Select this option and the Forecasted Positions field appears. The calculation uses the compensation package defined for the job code associated with the specified position and multiplies it by the number of people selected for the simulation. |
Structure Effect |
Refer to the Understanding Technical Details topic for the definition of the structure effect. To measure the structure effect, assign your headcount increase to a group. |
Number of People |
Enter the number that represents the headcount increase. |
Simulation Parameters |
Click to enter additional simulation parameters for the calculation process. |
Average Amount |
When Headcount Increase Type is Avg Amnt, specify the average amount of the salaries for all people added, based on the frequency specified. For example, five new people get 5000.00 EUR (1000.00 EUR each) every other week, so the frequency is bi-weekly. You would enter 1000 in the Avg Amnt field. |
Currency |
When Headcount Increase Type is Avg Amnt, select the currency that the calculation process uses. |
Frequency |
When Headcount Increase Type is Avg Amnt, specify how often the new people are to be paid. During the calculation process, the frequency is converted to match the elementary period type. For example, the elementary period type is monthly, and you enter five new people who get 1000.00 EUR weekly. The system calculates 5000.00 EUR weekly, and then converts it to a monthly frequency using the frequency annualization factor. The monthly figure is 20000.00 EUR. The calculation process adds 20000.00 EUR every month, starting with the triggering period defined for this event. Frequency values come from the Frequency table. |
SetID |
When Headcount Increase Type is JobCode, specify the setID for the job code for the new hires. These values come from the SetID table. |
Forecasted Job |
When Headcount Increase Type is JobCode, specify a forecasted job for the new hires. Each job code must have its own event. These values come from the Job Code table. |
Forecasted Positions |
When Headcount Increase Type is Position, specify a forecasted position for the new hires. |
Access the Incentives page (Set Up HRMS, Product Related, Compensation, Forecast Compensation FRA, Incentive event setup panel, Incentives).
Number of People |
Enter the number of people who receive a lump sum incentive award. |
Average Amount |
Enter the average amount each person is to receive. For example, if you select 5 for the number of people and 500 for the average amount, the calculation adds 5 times 500.00 EUR, or 2500.00 EUR, to the triggering period. |
Structure Effect |
Enter the Group ID to receive this award. Refer to the Understanding Technical Details topic for information about the structure effect. |
Access the Compensation Increases page (Set Up HRMS, Product Related, Compensation, Forecast Compensation FRA, Salary Increase event setup, Compensation Increases).
Individual Measure |
Select if the increase is an individual measure. This check box relates to La Masse Salariale method of analysis. It classifies compensation increases into three categories: general increases (applies to the overall simulated population); increases by category (a category being a subset of the overall simulated population); and individual measure (the compensation increase is an increase for an individual). To simulate general increases, deselect this check box. |
Compensation Increase Rate Codes |
Define the rate codes to be increased. All people in a group with a compensation package containing specified compensation rate codes receive the increase that is specified on this page as of the triggering period of this event. Select the way to change a person's compensation for a given rate code from these choices: Percent Amount, Change Amount, Change Percent, Change Points, Percent of Points, Currency, and Rate Code Class. Specify any components of pay and any increases. Depending on the component type, fill in the fields as follows. (Fields not related to certain component types are unavailable for selection.) If the component type is flat amount or hourly, enter either a Percent Amount or a Change Amount. If the component type is percentage, enter only a Change Percent. If the component type is points, enter either a Percent of Points or a Change Points. |
Access the Headcount Decreases page (Set Up HRMS, Product Related, Compensation, Forecast Compensation FRA, Headcount decrease event setup, Headcount Decreases).
Description |
Enter a description of the headcount decrease event. Specify the group to which this event applies on the Scenario Definition page. For example, if five workers retire as of the date specified by the triggering period, create a group that includes those five workers. At the scenario level, attach this group to the headcount decrease event. |
Access the Promotions page (Set Up HRMS, Product Related, Compensation, Forecast Compensation FRA, Promotion event setup panel, Promotions).
From |
Enter values in the SetID and Job Code fields for a group's current position. |
To |
Enter values in the SetID and Job Code fields for a group's promoted position. |
Access the Seniority page (Set Up HRMS, Product Related, Compensation, Forecast Compensation FRA, Seniority Setup panel, Seniority).
Seniority Calculation Freq (seniority calculation frequency) |
Enter either Monthly or Semimonthly for seniority pay. At the event level, define the frequency of seniority calculation; that is, how often seniority is evaluated. |
Access the Working Schedule page (Set Up HRMS, Product Related, Compensation, Forecast Compensation FRA, Working Schedule event setup, Working Schedule).
Standard Hours |
Enter the number of standard hours per frequency period. For example, 35 hours is standard hours for a weekly frequency. To simulate the effect of a group of people moving from 39 to 35 hours, enter the target frequency (35 hours a week) in this field. The group of people that will change its working schedule is defined at the scenario level. |
Frequency |
Enter the frequency of the standard hours that you select. |
Access the Proration setup panel page (Set Up HRMS, Product Related, Compensation, Forecast Compensation FRA, Proration setup panel, Proration setup panel).
Time Period ID |
The system displays the Time Period ID that you entered. |
Period Type |
The system displays a period type of either Monthly or Semi-Monthly. |
Type of Elementary Period |
Depending on the combination of period type and type of elementary period that you selected, the system displays fields that enable you to rate how to pay per elementary period. |
12 Months |
Select to weigh each month equally. |
13 Months |
Select to weigh one month out of a year twice. |
14 Months |
Select to weigh one month out of a year three times. |
15 Months |
Select to weigh one month out of a year four times. The system calculates all the ratios, but you can modify them. For instance, if you select 13 Months, you could weight December twice (default calculation) or half-weight June and December. In this case, you would overwrite the default ratios. |
Access the Hours rate setup panel page (Set Up HRMS, Product Related, Compensation, Forecast Compensation FRA, Hours rate setup panel, Hours rate setup panel).
Hours Rate Effective Date |
Enter the date these rates are effective. |
Sequence |
These numbers represent the sequence of counting hours. They are automatically generated. |
From and To |
Enter the first and last number in the range of hours. The first sequence must begin with 0. |
Frequency |
Enter the valid frequency for this range of hours. |
Rate (%) |
Enter the percentage rate for each sequence. |
To define scenarios, use the Scenario setup panel (LMS_SCENARIO_GBL) component.
This section discusses how to:
Associate events with a scenario.
Assess the structure effect.
Page Name |
Definition Name |
Navigation |
Usage |
LMS_SCENARIO |
|
Define scenarios. You associate a working periods ID with a group and a set of events. |
|
LMS_SCENAR_CTG |
|
Define the groups used to assess the structure effect. |
Access the Scenario Definition page (Set Up HRMS, Product Related, Compensation, Forecast Compensation FRA, Scenario setup panel, Scenario Definition).
Group ID |
Enter a value for this scenario. The group could be your whole organization. For calculation performance reasons, create a smaller group that represents your organization in compensation terms or create a group from a certain department. |
Working Periods ID |
When you select a working periods ID and press TAB to move out of the field, the system displays all events applicable for that working periods ID. For certain events, you can limit the population for the event by selecting a Group ID. Note that Scenario KFSCEN01 applies to all the workers in Group ID KF0006. |
Scenario Events |
All the events defined for this working period ID appear. Each event is listed by Event ID, Triggering Period, and Description. To include the events in calculations, select the corresponding check box. Click the Detail link to go to the Event Definition page to make adjustments to an event. Click the Def. link to go to the Group Definition page and modify a group. Use the Group ID fields to restrict an event to a subset of the group that is defined in the previous Group ID field. Restrict the population for the following types of events: headcount decrease, promotion, seniority, working schedule. The headcount increase and incentives events do not need a subgroup. |
Note. For a compensation increase event, the population to consider is all the workers from the main group (the one defined in the Group ID field at the scenario level) who have, in their compensation package, the compensation rate codes defined in the event.
Access the Structure Effect page (Set Up HRMS, Product Related, Compensation, Forecast Compensation FRA, Scenario setup panel, Structure Effect).
Scenario Structure Effect Groups |
Define a subgroup of your overall population, which you defined in the first Group ID field on the Scenario Definition page. Enter groups forming a subset of your overall population. Ensure that the groups do not overlap and that the sum of their populations exactly equals the overall population. For example, organization ABC has several categories of workers: executives, managers, and workers. You want to study how the compensation is changing due to the movement of people from one category to another. The Salary Forecasting module calculates it automatically: Define your overall organization as being all workers in ABC. Then, define three groups to enter on the Scenario Structure Effect page: Group 1 is all executives from ABC, Group 2 is all managers from ABC, and Group 3 is all workers from ABC. Groups 1, 2, 3 do not overlap, and their sum equals the overall population of organization ABC. |
See Also
Technical Details: Compensation Effects
This section provides an overview of compensation forecasting and discusses how to:
Forecast compensation
Run a compensation simulation
Run the Scenario Comparison report
The calculation process divides both the reference period and the analysis period into sections by considering the elementary period type. For each elementary period, the process extracts from the HR database the base compensation (from the PS_COMPENSATION table) and the variable compensation (from PS_VC_AWARDS) for all the workers in the group specified at the scenario level. It also calculates the average headcount and full-time equivalents (FTEs) for each elementary period to create average compensation amounts.
This calculation process considers all the events defined for future elementary periods and calculates forecasted compensation. Any event defined for past or current elementary periods is not considered because data exists for those periods of time in the HR database.
The forecasted compensation amounts are stored in salary forecasting tables so that you can compare the results of several scenarios. Remember that the salary forecasting process does not update core HR transaction tables.
Page Name |
Definition Name |
Navigation |
Usage |
LMS_RUN_CNTL_PNL |
Compensation, Forecast Compensation FRA, Process Forecast, Forecast Compensation, Forecast Compensation |
Initiate compensation forecasting based on specified criteria. |
|
RUNCTL_LMS_REPORT |
Compensation, Forecast Compensation FRA, Process Forecast, Forecasted Compensation Rpt, Forecasted Compensation Rpt |
Report on compensation scenarios. |
|
RUNCTL_LMS_REPORT |
Compensation, Forecast Compensation FRA, Process Forecast, Scenario Comparison Rpt, Scenario Comparison Rpt |
Define forecasted compensation and compare scenarios. |
|
RUNCTL_LMS_RATE_CL |
Compensation, Forecast Compensation FRA, Process Forecast, Rate Codes w/out Class Rpt, Rate Codes w/out Class Rpt |
Report on rate codes that do not have a rate code class attached to them. |
Access the Forecast Compensation page (Compensation, Forecast Compensation FRA, Process Forecast, Forecast Compensation, Forecast Compensation).
Scenario ID |
Select a scenario ID. |
Scenario Definition |
Click to go to the Scenario Definition page of the selected scenario ID. |
Fixed Exchange Rate |
Select if this currency has a fixed exchange rate. |
Re-Extraction |
Select if this process is re-extracting the base compensation from the Human Resource database. |
Structure Effect |
Select if the variance in the overall compensation is due to internal moves within the organization. |
Rate Type |
Select a compensation rate type. |
Carry-Over Factor |
The carry over effect represents the impact on a given period of all the measures taken during the previous period. Indicate what will be carried over to the next period. |
Access the Forecasted Compensation Rpt page (Compensation, Forecast Compensation FRA, Process Forecast, Forecasted Compensation Rpt, Forecasted Compensation Rpt).
Select a User ID and a Run Control ID, then click the Refresh button. Refreshing populates the Scenario History Report group box. Select the check box for the Scenario ID you want to report on and click Run.
See Also
Technical Details: Compensation Effects
Access the Scenario Comparison Rpt page (Compensation, Forecast Compensation FRA, Process Forecast, Scenario Comparison Rpt, Scenario Comparison Rpt).
Scenario Filter |
This group box enables you to narrow the choice of scenarios to report by User ID and Run Control ID. |
|
Click to display scenarios that meet the scenario filter requirements. |
Scenario History Report |
This group box displays all scenarios that meet the scenario filter requirements. Scenarios are listed by Scenario ID, Scenario Run DateTime, User ID, Run Control ID, and Description. To run one scenario at a time, select its check box. |
All the results from of the calculation of any scenario are stored in the database. Define several scenarios with different sets of events, run the calculation for all scenarios, and compare the results. Then, select the scenario that best mirrors your compensation policy. You may then purge from the database the results of some scenario calculations you are not going to use. When you purge scenario history, the calculation results are purged but not the scenario definition.
Page Name |
Definition Name |
Navigation |
Usage |
RUNCTL_LMS_PURGE |
Compensation, Forecast Compensation FRA, Process Forecast, Purge Scenario History |
Run the Application Engine process HR_LMSPURGE to delete the results of all the selected scenario calculation runs. |
Access the Purge Scenario History page (Compensation, Forecast Compensation FRA, Process Forecast, Purge Scenario History).
Scenario Filter |
This group box identifies the User ID and Run Control IDs by which to search. To search all histories, click the lightning icon. |
Scenario History Purge |
Chose a scenario to purge by selecting the Purge check box. Note that only the results of the scenario calculation are purged; the scenario definition remains in the database. Information appears in all fields here. |
Click Run to run this request. PeopleSoft Process Scheduler runs the Purge Scenario History process at user-defined intervals.
Perform forecasting activities in two ways:
Define different scenario IDs, attach a different set of events to them, and run the calculation process for each scenario ID.
Define only one scenario ID and change the events associated with this scenario ID each time that you process a new calculation.
Use the Scenario History pages to find which events were used for any scenario calculation. Modify and calculate a scenario repeatedly without recalling the events that were used in each calculation.
Page Name |
Definition Name |
Navigation |
Usage |
LMS_SCENAR_HISTORY |
Compensation, Forecast Compensation FRA, Process Forecast, Review Scenario History |
Inquire about the process history of scenarios. |
|
LMS_SCENARHIST_SEC |
Click Information on the Scenario History page. |
View the run control parameters and events for any calculation. |