Skip to Content

PEP Configuration

The purpose of this document is to provide information on maintaining the different configurations essential for running PEP projections.  Missing configuration can cause PEP executions to fail or not launch at all. There are global PEP configurations and underlying configurations specific to Fiscal Period PEP and Pay Period PEP described below.

1. Global PEP Configuration

These configurations are in effect for all types of PEP projections

1.1. Maintain Fiscal Year Variant Configuration

  • The fiscal year variant is needed for many applications in PBF. It defines the number of periods and period date ranges for the fiscal year.
  • It is required for Fiscal Period PEP and Pay Period PEP
  • Use transaction SPRO to maintain Customizing data. The following menu path will take you to the correct IMG node:


Path:

SAP Customizing Implementation Guide g SAP Net Weaver g Business Intelligence g General BI Settings g Maintain fiscal year variant.

PBF Requirements:

  • There can be only one fiscal year variant defined for PBF.
  • It must not be calendar based.
  • It must have 12 fiscal periods defined.
  • Each fiscal period must be limited to the calendar dates for a month.

Sample entry:

1.2. Maintain PBF Global Configuration

The PBF Global table contains a single table entry to define default parameters that are used by the PEP.

Other references:

  • Use transaction /PBFBI/START_PBF_IMG
  • Use transaction SPRO to maintain Customizing data with the following menu:

Path:

SAP Customizing Implementation Guide->Public Budget Formulations (PBF)->Maintain PBF Global Settings

Sample entry:

Important usages by PEP:

  • Fiscal Year Variant: Fiscal year variant to be used by PBF processes. Fiscal year variant defines the number of fiscal periods and related calendar dates for each fiscal period.
  • Country Grouping: Default country ID which is used in conjunction with salary and benefits
  • Currency: Default currency for calculations. Currency details can also come from other sources, such as the Financial Management (FM) area, Position and Employee Master data
  • Employment Status: The InfoObject Employment Status contains configurable employment statuses, such as Active, Inactive, Retired, etc. The Employment Status that is set in the /PBFBI/GLOBALS table defines which status is considered the Active status. It is used during PEP projections to include those employees and positions that have the Active status
  • PEP Curr Conv Type: The currency conversion type that will be used by PEP calculations
  • Apply Rounding: This indicator is read during PEP calculations to determine if rounding of results should be performed or not.


1.3. Parallel Processing Configuration

The Parallel Process configuration is required to execute all types of PEP projections. The number of Parallel Processes and the Block Size maintained in this PBF configuration has an influence the performance of the DTP processes utilized by all PEP executions. The optimal setting is highly dependent on various aspects of landscape configurations.  Package Size defines the total number of Employees/Positions to be executed in each Work Process. It’s so crucial to set the package size to optimize the performance of PEP calculation.

It’s advised to set the Package Size in such a way that the total number of resultant records generated out of each work process shouldn’t exceed 100000 (1 Lakh).

Example:
The formula to calculate the number of records that PEP will generate is:

  • Total no of Calculated records = ( number of employee + number of positions) * average no of benefits per employee / position * average no of allocation * projection duration in fiscal period.
  • Number of Employees is 10000, Positions are 10000, and projection duration of  2 years and average number of 9 benefits considered for this scenario.

Data volume in the /PBFBI/PROJ_1 is 1,300,550 and in the /PBFBI/PROJ_2 is 17,800,221

In this example, we are assuming that there are 9 benefits and no allocations and the duration is 2 years. Hence it should be 100000/(10*24) ~ 400. Any packet size less than 400 will give the optimal results but it is advised to maintain minimum packet size of 50.

See Performance Tips for Data Transfer Service for more information on determining the optimal settings of these parameters It can be configured via the path:

SPRO->SAP Reference IMG->Public Budget Formulation (PBF)->Projection Calculation Configuration->Click on Parallelization of Projection Processing

1.4. PBF Projection Type Configuration

Projection type configuration is required to execute PEP Projections and for use when calculating positions  in the Budget Form Position tab. Parameters are maintained for the maximum start and end Fiscal Period / Fiscal Years for the projections and default settings for vacant selection, allocation calculation, Projection Re-runs capability and Skip Accumulator. This data is used to define certain aspects and defaults for the projections when a user runs projections.

Below is an example of the configuration settings:

  • Projection type:
    • BASE : This projection type refers to the base projection which contains the costs for all employees and positions maintained in the master data.
    • BUDG : This projection type refers to projections that are executed through the budget form, on the Position tab. This type of projection will calculate costs for decision package positions which are not yet active positions.
    • PROJ : This projection type refers to projections that are executed through the Projection Parameter screen. This allows new projections to be created that will reference the base projection but allow overrides to salaries and benefits.
  • Start Date : This is the earliest possible starting fiscal period / year for the projection calculations.
  • End Date : This is the latest possible ending fiscal period / year for the projection calculations
  • Vacant Selection : The projection will use this default to determine if open positions, filled positions or both are to be included in the projection.
  • Allocation : The projection will use this default to determine if the projection should be split out into the employee / position allocation amounts or not.
  • Proj ReRun flag : This flag determines if a Fiscal Period Projection can be RE-Run or not i.e. if the same projection can be run again or not. If this flag is set, then we can re-run a fiscal period projection.
    Note: This flag affects only fiscal period projection. It does not affect a Pay Period Projection. A Pay Period Projection cannot be Re-Run.
  • Skip Accum flag :  This flag determines if the accumulator records (generated during PEP Calculations) are to be stored in the employee/position DSO or not. If this flag is set, then the accumulator records are not inserted in the respective DSO thereby, saving memory. Therefore, if accumulator details are not required, this flag can be set.

2. Fiscal Period PEP Configuration

These configurations apply only to Fiscal Period PEP projections.

2.1. Process Chain Configuration - Fiscal Period PEP

The configuration provides the process chain ID, the InfoProvider name and the Employee and Position Monthwise DSO names. 

Path:

SPRO->SAP Reference IMG->Public Budget Formulation (PBF)->Projection Calculation Configuration->Process Chain Configuration->Click on Process Chain Configuration

In order to execute Fiscal Period PEP projections the following three process chains need to be configured.

Process Chain (ID)

InfoProvider

Position Monthwise DSO

Employee Monthwise DSO

What-if

/PBFBI/PEP_PC0400_01

/PBFBI/PROJ_1

/PBFBI/HRPAO08

/PBFBI/HRPAO07

/PBFBI/PEP_PC0400_02

/PBFBI/PROJ_2

/PBFBI/HRPAO10

/PBFBI/HRPAO09

/PBFBI/PEP_PC0500_01

/PBFBI/RBPSP01

/PBFBI/RBPSP01

/PBFBI/RBPSE01

X

3. Pay Period PEP Configuration

In PBF 8.1 Release, other configurations have been added which are Pay Period projection specific. Therefore, to execute a successful Pay Period projection, following configurations and settings are to be properly maintained along with the global configurations mentioned above.

3.1. Pay Period Types

The Pay Period types can be stored automatically by running /PBFBI/PAY_PRD_D and the master data stored in /PBFBI/PAY_TYP info object.

Path:

SPRO->SAP Reference IMG->Public Budget Formulation (PBF)->Projection Calculation Configuration->PEP Flexible Pay Period Configuration->Click on Maintain Pay Period Types.

The pay period types listed above are supported by PBF. The Min Pay Periods and Max Pay Period values are used by the Pay Period Upload program to validate the data to be uploaded.

3.2. Upload Pay Periods

The Pay Periods should be uploaded for different Pay Period types and these periods must be loaded through a CSV file.

Path:

SPRO->SAP Reference IMG->Public Budget Formulation (PBF)->Projection Calculation Configuration->PEP Flexible Pay Period Configuration->Click on Upload Pay Period Table from file.

Notes:

  • For more information on the program or the expected file format press the blue Info icon next to the Execute button.
  • The check box (Test Only (NO Table Updates)) is checked by default. It is recommended to execute the program with this flag on to get a list of any errors with the file which will need to be corrected. Once the test execution is error free then uncheck Test Only check box and execute the program again.. Now the Pay Periods should be stored in the /PBFBI/PAY_PRD table.

The Pay Period table contents can be displayed by executing IMG node Display Pay Period Table entries.

Path:
SPRO->
SAP Reference IMG->Public Budget Formulation (PBF)->Projection Calculation Configuration->PEP Flexible Pay Period Configuration                  ->Display Pay Period Table Entries

The image below shows an example of Bi-Weekly pay period entries for a year in which there are 27 pay periods.

3.3. Alternate Source Configuration

PBF 8.1 provides an option for users to assign DSOs (Direct update or Standard DSOs) as a source of master data for Employees and/or Positions. This configuration is optional and only needed if users wish to use master data other than the Employee and Position InfoObject master data. The pre-requisite with this option is that users will have to load the desired Employee and Position master data into DSOs and create the queries exactly similar to the PBF delivered queries on the source DSO.

PBF Delivered Queries for Employee and Position:

  • Employee: /PBFBI/PPRDEMP(DSO)    /PBFBI/DSO_I02_Q0001(Query)
  • Position:   /PBFBI/PPRDPOS(DSO)     /PBFBI/DSO_I01_Q0001(Query)

Once the DSO data and the queries are in place they need to be configured as a PEP source ID. When users execute Pay Period projections they can then choose the PEP source ID from the list of configured PEP sources.

Path:

SPRO->SAP Reference IMG->Public Budget Formulation (PBF)->Projection Calculation Configuration->Click on Maintain Master Data DSO for Employee and Position

3.4. Process Chain Configuration- Pay Period PEP

In Pay Period PEP two process chains need to be configured.

  • /PBFBI/PPRD_PROJ_S01 : Pay Period Projection
  • /PBFBI/PPRD_AB : Attrition and Backfill Projection

Path:

SPRO->SAP Reference IMGàPublic Budget Formulation (PBF)->Projection Calculation Configuration->Process Chain Configuration->Click on Maintain Pay Period  Process Chains

In PBF 8.1 release, a parallel chain- /PBFBI/PPRD_PROJ_01 is also provided for running Pay Period Projection. However, it can be used only if the system can support the required number of work processes.

Please, refer to the FAQ Document for detailed information.

   PEP FAQ

3.5. PBF 8.1 High Volume Framework

The High Volume Projection Kit configured with multiple DSOs (3 DSO’s for Employee +3 DSO’s for Positions) can be introduced to distribute the load and to improve the DSO Insert and the DTP performance. To further increase the performance, we can introduce same number of InfoCubes (3 InfoCubes) to capture the result. Multiprovider /PBFBI/PPRD_M1 can be created to combine the results.

The calculated data is stored in a set of 6 DSO’s and 3 Cubes (configurable). The transfer of data from the DSO to the Cube is done through DTP’s (Data Transfer Process).

The difference between the 2 chains delivered is that one chain executes the DTP’s for the 3 DSO’s sequentially and the other executes it in parallel.

The process chain with parallel work process is to be used only if the required number of background work processes is supported in the system. Otherwise, the process chain with sequential DTP’s should be used.

For example, if there are 3 DTP’s, a minimum of 9 background work processes are required for it to allow parallel processing since each DTP needs 3 work process for the best performance. Similarly, for more number of DTP’s , i.e. more number of DSO’s and Cubes configured, the number of background work processes required will also change. Therefore, if the required number of work processes is not available, sequential process chain has to be used.

The High Volume Projection Kit can be configured in SPRO in BW and the steps as follows.

SPRO->SAP Reference IMG->Public Budget Formulation (PBF)->Projection Calculation Configuration->Process Chain Configuration->Maintain Pay Period Process Chains

  • Pay Period Projection Scenario Sequential : /PBFBI/PPRD_PROJ_S01
  • Pay Period Projection Scenario (Parallel) : /PBFBI/PPRD_PROJ_01

4. PEP configuration check program

To check the basic configurations required to run a successful PEP Projection, a report program has been developed. This report will check the following configurations:

  • The Global settings required for PEP
  • Parallel Processing Configuration
  • Process chain configuration for both- Fiscal PEP and Pay Period PEP (checks whether the respective chains are maintained or not).
  • Pay Type Maintenance for Pay Period PEP (checks for at least one entry in the pay type table)
  • Pay Calendar Maintenance for Pay Period PEP (checks for at least one entry in the pay calendar table)
  • Projection Type configuration required for PEP

To know whether the minimal configuration required for a successful PEP Projections are properly maintained or not, this report can be executed. However, this report will only check the very basic configurations.

Tags:
Former Member

No comments