SAP Budgeting and Planning For Public Sector

USER GUIDE | INTERNAL
Document Version: 1.0 – 2020-06-12
SAP Budgeting and Planning for Public Sector

© 2020 SAP SE or an SAP affiliate company. All rights reserved.
THE BEST RUN

Content
1 SAP Budgeting and Planning for Public Sector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2 What's New. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3 Excel Add-In. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.1 Connecting to Budgeting and Planning for Public Sector via Excel. . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.2 Creating Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.3 Using Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.4 Excel Add-In Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4 Budget Formulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.1 Budget Form. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Copy Button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Download Button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Advance Stage Button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Delete Button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Recent Objects Button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Universal Worklist: Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Budget Form Template: Technical Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Copy Form Feature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Budget Form Download. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Budget Form Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Deleting Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Reallocations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.2 Resource Planning Form. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.3 Ranking Form. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
Federal Ranking Form. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
4.4 Planning Form. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
5 Budget Development. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
5.1 Base Budget Adjustment Form. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
5.2 Capital. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Capital Form. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Capital Ranking Form. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
5.3 Decision Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Decision Package Adjustment Form. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
Decision Package Ranking Form. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
5.4 Multi-year Projection Form. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

2 INTERNAL Content
5.5 Revenue Projection Form. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
5.6 Roll-Over Process/Year-Begin Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
5.7 Transfer and Re-Distribution Form. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
6 Personnel Expenditure Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

6.1 Running Fiscal Period PEP Scenario Calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
6.2 Running a What-if Scenario Calculation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
6.3 Running a Pay Period PEP Projection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
6.4 Running an Attrition and Backfill Projection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
6.5 Deleting Projection Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
7 Additional Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106

7.1 Dictionary Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
7.2 Application Help Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
8 SAP Budgeting and Planning for Public Sector Administration. . . . . . . . . . . . . . . . . . . . . . . . 109

8.1 Maintaining BI Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
8.2 Non-FM Master Data Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
8.3 Budget Form Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Creating a Comment Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Creating a Comment Type Tree. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Creating a Combo Edit Rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Defining Form Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117
Maintaining Stages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Stage Advancer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Form Mass Soft Deletion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Manage Deleted Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Workflow Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
8.4 Personnel Expenditure Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Job Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Position Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Employee Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Employee and Position Comparison. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Creating Pay Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Creating Projection Distributions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Maintaining Benefit Rates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Maintaining Benefit Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
PEP Attrition and Backfill Projections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Business Add-in (BAdI) for Attrition and Backfill (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . 160
9 Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
10 Portal Content for SAP Budgeting and Planning for Public Sector. . . . . . . . . . . . . . . . . . . . . 162

Content INTERNAL 3
10.1 Budget Formulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162
Budget Formulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
10.2 PEP Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
PEP Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
10.3 PBF Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
PBF Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
11 BI Content for SAP Budgeting and Planning for Public Sector. . . . . . . . . . . . . . . . . . . . . . . . 170
11.1 Public Sector Budgeting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170
InfoCubes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
MultiProviders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Key Figures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
PEP Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Public Budget Formulation — Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
Budget Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
Budget Development Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392

4 INTERNAL Content
1 SAP Budgeting and Planning for Public
Sector
Product Information
Product SAP Budgeting and Planning for Public Sector
Release 1.0 FP03
Based On SAP NetWeaver 7.4
Documentation Published July 2017
Use
SAP Budgeting and Planning for Public Sector is an add-on component that provides a dynamic and
collaborative environment to accommodate the requirements of the end-to-end public sector budget
formulation process by providing:
● Easy access to your budgeting data via a new Microsoft Excel add-in.
● A single point-of-entry for all budget types enabling real-time budget reporting and analysis
● Robust personnel expenditure projection tools with integration to SAP HCM to provide easier reconciliation
of position/employee changes throughout the budget life cycle
● Integrated capital and operating budget data to support comprehensive reporting and analysis
● Automated creation of the budget books
● Streamlined budget request and review process including tools for prioritizing and making budget
decisions
● Improved budget monitoring capabilities after budget adoption
● Integration to SAP BCS (FM)
Through configuration options, SAP Budgeting and Planning for Public Sector can be tailored to meet the
process requirements of many differing public sector entities without the need for further coding, or
customization.
Integration
SAP Budgeting and Planning for Public Sector uses the foundation of SAP NetWeaver to provide a seamless
environment for the complete budget life cycle.

SAP Budgeting and Planning for Public Sector INTERNAL 5
Life Cycle of SAP Budgeting and Planning for Public Sector
Budget planners, analysts, and decision makers can use interactive form templates, BI integrated planning (BI-
IP) tools, personnel expenditure projection calculations, and a diverse source of organizational data to
formulate meaningful and realistic budgets. BI capability allows the budget formulation process to be
completed using realistic data without actually altering the real data.
The following high-level steps define the budget formulation configuration process in SAP Budgeting and
Planning for Public Sector:
1. Master Data Maintenance [page 109]

2. PEP Configuration and Maintenance [page 126]
3. PEP Projection [page 88]
4. Budget Form Component [page 111] and Template Configuration [page 21]
5. Ranking Configuration [page 44]
Features
The various features of SAP Public Budget Formulation allow governmental agencies at the national, state,
regional, or municipal levels to collaborate in the process through budget proposals, approval stages, and
budget adoption.
This solution supports the iterative process of public sector budget formulation and the related analysis. This
capability is possible through the key features that the solution delivers:
● Excel Add-in
The SAP Budgeting and Planning for Public Sector Excel add-in, included as part of SAP Budgeting and
Planning for Public Sector, allows you to create and maintain a library of budget form templates for
managing the public sector budgeting process and to use those forms to maintain your budget data from

6 INTERNAL SAP Budgeting and Planning for Public Sector
within Excel. The Excel add-in communicates with the back-end and uses the same planning objects as the
web client does.
● Budget Forms
Budget form templates are Visual Composer (VC) models that allow configuration for individual
requirements, policies, and practices. Budget forms make it possible for users to create base budget, new
decision packages, capital project, transfer funds across other budget forms, and other types of requests
for specific dimensions including fund centers, funds, funded programs, grants, and functional areas, while
restricting access through authorizations. Once submitted, requests can be reviewed and managed
through a series of user-defined stages. For more information, see Budget Form [page 21].
● Personnel Expenditure Planning (PEP)
PEP projects salary and benefit costs based on timely HR information including positions, employees, job
profiles, and salary and benefit costs. Using PEP projections, analysts can compare and plan for various
contingencies regarding personnel costs during the budget formulation process and mid-year analysis.
● Comments and Narrative
Comment types [page 112] and comment type trees [page 113] provide the tools to capture text
descriptions on budget requests. At every stage of budget formulation, it is possible to track reasons for
change to budget requests. Additional comment types, or boxes, can be added to capture information
about a request. Comment type trees allow relationships to be created among comment types. A standard
comment type tree for Strategic Planning defines the relationship between mission, goals, and objective
comment types and allows the ability to define at which levels performance targets can be defined.
● Budget Request Ranking
Ranking forms facilitate prioritization of budget requests at different levels of the financial management
dimensions. Once prioritized, ranking can be used to establish a funding level and cut-off to determine
which requests are included in the final budget. To learn about the ranking form and its features, see
Ranking Form [page 44].
● Reporting
The underlying BI infrastructure when integrated with solutions such as SAP BusinessObjects allows
extensive data mining and analysis based on stored content. Users can analyze various budget
characteristics and figures to evaluate performance against stated objectives. For more information, see
Reports [page 161].

SAP Budgeting and Planning for Public Sector INTERNAL 7
2 What's New
The following tells you what's new in SAP Budgeting and Planning for Public Sector 1.0 FP03.
Personal expenditure projection (PEP) scenarios with budget form positions
Function Type of Chnage Description
Vacancy Flag Selection for budget form Enhancement PEP now has the capability of running
positions in PEP projections on the budget form position
data. The Vacancy Flag field on the pro
jection configuration screen will have a
new value to select called 'Budget Form
Positions'. For more information, see
Running Fiscal Period PEP Scenario
Calculations [page 92] and Running a
Pay Period PEP Projection [page 99].
Fiscal Period PEP Projections New Fiscal Period PEP now supports projec
tions on budget form positions. The cal
culations and results are processed and
posted in the same manner as filled, va
cant, or both filled and vacant type pro
jections. For more information, see
Running a Pay Period PEP Projection
[page 99].
Flexible Pay Period PEP Projection New Flexible Pay Period PEP now allows pro
jections on budget form positions The
calculations and results are processed
and posted in the same manner as fil-
led, vacant, or both filled and vacant
type projections. For more information,
see Running Fiscal Period PEP Scenario
Calculations [page 92].

8 INTERNAL What's New
Enhancements to the Microsoft Excel budget form add-in
Function Type Description
Support for Custom Buttons New Custom buttons can now be defined as
a part of the form definition and linked
to custom remote function calls (RFCs),
functions, and planning sequences. For
more information, see Creating Forms
[page 12].
Text box usage control New Users will now have an HTML format
ting controls to use when entering text
comments in their budget form instan
ces similar to the functionality available
in the web forms. For more information,
see Creating Forms [page 12].
Optional workflow settings New The Form Designer configuration tool

now includes an option to turn off work
flow for staging in budget forms. For
[page 12].
Optional currency conversion settings New The Form Designer configuration tool
now includes an option to turn off cur
rency conversion in budget forms. For
[page 12].
Mass form delete utility
Mass form delete utility New Budget Administrators now have the
ability to delete form data, including
text, from prior years and for specific
form definitions. For more information,
see Form Mass Soft Deletion [page
121].

What's New INTERNAL 9
Flexible form header" dimension fields (addition of generic dimensions)
Flexible header dimensions on VC Tem New The Visual Composer budget templates
plates and Excel Workbooks and Microsoft Excel Client budget form
designer now include generic multi-use
dimensions for use in budget form con
figuration. For more information, see
Budget Form [page 21].

10 INTERNAL What's New
3 Excel Add-In
The Excel add-in included as part of SAP Budgeting and Planning for Public Sector allows you to create and
maintain a library of budget form templates for managing the public sector budgeting process and to use those
forms to maintain your budget data from within Excel.
The Excel add-in communicates with the back-end and uses the same planning objects as the web client does.
The SAP Budgeting and Planning for Public Sector Excel add-in's functionality supports two main scenarios:
● Creating Form Templates [page 12]

Users with the Form Designer role can create and modify Excel-based budget form templates that support
their organization's budget planning and preparation process.
● Using Forms [page 18]
Budget users can use the library of created forms to maintain budgeting data in order to manage the
process.
3.1 Connecting to Budgeting and Planning for Public

Sector via Excel
Prerequisites
In order to maintain forms and work with SAP Budgeting and Planning for Public Sector data via Mirosoft Excel,
you must:
● Make sure you have Microsoft Visual Studio Tools for Office installed. For more information, see https://
msdn.microsoft.com/en-us/library/ms178739.aspx .
● Make sure the SAP BusinessObjects Analysis, edition for Microsoft Office add-in is installed and active in
Excel. For more information, see https://help.sap.com/boaa .
● Make sure you have configured SAP BusinessObjects Analysis, edition for Microsoft Office by selecting
File Analysis Settings and entering the values provided by your system administrator.
● Make sure the SAP Budgeting and Planning for Public Sector Excel add-in is installed by selecting File
Budgeting Planning About . This will show the details of the SAP Budgeting and Planning for Public
Sector Excel add-in. For more information, see the Installation Guide at https://help.sap.com/sbp .

Excel Add-In INTERNAL 11
Procedure
1. On the Analysis tab of the Excel ribbon, click the Insert Data Source button.
2. Select a data source from the list that appears or choose a new one by selecting the Select Data Source ...
menu option. Depending on your configuration, you may need to provide credentials to log in to the
relevant back-end system.
3. In the dialog that appears, specify values that will serve as parameters for the data connection, then click
OK.
Next Steps
● Creating Forms [page 12]

● Using Forms [page 18]
● Settings [page 20]
3.2 Creating Forms
Prerequisites
In order to create and maintain budget forms via the Excel add-in, you must have the Forms Designer role
assigned to you. For more information, see the Security Information section of the Master Guide. Users with
the Forms Designer role will be able to see a Forms Designer group on the Budget Planning tab of the Excel
ribbon.
Procedure
1. From within Excel running the SAP Budgeting and Planning for Public Sector add-in, connect to your data
source. For more information, see Connecting to Budgeting and Planning for Public Sector via Excel [page
11].
2. On the Budget Planning tab of the Excel ribbon, click the Log On button.
3. On the Budget Planning tab of the Excel ribbon in the Forms Designer group, click the Forms Configuration
button (only visible if you have the Forms Designer role).
4. Select the appropriate template for the type of form you wish to create from the Form Template Name
drop-down.

12 INTERNAL Excel Add-In
The default list of available forms includes both budget forms (see Budget Form [page 21]) and ranking
forms (see Ranking Form [page 44]). If you choose to work on a ranking form, you will be further
prompted to select the budget form you wish to rank.
For more information on the various types of forms and how they work to support the public sector
budgeting process, see Budget Formulation [page 21].
5. On the Header Fields tab, select the fields by which you wish to organize the data to be maintained via the
form you are creating. Each header field defines a specific dimension, such as fund center, fund, and so on.
The header fields configured in this tab will be used globally throughout the workbook, such as in all dialogs
and on the funding sheet.
The Header Fields tab displays a list of available fields based on the type of form template you selected.
○ The Enable workflow for stage advance checkbox is checked by default, which means that the workflow
request will be triggered when the budget request is advanced to the next stage. You can uncheck this
checkbox if you want to disable the workflow on stage advancement.
○ To include a field in the worksheet's header, check the Included box. Depending on the form type you
selected, some header fields will be selected by default and cannot be deselected.
○ To reorder your selected fields, select a field you wish to move and click the up and down arrow buttons
above the table to move that field higher or lower in the list.
○ If you wish to include a header field for data purposes but do not wish it to appear in the generated
workbook and its dialogs, select the corresponding checkbox in the Hidden column.
○ You can display fields but set them as read only with the Read Only checkbox.
○ You can flag fields as mandatory for input using the Required checkbox.
○ You can flag fields as hierarchical with the Hierarchical checkbox. In the generated form, hierarchical
field values will be validated against a hierarchy of values rather than the complete list of valid master
data values and analysis authorizations will be in effect.
○ You may specify a Default Value for any field except those that have been included by default.
○ You can change the default label for an included field in the Label column.
○ You can create a tooltip for a field in the Tooltip column.
 Note
Fields marked Hidden are effectively read-only, and read-only fields must have a default value defined if
they are marked as required.
 Example
If you have only one FM area, you may wish to present it on the funding sheet, but you do not need to
display it in the workbook's header. To accomplish this, you can include the field on the Header Fields
tab of the Form Configuration dialog, mark it as Hidden, and specify your single FM area as its default
value. It will then be available for display when you maintain the details for your funding sheet.
6. On the Sheets tab, manage the sheets that will appear on your form.
○ To add a new sheet, click the Add button and select the desired sheet from the drop-down menu.
○ Available sheets for budget forms include Funding, User Defined, Query, Position, Narrative, and
Attachments sheets. A workbook can include only a single Funding sheet, Position sheet, and
Attachment sheet, but may include multiple User Defined, Query, and Narrative sheets.
○ Available sheets for ranking forms include Funding, User Defined, and Query sheets only.
○ You may change the default name of each sheet in the Sheet Name column. This name will appear as
the worksheet name in the generated Excel workbook.

○ To rearrange the order of the sheets, select a sheet you added and use the up and down arrow buttons
next to the Add button to move it up or down. The order of the sheets in the list controls the order of
the sheets in the generated workbook.
○ You can specify the origin cell of the sheet in the Start Position column. The start position defines the
first Excel cell within the generated worksheet at which content will be inserted.
○ Remove a sheet you have added by clicking the Trash Can icon for that sheet.
7. On the Sheet Details tab, maintain the settings and layouts for your selected sheets. Available settings
depend on the sheet type:
Sheet Type Details
Funding For the entire sheet:
○ Set the Number of Layout-Columns field to specify the number of lay

out-columns you wish to display on your funding sheet.
○ Set the Row Offset field to specify the number of Excel rows that ap
pear vertically between your selected fields within a single layout col
umn.
○ Set the Column Offset field to specify the number of Excel columns
that appear between your layout columns.
For each field, use the Key Column Span and Description Column Span fields
to specify the number of Excel cells across which the field will be displayed.
User Defined You can use user-defined sheets to create title pages, include logos, offer in
structions to end users, and more. The user defined sheet has to be main
tained as part of the workbook definition so that during workbook genera
tion the application does not to delete it and places it properly with respect
to other worksheets within the workbook.
Query 1. Select a query from the Technical Query Name drop-down or click the +
button to search for and import a new query that doesn't appear in the
Position
drop-down list and is not yet part of the workbook.
2. Once you have selected a query, click the Variable Mappings button.
The Query Variable Mapping dialog appears.
3. For each field in the Variable Name column, you can select a target field
from the Mapping column.
○ Click the Suggest Mapping button to automatically map variables.
○ Click the Copy button to copy the currently mapped variables to
the clipboard.
○ Click the Paste button to paste variable mapping data from the
clipboard.
Click the OK button when you are finished.
4. The progress bar under the Variable Mappings button indicates how
many fields have been mapped out of the total number of fields. The
bar will be red until all mandatory fields have been mapped to proceed,
at which time it will turn blue. It will turn green when all fields have been
mapped.

Sheet Type Details
Narrative To add comment fields and form elements, click the Add button and select
the item you would like to add from the drop-down menu. Next, select the
specific comment or form element you would like to add from the dialog
that appears. You can use the arrow buttons next to the Add button to reor
der your selected fields.
For the entire sheet:
○ Set the Number of Layout-Columns field to specify the number of lay

out columns you wish to display on your funding sheet.
○ Set the Row Offset field to specify the number of Excel rows that ap
pear vertically between your selected fields within a single layout col
umn.
○ Set the Column Offset field to specify the number of Excel columns
that appear between your layout columns.
For each field, use the Row Span, Column Span, and Start Position fields to
specify the number of Excel cells across which the field will be displayed –
that is, specify your desired height and width in Excel cells for the text box. If
you click on the comment (Description and Justification) boxes, a text edi
tor window opens in which you can enter text and apply formats such as
bold, italics, indentation, numbering, and the like.
Attachments After the form has been generated, end users can use the Attachments
sheet to attach external documents to the data being maintained in the
generated workbook.
8. On the Operations tab, specify the mapping between the buttons on the Budget Planning ribbon tab in
Excel and the backend planning to be executed when they are clicked.
○ For each operation that you wish to include, check the Included checkbox.
○ In the Planning Sequence column for each selected item, select a planning sequence from the drop-
down or click the + button to search for and import a target new planning sequence that is not yet
included in the drop-down.
○ Once you have selected a planning sequence, maintain mappings for the planning sequence's variables
by clicking the Variable Mapping button. The progress indicator to the right of the button indicates how
many mappings must be maintained.
9. On the Groups & Buttons tab, add groups and buttons to be displayed on the Task Pane on the right side in
Excel at run time and perform custom actions like Save, Refresh, Reset, RFC, Planning Sequence, and
Prompt Message Display when those buttons are clicked.
○ To add groups, click the Addgroup button and maintain the group configuration, like label, tooltip, and
visibility status on the right side:.
Label The name of the group.
Tooltip This sets the tooltip of the group

Visibility
Group Configuration
Load Status True If a Group needs to be visible

only when a form is loaded.
False If a Group needs to be visible

when a form is not loaded.
All Group will always be visible.
Edit Status True If a Group needs to be visible

only when a form is in edit
mode.
False If a group needs to be visible

when a form is not in edit
mode.
All If a Group needs to visible al

ways.
Sheet Type Depending on the sheet type selected, the group will be visible. For
example, if this option is set to "Narrative Sheet," the buttons will
be visible or enabled only for narrative sheets..
Sheet Name This dropdown becomes visible only when “UserDefined” or

“QuerySheet” is selected as SheetType. You can select the sheets
for which the group will be visible.
○ To add buttons, click on the group where a button needs to be added, then click the AddButton button.
Maintain the button configuration like button label, tooltip, icon of the button, visibility and enability
properties from the “Configuration” tab on the right side.
Button Configuration
Label Label: This sets the name of the button created.
Tooltip This sets the tooltip of the button in the SBP Task Pane.
Image This sets the icon of the button.
Visibility/Enability This sets the properties under which the button will be
visible/enable.
 Note
See Group Configuration, above, for detailed information on these properties.

○ To add actions to a button, select the button, then switch to the ManageActions tab on the right . Click
the + button to add custom actions. Choose from the list and configure the action accordingly, if
required. The configurations for the custom actions can be done in the following way:
○ Prompt Action: This actions prompts the user with a message when the corresponding button is
clicked. Add the title and message on the right side.
○ Planning Sequence Action: Select a planning sequence from the dropdown in the right or click the
+ button to search for and import a target new planning sequence that is not yet included in the
drop-down. Once you have selected a planning sequence, maintain mappings for the planning
sequence’s variables by clicking the Variable Mapping button. The progress indicator to the right of
the button indicates how many mappings must be maintained. Action Output is given as a
mapping option to map an added RFC's output parameter to an input of Planning Sequence
variable. If you select the Action Output mapping option, it should list all the custom RFC actions
that were added. Once you select any RFC action name in the second dropdown, it will list all the
output parameters of that RFC in the last dropdown. Select the output parameter that you want to
map.
○ RFC Action : Select an RFC from the dropdown in the right or click the + button to search for and
import a target new RFC that is not yet included in the dropdown. Once you have selected an RFC,
click Parameter Mapping Go to Input tab and maintain mappings for the RFC parameters.
You can see the list of the output parameters from the Output tab. The progress indicator to the
right of the button indicates how many mappings must be maintained. Action Output is given as a
mapping option to map an added RFC’s output parameter to an input of RFC parameter. If you
select mapping option as Action Output, it should list all the custom RFC actions that were added.
Once you select any RFC action name in the second drop down, it will list all the output parameters
of that RFC in the last dropdown. Parameters of table type are not supported at present while
using RFC action. Select the output parameter that you want to map.
○ Save Action: There is no configuration for this action. It will save all the planning data of the
workbook at runtime.
○ Reset Action: There is no configuration for this action. At runtime, it will revert all the changes in
the planning buffer of the workbook.
○ Buffer Action: There is no configuration for this action. When action is added, at runtime the data
should be written to the planning buffer.
○ Refresh Action: Select the sheets that you want to refresh when this custom button is clicked at
runtime.
○ To delete custom actions, select the action that needs to be deleted and click the – button. To
rearrange the order of the custom actions, use the up and down arrows.
10. Save the form configuration, then save the form template itself.
○ Saving your configuration – While working in the Forms Configurator, you can:
Save – Click the Save button or press CTRL+ALT+S to commit your workbook changes to memory.
Cancel – Click the Cancel button or press CTRL+ALT+C to discard any changes to your workbook
since you last clicked Save or Save and Generate.
Save and Generate – Click the Save and Generate button or press CTRL+ALT+G to save your changes,
generate the form, and exit the Forms Configurator.
○ Saving your workbook
After generating a workbook with the Save and Generate button in the Forms Configuration dialog, you
must save the workbook itself if you wish to make it available to other users. To do so:
1. Select File Analysis Save Workbook .

2. Select Save Workbook - Save workbook to the SAP NetWeaver Platform. (This is the second option
displayed.)
3. Select the location within the displayed structure in which you want your workbook to appear.
4. Specify a Name and Description for your workbook and click Next.
3.3 Using Forms
Procedure
1. From within Excel running the SAP Budgeting and Planning for Public Sector add-in, connect to your data
source. For more information, see Connecting to Budgeting and Planning for Public Sector via Excel [page
11].
2. Select File Analysis Open Workbook Open workbook from the SAP NetWeaver platform .
 Note
Until you open a form, most of the buttons on the Budget Planning tab in Excel with be inactive. Once
you have selected a form and opened it, you will be able to use the buttons to work with your budget
data.
3. In the Open Document dialog that appears:

○ You can use the Search tab to search for a form if you know the name.
○ You can use the My Documents tab to browse for forms you have worked with before.
○ You can use the Role tab to browse all forms available to you.
When you have selected the form you wish to work with, click Open.
4. On the Budget Planning tab in the Excel ribbon, do one of the following:
○ Click the Open to select an existing form
○ Click the New button to create a new form
○ Click the Recently Used button to open a recently used form
○ Click the Search button to search for an existing form
5. Once you have loaded a form, you can view the data for that form. There will be several Excel sheets,
depending on the forms design. Sheet types include:
Funding Sheet A worksheet consisting of the form's header fields configured and showing the header
values for the currently loaded budget request. There can be only one Funding Sheet per
workbook.
Query A worksheet that displays the results of a given query.

Position A specialized type of query sheet used for working with budget form positions. There can be
only one Position Sheet per workbook.
Narrative A worksheet containing comments and form elements that allow the you to enter narrative
text.
Attachment A worksheet that displays the list of attachments associated with the currently loaded
budget request and allows you to upload new attachments. There can be only one
Attachment Sheet per workbook.
User A worksheet that can contain any type of supplemental information. Its contents will not be
Defined modified during the workbook generation process. User Defined sheets can be used to
create title pages, instructions, links to further information, and more.
 Note
The designer of the form you are working with may have renamed the different sheets.
6. At any time after you have loaded a form, you can:

○ Click Delete to delete that form.
○ Click Copy and select either Copy Form Instance or Search Form Instance to Copy. For more
information on copying, see Copy Button [page 26].
○ Click Advance to advance the stage. For more information on advancing the stage, see Advance Stage
Button [page 27].
 Note
You cannot advance the stage when you are in edit mode. If you have modified the data (see
below), be sure to save or cancel your changes before attempting to advance the stage.
○ Click Edit to make changes to the loaded form's data.

○ Click Save to save the changes you have made to the form.
○ Click Cancel to cancel your changes and revert to the most recently saved version of the data.
Once you save or cancel, the form returns to Display mode.
 Caution
As soon as you click Save on the Budget Planning ribbon tab, your changes will be saved.
You do not have to save your form via File Analysis Save Workbook ; that option is for
saving the workbook itself, not the form data, and it will be available only for users with appropriate
permissions.
7. ○ If you are working with a budget form that has a Positions sheet, when you are working with that sheet
the Delete Position, Add Position, Edit Position, Copy Position, and Calculate Positions buttons in the
Budget Request group of the Budget Planning ribbon tab be active.
For more information on position management, see Personnel Expenditure Planning [page 88].
○ If you are working with a budget form that has an Attachments sheet, when you are working with that
sheet the Load Attachment and Delete Attachment buttons in the Budget Request group of the Budget
Planning ribbon tab be active.

○ If you are working with a ranking form, the buttons in the Ranking group will be active. For more
information on working with ranking forms, see Ranking Form [page 44].
○ Click the Line Item Text button to add a comment line to the selected row in the Query Sheet data
table.
8. Once the workbook is generated or loaded from the server, the Display Task Pane button on the SBP
Ribbon will be enabled. Clicking the button will open the Task Pane on the right, where you can see the
custom groups and the buttons that were added in form configuration. Based on the configurations done
the groups/buttons be will visible/invisible or enabled/disabled. Buttons should perform the custom
actions maintained in the configuration when they are clicked.
3.4 Excel Add-In Settings
The Budget Planning Excel Add-in contains settings that can be customized by the user. The Setting dialog box
is divided into the two tab pages: Accessibility and Connectivity.
To open the settings dialog, from within Excel select File Budget Planning Settings .
Accessibility
On this tab, you can personalize the Screen Magnification percentage.
 Note
Once a change is made, the application must be restarted for it to take effect. Three magnification levels
are provided for personalization.
● 100%
● 150%
● 200%
Connectivity
Reset the connectivity cache. Here, you can clear your local connectivity cache. This is required only in rare
cases such as after a major system upgrade.

4 Budget Formulation
4.1 Budget Form
Definition
The Budget Form template is a Visual Composer (VC) model thattakes full advantage of the latest BI Integrated
Planning (BI-IP) integration as well as the formerly named 'black box' capability. BI-IP integration allows users
of SAP Budgeting and Planning for Public Sector to interact with the budgeting data, which is stored in BI and
allows customers to expand and adapt their screens based on changes to the BI-IP queries they define.
The 'black box' functionality, which is the option to expand VC capability using Web Dynpro for Java, allows the
integration of several functions previously not available under plain VC, for example, spell checking framework,
comment text box integration, and so on.
 Recommendation
Copy the default budget form template provided in SAP Budgeting and Planning for Public Sector and
change the copy to create budget form definitions to meet individual customer requirements for the budget
formulation process.
A typical implementation requires from three to nine budget form definitions.
Use
Budget form definitions will be used by the end user to submit budget requests. A budget form definition
supports the following budget formulation activities:
● Base and incremental budgeting for both expenditures and revenues

● Multi-year, enterprise, and internal service budgeting
● Capital budgeting
● Performance budgeting
● Modeling and forecasting
● Budget review through client-defined budget stages
Budget forms are used to capture budget expenditure, revenue amounts, and new position requests by
financial management (FM) dimensions. The budget form allows text justifications at the request and line level,
new positions, client-defined request attributes through the use of form elements, and performance budgeting
elements (mission, goals, objectives and measures). SAP Budgeting and Planning for Public Sector provides a
single source for all of an organization’s budget formulation processes and can be configured to meet the
requirement for each.

Budget Formulation INTERNAL 21
Users are allowed to maintain one additional currency above the FM area currency on Budget Forms. When the
user creates a new budget form, he or she will have to choose a currency that he or she wants to work with on
this form.
The data on each of the tabs (Expenses, Revenues, and Positions) will then be stored in the form currency
selected by the user.
New currency translation type /PBFBI/BFC has been introduced for Budget Forms. All the currency conversion
in Budget Forms will happen based on the exchange rate type maintained in this currency translation type.
Authorized users can access budget forms for SAP Budgeting and Planning for Public Sector by choosing
Budget Formulation Budget Forms .
As of PBF 8.0 SP02, the terminology on the column headers for the year has been changed. Prior to SP02, the
columns had headings such as ‘Yr1’ for the current fiscal year and‘Yr 2’ for fiscal year + 1. In SP02, ‘Yr 1’ has
been replaced with the actual current fiscal year (such as 2012), ‘Yr 2’ with fiscal year + 1 (such as 2013), and
so on. This applies to the Budget Form and the Budget Development forms introduced in SP01. The
documentation will continue to refer to Yr 1, Year 1, and so on, but the column descriptions in the forms will
reflect the actual years.
With PBF 8.1, new buttons and features were introduced in the standard budget form template.
● Copy Button [page 26]

● Download Button [page 26]
● Advance Stage Button [page 27]
With SAP Budgeting and Planning for Public Sector 1.0, new buttons and features are introduced in the
Standard Budget Form Template.
● Delete Button [page 27]

● Recent Objects Button [page 27]
Structure
The default budget form template provides a base to create budget form definitions. The template contains a
header area to capture information for the entire request and tab areas that allow users to enter request
information broken down into categories.
Header Area
The header of a budget form definition contains FM dimensions, currency, form ID, description, and budget
formulation stages. The form ID is system generated and the form description is user defined. The following
standard FM dimensions can be used to define the scope of a budget request:
● FM Area
● Fund Center
● Fund
● Funded Program
● Grant
● Functional Area
● Currency
● Multi Use Dimension1

22 INTERNAL Budget Formulation
The budget form template provides two multi use dimensions, but customers can configure up to five multi use
dimensions to fit their requirements. Budget formulation stages represent the phases of budget request
development and review. Users are given access to the budget form at specific stages and cannot see the
budget request for stages to which they have no access. Stages vary by organization and should be defined
during implementation.
Users can maintain the currency at the budget form level apart from the currency maintained at FM area level.
This is referred to as 'Form Currency'.
Tab Area
The template provides a standard set of tabs, all of which can be altered through the VC model. Customers can
create additional tabs as needed. The tabs on the budget form template are as follows:
Expense
On the Expense tab, you enter non-position related costs associated with the request — for example, supplies
and materials, contractual services, and equipment. The tab layout, or entry grid, contains:
● Fund Center Key: fund center code for the budget request line.
● Fund Center: fund center name for the selected fund center key
● Commitment Item Key: commitment item code for the budget request line.
● Commitment Item: commitment item value and description for the selected commitment item key
● Year 1 Actuals: previous year actual amount
● Year 1 Budget: previous year budget amount
● Year 1 Total Base Bud: budget request amount for the first budget development year.
● Year 2 Total Base Bud: budget request amount for the first budget development year.
● Total Budget Yr 1 & Yr2: system generated total of the Year 1 and Year 2 request amounts
File Upload
In NW 730 SP07, Visual Composer introduced a new action called IMPORT that enables comma-delimited
Excel file (.CSV) upload into a table in the screen. This feature has been integrated into the delivered budget
form in two ways. The first one is providing a staging area (as a popup) in which the data can be viewed, tested,
and manipulated before being added to the main table. The second is a Replace All option that deletes existing
rows and adds the new rows. There is, of course, a simple option of adding the rows to the table, which wasn’t
implemented.
Data validation usage and best practice:
1. In order to make sure that the data being uploaded is valid, there are a few validation rules:
○ The uploaded file and the screen table must have exactly the same number of columns, with the same
name, same order, and matching data types.
○ Where an entry list exists, a validation of the value upload is triggered against the allowed value set.
2. A best practice is to use the Export Excel functionality from the ALV table and use the generated file as a
template for the new CSV file. This ensures that most of the above-mentioned rules are enforced.
3. Read-only columns in the screen table are skipped during the upload process, even if they contain data in
the uploaded file.
4. If validation fails, the entire operation aborts and a list of invalid cells is displayed. If there are too many
errors, a link pops up allowing the download of the error log file with the information on the invalid data.

 Note
The new upload functionality does not create master data, so it cannot be used in tabs that require master
data creation, for example the Positions tab.
There is a limitation of 5,000 on the total number of cells uploaded (that is, number of rows * number of
columns).
In the standard budget form template there is an authorization check to determine whether a user has
authorization to use the Export (Excel) functionality in the ALV table. This is the same authorization check used
in the Form Download feature.
1. Authorization Object Name —/PBFBI/DWL

2. Authorization Check Function Module —/PBFBI/BF_DL_AUTH_CHECK
Revenue
On the Revenue tab, you enter estimated revenues such as taxes, grants, service fees, and other sources of
revenue. The tab layout, or entry grid, contains:
● Fund Center
● Commitment Item
● Year 1 Total Base Bud
● Year 2 Total Base Bud
● Total Budget Yr 1 & Yr2
Position
On the Positions tab, you enter requests for new positions by providing relevant information about the job, the
organizational grouping, pay level, percentage of compensation, and counts. The system then calculates the
cost of the requested position using pay level amounts and default benefits defined for the job. When the
underlying master data changes (for example, pay scale, benefit rules, benefit rates, job, and so on), based on
global configuration administrators can trigger auto-position recalculation.
● Position: system generates a position number when you click New.

● Job: job code assigned to a requested position.
On entering a job code and clicking Job Defaults, the system displays the associated information for
Country Grouping, Pay Scale Type, Pay Scale Area, ES Grouping CAP, Pay Scale Group, Pay Scale Level,
Performance Period, and Performance Start Period from the job code.
● Fund Center: fund center code defined for the position request.
● Start Month/Year: starting month and year for the position request.
● End Month/Year: ending month and year for the position request.
● Number of Positions: position count for the position request.
● Report FTE: user entered FTE for the position request.
● Benefit %: benefit percentage for the position request.
● Salary %: salary percentage for the position request.
● Salary: override salary amount for the position request. This amount will be used in the calculation of costs
instead of the amount in the pay level table.
● Year 1 Costs: position request costs calculated for year one.
● Year 2 Costs: position request costs calculated for year two.
Narrative

On the Narrative tab, you provide a place for users to enter required text to justify budgetary requests, explain
impacts of the decisions, track decisions, and relate budgetary expenditures to programmatic operations.
Attachments
On the Attachments tab, you can attach supporting documents for the budget request.
History
The History tab displays audit logs that are saved as part of configuring the audit trail. The History tab of the
budget form template has three views. The first view (Change History) displays the header records for
selection. Fields displayed are:
● Date the record was created/modified in /PBFBI/BF_CUBE

● Time the record was created/modified
● User Name responsible for modifying the record
● Budget Stage the record was in at the time of saving
The second view (Change Details) displays the details of the selected record from the first view (Change
History).
The third view (Reason for Change) displays the corresponding reason for change text that is created at the
time of saving the data in the budget form.
 Note
● Audit trail logs are recorded and displayed only if auditing is turned on in the PBF global settings.
● Audit trail records are only logged when an amount value or key figures — for example, budget costs —
are changed. Changes to text descriptions, comments, and line texts are not logged.
● Users can only view history for the form instances they are authorized to view based on the stage the
form is in. Standard PBF stage authorization is applied.
Stage Advance Log
This tab contains a table listing the entire approval log related to a given budget form. It displays the work item
ID (a unique ID for each approval request), the stage to which the form was advanced, and relevant dates and
decisions along with user who made the decision. Decision reasons can be viewed by clicking the line item in
the table for forms that were rejected. Note that the standard budget form template only supports decision
reasons for approval requests that were rejected.
Integration
Using the combo edit configuration, you can define:
● rules to limit the selection of each FM dimension based on a defined hierarchy and levels at the header and
detailed line
● leaf rules to limit the selection of FM dimensions based on defined valid combinations
Each rule can be mapped to one or many form definitions.
Comment boxes, comment type trees, and form objects are defined in the portal and can then be included in
any of the form definitions.

More Information
● Budget Form Configuration [page 111]

● Creating a Combo Edit Rule [page 114]
● Universal Worklist: Tasks [page 27]
● Budget Form Template: Technical Details [page 28]
● Copy Form Feature [page 31]
● Budget Form Download [page 32]
● Reallocations [page 35]
4.1.1 Copy Button
The Copy Form functionality can be used to create new forms using existing Budget Forms (of the same type or
definition) as a reference. A new form ID is generated, and all the funding details, line items, line texts, and
comments are copied to the new form. New position master data is generated as a part of the copy process.
The stage of the newly copied form is set to the initial stage defined in the Form Definition master data.
The reference budget form can be from previous years, and the new budget form is created for the current
budget year (the budget year set in the PBF global settings). The fiscal year and fiscal period of the reference
form are calculated using an offset value that is the difference between the budget year of the reference form
instance and the budget year maintained in the PBF global settings.
Limitations
● This feature is only available for form type FI.

● Existing form instance data from the previous budget years that is chosen to be copied should exist in the /
PBFBI/BF_CUBE infoprovider.
● Ensure that number ranges are maintained as per instructions in the SAP Budgeting and Planning for
Public Sector Configuration guide.
● Archived form instance data will not be copied over to the new form instance.
● No data is copied to the new form instance if data already exists for the new form instance based on the
filter restriction of the planning function filter.
● Form instance ID /PBFBI/FORM_ID, budget year /PBFBI/BDGT_YR, and budget stage /PBFBI/STAGE
should be available in the aggregation level for the planning function to work.
4.1.2 Download Button
The Download button can be used to create an export file and download budget form data from the Funding,
Narrative, and Line Item tabs — for example, Expense, Revenue, and Positions. Attachments, change logs, and
workflow logs are not downloaded to the export file. Clicking this button displays a popup window with a link to
download the file. The Download button is only visible if the user has Download authorization. The relevant
authorization object is /PBFBI/DWL.
The file is a WebDynpro cached file, and the link is only valid for a certain period of time. If the link expires, a
new link can be generated by clicking the Download button again. Contact System Admin for more info on how
to adjust this time.

Formatting tags such as bold, italics, headings, and line breaks are removed from rich text comments when
downloading a file.
4.1.3 Advance Stage Button
The Stage Advance feature is integrated with the SAP Budgeting and Planning for Public Sector Stage
Workflow. Users can now submit the form for approval along with priority and comments, and a work item gets
generated for the approver. While the form is awaiting a decision, the entire form is changed to display-only
mode and protected from updates until a decision is made.
4.1.4 Delete Button
You can use the Delete buton to temporarily delete a file. You cannot delete forms that are funded or
reallocated, nor forms that are in a stage that does not permit deletion. Once the form is deleted by the user, it
can be either recovered or permanently deleted by and administrator on request.
4.1.5 Recent Objects Button
You can get a list of objects you have recently accessed and then select an object from that list for further work.
This can save you time over having to search in the list of frequently used forms via F4 help. The size of the
recently used objects list depends on maintained global configuration .
4.1.6 Universal Worklist: Tasks
Budget forms submitted for stage approval can be viewed under Home Work Universal Worklist Tasks
Budget Request Approval . Refer to the Universal Work List (UWL) help guide for more information on how
to work with UWL.
The customized SAP Budgeting and Planning for Public Sector sub-view provides additional PBF fields such as
Form Name, Form ID, Stage, and Description. Additionally users (approvers) can approve or reject a request
directly from the UWL and record a justification (mandatory) if rejecting.
Users can see work items in the UWL Tasks table only if there are work items awaiting approval from them —
that is, only if their user IDs are maintained in the approval list for the respective form definition or form ID.
Selecting or clicking a work item allows users to view more details and take actions (for example, preview form
or make a decision). The Preview Form button navigates users to the Budget Form screen and prefills the
respective Form ID.
Notifications are generated on either rejecting or approving a stage approval request. They are located under
the SAPoffice Mails tab of the UWL and indicate the form ID for which the decision was taken. The budget form
is advanced to the indicated target stage only if a Stage Advance request is approved. It remains in the existing

stage when the request is rejected. Regardless of the decision, the form is unlocked and released for further
changes and updates after a decision is made. Decisions and reasons are logged and can be found in the Stage
Advance Log under the standard Budget Form screen.
4.1.7 Budget Form Template: Technical Details
VC Development Component Name: /cdev/pbf/budget_form_template
Object Type Object Name Value Comments
Info Object /PBFBI/FRM_TYP FI Form type for Resource Plan

ning
Info Object /PBFBI/VCNAME DP2009 Form Name Resource Plan

ning
Info Object /PBFBI/VCNAME DP2009_TAB_EXP Form Definition of type Tab

for creating combo edit rule
for Expense tab
Info Object /PBFBI/VCNAME DP2900_TAB_REV Form Definition of type Tab

for creating combo edit rule
for Revenue tab
Info Object /PBFBI/RULE R1 Rule for defining combo edit

settings for Form definition
DP2009 and
DP2900_TAB_EXP
Info Object /PBFBI/RULE R2 Rule for defining combo edit

settings for Form definition
DP2900_TAB_REV
Info Object /PBFBI/PROJID 2 Represents expense records
Info Object /PBFBI/PROJID 3 Represents revenue records
Info Object /PBFBI/PROJID 1 Represents position records
Hierarchy /PBFBI/CMMT_IT CMMT IT HIERARCHY Commitment Item Hierarchy

to be used
Hierarchy /PBFBI/FUND_CT FUND_CT_HIER Fund Center Hierarchy

Queries
Tab Query Description
Expense /PBFBI/A_BF_CU1_QI001 Expense query
Revenue /PBFBI/A_BF_CU1_QI003 Revenue query
Positions /PBFBI/A_BFCU_QI000 Position query
History /PBFBI/BF_CUBA_QI001 Audit trail query
History /PBFBI/BF_CUBA_QI002 Audit trail query
RFCs
Technical Name Feature Description
/PBFBI/READ_FORM_INSTANCE Form Header Returns a list of form ids and fall under
given criteria.
/PBFBI/ Form Header Returns budget form header (Funding tab

READ_BUDGET_FORM_HEADER values) for given form ID.
/PBFBI/NEW_FORM_INSTANCE Form Header Creates a new budget form instance.
BAPI_CURRENCY_GETLIST Form Header Returns the currency list.
/PBFBI/UPDATE_FORM_DESCRIP Form Header Updates the form description for a given

TION form ID.
/PBFBI/STAGE_ADVANCE Workflow Advances the form to the indicated stage.

This function is replaced with /PBFBI/
WF_STAGE_ADVANCE with PBF 8.1 and is
instead called in Budget Form Workflow.
/PBFBI//LIST_RECENT_OBJECTS Recent Objects Returns the list of recently used objects.
/PBFBI/CHECK_FORM_DELETION Form Deletion Checks if the form can be deleted or not.
/PBFBI/GET_AUTHORIZED_STAGES Workflow Returns authorized stages to which form

can be advanced.
DD_DOMA_GET Workflow Returns domain values and is used to get

values for the Priority field.

/PBFBI/WF_STAGE_ADVANCE Workflow Triggers the stage approval workflow for a
given form ID and stage combination.
/PBFBI/WF_IS_FORM_LOCKED Workflow Returns true if a given form ID is locked for

stage workflow.
/PBFBI/WF_GET_DEC_REASON Workflow Returns the decision reason for a given

work item ID.
/PBFBI/WF_GET_APPLOG Workflow Returns the workflow approval log for a

given form ID.
/PBFBI/ Value Help Returns info object master data values.

READ_MASTER_DATA_VALUES
/PBFBI/GET_ITEM_LEAF_VALUES Value Help Returns valid leaf values that satisfy crite
ria defined using the combo-edit feature
for agiven characteristic (for example,
fund center, commitment item, and so on).
/PBFBI/GET_HEADER_TEXT_NODES Value Help Returns valid text nodes that satisfy crite
ria defined using the combo-edit feature
for a given characteristic (for example,
fund center, commitment item, and so on).
/PBFBI/READ_TEXT_BY_GUID History tab Returns the reason for change text for a
given GUID.
/PBFBI/CREATE_TEXT Reason for change Creates a reason for change entry for given
form ID.
/PBFBI/READ_JOB Position tab Returns default pay settings maintained

for a given job code.
/PBFBI/GET_NEW_DP_POSITION Position tab Returns a new position ID from number

range.
/PBFBI/CREATE_DP_POSITION_MD Position tab Creates position master data.
/PBFBI/BF_DL_AUTH_CHECK Form Download Returns True if the user has download au
thorization /PBFBI/DWL.
/PBFBI/LIST_VALID_BUDGET_YEARS Copy Form Lists valid budget years.
/PBFBI/GET_HELP_LINK Help Used to get help the URL for given screen
ID. Screen IDs and help URLs can be de
fined using the Help Admin page in the
PBF Admin section.

4.1.8 Copy Form Feature
Technical Description
Transaction data from /PBFBI/BF_CUBE, Form Elements, Comments, and Line Item Text will be copied from
the existing form instance to a newly created form instance. All the contents of the existing form instance will
be copied into the new form instance with the exception of attachments. For each existing position number in
the Position tab of the existing form instance that is chosen for copy, a new position number is created in
InfoObject /PBFBI/POSTN, and the corresponding attribute values of the existing position number will be
copied to the corresponding new position. The initial stage defined for the form definition will be set to budget
stage /PBFBI/STAGE copied to transactional data. Budget year /PBFBI/BDGT_YR of the new form will be set
to the budget year maintained in the PBF global configuration settings, maintained using transaction SPRO.
Fiscal year 0FISCYEAR and fiscal year/period 0FISCPER of the copied to transaction data will be added by a
offset value that is calculated by the difference between the budget year of the existing form instance and the
budget year of the new form instance.
Prerequisites
● Master Data requirements:

Maintain master data for Number Range Interval InfoObject /PBFBI/NR_INTV.
The number range defined for object /PBFBI/POS in transaction SNUM should also be maintained as
master data in InfoObject /PBFBI/NR_INTV.
Maintain Master Data for /PBFBI/NR_INTV:
○ Number range interval: 02
○ Language: EN
○ Long Description: Position Interval used in Budget Form Template
● Configuration
Maintain PBF global settings in transaction SPRO, path Goto SAP Reference IMG SAP Budgeting and
Planning Maintain Global Settings Budget Year .
Technical Details
Object Type Object Name Comments
Cube /PBFBI/BF_CUBE Input and Output
Planning Function /PBFBI/PF_BFCU_COPY Copy all data to a new form for the
budget form template
Planning Function Filter /PBFBI/F_BFCU_A Filter spanning all standard budget

form tabs
Planning Function Type /PBFBI/PFT_COPY_FORM Copy all form data to a new form
Aggregation Level /PBFBI/A_BFCU_A Aggregation level spanning all standard

budget form tabs
InfoObject /PBFBI/NR_INTV Number range interval value
BW Variable /PBFBI/COSNRINT Number range interval value

Class /PBFBI/CL_PF_COPY_FORM Planning function to copy all form data
to a new form
Technical Prerequisites
Info Object /PBFBI/FORM_ID /PBFBI/CMSFI01 Variable Value restriction for fil-

ter /PBFBI/F_BFCU_A
Info Object /PBFBI/FORM_ID /PBFBI/CMSFI01 Variable Value restriction for Pa

rameter (F5) in Planning Func
tion /PBFBI/PF_BFCU_COPY
Info Object /PBFBI/NR_INTV /PBFBI/COSNRINT Variable Value restriction for Pa

rameter (F5) in Planning Func
tion /PBFBI/PF_BFCU_COPY
Form instance ID /PBFBI/FORM_ID, budget year /PBFBI/BDGT_YR, and budget stage /PBFBI/STAGE should
be available in the aggregation level for the planning function to work
4.1.9 Budget Form Download
To use the form download feature for custom forms check development component CDEV/PBF/
BF_DOWNLOAD. The implementation in the budget form template can be used an example to understand how
to implement this feature. Input parameters to this DC define what the download or export file will look like.
These parameters can be defined by setting initial values in corresponding shares —for example, check
Funding Share in the DownloadForm model of the standard budget form template (cdev/pbf/
budget_form_template). To access this, right-click Funding Share, then click Define Data, then Initialize Data.
The following sections explain each input parameter in more depth.
Meta
Meta setting defines the total number and order of tabs to be created in the Excel export file.
Field Name Description Example Values
TAB_ID Order of tab 1, 2, 3, and so on
TAB_DESC Description of tab Expense, Revenue
TAB_TYPE Type of tab; allowed values are: T, Q, F
● T — Text Fields
● Q — Query Data
● F — Funding
Funding

Funding setting defines order and names of Funding tab parameters that should be written to the output file.
FIELD_POSITION Order of field 1, 2, 3, and so on
FIELD_NAME Technical name of field. Allowed values ● FORM_ID

for Funding parameters are: ● FM_AREA
● FORM_ID ● FUND_CENTER
● FM_AREA ● FUND
● FUND_CENTER ● FUNCTIONAL_AREA
● FUND ● FUNDED PROGRAM
● FUNCTIONAL_AREA ● GRANT
● FUNDED PROGRAM ● CURRENCY
● GRANT
● CURRENCY
FIELD_DESC Descriptions of fields Form ID, Fund Center, Financial Man

agement Area
 Note
It is okay to add new or custom field names to this table as long as the corresponding logic to handle these
fields is defined using the SAP Budgeting and Planning for Public Sector Download BADI.
Query
The Query tab setting defines what queries should be executed for tab of type ‘Q (Query).
TAB_ID Tab order number as defined in 1, 2, 3, and so on

Meta setting
PROJ_ID Projection ID for relevant tab 1. Positions

2. Expenses
3. Revenues
QUERY_NAME Technical name of query For Projection ID 2: /PBFBI/

A_BF_CU1_QI001
For Projection ID 3 /PBFBI/

A_BF_CU1_QI003
For Projection ID 1 /PBFBI/A_BFCU_QI000
QUERY_DESC Query Description Expense Query, Revenue Query
For information use only
Text

Text settings define order and names of comments and form elements that should be displayed in the form.
FIELD_POSITION Order of field 1, 2, 3, and so on
FIELD_NAME Technical name of comment or form el CONTACT, Justification, Description

ement
These values are the ones that are de
fined in PBF Comment Administration
screen
FIELD_TYPE Type defines whether it is a comment or CT

form element. Valid values:
FE
● FE — Form Element
● CT — Comment Type
FIELD_DESC Description of field Justification, Contact Name
4.1.10 Budget Form Overview
Overview of the budget form is a new feature introduced in the SAP Budgeting and Planning for Public Sector
1.0. You can use it to get an overview of the budget form in a single tab or by a single step without navigating to
each individual section of the budget form like expense, revenues, and positions. The overview of the budget
form is represented using charts and a single table, with the totals of all the key figures.
This overview of the budget form is shown in a newly introduced tab called Overview on the budget form and on
all the budget development form screens. It is mainly useful when you want to get an overview of the selected
budget form without navigating to all the individual tabs.
The overview tab of the budget form contains the following sections:
1. Consolidated chart: The consolidated chart is a single graphical representation with the totals of all the key
figures of all the records of expenses, revenues, and positions.
2. Individual charts: The individual charts are the separate graphical representations with the totals of all the
key figures of all records of expenses, revenues, and positions.
3. Overview Table: The overview table is a consolidated table that contains the totals of all the key figures of
all the records of the expenses, revenues, and positions.
Technical Details

Query /PBFBI/A_BF_CU1_OVERVIEW_T Output
Filter /PBFBI/F_BF_OVERVIEW Filter created for the budget form over

view
4.1.11 Deleting Forms

NOT CONTENT WAS PROVIDED FOR THIS SECTION YET.
4.1.12 Reallocations
During the Budgeting Cycle there is often a need to move/transfer funds from one Decision package request to
one or more Decision Package Request forms, the process of moving funds between Decision Packages is
called Reallocations.
Usage is recommended for SAP Budgeting and Planning for Public Sector budgeting at the end of Budgeting
Cycle.
Users are provided with a new screen to allocate budget forms expenses, revenues or position entries
separately. The user has to select a form ID and then choose to allocate the cost associated with the expenses,
revenues and positions to a different form ID.
Authorized users can access Reallocations for SAP Budgeting and Planning for Public Sector by choosing
Budget Formulation Reallocations .
The template allows the user to select a form ID as sender and transfer the position, expense, and revenue
funds to other form IDs that are referred to as receivers. The wizard-based template has the following steps:
1. Select the following details:

○ Form ID: Sender Form ID is entered here
○ Type of Entry: Used to determine whether an expense, revenue, or position entry has to be allocated
○ Fiscal year: The year from which the amount has to be deducted
A query will also be executed on the form ID, fiscal year, and type of entry to determine the total amount
available for allocation in the form ID. The user cannot enter an amount greater than the available amount
in the Amount to allocate column of the Select Sender Rows table.
2. Enter FM dimensions to retrieve a list of form IDs that could be the receiver form IDs.
The user has to then select the form IDs that will serve as the receivers.
3. Enter the FM details for each form ID and the amount that will be allocated against each form. For each
form ID, the user will have to enter the receiving funds center and the commitment item.
The user will also have the option of allocating based on percentages instead of entering full amounts.
 Note
The amount specified under the Amount to Allocate column in Step 1 should be completely allocated to one
or more receivers in Step 3. Partial allocation of this amount is not possible.

Button Functions
● Add Receiver: This is available only for the Expense and Revenue Type allocation. It is used to add the
receiver form IDs manually.
● Copy: Copies the selected form details to the new row.
● Delete: Used to delete the receiver form IDs from the list selectively.
● Save & Reallocate: Only enabled during the last step of reallocation. Once the amount/percentage is
specified against each receiver, this button executes an RFC, and a planning function is triggered to create
the entered allocations for the intended receivers.
Reversing Reallocations
Users can reverse allocations by clicking the Goto Deletion Screen button at the top-right corner of the
reallocations page.
On the Goto Deletion Screen, the user must enter a sender/receiver form ID and click on search. This displays
the list of transactions previously executed in the Allocation Entries table and the list of sender/receiver form ID
details per allocation in the Allocation details table.
In the Allocation Entries table, the user can select the transaction record for which the allocation has to be
reversed with respect to the Transaction ID and Type Of Entries Re-allocated and click the Reverse Selected Re-
allocation button at the top-left of the reallocations page.
 Note
● Transaction ID is a unique ID generated during each allocation transaction.

● Type of Entries Re-allocated:
○ 000001 – Indicates a position entry allocation
○ 000002 – Indicates an expense entry allocation
○ 000003 – Indicates a revenue entry allocation
4.2 Resource Planning Form
Use
The Resource Planning form is an extension of the existing budget form to support quantity planning. The
functionality supports price maintenance at different levels and allows users to select the appropriate pricing
category that is applicable for any given budget request. The Resource Planning framework supports
commodity planning, activity planning, and position cost planning (based on internal transfer prices).
Consider the following example: A central procurement organization can maintain a contractually agreed price
for a given activity like External LABOR. The maintenance framework is flexible enough to allow, users to
maintain different prices for the same activity, and the budget form would allow the project planner to select
the appropriate activity type for a given activity and enter the quantity required.

The commodity planning is also based on a similar concept. For example, a public health department can
request 1000 units of a certain item. The prices for the different commodities can be maintained at a few
different levels, allowing users to select the appropriate price based on the commodity type or even location.
The new position cost calculation function allows users to plan for a certain amount of an existing position’s
time. For example, for the construction of the new court house, an inspection authority’s time can be requested
in a given form. This inspection authority’s time and the costs can be calculated based on transfer prices or
using the personnel expenditure projections (PEP) cost calculation. The price maintenance is flexible enough
to allow users to maintain prices at different levels and would allow the end users to select the appropriate
pricing scheme that is applicable for this construction project.
Prerequisites
1. You must be on NW 730 SP07 or higher. If the installed SP is SP07, it is mandatory to have the corrections
in OSS Note 1716687 and its dependent notes implemented before installing SAP Budgeting and Planning
for Public Sector.
2. The budget development form templates have to be copied and adapted based on the customer’s data
volume, performance, and sizing considerations.
3. To customize authorizations for the adapted forms please refer to the SAP Budgeting and Planning for
Public Sector master guide security section.
4. To customize currency translation/conversion for the adopted forms please refer to one of the following:
1. SAP Budgeting and Planning for Public Sector Installation Guide, section Post-Implementation
Currency Conversion
2. SAP Budgeting and Planning for Public Sector Upgrade Master Guide, post-upgrade steps
5. All delivered budget development form templates need specific master data values as outlined in the pre-
requisites section. These default master data values will be created using the /PBFBI/ /PBFBI/
CREATE_MD_SL_01 (transaction /PBFBI/MD_SL01) program.
The following pieces of master data are used within the Resource Planning form and must exist in the system
for the form to work properly.
Info Object /PBFBI/FRM_TYP FI Form type for Resource Planning
Info Object /PBFBI/VCNAME DP2009 Form Name Resource Planning
Info Object /PBFBI/VCNAME DP2009_RP_POS Form Name Resource Planning Position

Tab
Info Object /PBFBI/VCNAME DP2009_RP_ACT Form Name Resource Planning Activity

Tab
Info Object /PBFBI/VCNAME DP2009_RP_CMD Form Name Resource Planning Com

modity Tab
Info Object /PBFBI/RULE RPP Rule for Resource Planning Position Tab

Info Object /PBFBI/RULE RPA Rule for Resource Planning Activity Tab
Info Object /PBFBI/RULE RPC Rule for Resource Planning Commodity

Tab
Info Object /PBFBI/PROJID 5 Represents position’s records
Info Object /PBFBI/PROJID 6 Represents Activity’s records
Info Object /PBFBI/PROJID 7 Represents Commodity’s records
Info Object /PBFBI/PU VALTP A1 Fixed Value Type for Resource Planning
Form
Hierarchy /PBFBI/CMMT_IT CMMT IT HIERARCHY Commitment Item Hierarchy to be used
Process
Data for the Resource Planning form is read from the Resource Planning cube (/PBFBI/RP_CUBE). Data is
written back to the Resource Planning cube only. The Resource Planning form has a header section and three
different tabs for maintain Position’s Cost, Activity Cost, and Commodity Cost as described below:
Form Section/Tab Description
Header Area Data: Form ID, Description, Stage, Funding status
Functions:
● Form ID F4 Help: F4 help list displays all the form IDs

created using Budget Form screen.
 Note
The new form IDs can’t be created directly using this
screen.
Funding Tab FM dimensions, Currency, and Description. The dimension

data shown on the screen is derived from the existing Form
ID selected in the header area.
 Note
All the dimensions are display only on this tab.

Positions Tab Contains the list of Master Data Positions added for the re
source planning.
Data:
● Position ID (F4 displays all the Active Master Data Posi

tions)
 Note
Active positions: Positions with Employment Status
same as the Employment Status maintained in the
Global Table)
● Fund Center (F4 displays all the child nodes of the

header Fund Center)
● Commitment Item
● Fiscal Period
● Rate Type
● Quantity
● Unit Of Measure (derived from entered Rate Type Mas
ter Data)
● Position Cost (Calculated Amount in Form Currency)
Functions:
● Add: Provides a popup screen where the master data

position can be added for positions cost planning.
● Edit: Provides a popup screen where except the Position
ID, other attributes can be modified for positions cost
planning.
● Delete: Deletes Positions from the positions cost plan
ning.
● Calculate Using PEP: Calculates the position’s cost us
ing the personnel expenditure projections (PEP) cost
calculation.
Notes:
1. Rate Type selected for all the added positions must be
“PEP1” for calculating the cost using PEP.
2. The system will calculate the salary and benefit costs
based on the position master data and then calculate
the average cost per day. Using average daily cost, the
Total Cost is computed for the entered Number of Days
● Calculate By Rate Type: Calculates the position’s cost
based on transfer prices/Rates maintained in the Rate
Type DSO.
Note: Rate Type selected for any of the added positions
must not be “PEP1” for calculating the cost using PEP.

Activities Tab Contains the list of Activities added for the resource plan
ning.
Data:
● Activity Type
● Activity Pricing Group
header Fund Center)
● Commitment Item
● Fiscal Period
● Rate Type
● Quantity
● Unit Of Measure (derived from entered Activity Type
Master Data)
● Activity Cost (Calculated Amount in Form Currency)
Functions:
● Add: Provides a popup screen where the various activi

ties can be added for activity cost planning.
● Edit: Provides a popup screen where the attributes
other than Activity Type can be modified for activity
cost planning.
● Delete: Deletes Activities from the activity cost plan
ning.
● Calculate: Calculates the activity’s cost based on trans
fer prices/rates maintained in the Activity Price Mainte
nance DSO.

Commodities Tab Contains the list of commodities added for the resource
planning.
Data:
● Commodity
● Commodity Location
● Price Indicator
header Fund Center)
● Commitment Item
● Fiscal Period
● Rate Type
● Quantity
● Unit Of Measure (derived from entered Commodity
Type Master Data)
● Commodity Cost (Calculated Amount in Form Cur
rency)
Functions:
● Add: Provides a popup screen where the various com

modities can be added for commodity cost planning.
● Edit: Provides a popup screen where attributes other
than Commodity can be modified for commodity cost
planning.
● Delete: Deletes Commodities from the commodity cost
planning.
● Calculate: Calculates the commodity’s cost based on
transfer prices/Rates maintained in the Commodity
Rate Maintenance DSO.
Technical Details
The following BI-IP objects are used in the Resource Planning form and must be installed and activated for the
form to work properly.
Object Type Object Name Filter Comments
Cube /PBFBI/RP_CUBE N/A Used for storing Resource Planning

Cost
Aggregation Level /PBFBI/A_RP_C02 N/A Aggregation level for Resource

Planning Position’s Cost

Planning Activity’s Cost


Planning Commodity’s Cost
Query /PBFBI/ /PBFBI/F_RP_C03 Query for Resource Planning form

A_RP_C02_Q0002 Position’s Cost

A_RP_C03_Q0001 Activity’s Cost

A_RP_C04_Q0001 Commodity’s Cost
Planning Function /PBFBI/PF_RP_C02 /PBFBI/F_RP_C03 Planning Function for Resource

Planning form Position’s Cost Cal
culation

Planning form Activity’s Cost Cal
culation

Planning form Commodity’s Cost
Calculation
Planning Function /PBFBI/PF_RP_D02 /PBFBI/F_RP_D02 Planning Function for Resource

Planning form Position Deletion

Planning form Activity Deletion

Planning form Commodity Deletion
VC Model Details
● DC name: cdev/pbf/resource_planning
● Main Model: MainFrom
● Position Tab Model: PositionTab
● Activity Tab Model: ActivityTab
● Commodity Tab Model: CommodityTab
DSO Maintenance Screen
Rate Type Maintenance
The Resource Planning form uses rate types to calculate the position cost for the entered quantity on the
Resource Planning form. These rate types can be maintained using the Rate Type Maintenance screen in the
CE portal. The rate type price can be maintained at either the position or job level for the given period.
● If rate type is maintained on the job level, it will be applicable for all positions under that job.
● Period should not overlap for same job or position.

VC Model Details
● DC Name: cdev/pbf/rp_cost_maint
● Model Name: RateType_Maint
Backend Services Used
DSO /PBFBI/RP_O01
RFC /PBFBI/READ_DS_RP_O01 Read data from DSO for selected rate type
RFC /PBFBI/MODIFY_DS_RP_O01 Modify and create new records for selected rate
type
Activity Maintenance
The Resource Planning form uses the activity price to calculate the total cost for the entered quantity on the
Resource Planning form. The activities price can be maintained using the Activity Maintenance screen in the CE
portal for the given period.
● If the activity type is blank, it will be applicable for the entered Activity Group.
● Period should not overlap for the same activity type.
VC Model Details
● Model Name: Activity_Maint
Object Object Name Comments

Type
DSO /PBFBI/SL_RTE
RFC /PBFBI/READ_DS_SL_RATE Read data from DSO for selected Activity Group
RFC /PBFBI/MODIFY_DS_SL_RATE Modify and create new records for selected Activity Group
Commodity Maintenance
The Resource Planning form uses the commodity price to calculate the total cost for the entered quantity on
the Resource Planning form. The commodity price can be maintained using the Commodity Maintenance
screen in the CE portal.
● If the commodity location is blank, the commodity price will be applicable for all locations.
● Period should not overlap for the same commodity.
VC Model Details
● Model Name: Commodity_Maint

DSO /PBFBI/CM_RATE
RFC /PBFBI/READ_DS_CM_RATE Read data from DSO for selected Com

modity
RFC /PBFBI/MODIFY_DS_CM_RATE Modify and create new records for se

lected Commodity
4.3 Ranking Form
Definition
The ranking template is a Visual Composer (VC) model that allows users of SAP Budgeting and Planning for
Public Sector to prioritize budget requests by assigning ranking values. Ranking can occur at different
organizational levels; the availability of previous and current ranks for each budget request also provides
greater insight into priorities at previous ranking levels.
Ranking is available for all requests within a budget form definition.
 Recommendation
Copy the default ranking template provided in SAP Budgeting and Planning for Public Sector and change the
copy to create ranking form definitions.
Not every budget request will have a corresponding ranking definition.
Use
Ranking is used to assign priority ranks to budget requests, compare request amounts by FM dimension
combinations, and then determine which requests could be funded by defining funding levels. You can rank and
re-rank as many times as needed and the system will re-sequence the budget requests based on the assigned
rank. Ranks can be defined for each phase of the budget. You can also change the funding levels after they have
been established.
Funded or unfunded ranking forms are also known as decision packages.
Authorized users can access the ranking forms for SAP Budgeting and Planning for Public Sector by choosing
Budget Formulation Ranking Forms .

Structure
The Ranking screen provides the ability to view and rank individual budget requests that have been grouped by
FM dimension and version combinations. You can assign ranking priority, perform mass sequencing updates,
and establish and/or reset funding levels.
Load Version
When loading the Ranking screen through the Load Version popup window, you select the budget form header
FM dimension combination and the ranking version for the FM dimension combination that should be
displayed in the ranking form. The FM dimension criteria are subject to the hierarchy established in the Combo
Edit [page 114] rule for the form definition. This means that if a branch in a hierarchy is selected, budget
requests that have the selected code or any code that roll up to the selected code will appear in the ranking
screen. Multiple versions can be established and reused for each unique FM dimension header combination.
The following FM dimensions are available in the Load Version popup window:
● FM Area
● Fund Center
● Fund
● Funded Program
● Grant
● Functional Area
The budget form template provides two multi use dimensions, but customers can configure up to five multi use
dimensions to meet their requirements. Once the FM dimensions and version have been selected in the Load
Version popup window, click Load to populate the main Ranking screen.
Copy
The Copy button, copies the currently displayed version of ranking into a new version. A popup screen allows
you to select which version the currently displayed version should be copied to. A version can be copied to
different versions, multiple times.
Save
The Save button saves the changes made on the Ranking screen.
Mandatory Fields
This section allows a user to select a specific ranking form. However, the user can only open forms that match
the budget year, form type, and ranking form name defined in the underlying ranking definition (VC model).
Functions
On this section, users can create new versions of ranking forms depending on the funding status of the ranking
form and the stage authorization of the user. The following restrictions apply to a user while creating a new
version of a ranking form:
● A user cannot create a new version or a copy of a ranking form that is funded.
● A user cannot access a ranking form that is in a stage for which the user has no authorization.
Ranking Table

The ranking table displays budget requests that match the FM dimension and version criteria in the Load
Version popup window. The following columns are available in this table:
● Prior Rank: ranking value from the previous version of the ranking form
● Current Rank: ranking value entered for the current version of the ranking form
● Form ID (key): the budget request form ID
● Form ID (text): the budget request form description
● Yr 1 Total Budget: the budget request total for year one
● Yr 1 Cumulative: the running total for year one for all budget requests in the ranking table
● Yr 2 Total Budget: the budget request total for year two
● Yr 2 Cumulative: the running total for year two for all budget requests in the ranking table
● Total Yr 1 & Yr 2: the total requested amount for year one and year two
● Yr 1 Comparison: the budget request total for the subset of amounts related to the comparison FM
dimensions for year one
● Cum Comp Yr 1: the running total for the year one comparison amounts
● Yr 2 Comparison: the budget request total for the subset of amounts related to the comparison FM
dimensions for year two
● Cum Comp Yr 2: the running total for the year two comparison amounts
● Total Comp Yr 1 & Yr 2: total amount for year one and year two comparison columns
● Funded: indicates if the budget request has fallen within the funded amount
Buttons
● Refresh: refreshes the data in the ranking table according to the entered current rank values.
● Fund Forms: provides a popup window where you can define budget funding levels by specifying the
available funds for each available fiscal year. The funding level (along with the rank) helps to determine
which budget requests are funded. Each budget request is then marked as funded or unfunded based on
the funding calculation.
After entering the available funding levels, the system calculates the difference between available funds
and the cumulative requested funding, and indicates the remaining balance amount for each year which
can be seen by clicking the Fund Forms button again after the initial funding.
If the ranking version currently being funded is the “official” version, as established in the Globals table,
then the budget requests that have been marked as either Funded or Unfunded become uneditable. If the
ranking version is not the “official” version, then the budget requests are marked as either Funded or
Unfunded but remain available for edits.
● Reset Funding: removes all funded and unfunded indicators for each budget request in the Ranking screen.
The funding status returns to Unassigned. If in the official ranking version, then the forms become editable
again.
● Resequencing: provides a popup screen where the currently selected budget request can be moved in with
the list by entering a new current rank.
Integration
The ranking versions must be created in master data, once established in the system. The official version can
be defined in the Global settings, in Customizing for SAP Budgeting and Planning for Public Sector.

4.3.1 Federal Ranking Form
Use
Budget requests often have to compete against each other for financing approval. To assist in this competition,
budget requests are often ranked in priority order. Ranking is an optional process that can be applied to any
budget forms that have been defined with the standard SAP Budgeting and Planning for Public Sector budget
form template. Rankings are assembled within versions at different stages. Ranking goes beyond an ordinal
scale; it is also used to develop funding lines. For example, a government may create a budget ceiling for all new
and expanded programs. The highest ranked budget requests within the budget ceiling will be funded, the
remainder eliminated or postponed until additional revenues are forecasted or produced to support expanded
funding.
Many federal public sector organizations must review budget requests that were approved for funding in
previous budget years in order to ensure that the ongoing costs for these requests are accounted for during the
current budget cycle. The Federal Ranking form supports this requirement by allowing the user to specify the
budget year when loading a ranking version. When a version is loaded using a previous budget year, the form
instances that will be loaded are restricted to budget requests created in that budget year.
Prerequisites
A new configurable setting (Inlying Years) has been introduced to the SAP Budgeting and Planning for Public
Sector global settings that can be used to limit the set of previous budget years available to the user when
loading a version using the Federal Ranking form. For example, if Inlying Years is set to 2, the user will be able to
load ranking versions for the current budget year (as configured in the SAP Budgeting and Planning for Public
Sector global settings) as well as for the two previous budget years. If Inlying Years has not been configured or
is set to the value zero, only the current budget year will be available to users when loading a version and the
federal ranking form will function exactly as the standard (non-federal) ranking form.
In addition to configuring the new Inlying Years setting, the following pieces of master data are used within the
Federal Ranking form and must exist in the system for the form to work properly.
Info Object /PBFBI/FRM_TYP FI Form type for Decision Package forms
Info Object /PBFBI/FRM_TYP RNK Form type for Ranking forms
Info Object /PBFBI/VCNAME DP2009 Form name for the budget form being ranked (stand
ard Budget Form template)
Info Object /PBFBI/VCNAME PBF_FED_RANK Form name for the Federal Ranking form
ING
Info Object /PBFBI/RULE R1 Standard Budget Form template combo edit rule
Info Object /PBFBI/PROJID 1 Represents position request records

Info Object /PBFBI/ PROJID 2 Represents expenditure request records
Process
Data for the Federal Ranking form is read from the Budget Form cube (/PBFBI/BF_CUBE) and the Ranking
cube (/PBFBI/RANKING). Data is written back to the Ranking cube only.
The Federal Ranking form has a header section and a main ranking area as described below:
Header Area Data: Current Version, Budget Year, and Stage
Functions:
● Load Version: A popup window is provided to search for ranking versions that can be
loaded by the user.
● Advance Stage: Advances the stage of the currently loaded version based on the user’s
authorizations.
● Copy: A popup window is provided to copy the current state of the currently loaded ver
sion to another ranking version. The user may choose to copy the complete history of
the loaded version or only the details of from the version’s current stage.
Main Ranking Area Contains the list of budget requests that match the criteria selected while loading the current
ranking version.
Data:
● Prior rank
● Current rank (editable)
● Form ID and description
● First fiscal year budget
● First fiscal year cumulative
● Second fiscal year budget
● Second fiscal year cumulative
● First and second fiscal years total
● Funding status
Functions:
● Refresh: Refreshes the table of budget requests.

● Resequence: Provides a popup screen where the currently selected budget request can
be moved in with the list by entering a new current rank.
● Fund forms: Update funding status based on current priority of budget requests:
○ Strict Rank – Fund budget requests in priority order based on current rank. On the
first occurrence of a request that could not be funded (based on the entered fund

ing amounts), all other requests with a lower priority will not be funded even if there
is sufficient funding amount remaining.
○ Exhaust Funds – Fund budget requests in priority order based on current rank.
When a request is encountered that cannot be funded based on the entered fund
ing amounts, the request is set to not funded and lower priority requests will con
tinue to be funded if sufficient funding amounts remain.
● Reset funding: Resent the funding status of all budget requests to Unassigned.
● Accept prior ranks: Initialize the current rank for each budget request to its prior rank. A
budget request’s prior rank is the rank for that budget request from the previous stage
of the current version.
Technical Details
The following BI-IP objects are used in the Federal Ranking form and must be installed and activated for the
Multi Provider /PBFBI/BF_RANK N/A
Cube /PBFBI/BF_CUBE N/A Used for reading data only
Cube /PBFBI/RANKING N/A Used for reading and writing data
Aggregation /PBFBI/A_RANK03 N/A Aggregation level for standard PBF ranking

Level forms
Query /PBFBI/ /PBFBI/F_RANK03_07 Query for Federal Ranking form

A_RANK03_QI001
Planning Func /PBFBI/UNAS /PBFBI/F_RANK03_11 Change funding status of all forms in the data
tion SIGN_FORM slice
Planning Func /PBFBI/ /PBFBI/F_RANK03_11 Stores yearly funding amounts for use while
tion STORE_AMOUNTS funding
Planning Func /PBFBI/RANK03_PFX02 /PBFBI/F_RANK03_11 Assign a new current rank to a given budget
tion request and adjust the current rank of all af
fected budget requests appropriately
Planning Func /PBFBI/ RANK03_PFX01 /PBFBI/F_RANK03_11 Fund/Unfund Form Instances

tion
Planning Func /PBFBI/RANK03_PFC02 /PBFBI/F_RANK03_08 Copy Prior Ranks

tion
Planning Func /PBFBI/RANK03_PFC01 /PBFBI/F_RANK03_09 Copy version with history from all previous
tion stages

Planning Func /PBFBI/RANK03_PFC01 /PBFBI/F_RANK03_10 Copy version without history from previous
tion stages
4.4 Planning Form
Definition
Planning form is a combination of a Web Dynpro header and workspace, and a Visual Composer (VC) layout to
capture performance measurement data.
Use
A planning form captures an organization’s strategic objectives such as mission, goals, objections, and
performance measure data by financial management (FM) area and fund center.
To view and maintain planning forms, choose Budget Formulation Planning Forms .
Structure
The strategic planning form contains a header and workspace area. The header requires a user to select a FM
area and fund center and then load the strategic planning data or save any data changed in the workspace. The
workspace is used to enter the strategic planning text and data.
The planning form consists of a header and workspace area.
In the header area, users can choose the FM area and the fund center to create a strategic plan.
● Load: loads the data into the workspace for the selected FM area and fund center.
● Save: saves the data in the workspace.
The workspace area displays relevant comment types into which users can enter the strategic plans for the
organization. Users can also specify the measurement criteria for objectives that are measurable.
The following fields allow users to maintain the measurement criteria:
● Measure Key: unique code for the measure

● Measure Description: text description of the measure
● Unit: unit of measure of the measure
● Target Value: target value for the measure

Integration
The Strategic Plan (technical name: MISSION-GOAL) comment type tree settings determine the behavior of
the workspace, specifically if the workspace level is measurable allowing performance data information to be
added. To learn how to create comment type trees, see Creating a Comment Type Tree [page 113].

5 Budget Development
1. The customer is expected to be on NW 7.4 SP07 or higher. If the installed SP is SP07, it is mandatory to
have the corrections in OSS Note 1716687 and its dependent notes implemented before installing SAP
Budgeting and Planning for Public Sector.
2. The budget development form templates have to be copied and adapted based on the customer’s data
volume, performance, and sizing considerations.
3. To customize authorizations for the adapted forms please refer to the SAP Budgeting and Planning for
Public Sector Master Guide security secution.
4. To customize currency translation/conversion for the adopted forms please refer to one of the following:
1. SAP Budgeting and Planning for Public Sector Installation guide, section Post-Implementation
Currency Conversion
2. SAP Budgeting and Planning for Public Sector Upgrade Master Guide, post-upgrade steps
5. All delivered budget development form templates need specific master data values as outlined in the pre-
requisites section. These default master data values will be created using the /PBFBI/CREATE_MD_SL_01
(transaction /PBFBI/MD_SL01) program.
5.1 Base Budget Adjustment Form
Use
The Base Adjustment form is designed to allow departmental users to adjust their non-personnel operating
budget expenditures, some personnel (non-PEP related) operating budget expenditures, and revenues
between commitment items within a department as part of the budget development process. Prior-year one-
time adjustments will also be shown as a reduction. While the intent of the base adjustment form is not to
change the total budget amount, it requires that the changes net to zero.
As described in the Transfer/Redistribution form, amounts displayed as the Revised Base Budget in the Base
Adjustment form are the combination of the current year adopted budget plus base adjustment amounts plus
changes entered in the Transfer/Redistribution form.
If amounts are entered in the Transfer/Redistribution form after the Base Adjustment form has been used, the
respective Base Adjustment form needs to be re-opened and saved to incorporate the base adjustment
amounts into the revised base budget.
This form is developed based on the assumption that the base budget is the current year adopted budget.
However, the base budget can be established with one of the following scenarios as well:
1. Current fiscal year adopted budget

2. Current fiscal year inflated actuals
3. Weighted average of last three year actual

52 INTERNAL Budget Development
Prerequisites
Object Type Object Name Value Source Comments
Info Object /PBFBI/FRM_TYP BB Form Type – Base

Budget
Info Object /PBFBI/VCNAME FD03 /PBFBI/BF_CUBE Base Adjustment form
Info Object /PBFBI/VCNAME FD04 /PBFBI/BF_CUBE Base Adjustment Rev

enue tab
Info Object /PBFBI/RULE SL1 Budget Development

Combo Edit Rule 1 –
Typically used for de
fining combo edit rule
for overall form
Info Object /PBFBI/RULE SL2 Budget Development

Combo Edit Rule 2 –
Typically used for de
fining combo edit rule
for individual tabs that
have different settings
that are not satisfied
by Rule 1.
Info Object /PBFBI/PU VALTP F1 /PBFBI/SL_C01 (*) Represents Adopted

Budget Amount
Info Object /PBFBI/PU VALTP G1 /PBFBI/SL_C02 (*) Represents Yea-To-

Date Inflated Amount
Info Object /PBFBI/PU VALTP G2 /PBFBI/SL_C02 (*) Represents Three Year

Average Amount
Info Object /PBFBI/PU VALTP A2 /PBFBI/BF_CUBE Represents Base Ad

justed Amount
Info Object /PBFBI/PU VALTP A3 /PBFBI/BF_CUBE Represents Revised

Base Amount
Info Object /PBFBI/PU VALTP A4 /PBFBI/SL_C02 (*) Represents One Time

Removal
Info Object /PBFBI/PU VALTP A5 /PBFBI/SL_C02 (*) Represents Annual

Amount
Info Object /PBFBI/PU VALTP A6 /PBFBI/BF_CUBE (**) Represents Transfer &

Redistribution Form

Budget Development INTERNAL 53
Info Object /PBFBI/PU VALTP A7 /PBFBI/BF_CUBE Represents Initial Base
Amount
Info Object /PBFBI/PROJID 2 Represents Expenses
Info Object /PBFBI/PROJID 3 Represents Revenue
Hierarchy FUND_CT_HIER Used for Fund Center

(Info Object /PBFBI/
FUND_CT)
Hierarchy CMMT IT HIERARCHY Used for Commitment

Item (Info Object /
PBFBI/CMMT_IT)
Hierarchy /PBFBI/STAGE 111, 112, 115, 116 Stages for base adjust
ment form. The BC
sets program will cre
ate the stages and as
sign them to the form
as explained in the
special notes section.
(*) The /PBFBI/SL_C01 and /PBFBI/SL_C02 cubes are populated during a year-end process at the end of the
budgeting cycle.
(**) The amounts for the transfer and redistribution come from the Transfer and Redistribution forms that exist
in the system. Therefore these types of adjustments are not entered directly in the Base Budget Adjustment
form but must be entered and saved in a Transfer and Redistribution form. Data written from those forms
(value type A6) will be read by the Base Budget Adjustment form.
Process
Technical Overview
Data for the Base Budget Adjustment form is read from and written to the Budget Form cube.
The Base Budget Adjustment form has a header section and several tabs as described below:
Header Area The major categorizations of the decision package are found
here, such as Form ID and Description, FM dimensions,
Stage, and Funding status.

Expenses Tab Lists the various expenditure items for the base budget ad
justments. Data includes FM dimensions and one editable
key figure, the base adjustment amount. Other key figures
that are displayed are:
● Adopted budget/YTD Inflated/3-Year Average (one of

these will be displayed depending on user selection)
● One-time removals
● Annualization
● Transfer/redistribution
● Initial base budget calculated as: Adopted budget/YTD
Inflated/3 Year Average + One Time Removal + Annuali
zation + Changes from Transfer/Redistribution Form
● Base adjustment (editable)
● Revised base budget calculated as: Initial Base Budget
+ Base Adjustment
Functions:
● Delete
● Line text
● Adopted budget – displays and uses the adopted
budget values
● YTD inflated – displays and uses the YTD inflated
● 3-year average – displays and uses the 3-year averages

Revenues Tab Lists the various expenditure items for the base budget ad
justments. Data includes FM dimensions and one editable
key figure, the base adjustment amount. Other key figures
that are displayed are:
● Adopted budget/YTD Inflated/3-Year Average (one of

these will be displayed depending on user selection)
● One time removals
● Annualization
● Transfer/redistribution
● Initial base budget calculated as: Adopted Budget + One
Time Removal + Annualization + Changes from Trans
fer/Redistribution Form
● Base adjustment (editable)
● Revised base budget is calculated as: Initial Base
Budget + Base Adjustment
Functions:
● Delete
● Line text
● Adopted budget – displays and uses the adopted
budget values
● YTD inflated – displays and uses the YTD inflated
● 3-year Average – displays and uses 3-year averages
Description Tab The Adjustment Description, Budget Department Review

Notes, and Publication Adjustment Description text areas
are available.
Attachments Attachments can be uploaded to the form.
Technical Details
Multi Provider /PBFBI/SL_M01
/PBFBI/SL_C01
/PBFBI/SL_C02
Query & Filter /PBFBI/A_SLM012_QI001 (Filter / Expense Tab

PBFBI/F_SLM012E)
Query & Filter /PBFBI/A_SLM012_QI002 (Filter / Revenue Tab

PBFBI/F_SLM012R)
Planning Function & Filter /PBFBI/PF_SLM012_D Delete data Base Budget form

Planning Function & Filter /PBFBI/PF_SLM012 One-time removal and annualization
Planning Function & Filter /PBFBI/SLM012_CURTR (Filter / Expense Tab Currency Translation
PBFBI/F_SLM012E)
Planning Function & Filter /PBFBI/SLM012_CURTR (Filter / Revenue Tab Currency Translation
PBFBI/F_SLM012R)
DSO /PBFBI/SL_O04 DSO to store the current button under

which user entered or saved the data
5.2 Capital
5.2.1 Capital Form
Use
Capital planning is an iterative process. Capital projects typically require preliminary funding to analyze project
scope, address site locations, and establish comprehensive project plans for future phases. Just as
importantly, the Capital Budget Form in SAP Budgeting and Planning for Public Sector will support the unique
needs of participants in the capital programming process. Departments will be responsible for requesting,
planning, and justifying capital projects, while the Department of Engineering will retain its responsibility for
managing design and construction.
The Capital Budget Form is designed to allow Capital Program end-users to enter or adjust their respective
capital project budgets (in addition to publication text box requirements and anticipated personnel
expenditures/non-personnel expenditures operating impacts).
 Note
All operating impacts are entered separately from the Decision Package form, since the capital budget
amounts are informational only and do not feed into the decision package directly.
 Recommendation
Copy the default Capital Form template provided in SAP Budgeting and Planning for Public Sector and
change the copy to create capital form definitions to meet individual customer requirements for the budget
formulation process.
The capital form will be used by the end user to submit capital requests. These capital requests will be reviewed
by the Capital Improvements Program Review and Advisory Committee (CIPRAC). CIPRAC provides a high-
level review of the prioritization process for the entire CIP. The committee ensures conformance with the

mayor's and council's policy goals, departmental priority needs, and anticipated funding sources. CIPRAC
performs the following:
● Facilitates project coordination to increase cost effectiveness and minimize community disruptions,
including long-term planning for public capital needs
● Reviews and approves multi-year CIP plans
● Provides key leadership, authority, oversight, and coordination for the CIP
● Assigns the following responsibilities to the appropriate departments or offices:
○ Identify, leverage, and optimize funding sources
○ Streamline and improve coordination and functionality of CIP-related processes
○ Review and assess efficiency of required processes
○ Work with the Independent Budget Analyst to identify ways to streamline the process
● Ensures that the financial/accounting system continues to support the needs of the CIP process
● Coordinates various responsibilities of service departments
● Makes certain that projects are reviewed for conformance with the General Plan and Community Plans
CIPRAC's goal is to ensure that projects are ranked on a City-wide perspective, balancing needs and budget
with policy objectives. The Committee communicates with departments and other stakeholders about the CIP
process and projects.
Capital forms are used to capture budget expenditure, revenue amounts, finance reservation for current and
upcoming years ,and new position requests by financial management (FM) dimensions. The capital form allows
text justifications at the request and line level, new positions, client-defined request attributes through the use
of form elements, and performance budgeting elements (mission, goals, objectives, and measures). SAP
Budgeting and Planning for Public Sector provides a single source for all an organization’s budget formulation
processes and can be configured to meet the requirement for each.
Users are allowed to maintain one additional currency above the FM area currency on capital forms. When the
user creates a new budget form, he or she will have to choose a currency that he or she wants to work with on
this form.
The data on each of the tabs (Expenses, Revenues, Positions, and Finance Schedule) will then be stored in form
currency selected by the user.
Currency translation type /PBFBI/BFC has been used for Capital forms. All the currency conversion in the
capital form will take place based on the exchange rate type maintained in this currency translation type.
Authorized users can access capital forms for SAP Budgeting and Planning for Public Sector by choosing PBF
State & Local Capital .
 Recommendation
The delivered Capital forms template in SAP Budgeting and Planning for Public Sector contains currency
translations. Customers who only work with a single currency throughout their budgeting process, can
remove the currency translation in their custom capital forms template by following the steps mentioned in
note number 1650724.

Prerequisites
● You have defined the following SAP Budgeting and Planning for Public Sector–specific settings:
○ Comment Types
○ Comment Type Trees
○ Form Elements
○ Stages
○ Combination Edit Rules
● You have loaded the data from ECC to BW system for:
○ Current Budget
○ Expenditure
○ Encumbrance
● You have supporting Encumbrance Documents to be uploaded in the form.
● You have set up the following master data:
Info Object /PBFBI/FRM_TYP BB Form type for Capital forms
Info Object /PBFBI/FRM_TYP RNK Form type for Capital form tabs
Info Object /PBFBI/VCNAME FD12 Form name for the form being ranked (Capital form)
Info Object /PBFBI/VCNAME FD12_TAB_EXP Form name for the Capital Expense Tab
Info Object /PBFBI/VCNAME FD12_TAB_REV Form name for the Capital Revenue Tab
Info Object /PBFBI/VCNAME FD12_TAB_FS Form name for the Capital Finance Schedule Tab
Info Object /PBFBI/RULE SL1 Budget Development Rule 1
Info Object /PBFBI/PROJID 2 Represents expenditure request records
Info Object /PBFBI/PROJID 4 Represents finance schedule request records
Process
Technical Overview
The default Capital form template provides a base to create capital requests. The template contains a header
area to capture information for the entire request and tab areas that allow users to enter request information
broken down into categories.

The Capital form has a header section and a main ranking area as described below:
Header Area The header of a capital form definition contains FM dimensions, Currency, capital re
quest form ID and description and stages. The form ID is system generated and the form
description is user defined.
Functions:
● Search: Allow the users to search the form IDs based on the FM dimensions or by
the description
● New: Allows users to create new form IDs
● Edit: Allows users to edit the description of the form and adjust the amounts
● Advance Stage: Allows the form to be forwarded to next department by advancing
the stage
Funding The following standard FM dimensions can be used to define the scope of a budget re
quest:
● FM Area
● Fund Center
● Fund
● Funded Program
● Grant
● Functional Area
Expense On the Expense tab, you enter non-position-related costs associated with the request.
For example, supplies and materials, contractual services, and equipment. The tab lay
out, or entry grid, contains:
● Fund: fund code for the capital request line.

● Fund Center: fund center code for the capital request line.
● Commitment Item: commitment item code for the capital request line.
● Capital FY: budget request amount for the current year.
● Capital FY1: budget request amount for the year two.
● Capital FY2: budget request amount for the year three.
● Capital FY3: budget request amount for the year four.
● Capital FY4: budget request amount for the year five.
Functions:
● Add: Add a new row

● Copy: Copy the existing row to new row along with the FM dimensions
● Delete: Delete the currently selected row
● Line Text: Enter the justification for every row entered

Revenue On the Revenue tab, you enter estimated revenues such as taxes, grants, service fees,
and other sources of revenue. The tab layout, or entry grid, contains:
● Fund
● Fund Center
● Commitment Item
● Capital FY Total Base Budget
● Capital FY1 Total Base Budget
Functions:

● Delete: Deletes the currently selected row
● Line Text: Allows the users to enter the justification for every row entered

Position On the Positions tab, you enter requests for new positions by providing relevant informa
tion about the job, the organizational grouping, pay level, percentage of compensation,
and counts. The system then calculates the cost of the requested position using
● Position: System generates a position number when you click New

● Job: Job code assigned to a requested position
When you enter a job code and click Job Defaults, the system displays the associated
information for Country Grouping, Pay Scale Type, Pay Scale Area, ES Grouping CAP, Pay
Scale Group, Pay Scale Level, Performance Period, and Performance Start Period from
● Fund Center: fund center code defined for the position request
● Start Month/Year: Starting month and year for the position request
● End Month/Year: Ending month and year for the position request
● Number of Positions: Position count for the position request
● Report FTE: user entered FTE for the position request
● Benefit %: benefit percentage for the position request
● Salary %: salary percentage for the position request
● Salary: Override salary amount for the position request. This amount will be used in
the calculation of costs instead of the amount in the pay level table
● Year 1 Costs: Position request costs calculated for year one
● Year 2 Costs: Position request costs calculated for year two
● Year 3 Costs: Position request costs calculated for year three
● Year 4 Costs: Position request costs calculated for year four
● Year 5 Costs: Position request costs calculated for year five
Functions:
New: Prepopulates the new position ID –
Users should enter a valid job. When job defaults is clicked, all the pay attributes of the
job will be defaulted to this position. The user should even enter the salary and benefit
percentage.
● Copy: Copies the existing position details to new position

● Delete: Deletes the currently selected position from cube
● Calculate: Calculates the monthwise cost for the position entries and displays the
annual amount in the respective columns for a given fiscal year
● Save: Saves the monthwise and annual records in the planning buffer to the respec
tive cubes

Financial Schedule On the Financial Schedule tab, you enter year to date project data including display of
expenses, budget, and data entry fields for current and future budget.
● Fund: fund code for the capital request line.

● Fund Center: Fund center code for the capital request line
● Commitment Item: Commitment item code for the capital request line
● Current Budget: Budget amount available for the current budget year
● Expended: Budget amount already spent
● Encumbered: Amount of money that is required to spend on a stated thing in future
● Continuing Appropriation: Obtained by deducting expended and encumbered
amount from current budget
● Subtotal: Sum of Expended, Encumbered, and Continuing Appropriation
● Capital FY: Budget amount reserved for year one
● Capital FY1: Budget amount reserved for year two
● Capital FY2: Budget amount reserved for year three
● Capital FY3: Budget amount reserved for year four
● Capital FY4: Budget amount reserved for year five
Functions:

● Delete: Delete the currently selected row
● Line Text: Allow the users to enter the justification for every row entered
Narrative On the Narrative tab, you provide a place for users to enter required text to justify budg
etary requests, explain impacts of the decisions, track decisions, and relate budgetary
expenditures to programmatic operations.
Attachments On the Attachments tab, you can attach supporting documents for the budget request.
Technical Details
Cube /PBFBI/BF_CUBE
Cube /PBFBI/HRPJ_R01
Cube /PBFBI/SL_C01
Aggregation Level /PBFBI/A_SLM013

/PBFBI/
Query & Filter /PBFBI/F_SLM016 Expense
A_SLM013_QI001
/PBFBI/
Query & Filter /PBFBI/F_SLM016R Revenue
A_SLM013_QI002
/PBFBI/
Query & Filter /PBFBI/F_SLM021 Position
A_SLM02_QI002
/PBFBI/
Query & Filter /PBFBI/F_SLM016F Financial Schedule
A_SLM013_QI003
Planning Function & Fil

/PBFBI/PF_SLM021_D1 /PBFBI/F_SLM021_D Delete Position
ter
Planning Function & Fil

/PBFBI/PF_SLM021_D2 /PBFBI/F_SLM021_D Delete Position
ter
Planning Function & Fil /PBFBI/ /PBFBI/

Calculate
ter PF_SLM021_POS F_SLM021_POS
5.2.2 Capital Ranking Form
Use
Capital budget requests often have to compete against each other for financing approval. To assist in this
competition, capital budget requests are often ranked in priority order. Ranking is an optional process that can
be applied to any budget forms that have been defined with the Capital form template. Rankings are assembled
within versions at different stages. Ranking goes beyond an ordinal scale, it is also used to develop funding
lines. For example, a government may create a budget ceiling for all new and expanded programs. The highest
ranked budget requests within the budget ceiling will be funded, the remainder eliminated or postponed until
additional revenues are forecasted or produced to support expanded funding.
The ranking process supports the dynamic assignment and change of relative rankings for each capital form
(project), displays the rankings on the screen, and generates a cumulative total of the budgetary requests.
Ranking can be re-ranked as many times as needed, and the system will re-sequence the capital requests
based on the assigned rank. The funding levels can be changed after they have been established by clicking the
Reset Funding button.

Prerequisites
The following pieces of master data are used within the Capital Ranking form and must exist in the system for
the form to work properly.
Info Object /PBFBI/FRM_TYP FI Form type for Capital forms
Form name for the form being ranked (Capi

Info Object /PBFBI/VCNAME FD12 tal form)
Info Object /PBFBI/VCNAME FD17 Form name for the Capital Ranking form
Process
Data for the Capital Ranking form is read from the Budget Form cube (/PBFBI/BF_CUBE) and Ranking cube (/
PBFBI/RANKING). Data is written back to the Ranking cube only.
The Capital Ranking form has a header section and a main ranking area as described below:
Header Area Data: Current version and Stage
Functions:
● Load Version: Popup window is provided to search for

ranking versions that can be loaded by the user.
● Copy: Popup window is provided to copy the current
state of the currently loaded version to another ranking
version. The user may choose to copy the complete his
tory of the loaded version or only the details of from the
version’s current stage.
● Advance Stage: Advance the stage of the currently
loaded version based on the user’s authorizations.

Main Ranking Area Contains the list of Capital requests that match the criteria
selected while loading the current ranking version.
Data:
● Prior rank
● Current rank (editable)
● Budget Year Positions
● Year 1 Budget
● Year 1 Cumulative
● Year 2 Budget
● Year 3 Budget
● Year 4 Budget
● Year 5 Budget
● Funding status
Functions:

● Resequence: Provides a popup screen where the cur
rently selected budget request can be moved in with the
list by entering a new current rank.
● Fund forms: Update funding status based on current
priority of budget requests
○ Strict Rank – Fund budget requests in priority or
der based on current rank. On the first occurrence
of a request that could not be funded (based on the
entered funding amounts), all other requests with a
lower priority will not be funded even if there is suf
ficient funding amount remaining.
○ Exhaust Funds – Fund budget requests in priority
order based on current rank. When a request is en
countered which cannot be funded based on the
entered funding amounts, the request is set to not
funded and lower priority requests will continue to
be funded if sufficient funding amounts remain.
● Reset funding: Reset the funding status of all budget
requests to Unassigned.
● Accept prior ranks: Initialize the current rank for each
budget request to its prior rank. A budget request’s
prior rank is the rank for that budget request from the
previous stage of the current version.
Technical Details

The following BI-IP objects are used in the Capital Ranking form and must be installed and activated for the
Multi Provider /PBFBI/SL_RANK N/A
Aggregation Level /PBFBI/A_SLRANK N/A Aggregation level for ranking
Query /PBFBI/A_SLRANK_QI001 /PBFBI/F_SLRANK Query for Capital Ranking form
Planning Function /PBFBI/PF_SLRANK_M06 /PBFBI/F_SLRANK5 Change funding status of all forms in the
data slice
Planning Function /PBFBI/PF_SLRANK_M05 /PBFBI/F_SLRANK5 Stores yearly funding amounts for use
while funding
Planning Function /PBFBI/PF_SLRANK_M04 /PBFBI/F_SLRANK5 Assign a new current rank to a given

capital request and adjust the current
rank of all affected capital requests ap
propriately
Planning Function /PBFBI/PF_SLRANK_M03 /PBFBI/F_SLRANK5 Fund/Unfund Form Instances
Planning Function /PBFBI/PF_SLRANK_M02 /PBFBI/F_SLRANK4 Copy prior ranks
Planning Function /PBFBI/PF_SLRANK_M01 /PBFBI/F_SLRANK2 Copy version with history from all previ
ous stages
Planning Function /PBFBI/PF_SLRANK_M01 /PBFBI/F_SLRANK3 Copy version without history from previ
ous stages
5.3 Decision Package
5.3.1 Decision Package Adjustment Form
Use
The decision package process will be utilized to support new initiatives and reductions. A decision package is a
proposal to modify (incrementally) an agency’s base budget or to incorporate a base budget modification

approved during the current fiscal year. Each decision package details the costs, associated revenues, and
justification in one budget action. Decision packages incorporate the ability to request funds and identify
funding sources. The action proposed in each decision package is a discrete unit that can be evaluated on its
own merit, independently of any other proposals. Decision packages can be grouped by initiatives and can be
ranked and prioritized against alternatives. Changes to decision packages can be tracked in an audit trail.
Decision packages can be ranked by the Decision Package Ranking form. Decision packages are selected for
ranking based on FM dimensions saved on the Decision Package forms.
Prerequisites
The following pieces of master data are used within the Decision Package form and must exist in the system for
the form to work properly.
Info Object /PBFBI/FRM_TYP FI
Info Object /PBFBI/VCNAME FD05
Info Object /PBFBI/RULE SL1 Except for Revenue
Info Object /PBFBI/RULE SL2 For Revenue
Info Object /PBFBI/PUVALTP A1 Represents Plan Budget Amounts (*)
Info Object /PBFBI/PUVALTP A8 Represents On-Going Cost Amounts (*)
Info Object /PBFBI/PUVALTP A9 Represents Full Year Cost Amounts (*)
Info Object /PBFBI/PUVALTP D1 Represents One Time Adjustment Amounts (*)
Hierarchy /PBFBI/FUND_CT FUND_CT_HIER Used for Fund Center
CMMT IT HIER
Hierarchy /PBFBI/CMMT_IT Used for Commitment Item
ARCHY
(*) These info cubes and key figures are populated during a year-end process. When the budgets are rolled to
begin the next-year budget cycle, there is a year-end process to populate data in these cubes. There are a
series of planning sequences and planning functions used to prepare data for the start of a new budget cycle.
Please refer to the documentation for the year-end process for details on these pre-requisites.
Process
Data for the Decision Package form is read and written to the /PBFBI/BF_CUBE info cube and periodic records
for positions to /PBFBI/HRPJ_R01.

The Decision Package form has a header section and several tabs as described below:
Header Area The major categorizations of the decision package are found here.
Data:
● Form ID
● Description
● Stage
● Funding status
Functions:
● Search: Popup window is provided to search for existing decision package form.
● New: Popup window is provided to enter FM dimensions, currency, and description to create
new decision package form.
● Edit: Edit the currently loaded Decision Package form.
● Advance Stage: Advance the stage of the currently loaded Decision Package form based on the
user’s authorizations.
Overview An overview of the Decision Package Adjustment form, available without navigating to the individual
sections like expenses, revenue, and positions. The overview of the Decision Package Adjustment
form is shown using charts and a table with all the consolidated values.
Funding Tab FM dimensions, Currency, and Description. Note the dimension data is entered on a popup screen
when creating a Decision Package form.
Expenditures Tab Lists the various expenditure items for the decision package.
Data (all fields are editable):
● Fund Center
● Functional Area
● Commitment Item
● BY On-going
● BY One Time cost
● BY Full Year Cost
● Budget Year + 1
Data can be changed or deleted.
Functions:
● Add: Add a new line item in expense tab.

● Delete: Delete the selected line item row from the expense tab.
● Line Text: Enter a line item description for the selected line item row from the expense tab.
Revenues Tab Lists the various revenue items for the decision package. Data includes FM dimensions, and four key
figures (all fields are editable):
● Ongoing revenues

● One-time revenues
● BY full year revenue
● Budget year + 1
Data can be changed or deleted.
Functions:
● Add: Add a new line item in revenue tab.

● Delete: Delete the selected line item row from the revenue tab.
● Line Text: Enter a line item description for the selected line item row from the revenue tab.
Positions Tab Each line item has the following:
● Fund Center
● Position
● Job
● Start Date
● End Date
● Country Grouping
● Pay Scale Area
● Pay Scale Type
● Pay Scale Group
● Pay Scale Level
● Performance Period
● Performance Start Period
● Number of Positions
● Benefit %
● Salary %
● Salary
● Yr 1 Cost
● Yr 2 Cost
Functions:
● New: Provide position information. The information can be defaulted from a selected job. After
providing data user presses OK and data is populated in the item row.
● Edit: Edit existing position information.
● Copy: View the values copied from a selected row. After making necessary changes, the user
clicks OK and data is populated to a new row in the position table.
● Delete: Delete the selected line item row from the position tab.
● Calculate: A planning function is used to calculate the position costs and posts the amounts to
the Yr1 cost and the Yr2 cost. Yr1 points to budget year. These costs fields are not editable. In
order to adjust total costs, other position data or salary can be changed and re-calculated to
change the total costs.

Description Tab Three text areas are defined here: Adjustment Description, Publication Adjustment Description, and
Impact of Not Funding. At stage 123 Budget Department Review Note is also available.
Technical Details
Multi Provider /PBFBI/SL_M01, N/A
/PBFBI/SL_M02
Cube /PBFBI/BF_CUBE, N/A Input and Output
/PBFBI/HRPJ_R01
Aggregation Level /PBFBI/A_SLM02 N/A Position query
Aggregation Level /PBFBI/A_SLM012 N/A Expense and Revenue query
Aggregation Level /PBFBI/A_SLM021 N/A Position planning functions.
Query & Filter /PBFBI/ /PBFBI/ Expense Tab

A_SLM012_QI004 F_SLM014E1
Query & Filter /PBFBI/ /PBFBI/ Revenue Tab

A_SLM012_QI005 F_SLM014R1
Query & Filter /PBFBI/ /PBFBI/F_SLM02 Position Tab

A_SLM02_QI001
Query & Filter /PBFBI/ /PBFBI/ Overview Tab

A_SLM012_OVER_V F_SLM014_O
IEW
Planning Function /PBFBI/ /PBFBI/ Delete Position

PF_SLM021_D1 F_SLM021_D
Planning Function /PBFBI/ /PBFBI/ Delete Position

PF_SLM021_D2 F_SLM021_D
Planning Function /PBFBI/ /PBFBI/ Calculate Position costs

PF_SLM021_POS F_SLM021_POS

5.3.2 Decision Package Ranking Form
Use
Decision packages are incremental budget requests that often have to compete against each other for
financing approval. To assist in this competition, decision packages are often ranked in priority order. Ranking
is an optional process that can be applied to any budget forms that have been defined with the decision
package template. Rankings are assembled within versions at different stages. The Decision Package Ranking
form is used to assign priority ranks to budget requests, compare request amounts by Funds Management
(FM) dimension combinations, and then determine which requests should be funded by defining funding levels.
The ranking process supports the dynamic assignment and change of relative rankings for each decision
package, displays the rankings on the screen, and generates a cumulative total of the budgetary requests.
Ranking can be re-ranked as many times as needed, and the system will re-sequence the budget requests
based on the assigned rank. The funding levels can be changed after they have been established with the Reset
Funding button.
Prerequisites
The following pieces of master data are used within the Decision Package Ranking form and must exist in the
system for the form to work properly.
Info Object /PBFBI/FRM_TYP FI Form type for Decision Package forms
Info Object /PBFBI/VCNAME FD05 Form name for the budget form being ranked (De
cision Package form)
Info Object /PBFBI/VCNAME FD11 Form name for the Decision Package Ranking
form
Process
Data for the Decision Package Ranking form is read from the Budget Form cube (/PBFBI/BF_CUBE) and the
Ranking cube (/PBFBI/RANKING). Data is written back to the Ranking cube only.

The Decision Package Ranking form has a header section and a main ranking area as described below:
Header Area Data: Current version and stage
Functions:
● Load Version: Search for ranking versions that can be loaded by the user.
● Copy: Copy the current state of the currently loaded version to another ranking version. The
user may choose to copy the complete history of the loaded version or only the details of
from the version’s current stage.
● Advance Stage: Advance the stage of the currently loaded version based on the user’s au
thorizations.
Main Ranking Area Contains the list of Decision Package that match the criteria selected while loading the current
ranking version.
Data:
● Prior rank
● Current rank
● Budget Year Positions
● Budget Year Expenditures
● Budget Year Cumulative
● Budget Year + 1 Net
● Funding status
Functions:

● Resequence: Display the currently selected budget request, which can be moved in with the
list by entering a new current rank.
● Fund Forms: Update funding status based on current priority of budget requests
○ Strict Rank – Fund budget requests in priority order based on current rank. On the first
occurrence of a request that could not be funded (based on the entered funding
amounts), all other requests with a lower priority will not be funded even if there is suf
ficient funding amount remaining.
○ Exhaust Funds – Fund budget requests in priority order based on current rank. When a
request is encountered which cannot be funded based on the entered funding
amounts, the request is set to not funded and lower priority requests will continue to
be funded if sufficient funding amounts remain.
● Reset funding: Resent the funding status of all budget requests to Unassigned.
● Accept prior ranks: Initialize the current rank for each budget request to its prior rank. A
budget request’s prior rank is the rank for that budget request from the previous stage of
the current version.
Technical Details
The following BI-IP objects are used in the Decision Package Ranking form and must be installed and activated
for the form to work properly.

Multi Provider /PBFBI/SL_RANK N/A
Aggregation /PBFBI/A_SLRANK N/A Aggregation level for ranking

Level
Query /PBFBI/ /PBFBI/F_SLRANK1 Query for Decision Package Ranking form

A_SLRANK_QI002
Planning Func /PBFBI/ /PBFBI/F_SLRANK5 Change funding status of all forms in the
tion PF_SLRANK_M06 data slice
Planning Func /PBFBI/ /PBFBI/F_SLRANK5 Stores yearly funding amounts for use while
tion PF_SLRANK_M05 funding
Planning Func /PBFBI/ /PBFBI/F_SLRANK5 Assign a new current rank to a given budget
tion PF_SLRANK_M04 request and adjust the current rank of all af
fected budget requests appropriately
Planning Func /PBFBI/ /PBFBI/F_SLRANK5 Fund/Unfund Form Instances

tion PF_SLRANK_M03
Planning Func /PBFBI/ /PBFBI/F_SLRANK4 Copy Prior Ranks

tion PF_SLRANK_M02
Planning Func /PBFBI/ /PBFBI/F_SLRANK2 Copy version with history from all previous
tion PF_SLRANK_M01 stages
Planning Func /PBFBI/ /PBFBI/F_SLRANK3 Copy version without history from previous
tion PF_SLRANK_M01 stages
5.4 Multi-year Projection Form
Use
The Multi-Year Projection form is intended to be an ongoing planning tool that will be utilized in each year’s
budget process. It provides an early perspective of the projected budgetary gap for the coming year and allows
budgeting staff to analyze corrective actions needed to address these gaps before beginning the budget
process. Additionally, it serves as the basis for longer term planning and fiscal decision making throughout the
year.

The multi-year financial forecast is a process that produces a comprehensive, long-range analysis of revenues
and expenditures. This model can be used to analyze major decisions as they are being considered and should
be updated to assist with the annual budget process.
Process
Data for the multi-year projection utilizes data from different cubes during different processes. Create mode:
When a Multi-Year form is initially created data is read from the following:
● Info cube /PBFBI/SL_C01 – Actual/Previous year budget

● Info cube /PBFBI/SL_C02 – Annualized aggregated projection scenario data
● Info cube /PBFBI/SL_C03 – Previous year budget data (Historical)
● Data Store Object /PBFBI/SL_O05 – Inflationary Rate
See the prerequisite section below for details regarding this data. Upon saving the form, the data is saved to
the Info cube /PBFBI/BF_CUBE.
Edit mode: Data is read and written from Info cube /PBFBI/BF_CUBE.
The Multi-year Projection form has a header section and several tabs as described below:
Header Area Form ID, Description, Stage, Funding status.
Overview An overview of the Multi-Year Projection form without the need to navigate
to individual sections like expenses and revenue. The overview of the
Multi-Year Projection form is shown using charts and a table with all the
consolidated values.
Funding Tab FM dimensions, Currency and Description. Note the dimension data is en
tered on a popup screen when creating a Multi-year Projection.
Expenses Tab Lists the various expense figures for the multi-year projection. FM dimen
sions at the line item level include Fund Center, Functional Area and Com
mitment item. Eight key figures are presented:
● Prior Year Actuals

● Adopted Budget
● Revised Budget
● Projection Year 1 (calculated initially, but is editable by the user)

Revenue Tab Lists the various revenue figures for the multi-year projection. FM dimen
sions at the line item level include Fund Center, Functional Area and Com
mitment item. Eight key figures are presented:

● Adopted Budget
● Revised Budget
Description Tab Two text areas are defined: Forecast Description and Publication Forecast
Description. At stage 225 Budget Department Review Note is available.
Attachment Tab Documents can be uploaded and attached to the form
Technical Details
Multi Provider /PBFBI/SL_M01 .
Cube /PBFBI/BF_CUBE Input and Output (all data except key figures below)
/PBFBI/SL_C01 Read only (Prior Year Actuals)
/PBFBI/SL_C02 Read only (YTD Inflated)
/PBFBI/SL_C03 Read only (Adopted Budget)
DSO /PBFBI/SL_O05 Multi-Year Projection Inflationary Rates
Aggregation Level /PBFBI/A_SLM011 .
Query & Filter /PBFBI/A_SLM011E1_QI004 (Filter / Expense Tab

PBFBI/F_SLM011E)
Query & Filter /PBFBI/A_SLM011_OVERVIEW Overview Tab
Query & Filter /PBFBI/A_SLM011R1_QI004 (Filter / Revenue Tab

PBFBI/F_SLM011R1)

5.5 Revenue Projection Form
Use
The Revenue Projection form is intended to be an ongoing planning tool that will be utilized in each year’s
budget process. It provides an early perspective of the projected revenues with underlying assumptions
associated with the revenue source for the coming year. The forecasting staff needs to consider to what degree
the revenue is affected by economic conditions, changing citizen demand and changes in government policies.
These assumptions help determine an economic factor rate. The projection planning tool uses an economic
factor rate to calculate the projection. Other adjustments could also be incorporated such as seasonal
adjustment. Once the projection has been made, the estimates will be evaluated by re-examining the revenue
source. The projected amounts, then, can be overridden.
Prerequisites
Object Type Object Name Value Source Comments
Info Object /PBFBI/FRM_TYP BB
Info Object /PBFBI/RULE 1
Info Object /PBFBI/PU VALTP E3 /PBFBI/SL_C01 Represents Prior Year Actual
Info Object /PBFBI/PU VALTP G1 /PBFBI/SL_C02 Represents YTD Inflated Amount
Note that this data is populated

as part of a year- end process.
Planning function /PBFBI/
PF_SLM012_YTD can be utilized
populate the data.
Info Object /PBFBI/PU VALTP A1 /PBFBI/SL_C03 Represents Adopted Budget
Info Object /PBFBI/PU VALTP H2 /PBFBI/SL_C02 Represents Initial Projection
Info Object /PBFBI/PU VALTP C2 /PBFBI/BF_CUBE Represents Initial Projection
Info Object /PBFBI/PU VALTP C3 /PBFBI/BF_CUBE Represents Other Adjustment
Info Object /PBFBI/PU VALTP C4 /PBFBI/BF_CUBE Represents Projected Amount
Hierarchy /PBFBI/CMMT_IT CMMT IT HIER

ARCHY

Process
Data for the Revenue Projection form is read and written to the Budget Form cube (/PBFBI/BF_CUBE), and
only read from Annualized Aggregated Projection Scenario Data cube (/PBFBI/SL_C02), Budget Forms:
Actual/Previous Year Budget cube (/PBFBI/SL_C01) and Budget Forms Historical: Previous Year Budget data
cube (/PBFBI/SL_C03).
The Revenue Projection form has a header section and several tabs as described below:
Header Area Data:
● Form ID
● Description
● Stage
● Funding status
Functions:
● Search: Search for form instance according to a given set of criteria.

● New: Create a new form instance.
● Edit: Edit the currently loaded form instance.
● Advance Stage: Advance the stage of the currently loaded version based
on the user’s authorizations.
Overview Tab An overview of the revenue projection without the need to navigate to individ
ual sections like revenue. The overview of the revenue projection is shown us
ing charts and a table with all the consolidated values.
Funding Tab Data:
FM dimensions:
● FM Area
● Fund Center
● Fund
● Grant
● Fund Program
● Functional Area
● Description
● Form Currency

Revenue Tab Lists the various revenue items for the revenue projection.
Data:
● Functional Area
● Fund Center
● Commitment item
Six key figures are presented:

● YTD inflated
● Adopted Budget
● Initial Projection (calculated initially, but is editable by the user)
● Other Adjustment (editable)
● Projected Amount (total of Initial Projection and Other Adjustments)
Functions :
● Add: Add new revenue line for the currently loaded form instance
● Copy: Copy the select revenue line into a new line
● Delete: Delete the selected revenue line
● Line Text: Add a line text to the selected line item
Narrative Tab Three text areas are defined: Forecast Description, Publication Forecast De
scription, and Budget Department Review Note.
Attachment Tab Documents can be uploaded and attached to the form
Technical Details
Object Type Object Name Filters Comments
Multi Provider /PBFBI/SL_M01 N/A
Cube /PBFBI/BF_CUBE
N/A Input and Output (all data except key fig-

ures below)
Cube /PBFBI/SL_C01 N/A Read only (Prior Year Ac

tuals)
Cube /PBFBI/SL_C02 N/A Read only (YTD Inflated)
Cube /PBFBI/SL_C03 N/A Read only (Adopted

Budget)
Aggregation Level /PBFBI/A_SLM012 N/A

Object Type Object Name Filters Comments
Query & Filter /PBFBI/A_SLM012_QI003 /PBFBI/F_SLM013 Revenue Tab
Query & Filter /PBFBI/A_SLM012_O /PBFBI/F_SLM013_O Overview Tab
Planning Functions /PBFBI/PF_SLM012_RP
/PBFBI/F_SLM012_RP Calculate Projected Revenue Amount
Planning Functions /PBFBI/PF_SLM012_YTD /PBFBI/F_SLM012_YTD Calculate YTD Inflated

Amount
 Note
The Budget Department Review Note comment box will be displayed only when the form instance has
reached stage 235.
5.6 Roll-Over Process/Year-Begin Process
Use
Rollover process data is updated in the historic and calculated cubes and is a prerequisite for the Multiyear
Projection, Revenue projection, and Base Adjustment. Admin users can use the following set of process chains
to achieving this:
● PBFBI/SL_MULTI_YEAR
● /PBFBI/SL_OTR_ANL
● /PBFBI/SL_INIT_PROJ
● /PBFBI/SL_3YR_AVG
● /PBFBI/SL_YTD_INFL
Previous year budgeted data should be copied from the BF cube to historic cube /PBFBI/SL_C03 using
process chain /PBFBI/SL_COPY_BF.
Process
As a prerequisite, actual budget data from the ECC system is updated to the /PBFBI/SL_C01 cube. For the
Multiyear Projection form, at the beginning of the budget process the /PBFBI/SL_MULTI_YEAR chain should
be executed. This will calculate the projection amount for the next five years by multiplying the previous year
adopted budget amount with the maintained inflationary rate and is updated in the /PBFBI/SL_C02 calculated
cube. When the form is loaded the key figures from the calculated cube is displayed and after save the
projected amount for five years is updated to BF cube.

For the Revenue Projection form, actual budget data from the ECC system must be updated to the /PBFBI/
SL_C01 cube as a prerequisite. When process chain /PBFBI/SL_INIT_PROJ is executed, the adopted budget
in /PBFBI/SL03 is used as the base and is multiplied with the projection rate, which is maintained in the /
PBFBI/SL_RATE customizing table ( SPRO SAP Budgeting and Planning State & Local Economic
Factor ). Using the /PBFBI/SL_YTD_INFL process chain, the actual budget amount is multiplied with the
economic factor maintained in the customizing table above.
For the Base Adjustment form, the adopted budget amount is updated to this historic cube using the /PBFBI/
SL_COPY_BF process chain, which will copy the previous year budgeted amount from the BF cube.
One Time Removal in Base Budget Adjustment
Source Target Processing Logic
Budget Year Exit -1 Budget Year Exit
Fiscal Year Exit -1 Fiscal Year Exit
Form Def / VC Name = Decision Form Def / VC Name = Base Adjust

Package (FD05) ment Form (FD03)
Value Type = D1 Value Type = A4
Key Figure = Amount; One Time Key Figure = Amount * -1 Amount pulling from value type D1 will be mul
Adjustment tiplied by -1 and posted to value type A4
Annualization in Base Budget Adjustment
Budget Year Exit -1 Budget Year Exit
Fiscal Year Exit -1 Fiscal Year Exit
Form Def / VC Name = De Form Def / VC Name = Base Adjust

cision Package (FD05) ment Form (FD03)
Value Type = A9 (Full Yr Value Type = A5(Annual Amount) Value Type A5 = A9 – A8

Cost)
Value Type = A8 (On-Going)
Key Figure = Amount; An Key Figure = Amount VT A5 = VT A9 (Full Year Cost) – VT A8 (On-Going)
nualization
* The result should be equal or greater than zero.
If the result is negative, leave the field blank.
Value Type A5 = > zero, else <>.
Three Year Average in Base Budget Adjustment

Budget Year Exit -1, Budget Year Budget Year Exit

Exit -2, Budget Year Exit -3
Fiscal Year Exit -1, Fiscal Year Exit Fiscal Year Exit
-2, Fiscal Year Exit -3
Key Figure = Amount; 3YR Key Figure = (Sum of 3yr Amount obtained after adding up previous 3 years
Amount )/ 3 amount will then be divided by 3 to obtain the aver
age and posted to value type G2
YTD in Base Budget Adjustment & Revenue Projection
Budget Year Exit Budget Year Exit
Fiscal Year Exit Fiscal Year Exit
Key Figure = Amount; YTD Key Figure = Amount * economic factor Amount will be multiplied by economic factor
and posted to value type G1
Initial Projection in Revenue Projection
● Planning function will be used for creating the data.

● Projection rate is set to 3% and needs to be updated every year.
● Adopted budget in ZBF_C03 will be used as a base to create the projected amount.
● Adopted Budget data will be moved from BF_Cube to ZBF_C03 as a step in the Year End/Year Open
Process.
● After the planning function has been executed, data will be stored in ZBF_C02.
Budget Year Exit -1 Budget Year Exit BY2011
Fiscal Year Exit -1 Fiscal Year Exit FY2011
Budget History Cube -- Calculation Cube -- ZBF_C02

ZBF_C03
Value Type = A1 Value Type = H2 Value Type H2 is an intermediate value type. It is used in
the planning function for calculating forecast amounts
and will be posted in Calculation Cube.
When the form is opened, the data will be pulled from the
calculation cube (C02) and displayed on the form. When
the form is saved, the value type will be saved as ‘C2’ in
the BF_Cube.

Key Figure = Amount Key Figure = Amount * Pull the amount from ZBF_C03 Cube with the following
Rev_Proj Factor criteria:
Budget Year Exit -1 , Fiscal Year -1, Value Type A1
Multiply the above amount with Revenue Projection fac

tor and post it to C02
Initial Projection in MultiYear Form for Projection Year1
Budget Year Exit -1 Budget Year Exit BY2011
Fiscal Year Exit -1 Fiscal Year Exit FY2011
Budget History Cube -- Calculation Cube -- ZBF_C02

ZBF_C03
Adopted Budget: Projection Year 1: Value Type H1 is an intermediate value type. It is used in
the planning function for calculating forecast amount
and will be posted in Calculation Cube.
Value Type = A1 Value Type = H1 When the form is opened, the data will be displayed on
the form based on the calculation. When the form is
saved, the value type will be ‘C1’ in the BF_Cube.
Key Figure = Amount Key Figure = Amount * Inflation Pull the amount from ZBF_C03 Cube with the following
Rate criteria:
Budget Year Exit -1, Fiscal Year -1, Value Type A1
Multiply the above amount with the rate inflation rate

stored in /PBFBI/SL_O05 and post it to C02
Technical Details
Process Chain Planning Sequence Planning Function Filter
/PBFBI/SL_MULTI_YEAR /PBFBI/PS_SLM011_MY /PBFBI/PF_SLM011_MY /PBFBI/F_SLM011_S
/PBFBI/SL_OTR_ANL /PBFBI/PS_SLM012 /PBFBI/PF_SLM012 /PBFBI/F_SLM012_S
/PBFBI/SL_INIT_PROJ /PBFBI/PS_SLM012_RP /PBFBI/PF_SLM012_RP /PBFBI/F_SLM012_RP
/PBFBI/SL_3YR_AVG /PBFBI/PS_SLM012_3YR /PBFBI/PF_SLM012_3YR /PBFBI/F_SLM012_3YR
/PBFBI/SL_YTD_INFL /PBFBI/PS_SLM012_YTD /PBFBI/PF_SLM012_YTD /PBFBI/F_SLM012_YTD

Multi Provider /PBFBI/SL_M01 Budget w/o Position
Cube /PBFBI/SL_C01 Budget Forms : Actual/ Previous Year Budget
Cube /PBFBI/SL_C02 Annualized Aggregated Projection Scenario Data
Cube /PBFBI/SL_C03 Budget Forms Historical: Previous Year Budget

data
Cube /PBFBI/BF_CUBE
DSO /PBFBI/SL_O05 Multi-Year Projection Inflationary Rate ( Direct Up

date )
Aggregation Level /PBFBI/A_SLM011 Transfer and Re-distribution Form
Aggregation Level /PBFBI/A_SLM012 Base Budget Adjustment
Planning Function Type /PBFBI/PT_SLM011_MY Multiyear Projection
Planning Function Type /PBFBI/PT_SLM012 One Time Removal & Annualization
Planning Function Type /PBFBI/PT_SLM012_3YR Three Year Average
Planning Function Type /PBFBI/PT_SLM012_RP Initial Projection for Revenue Projection
Planning Function Type /PBFBI/PT_SLM012_YTD YTD Inflation FISCPER
Planning Filter /PBFBI/F_SLM011_S Filter for Multiyear Planning Function
Planning Filter /PBFBI/F_SLM012_S Filter for One Time Removal & Annualization Plan
ning Function
Planning Filter /PBFBI/F_SLM012_RP Filer for Revenue Form Initial Projection Planning
Function
Planning Filter /PBFBI/F_SLM012_3YR Filter for Three Year Average Calculation Planning
Function
Planning Filter /PBFBI/F_SLM012_YTD Filter for YTD Planning Function

5.7 Transfer and Re-Distribution Form
Use
This form is designed to allow the Budget Department to move operating budget amounts between
departments prior to the beginning of the budgeting cycle. Departments may also use this form to move
operating budget amounts between fund centers within the department.
This form may also be used to enter mid-year governing board’s actions and approved decision packages,
which will impact the following year base budget development. Adjustments related to the midyear are entered
prior to the restructure adjustments.
Another process that this form supports is reorganization. In Public Sector, restructure within the organization
may also happen as a result of changes of the administration. This form allows users to transfer the budget
from the old to the new structure.
Prerequisites
Info Object /PBFBI/FRM_TYP FI Form Type- Allow multiple instances per

Fund and Business Area (Department).
Info Object /PBFBI/RULE SL1
Info Object /PBFBI/PU VALTP A6 Represents Transfer Form Change

Amounts
Info Object /PBFBI/PROJID 2 ,3 Represents Expenses , Revenue
Hierarchy COMM IT HIERAR Used for Commitment Item (Info Ob

CHY ject /PBFBI/CMMT_IT
Hierarchy FUND_CT_HIER Used for Fund Center (Info Object /

PBFBI/FUNC_CT
Process
Data for the Transfer and Redistribution form is read and written to the Budget Form cube. Once the form is
saved change amount value is written to Budget Form cube with a budget value type of A6 for the FM
dimension combination. This data will be displayed in the base adjustment form under the Transfer/
Redistribution header.

The Transfer and Redistribution form has a header section and several tabs as described below:
Header Area The major categorizations of the decision package are found here, such as Form ID and De
scription, FM dimensions, Stage, and Funding status.
Functions:
● Search: Provides a popup to allow users to search the form IDs based on the FM dimen
sions or by the description.
● New: Allows users to create new form IDs.
● Edit: Allows users to edit the description of the form and adjust the amounts.
● Advance Stage: Allows the form to be forwarded to next department by advancing the
stage.
Overview An overview of the Transfer and Re-Distribution Form without the need to navigate to the
individual sections like expenses and revenue. The overview of the Transfer and Re-Distribu
tion Form is shown using charts and a table with all the consolidated values.
Funding The following standard FM dimensions can be used to define the scope of a budget request:
● FM Area
● Fund Center
● Fund
● Funded Program
● Grant
● Functional Area
Expenses Tab Lists the various expenditure items for the adjustment/transfer. Data includes FM dimen
sions (Fund and Funded program are not applicable and not displayed), and one editable
key figure: Change amount.
Data can be changed, copied or deleted. If copied, only the FM dimension data is copied and
can be further edited.
● Functional Area: functional area for the budget transfer line.

● Fund Center: fund center code for the budget transfer line.
● Commitment Item: commitment item code for the budget transfer line.
● Changed Amount: budget amount to be transferred for the current year.
Functions:
● Add: A new row will be added.

● Copy: Copy the existing row to new row along with the FM dimensions.
● Delete: Deletes the currently selected row.
● Line Text: Allows the users to enter the justification for every row entered.

Revenues Tab Lists the various expenditure items for the adjustment/transfer. Data includes FM dimen
sions (Fund and Funded program are not applicable and not displayed) and one editable key
figure: Change amount.
Data can be changed, copied, or deleted. If copied, only the FM dimension data is copied
and can be further edited.
● Functional Area
● Fund Center
● Commitment Item
● Changed Amount
Functions:
● Add: Adds a new row.

● Copy: Copies the existing row to new row along with the FM dimensions.
● Delete: Deletes the currently selected row.
● Line Text: Allows the users to enter the justification for every row entered.
Narrative Tab The Adjustment Description, Publication Adjustment Description, and Budget Department
Review Notes are available. Basically, use this to describe the reason for the redistribution.
Attachments Tab Supporting documents can be added or deleted.
Technical Details
Multi Provider /PBFBI/SLM_01
Query/Filter /PBFBI/A_SLM011_QI001 /PBFBI/F_SLM015E Expense Tab
Query/Filter /PBFBI/A_SLM012_QI002 /PBFBI/F_SLM015R Revenue Tab
Query/Filter /PBFBI/A_SLM011_O /PBFBI/F_SLM015_O Overview Tab

6 Personnel Expenditure Planning
Use
Personnel Expenditure Planning (PEP) allows forecasting personnel expenditures to be included in a public
sector organization’s formulation of the adopted budget or to carry out a mid-year analysis of year-end cost
estimates. PEP uses information from the Human Resource (HR) system to establish an organization’s position
and employee salary and benefit costs.
The PEP calculation process forecasts personnel expenditures based on information from the HR system and
any changes made by budget analysts.
The PEP projection calculation forecasts personnel expenditures as of a point-in-time, allowing fixed amount
and percentage-based changes to salary and benefit costs without changing the underlying definitions of those
objects. The projection scenario can also include or exclude vacant positions. If the vacant positions are
included, you can also define a lag month value. Lag months are the number of periods before costs associated
with vacant positions begin to be calculated.
Currency conversion is supported by allowing a global currency, as defined by the currency attribute on the FM
area used in the projection, and an alternate currency. The alternate currency is defined in the Employee and
Position master data. PEP results will always include one key figure for the global currency and another key
figure for the employee and position currencies. Standard currency conversion configuration must be
maintained for the currency conversion to work properly.
There is no limit to the number of projection scenarios that can be executed within a budget cycle and each can
be used for analysis only or selected to participate in the budget development process. The results of a
projection scenario can be posted to the projection cube, the budget form cube, or both.
PEP Projection Types
SAP Budgeting and Planning for Public Sector offers two types of PEP projections:
● Fiscal period projections were the original type of projections offered by SAP Budgeting and Planning for
Public Sector. Fiscal period projections use the configured fiscal year variant to determine how the results
are to be calculated. For fiscal period PEP, the lowest level of results are at the fiscal period level.
Additionally what-if projections can be executed on top of fiscal period projections. What-if projections use
previously executed fiscal period projections, known as reference projections, and take additional
selections and input criteria to produce new results based on some specific scenarios. Examples include
adding or removing benefits, changing pay scale or step date criteria, and so on.
● Flexible pay period projections were added to address the requirement to produce results by pay period.
These projections produce results at the fiscal period and pay period levels. For flexible pay period PEP the
lowest level of results are at the pay period level. Flexible pay period PEP utilizes the same configuration
and master data as fiscal period PEP (with some exceptions) and also requires some additional
configuration. The same employee and position master data can be used for either fiscal period PEP or pay
period PEP with one exception: benefit rule maintenance requires additional information for pay period
month, year, and accumulators to calculate benefits for pay period PEP.
Pay period PEP offers the following additional functionality:
○ Attrition and Backfill Projections

88 INTERNAL Personnel Expenditure Planning
Attrition and backfill projections can be executed on top of pay period projections. Attrition and backfill
projections use previously executed pay period projections, known as reference projections, and take
previously configured attrition and backfill rules to produce new results based on some specific
scenarios. Attrition and backfill rules can be configured as attrition only, backfill only, or attrition and
backfill.
○ Flexible Source for Employee and Position Master Data
Pay period PEP supports having employee and position master data for PEP in DSO objects rather
than the employee and position InfoObjects. There are several setup steps and configuration required
to use this options. Details for all pay period PEP, attrition and backfill and maintaining employee and
position master data DSOs can be found in Solution Manager.
The following table illustrates what functionality each PEP type supports:
PEP Type Fiscal Period Re Pay Period Results What-if Scenarios Attrition and Back Employee and Po
sults fill Scenarios sition MD from
DSO
Fiscal Period PEP X - X - -
Flexible Pay Period X X - X X

PEP
PEP global configuration — such as parallelization parameters, global table settings, and currency conversion
types — are utilized by both fiscal period and pay period PEP. There are additional configuration steps specific
for fiscal period PEP and pay period PEP.
Assumptions
This document assumes that you have some level of familiarity with the terminology and the functions
associated with SAP Budgeting and Planning for Public Sector PEP. This document aims to provide you with all
the information you need to navigate through and optimize the performance of SAP Budgeting and Planning for
Public Sector PEP. We recommend that you refer to this document whenever necessary during the hands-on
operation of SAP Budgeting and Planning for Public Sector PEP.
1. While there are two types of PEP available — fiscal period PEP and pay period PEP — it is assumed that
customers will use one type or the other, but not both.
2. Fiscal period PEP Allows what-if scenarios and pay period PEP allows attrition and backfill scenarios. Fiscal
period PEP will not support Attrition and backfill scenarios and pay period PEP will not support what-if
scenarios.
Features
Most of the data needed for the fiscal period and pay period PEP calculation will be imported from the HR
system. The information will be imported at the beginning of each budget formulation process. Within SAP
Budgeting and Planning for Public Sector, the fiscal period and flexible pay period PEP calculations are based
on data defined for positions, employees, jobs, benefit rules and rates, and pay levels. Each of these elements
are defined separately but are related. Due to the relationships between each of the PEP elements, the
components must be defined in a specific order:
1. Pay Levels
2. Benefit Rules
3. Benefit Rates
4. Jobs

Personnel Expenditure Planning INTERNAL 89
5. Positions
6. Employees
Relationships
● Benefits are assigned to jobs, positions, and employees

● Jobs are assigned to positions and employees
● Positions are assigned to employees
SAP Budgeting and Planning for Public Sector supports and also qualifies all the positions and employees that
have different Job Classes maintained for a given position and its corresponding employees.
The PEP calculation will attempt to find the data at the employee level. If an item is not found for the employee,
the calculation will look to the related position and then, if necessary, will look to the job class maintained at the
employee level.
Similarly the PEP calculation will attempt to find the data at the position level. If an item is not found for the
position, the calculation will look to the job class maintained at the position level.
Screen Overview
There are a number of characteristics common to each of the PEP Projection screens. The fiscal period PEP
and flexible pay period PEP both have:
● An initial selection screen that can retrieve an existing projection, create a new projection, and copy a
projection
● A Projection Selection tab with characteristics used to filter the projection, such as FM dimensions, pay
grade levels, job, and so on
● A Projection Parameter tab with the date range of the projection
For fiscal period PEP the dates are converted to fiscal period and year. For flexible pay period PEP a pay
type is required (monthly, weekly, and so on) and the dates are converted to pay period and year.
● A Projection Configuration tab
The settings for indicating the calculation should include employees only or include vacant positions
(Vacant Flag), save the projection master data for use as a reference projection (Save Master Data Flag),
Source Form Name (VC name of the form), and saving the results only to the InfoCube or not (Post Results
Only to Cube Flag).
● A Benefit Table tab where increases or decreases to benefits can be entered
These are entered by fiscal period or pay period depending on which PEP application is being executed.
● A Salary Table tab where increases or decreases to salary grades can be entered
There are entered by fiscal period or pay period depending on which PEP application is being executed.

Prerequisites
The following configuration prerequisites apply to both fiscal period PEP and flexible pay period PEP (access
via backend IMG transaction SPRO):
● Maintain PBF Global Settings (PEP related settings)

● Maintain PBF Projection types
● Parallelization of Global Settings
The following configuration prerequisite applies only to fiscal period PEP:
● Process Chain Configuration
The following configuration prerequisites apply only to flexible pay period PEP (access via backend IMG
transaction SPRO):
● Maintain Pay Period Process Chains

● Maintain Pay Period Types
● Upload Pay Period Table from File
● Display Pay Period Table entries
● Maintain Master Data DSO for Employee and Position (optional)
● Business Add-in (BAdI) for Attrition and Backfill (optional)
The following master data prerequisites apply to both fiscal period PEP and flexible pay period PEP:
● Country ID
● Pay Scale Type
● Pay Scale Area
● ES Grouping CAP
● Pay Scale Group
● Pay Scale Level
● Promote Date
● Salary Override
● Employee Group
● Employee Sub Group
● Personnel Area
● Personnel Sub-Area
● FM Area
● Fiscal Year Variant
● Fund Center
● Funded Program
● Grant
● Functional Area
● Fund
● Benefit Area
● Benefit Plan
● Distributions
● Positions

● Employees
● Benefit Rules
● Benefit Rates
● Pay Levels
For flexible pay period PEP there is additional prerequisites:
● Benefit Rules for Pay Periods
For attrition and backfill projections there are additional prerequisites:
● Attrition Rules
● Attrition and Backfill Group Rules
6.1 Running Fiscal Period PEP Scenario Calculations
Use
The fiscal period PEP scenario calculation forecasts personnel expenditures as of a certain point-in-time and
produces results at the fiscal period level. Features include allowing fixed amount and percentage based
changes to salary and benefit costs without changing the underlying definitions of those objects. The
projection scenario can also include or exclude vacant positions. If vacant positions are included, you can also
enter a lag month value. Lag months are the number of periods before costs associated with vacant positions
begin to be calculated.
There is no limit to the number of projection scenarios that can be executed within a budget cycle. Scenario
based projections can be used either for analysis or for the actual budget development process. The results of
a projection scenario can be posted to the projection cube, the budget form cube, or both.
Fiscal period PEP offers the following features:
● Continuity in Step Date Calculation

In the PEP scenario, continuity in the step date calculation will also be retained. During calculation certain
employees and positions will be chosen for calculation. When employees and positions with multiple time
slices in the master data that have the same salary-related fields (Salary Override, Step Date, Salary%,
BENEFITS%, Pay Table fields, FTE Period) are processed, the pay level will be calculated for the first record,
but for subsequent records the system will process through the salary tables, maintain the step date
continuity, and promote the employees and positions to next pay level accordingly in the resultant records.
● Re-Run Projections
For every re-run of projections, the system will trigger the Deletion Run first followed by the PEP
calculation, in the same was as with New Projection Runs.
Prerequisites
You have defined the following:
● Positions

● Employees
● Jobs
● Pay Levels
● Benefit Rules
● Benefit Rates
● Distributions
Procedure
To calculate a fiscal period PEP projection scenario, do the following:
1. Choose PEP Maintenance Projection Scenarios . In the Detailed Navigation area, choose Fiscal
Period PEP Run Projection Scenarios .
2. In the Selection Screen area, click New.
3. In the popup, enter the FM area and a description for the projection.
The FM area determines the fiscal year variant and currency codes for the record.
New Feature: A new value 4 (Budget form positions) for the Vacant Flag is available when creating PEP
projections. Selecting this flag means all positions that are created in budget forms are considered for PEP
calculation
4. Click OK.
The popup window closes and the projection screen detail area becomes active.
5. In the Project Selection tab, enter one or more of the following filter values to limit the projection results
that are included in the projection scenario:
○ Enter values for a combination of Fund Center, Fund, Funded Program, Grant, and Functional Area to
calculate for specific accounting areas. To include all accounting items for an area, do not enter
specific values.
○ Enter values for Employee Group, Employee Sub Group, Personnel Area, Personnel Sub Area, Job, ES
Grouping for CAP, Pay Scale Group to further limit the projection scenario population.
Currency will be defaulted based on the FM Area selected and is not editable.
6. In the Projection Parameters tab:
○ Enter an appropriate stage and projection type. Note that these are optional fields.
○ Specify the start and end dates for the projection and press Enter. The dates determine the calculation
period for the projection scenario.
○ Enter the appropriate budget year. The budget year value specified in the PBF Globals table will be
defaulted.
7. In the Projection Parameters tab:
○ Vacant Flag: enter a value to indicate if the system should calculate costs for vacant positions, filled
positions, or for both vacant and filled positions.
○ Vacant Lag Months: enter the number of months after which the projection calculation should begin to
calculate costs related to vacant positions.
○ Select the Save Master Data checkbox if the projection is to be used as a referenced projection for
what-if projection scenarios. This will cause the master data used by the projection to be saved for use
in what-if projections.
○ Select the Delete PEP Results from the DSOs or Post Results only to Cube checkbox if the intermediate
employee and position data is not needed. If this option is selected, the results will still be posted to the
Projection Cube, but data storage of the intermediate results will not be saved.

○ Source Form Name is the VC name of the budget form from which you want to select the new
positions. The Source Form Name is enabled only when the vacant flag is 4. Usually, vacant flag 4
specifies "Budget Form Positions."
8. In the Benefit Table tab, enter the criteria to determine what actions will be taken against the projection
results of the filtered dimensions. Add new rows to specify the benefit-level changes that affect the filtered
records.
○ Enter the benefit area and benefit plan that will be affected.
○ Enter the start and end periods for which benefit-level changes must be calculated.
○ In Rate (%), indicate a percentage increase or decrease that should be calculated in the projection
scenario.
○ In Amount, specify the amount of increase or decrease that must be calculated in the projection
scenario.
9. In the Pay Table tab, enter the criteria to determine what actions will be taken against the projection results
of the filtered dimensions.
Add new rows to specify pay-level changes that affect the filtered records.
○ To influence specific position or employee records, enter values for Country ID, Pay Scale Type, Pay
Scale Area, ES Grouping CAP, Pay Scale Group, and Pay Scale Level.
○ Enter the start and end periods for which pay-level changes must be calculated.
○ In the Salary Override Filter field, indicate the salary record that should be considered during the
projection.
○ Yes – denotes that the amount in the Salary field on the Pay Details tab of positions and employees
is considered for projections.
○ No – indicates that the salary is determined based on the value found in the pay level table. If you
select this option, the system considers the pay details for the corresponding Country ID, Pay
Scale Type, Pay Scale Area, ES Grouping for CAP, Pay Scale Group, and Pay Scale Level.
○ In the Rate (%) field, enter the percentage increase or decrease that should be considered during the
projection scenario calculation.
○ In the Amount field, enter an increase or decrease amount that should be included in the projection
scenario calculation.
10. To calculate the projection scenario, click Calculate.
11. To save the projection scenario, click Save.
12. To exit without saving the changes, click Cancel.
To copy a projection scenario, do the following:
1. Search for and select the projection scenario that you want to copy.
The system displays the projection scenario details.
2. Click Copy, and enter a new description and FM Area.
3. To save the changes, click Save.

6.2 Running a What-if Scenario Calculation
Use
The what-if projection is an enhancement to the PEP framework to provide what-if PEP result analysis. The
what-if projections do not use employee or position master data. Instead they use the master data saved by a
fiscal period reference projection and allow many parameters to be changed to allow users to do what-if
analysis of PEP results.
The what-if projection is a two-step process. The first step is to create a fiscal period reference projection. A
reference projection is a PEP projection scenario executed with the Save Master Data option selected. The
second step is to create the what-if projection using the master data from the referenced projection completed
in first step. The what-if projection allows users to further filter the FM dimensions, date ranges, and other
selection parameters as well as change next pay scale levels, add benefits, and add or change allocations to
employees and positions thus allowing what-if analysis without affecting master data or other projections.
Screen Overview
The What-if projection screen has four sections as described below
● Selection Screen section

In this section users either display an existing what-if projection or create a new what-if projection based
on a reference projection.
● What-if Projection Filter section
This section allows users to change the selection filter for the what-if projection. The dimension
parameters used in the reference projection are defaulted and can be changed to reflect a smaller selection
or subset of the values inherited from referenced projection ID. This section will allow the users to restrict
what-if results by FM dimensions, employee group/subgroups, personnel area/subarea, job, pay scale
group, and so on.
● What-if Supplemental Data section
This section is similar to the existing Projection Scenario screen. Functionality in this section is to provide
supplementary salary and benefit rate/amount to increment or decrease the computed amounts.
● Step Date, Allocation, and Benefit Supplemental section
This section allows users to enter/change pay scale parameters like step months and next pay scale level
information and enter any additional benefits. Users can also add cost allocations to cause results to be
allocated differently than the reference projection. A variety of options are available to allow the changes to
affect all employees and positions or limited to specific employees or positions.
Prerequisites
● Reference projection
● Positions
● Employees
● Jobs
● Pay Levels

● Benefit Rules
● Benefit Rates
● Allocations
Procedure
To create and calculate a What-if projection scenario, do the following:
1. Choose PEP Maintenance Projection Scenarios . In the Detailed Navigation area, choose Fiscal
Period PEP Run What-if Scenarios.
2. In the Selection Screen area, enter a reference projection ID or use the Drop Down Help button to search for
reference projection IDs and select one from the list. Click New.
3. 3. In the popup, enter the What-if projection description for the projection.
4. Click Create New. The popup window closes and the fields in the What-if projection filter area become
active
5. In the What-if projection filter area, the dimension parameters used in the reference projection are
defaulted. They can be edited and will be limited to a smaller selection or a subset as compared to the
reference projection. For example, the projection start and end dates can be changed to a date range within
the date range of the reference projection, but dates outside of the range will not be allowed.
○ Enter values for a combination of Fund Center, Fund, Funded Program, Grant, and Functional Area to
calculate for specific accounting areas. To include all accounting items from the reference projection,
do not change the defaulted values.
○ Enter values for Employee Group, Employee Sub Group, Personnel Area, Personnel Sub Area, Job, ES
Grouping for CAP, Pay Scale Group to further limit the what-if projection scenario population.
○ Change the defaulted start and end dates for the what-if projection if it is desired to have a smaller
date range than the reference projection.
○ Vacant Flag: enter a value to indicate if the system should calculate costs for vacant positions, filled
positions, or for both vacant and filled positions.
○ Vacant Lag Months: enter the number of months after which the projection calculation should begin to
calculate costs related to vacant positions.
6. In the What-if Supplemental Data area enter criteria to change pay table data to Stage or Projection type.
Note that these are optional fields.
In the Pay Table tab, new criteria can be entered to change Pay Scale and Benefit calculations that were
used in the reference projection. To enter new benefits or affect step date calculations, see the Step Date,
Allocation and Benefit Supplemental Data section.
In the Pay Table tab, add new rows to specify pay-level changes that affect the filtered records.
○ To influence specific position or employee records, enter values for Country ID, Pay Scale Type, Pay
Scale Area, ES Grouping CAP, Pay Scale Group, and Pay Scale Level.
○ Enter the start and end periods for which pay-level changes must be calculated
projection
○ Yes – denotes that the amount in the Salary field on the Pay Details tab of positions and employees
is considered for projections.
○ No – indicates that the salary is determined based on the value found in the pay level table. If you
select this option, the system considers the pay details for the corresponding Country ID, Pay
Scale Type, Pay Scale Area, ES Grouping for CAP, Pay Scale Group, and Pay Scale Level.

In the Benefit Table tab, add new rows to specify benefit–level changes to affect the filtered records.
○ Enter the start and end periods for which benefit-level changes must be calculated.
scenario.
scenario.
7. To enter data in the Step Date, Allocation and Benefit Supplemental Data area press the Edit button.
In the Step Date, Allocation and Benefit Filter area enter values to limit the data selections to be affected by
criteria entered in the Pay Scale, Allocations and Benefit tabs below.
○ Enter values for a combination of Fund Center, Fund, Funded Program, Functional Area, Grant, Employee
Group, Employee SubGroup, and Job to limit data selections to be affected by criteria entered in the
Pay Scale, Allocations, and Benefit tabs. To include all data selections from the reference projection,
leave these fields blank.
○ In the Pay Scale tab the Step Month, Next Pay Scale Group, and Next Pay Scale Level can be changed
for the what-if projection.
○ Use the Employee ID filter to enter a list of specific employee or range of employees for which the
changes will be in effect. Use the More button to add more single employees or employee ranges.
Leave the employee filter blank to affect all employees included in the what-if projection.
○ To select the pay scale data criteria, press the Add button. In the popup screen enter the selection
criteria for the pay scale data to be used. The Country ID, Pay Scale Type, Pay Scale Area and ES
Grouping are required fields. Enter data in the Pay Scale Group and Pay Scale Area to further filter
selections, or leave blank to select all Pay Scale Group and Pay Scale Areas that apply. Press OK.
○ The list of master data Pay Scale Details will be displayed. Use the first line in the table as a filter
line to eliminate unwanted lines of data. Or select a line and press Remove to remove unwanted
data. Select a line and press Edit to change data. A popup will be presented that will allow the Step
Months, New Pay Scale Group and New Pay Scale Level to be changed. Enter desired data and
press OK. Note that the changes made here are only in affect for the current What-if projection;
pay level master data is not changed.
○ In the Allocation tab different cost allocations can be entered than what was used in the reference
projection
○ Use the Employee ID filter to enter a list of specific employee or range of employees for which the
changes will be in effect. Use the More button to add more single employees or employee ranges.
Leave the employee filter blank to affect all employee allocations included in the what-if projection.
○ Click the Add button to add a new allocation. A popup will be presented where the user enters the
Sender FM dimensions on the left side and the Receiver FM dimensions on the right side.
Additionally the Receiver side requires a start and end period and a percentage. Note that the
changes made here are only in affect for the current What-if projection; pay level master data is
not changed.
○ Use the Remove button to remove unwanted allocations
○ In the Employee Benefit tab new benefits can be added for employees. Press the Load Employees
button to add the employees included in the what-if projection to the selection table on the left side of
the screen. Selection the applicable employees and press the Add>> button. A popup screen is
provided to enter the Benefit Area, Benefit Plan, and Start and End Periods. Additionally an Exclude

flag can be selected to exclude a benefit from an employee. If lines from the benefit table should be
removed then select the lines and press the <<DEL button. When finished press the OK button
○ In the Position Benefit tab new benefits can be added for positions. Press the Load Position button to
add the positions included in the what-if projection to the selection table on the left side of the screen.
Select the applicable positions and press the Add>> button. A popup screen is provided to enter the
Benefit Area, Benefit Plan, and Start and End Periods. Additionally and Exclude flag can be selected to
exclude a benefit from a position. If lines from the benefit table should be removed then select the lines
and press the <<DEL button. When finished press the OK button.
8. To calculate the projection scenario, click Calculate.
9. To save the projection scenario, click Save.
Process Limitations
1. Before running what-if projection a PEP projection scenario must be run to be used as a reference
projection for what-If analysis. The Standard PEP projection is an eligible reference projection if it is
created with the Save Master Data checkbox set on.
2. Changes to master data during what-if analysis will not be propagated to underlying Master data
Characteristics.
3. Master data changes in the what-if projection screen are limited to a subset of Master Data values from the
reference projection. In the what-if Projection screen, all the header dimensions values are defaulted from
the referenced projection. Dimensions can be further restricted to allow the what-if scenario to be based
on a subset of the referenced projection.
4. Changes made in the Pay Scale tab in the Step Date, Allocation and Benefit Supplemental Data will only be
applied to those employees and positions that are assigned to the Pay Scale parameters specified
(Country grouping, Pay Scale Type, Pay Scale Area, ES Grouping, Pay Scale Group, Pay Scale Level and
validity period). Allowed changes are limited to only Step Months, Next Pay Scale Group and Next Pay
Scale. Furthermore the Pay Scale and Employee and Position Master Data need to have the correct data.
For example, the salary amounts, currency, and so on. must also have been maintained via the Pay Level
Maintenance screen, the Promotion Date must have been maintained for the employee via the Employee
Maintenance screen, and so on.
5. Any changes made to Employee or Position Master Data will require a new reference projection to be
created reflecting these changes before they will be reflected in a what-if projection. The Employee and
Position Master Data used to calculate what-if projections results is based on the master data that was in
effect at the time the reference projection was executed.
6. Any changes made to Pay Level or Benefit rates will be reflected immediately in what-if projections. The
Pay Level and Benefit rates used to calculate what-if projections results is based on the current rates
maintained at the time the what-if projection is executed.
7. Neither PEP Reference projections nor what-if projections can be re-run. They can be copied to create new
projections but not re-run.
Recommendations
1. To delete projections execute the Delete Projection Results. Choose PEP Maintenance Projection
Scenarios Delete PEP Results . It is recommended to periodically delete projections that are no longer
used in order to keep the size of the reference projection cube from becoming too large.
2. The system keeps track of how many what-if projections have been created from the same reference
projection. After creating six what-if projections using the same reference projection the system will issue a
Warning message each time a new what-if projection is created. This is intended to alert users that there
are what-if projections that could be candidates for deletion.

6.3 Running a Pay Period PEP Projection
Use
The PEP scenario calculation forecasts personnel expenditures as of a certain point-in-time and produces
results at the pay period and fiscal period levels. If a pay period crosses more than one fiscal period then a ratio
is applied to divide the total pay period amount across the applicable fiscal periods.
Features include allowing fixed amount and percentage based changes to salary and benefit costs without
changing the underlying definitions of those objects. The projection scenario can also include or exclude vacant
positions.
Pay period projections include a feature for allowing an alternate source for employee and position master from
DSOs. The alternate DSOs must be populated with the appropriate data, queries must be created for gathering
the data from the DSOs, and configuration needs to be completed to allow users to select the alternate source
in the pay period projection screen.
There is no limit to the number of projection scenarios that can be executed within a budget cycle. Scenario-
based projections can be used either for analysis or for the actual budget development process. The results of
a projection scenario can be posted to the projection cube, the budget form cube, or both.
Prerequisites
Pay period configuration such as Pay Types, Pay Period Table, and so on has been completed. Refer to Solution
Manager or more information.
● Positions
● Employees
● Jobs
● Pay Levels
● Benefit Rules, including new values for pay period, pay year and accumulator details
● Benefit Rates
● Distributions
Procedure
To calculate a Pay Period projection, do the following:
1. Choose PEP Maintenance Projection Scenarios Flexible Pay Period PEP Pay Period Projection .
3. In the popup, enter the pay type, FM area, and a description for the projection.
The pay type determines which pay calendar will be used, such as monthly, weekly, bi-weekly, and so on.

The FM area determines the fiscal year variant and currency codes for the record. Vacant Flag value 4 is
available when creating PEP projections. Selecting this flag gets all positions that are created in the
selected budget form.
4. Click OK.
The popup window closes and the fields in the Dimensions area become active.
5. In the Projection Selection tab, enter one or more of the following filter values to limit the projection results
that are included in the projection scenario:
○ Enter values in a combination of the Fund Center, Fund, Funded Program, Grant, and Functional Area
fields to calculate for specific accounting areas. To include all accounting items for an area, do not
enter specific values.
○ Currency will be filled based on the value of the attribute on the FM Area. It is not changeable.
○ Enter a value in the Job field to calculate employees and positions related to a specific job. To include
all jobs, do not enter specific values.
○ Enter values in the Employee Group, Employee Sub Group, Personnel Area, Personnel Sub Area, ES
Grouping for CAP, and Pay Scale Group fields to further limit the projection scenario population.
6. In the Projection Parameters tab maintain the following criteria:
○ Enter the projection type if desired.
○ Enter the start date for the projection and press Enter. The date determines the starting pay period
and year for the projection scenario.
○ Enter the stage if desired.
○ Enter the end date for the projection and press Enter. The date determines the ending pay period and
year for the projection scenario.
○ Enter the budget year for the projection scenario
○ The Start Pay Period/Year, Pay Type, and End Pay Period/Year fields will all be defaulted based on the
input criteria mentioned above.
7. In the Projection Configuration tab maintain the following criteria:
○ Vacant Flag: Enter a value to indicate if the system should calculate costs for vacant positions, filled
positions, or both vacant and filled positions.
○ Source Selection: Enter a source for employee and position master data if a source other than
theemployee and position InfoObject master data is desired. The source selection must have been
configured in order to select it here. See Solution Manager guide for configuration details.
○ Vacant Lag Months: Enter the number of months after which the projection calculation should begin to
calculate costs related to vacant positions. PEP will determine the appropriate pay period based on the
number of lag months and the date that the position first became vacant.
○ Select the Save Master Data checkbox if the projection is to be used as a referenced projection for
Attrition and Backfill projection scenarios. This will cause the master data used by the projection to be
saved for use in attrition and backfill projections.
○ Userid will be defaulted from the current user ID and is not changeable.
○ Select the Post Results only to Cube checkbox if the intermediate employee and position data is not
needed. If this option is selected, the results will still be posted to the projection cube, but data storage
of the intermediate results will not be saved.
○ Source Form Name is the VC name of the budget form. The Source Form Name is enabled only when
vacant flag is 4. Usually vacant flag 4 specifies Budget Form Positions. Selecting the source form name
gets positions related to the respective budget form.
8. In the Benefit Table tab, enter the criteria to determine what actions will be taken against the projection
results of the filtered dimensions. Add new rows to specify the benefit-level changes that affect the filtered
records.

○ Enter the start pay year and pay period and end pay year and period for which benefit-level changes
must be calculated.
scenario.
scenario.
9. In the Pay Table tab, enter the criteria to determine what actions will be taken against the projection results
of the filtered dimensions. Add new rows to specify pay-level changes that affect the filtered records.
○ To influence specific position or employee records, enter values for the Country ID, Pay Scale Type, Pay
Scale Area, ES Grouping CAP, Pay Scale Group, and Pay Scale Level fields.
○ The Supplemental type field is used to calculate the new salary and benefit values after adjusting the
period-wise salaries with the supplementary amounts and rates for pay period-wise salary/benefit
records.
○ ○ Increment
When the increment radio button is selected:
○ Salary override as fixed salary: The fixed salary is incremented by the rate and amount
entered.
○ Salary override as pay table salary: The employee’s pay scale salary is incremented by the rate
and the amount entered
○ Override
When the override radio button is selected:
○ Salary override filter as fixed salary : The employee’s fixed salary is overridden by the amount
entered.
○ Salary override filter as pay table salary :The employee’s pay-scale salary is overridden by the
amount entered.
○ Enter the start pay year and pay period and end pay year and pay period for which pay-level changes
must be calculated.
projection.
○ Fixed Salary
Denotes that the amount in the Salary field on the Pay Details tab of positions and employees is
considered for projections.
○ Pay Table Salary
Indicates that the salary is determined based on the value found in the pay level table.
If you select this option, the system considers the pay details for the corresponding Country ID,
Pay Scale Type, Pay Scale Area, ES Grouping for CAP, Pay Scale Group, and Pay Scale Level fields.

6.4 Running an Attrition and Backfill Projection
Use
An attrition and backfill projection takes a previously executed pay period PEP projection and applies an
attrition and backfill group rule to create new results. It is a two-step process:
1. The first step is to create a pay period projection with the Save Maser Data option is selected. This saves
the master data, also known as a the reference pay projection, that is a pre-requisite for the attrition and
backfill projection
2. The second step is to create the attrition and backfill projection. This step requires the reference pay
projection created in the first step and a pre-configured attrition and backfill group. The attrition and
backfill group contains individual attrition rules to reduce costs (attritions) and any associated backfill
criteria to increase future costs (backfill positions). The attrition and backfill projection writes the results
into a separate InfoCube. Queries can then be used to combine the original reference pay period projection
and the attrition and backfill projection results into a single report.
The attrition and backfill framework includes the attrition & backfill scenario screen, an analysis layer to store
data from the pay period reference projection and configuration DSOs for attrition and backfill rules. Attrition
and backfill scenarios will use the analysis layer from the reference pay period projection for the calculations as
well as attrition and backfill rules. Any PEP master data changes will need to be included in a pay period
reference projection before they can be considered by attrition and backfill projections. For any configuration
changes, such as benefit or pay level changes, a new reference pay period projection needs to be executed
before any subsequent attrition andbackfill projections are executed against it.
Attrition and backfill rules are configured, and one rule is specified in each attrition and backfill projection. The
configuration of attrition and backfill rules is a separate two-step process:
1. Maintain Attrition Rules

The attrition rule consists of selection criteria, such as the desired FM dimensions, employee group,
personnel group, pay scale group, job, and so on. Once the selection criteria are complete then the pay
year and period and attrition rate is entered. This combination of data represents an attrition rule.
2. Maintain Attrition and Backfill Group Rules
The attrition and backfill group rule incorporates the attrition rules configured in the first step and allows
backfill rules to be created. Each attrition rule can be included in one or more group rule backfill rules
require a backfill position which can be any position defined in master data, or new positions can be
created specifically for backfill purposes. The backfill position entered in the group rule will be used to
generate a new backfill position during the attrition and backfill projection calculation. The new positions
will have a different employment status so that it won’t be considered for other PEP projection
calculations. There are three types of group rules allowed:
○ Attrition only. These are attrition rules without any type of backfill. The type of rule can be used to
represent work force reductions.
○ Attrition and backfill: These are attrition rules with a dependent backfill rule. This type of rule can be
used to represent work force reductions followed by some percentage of backfilling (positions) based
on a percentage of those employees that were subject to attrition.
○ Backfill only. These are independent backfill rules with no associated attrition and represent a
workforce increase which could represent a hiring event. Backfill only rules require an actual number
(head count) used rather than based on a percentage of an attrition rule.

Once the attrition and backfill group rules have been configured and the pay period reference projection has
run successfully then users can execute attrition and backfill projection and enter the group rule in the Attrition
and Backfill Projection screen.
When the attrition and backfill projection executes, it will apply the attrition and backfill group rule that was
entered when the user creates the attrition and backfill projection. The PEP engine will read the attrition rule to
determine the number of employees to be attritioned using the selection criteria of the attrition rule and then
apply the attrition rates to the pay periods indicated in the attrition rule. It is important to note that:
● Only employees can be attritioned; positions are not attritioned

● Once an employee has been attritioned they are attritioned for the duration of the projection
● Several attrition rules can be used in one attrition and backfill group rule. There are no checks or warnings
for attrition rules that may have overlapping selection criteria. If there is overlap the attritions will be
calculated as per the configured group rules and attrition rules.
● Only positions are created for backfills; employees are not used for backfills.
● Once a backfill position is created they are included for the duration of the projection.
For more details on maintaining Attrition and Backfill rules please see Solution Manager.
Prerequisites
● A pay period PEP projection has been executed with the Save Master Data flag set so it can be used as a
reference projection.
● Attrition and backfill group rules and supporting attrition rules have been created.
Procedure
To calculate a Pay Period projection, do the following:
1. Choose PEP Maintenance Projection Scenarios Flexible Pay Period PEP Attrition and Backfill
Projection .
3. In the popup, enter the pay type, the attrition and backfill group rule, the pay period reference projection,
and a description.
The pay type determines which pay calendar will be used, such as monthly, weekly, bi-weekly, and so on.
The attrition and backfill group determines the attrition and backfill rules to be used when executing the
projection.
The pay period reference projection identifies the projection results to which the attrition and backfill rules
are to be applied.
4. Click OK.
The popup window closes and the fields in the Projection Selections become active.
Only the following fields are editable:
○ Description
○ Pay Projection Parameters tab: Projection Type and Stage
Click Calculate to execute the projection.

6.5 Deleting Projection Results
Use
The Delete Projection Results screen is a centralized screen that enables the user to delete all types of
projection IDs (fiscal period, pay period, what-if, attrition and backfill) at a single location. Authorization has
been invoked in this screen, so although users will be able view all the projections that exist in the system, they
can add only those projection IDs to the deletion queue for which they are authorized.
Procedure
Screen Description
The delete projection screen has two sections as described below:
1. Selection Criteria Section

The projection IDs can be searched based on three types of filter criteria: FM dimensions along with other
fields, user name, and projection IDs directly.
2. Projection ID Display Section
Based on the filter values provided by the user in the Selection Criteria section, the projections IDs will be
retrieved upon clicking the Search button and displayed as follows:
○ All the normal and reference projections IDs will be displayed separately.
○ All the what-if projection IDs will be grouped together along with their respective reference projection
IDs.
Concept of Authorization in the Delete Projection Screen
Once the projection ids are filtered and displayed, the select flag against each projection ID will be available
only for selection based on the following:
● Fiscal Period and Pay Period Projection ID

The user will be able to view projection IDs for which he or she is not the owner but can add only those
projection IDs to the deletion queue for which he or she is authorized. The select flag will be enabled only
for those projection IDs for which he or she is authorized
● What-if and Attrition and Backfill Projection IDs
1. The user is the owner of the reference projection ID
The user will be able to view all what-if or attrition and backfill projection IDs under a given reference
projection ID. The user can selectively add the what-if and attrition and backfill IDs to the queue. If the
user adds the reference projection ID to the queue, then all the what-ifs or attrition and backfills under
the reference projection IDs will be added to queue, regardless of whether it contains certain what-if or
attrition and backfill projection IDs of which the user is not the owner.
2. The user is not the owner of the reference projection ID
The user will be able to view all the what-if or attrition and backfill projection IDs under a given
reference projection ID. But the user can only add those what-if or attrition and backfill IDs to the
queue for which he or is authorized.
Steps

1. Enter the values for the filter criteria and click on search. The system displays the projection IDs based on
the filter criteria values. Select the checkboxes next to the projection IDs you wish to delete.
2. Click the Submit button.
The system will add the selected projection ID to the queue and delete the projection ID definition and the
related results.

7 Additional Functions
Use
Besides the main functions that help an organization plan and prepare its budget, SAP Budgeting and Planning
for Public Sector also provides certain ancillary functions that enhance user-experience.
Features
Dictionary
Textual entries in budget and planning forms play an important role in the budget formulation process,
especially at the higher stages of budget planning. The Dictionary utility helps users manage the list of words
and abbreviations that are accepted in the various text areas of the solution. To manage your own lexicon, see
Dictionary Maintenance [page 106].
Application Help
The very nature of SAP Budgeting and Planning for Public Sector as a portal application provides immense
opportunities for organizations to integrate other applications or screens using the SAP NetWeaver platform.
The Application Help utility allows users to maintain help links from custom screens to in-house
documentation. To learn more about managing help links, see Application Help Maintenance [page 107].
7.1 Dictionary Maintenance
Use
The dictionary function in SAP Budgeting and Planning for Public Sector provides the ability for organizations
to manage their lexicon of words. This function is an integral part of the spell checking capability in budget and
planning forms.
Features
You can manage your dictionary by maintaining words in the default dictionary or in a custom dictionary that
contains words that are unique within the organization. For example, in the public sector, new words and
abbreviations may be introduced with new policies or with amendments to existing policies and programs.
You can maintain the dictionary by choosing Administration Dictionary Management .

106 INTERNAL Additional Functions
The Add button facilitates creation of single words through a popup window. You can also import a list of words
from a file using the Add Words From File option.
Dictionary management also facilitates the occasional removal of words from the accepted dictionary. You can
achieve this by removing selected words from the dictionary into the Removed Words list.
Additionally, you can also export words from the Dictionary or the Removed Words list into a local file by
choosing the appropriate option under Export.
7.2 Application Help Maintenance
Use
This function allows you to enable context-sensitive help links for corresponding screens in SAP Budgeting and
Planning for Public Sector. The Application Help table also offers the flexibility to maintain links to
documentation that is created internally or is available within the organization.
Integration
When a user clicks the Help button on a screen, the system checks the Application Help table to display the
documentation linked to the corresponding screen.
Prerequisites
You have the following:
● Installed application help for SAP Budgeting and Planning for Public Sector in a compiled HTML Help
(.CHM) or Plain HTML format.
● The screen IDs of screens that you want to link with specific documentation.
Features
On the Application Help screen, you can:
● Create a new entry for a Language, Screen ID, and Link combination by clicking New
● Edit an existing entry by clicking Edit
● Preview the linked documentation by selecting an entry and clicking View

Additional Functions INTERNAL 107
Activities
To create a link to the CHM help file, do the following:
1. Open the CHM file and display the relevant topic in HTML Help Viewer.
2. In the topic window, right-click and choose Properties.
3. In the Properties window, copy the URL in the Address URL field and paste it in a text editor.
4. Extract the file path from the URL.
 Example
If the URL is mk:@MSITStore:E:\Help_FilesPBF\HTMLHelp\EN\00006657.chm::/

DF80173B4079CC7EE10000000A11402F/content.htm, then copy the text starting from E:. In this
case, the URL for the help link would be E:\Help_Files\PBF\HTMLHelp\EN\00006657.chm::/
DF80173B4079CC7EE10000000A11402F/content.htm.
5. Use the file path as the help link for the corresponding screen.
To create a link to the Plain HTML help, do the following:
1. Open the Plain HTML help by double-clicking start.htm from the installed location.
2. Navigate to the relevant topic in the structure.
3. In the topic window, right-click and choose Properties.
4. In the Properties window, copy the URL and use it as the help link for the corresponding screen.

108 INTERNAL Additional Functions
8 SAP Budgeting and Planning for Public
Sector Administration
8.1 Maintaining BI Master Data
Use
The budget formulation process requires the use of varied types of master data to define budget requests,
personnel expenditure projection results and other elements of the budget formulation process. The SAP
Budgeting and Planning for Public Sector solution facilitates easy maintenance of different master data through
the Master Data Maintenance screen.
Authorized users and administrators can maintain master data for SAP Budgeting and Planning for Public
Sector by choosing Budget Formulation Master Data Maintenance .
Prerequisites
Master data InfoObjects must exist in the system before you can search for or edit them.
Procedure
To search for a master data InfoObject, do the following:
1. On the Master Data Maintenance screen, select the search criteria and enter a search value. You can search
for master data using an InfoObject’s description, technical name, or both.
2. Click Search.
The system displays all InfoObjects that meet the search criteria.
3. Select the InfoObject to be maintained, and click Maintain.
The system displays the selected InfoObject maintenance screen.
To create a new master data record for master data without a compound key, do the following:
1. Search for and select the master data that you want to edit.
The system displays the Master Data Maintenance screen.
2. On the Maintain Master Data screen, click New.
3. In the Intervals for section, enter information in the following fields:
○ From: enter an effective start date for this time interval. This is a mandatory field.

SAP Budgeting and Planning for Public Sector Administration INTERNAL 109
○ To: enter an effective end date for this time interval. This is a mandatory field.
4. In the description section, enter any of the available descriptions.
5. In the Attributes section, enter information for the available attribute fields.
6. To save the information and create a master data record, click Save.
7. To exit without saving the information, click Cancel.
To edit a master data InfoObject, do the following:
1. Search for and select the master data that you want to edit.
The system displays the Master Data Maintenance screen.
2. Click Edit to change the time intervals, descriptions or attributes of the master data.
 Note
You cannot change the code for the master data.

8.2 Non-FM Master Data Integration
Definition
Master data integration is a two-step process. The first step stages the data from non-FM BI/non-BI data
sources in to a staging layer data store objects (DSOs). The second step uses the staged data and loads it to a
mapping layer data store object. The mapping layer provides the flexibility to perform any derivation of master
data values before being uploaded to target PBFBI FM dimension InfoObjects.
Use
1. Staging layer
Staging layer DSOs are delivered with generic non-FM dimensional info objects to stage non-FM master
data. The staging layer DSOs can be filled with data using Master Data Extractors from BI or non-BI data
sources. Staging DSOs are designed to be time-dependent to accommodate time slice variations of master
data attributes. Separate DSOs are delivered for each generic non-FM dimensional InfoObjects.
2. Mapping layer
DSOs are created for each /PBFBI/FM dimensional object. Mapping DSOs are designed to combine
information from non-FM dimensional info objects with corresponding /PBFBI/ FM dimensional info
objects. Mapping DSOs contains attributes of FM dimensional InfoObjects as data fields.
This layer will serve following purposes:
1. Providing flexibility to perform any derivation of master data values before being loaded to target
PBFBI FM dimension info objects.
2. Serving as a reference data store for lookup during retraction. By default the mapping between non-FM
dimensional and FM objects is one-to-one.

110 INTERNAL SAP Budgeting and Planning for Public Sector Administration
8.3 Budget Form Configuration
Use
The budget form template is a Visual Composer (VC) model. The budget form template will be copied to create
budget form definitions to capture budget requests for specific components of the budget formulation process.
A customer will have many form definitions and each will be configured to meet the user requirements for the
varying types of budget requests. A budget form template’s VC model queries and corresponding layouts
maybe changed to include or remove InfoObjects. Additionally, user-defined comment types, comment type
trees, and form elements may also be included.
Integration
Comment types, comment type trees, and form elements may be added to a form definition to capture
additional information about a budget request. These objects are defined in the Comment Type, Comment Type
Trees, and Form Element maintenance screens.
Budget form definitions are assigned Stages. Stages determine a user’s access to a budget request and also at
what point in the process entered changes are recorded. Stages are defined in the Stage Maintenance [page
118] screen.
Combination edit rules determine which FM dimension codes are available for selection and which code
combinations are valid. The combo edit rules and mapping are defined in the Combo Edit Rules Maintenance
[page 114] screen.
Prerequisites
● You have setup the following master data:

○ FM Area
○ Fiscal Year Variant
○ Fund Center
○ Funded Program
○ Grant
○ Functional Area
○ Fund
● You have defined the following SAP Budgeting and Planning for Public Sector specific settings:
○ Comment Types [page 112]
○ Comment Type Trees [page 113]
○ Form Elements [page 117]
○ Stages [page 118]
○ Combination Edit Rules [page 114]
○ Workflow Administration [page 123]

Features
The budget form template will be configured in Visual Composer. All of the Visual Composer features are
available.
8.3.1 Creating a Comment Type
Use
The budget formulation process requires the use of text inputs to justify budget requests, explain impacts of
decisions, track decisions, and so on. The SAP Budgeting and Planning for Public Sector solution facilitates the
creation of different texts through comment types. Using comment types, customers can configure text
categories based on their individual needs.
Prerequisites
Comment types must exist in the system before you can search for or edit them.
Procedure
To create a new comment type, do the following:
1. Choose Administration Budget Forms . In the Detailed Navigation area, select Comments
Comment Types
2. On the Comment Types screen, click New.
The system displays the New Comment Type popup.
3. In the New Comment Type popup, enter information in the following fields:
○ Technical Name: enter a technical name for the comment type. This is a mandatory field and the name
will not be editable after saving.
○ Name: enter a name for the comment type.
○ Description: describe the comment type.
4. To save the information and create a new comment type, click Create.
To search for a comment type, enter a search criteria and click Search. To retrieve all existing comment types,
click Search without entering a search criteria.
To edit a comment type, do the following:
1. Search for and select the comment type that you want to edit.
The system displays the Comment Type Details screen.
2. Click Edit to change the name and description of the comment type.

 Note
You cannot change the technical name of a comment type.

8.3.2 Creating a Comment Type Tree
Use
The budget formulation process requires the use of text inputs to justify budget requests, explain impacts of
decisions, track decisions, and so on. At times there is a need to create relationships between varying
comment types. SAP Budgeting and Planning for Public Sector facilitates the creation of relationships between
texts through comment type trees. Using comment type trees, customers can configure text categories within
a tree structure based on their individual needs. One of the available comment type trees, Strategic Planning,
creates a structure that allows the definition of a mission and the creation of goals related to the mission and
the objectives related to the goals.
Prerequisites
Comment types must be defined.
Comment type trees must exist in the system before you can search for or edit them.
Procedure
To create a new comment type tree, do the following:
1. Choose Administration Budget Forms . In the Detailed Navigation area, select Comment Type Trees
.
2. On the Comment Type Trees screen, click New.
The system displays the New Comment Type Tree popup.
3. In the New Comment Type popup, enter information in the following fields:
○ Technical Name: enter a technical name for the comment type tree. This is a mandatory field and the
name will not be editable after saving.
○ Name: enter a name for the comment type
○ Root Type: enter a root type for the comment type tree. This is the comment type that will be the top
level in the comment type tree.
○ Description: describe the comment type
4. To save the information and create a new comment type tree, click Create.
The system creates properties and structure tabs.

6. On the Structure tab, right-click the root entry and select New Existing .
The Find Comment Type popup is displayed.
7. On the Find Comment Type popup, search and select an existing comment type.
Repeat until all necessary comment types are included in the comment type tree.
8. To save, click on the Properties tab and click Save.
To search for a comment type tree, enter a search criteria and click Search. To retrieve all existing comment
types, click Search without entering a search criteria.
To edit a comment type tree, do the following:
1. Search for and select the comment type tree that you want to edit.
The system displays the Properties and Structure tabs.
2. On the Properties tab, click Edit to change the name and description of the comment type.
 Note
You cannot change the technical name of a comment type tree.
3. On the Structure tab, you can edit the comment type tree hierarchy by adding new nodes or deleting
existing nodes.
 Note
Deleting a tree node with subnodes removes the selected node and all its subnodes.
4. To save the changes, click Save on the Properties tab.

5. To exit without saving the changes, click Cancel on the Properties tab.
8.3.3 Creating a Combo Edit Rule
Use
The budget formulation process requires the ability to control how FM dimensions are used in the Budget Form,
Ranking, and Projection Scenario screens. These controls include:
● Limiting the selection of funds management (FM) dimensions based on defined hierarchies
● Limiting the selection of FM dimensions based on defined valid combinations within a budget form
Prerequisites
1. You have setup the following master data with at least one hierarchy:
○ FM Area
○ Fund Center
○ Funded Program

○ Grant
○ Functional Area
○ Fund
○ Commitment Item
○ Multi Use Dimension1
2. You have created form definitions.
Procedure
To create a new combo edit rule, do the following:
1. Choose Administration Budget Forms . In the Detailed Navigation area, choose Combo Edit .
2. On the Combo Edit Maintenance screen, click New.
The system displays the Create New Rule popup.
3. In the Create New Rule popup, enter a name for the combo edit rule.
4. To save the information and create a new combo edit rule, click Create.
The system creates hierarchies, leaf rules and form mapping tabs.
6. On the Hierarchies tab, click New to add a new info object and hierarchy combination.
The Add Hierarchy popup is displayed.
7. On the Add Hierarchy popup, search and select an existing info object name.
8. On the Add Hierarchy popup, search and select an existing hierarchy.
9. To add the info object and hierarchy, click Save.
 Note
○ Default node name should be filled only when the InfoObject is not present in the budget form
header but is used in the budget form line item section.
○ Commitment Item is not a part of the budget form header but is used in the budget form line-item.
○ Assign the rule to a form definition on the Form Mapping tab.
○ A budget form definition can be assigned to one rule only. However, one rule can have several
different form definitions assigned to it.
 Caution
Do not change the assignment of rules after having started using it during the budgeting process.
Reassignment of rules or changing rules midway through the budgeting process will lead to
inconsistencies in reporting.
10. To exit without adding the info object and hierarchy, click Cancel. The Header Level Setting and Line Level
Settings fields become available.
11. In the Header Level Setting, enter information in the following fields:
○ Header Level: enter a hierarchy level for the selected hierarchy which will available for selection in the
budget form.
○ Header Selector: enter the node selector indicator. The options are:
○ Only display nodes at the selected level

○ Display nodes at current level and nodes below
○ Leaves only
○ Default Node: enter the code of the node in the selected hierarchy to be used as the starting point in
the budget request. This is required if the InfoObject is not in the form definition hierarchy.
12. In the Line Level Settings, enter information in the following fields:
○ Leaf Level: enter a hierarchy level for the selected hierarchy which will available for selection in the
budget form lines.
○ Selector: enter the node selector indicator. The options are:
○ Only display nodes at the selected level
○ Display nodes at current level and nodes below
○ Leaves only
13. On the Leaf Filter tab, click New.
The system highlights an empty row in the Details table.
14. In the new row, enter information in the following fields:
○ FM Area: enter the financial management area for the combo edit leaf rule. This detail determines the
fiscal year variant and currency code for the combo edit leaf rule. This is a mandatory field.
○ Fund Center: enter the fund center associated with the combo edit leaf rule.
○ Funded Program: enter the funded program associated with the combo edit leaf rule.
○ Grant: enter the grant associated with the combo edit leaf rule.
○ Functional Area: Specifies the functional area associated with the combo edit leaf rule.
○ Fund: enter the fund that is associated with the combo edit leaf rule.
○ Date From: enter the valid start date for the combo edit leaf rule.
○ Date To: enter the valid end date for the combo edit leaf rule.
15. On the Form Mapping tab, click New.
The system highlights an empty row in the Details table.
16. In the new row, enter the form name code for the combo edit mapping.
17. To save the information for the combo edit rule, click Save.
To search for a combo edit rule:
1. Select the Find Rule by indicator and enter a rule name or a form name.
2. Enter a search criteria and press Enter. Leave the search criteria empty to view all the rules in the list.
3. Select a rule.
The system displays the rule details in the Hierarchies, Leaf Filter and Form Mapping tabs.
To edit a combo edit rule, do the following:
1. Choose Administration Budget Forms . In the Detailed Navigation area, choose Combo Edit
2. Search for and select the combo edit rule that you want to edit, and click Edit.
3. On the Hierarchies, Leaf Filter and/or Form Mapping tabs, change the header rule settings, line level
settings, leaf filter rows, and/or form mapping values.
To delete combo edit rule attributes, do the following:
1. Search for and select the combo edit rule where attributes should be deleted.
2. On the Hierarchies tab, select an info object and hierarchy combination row, and click Delete.

3. On the Leaf Filter tab, select leaf combination row, and click Delete.
4. On the Form Mapping tab, select a form row, click Delete.
8.3.4 Defining Form Elements
Use
The budget formulation process requires the use of text fields or input lists to further define budget requests.
The SAP Budgeting and Planning for Public Sector solution facilitates the creation of text fields or input lists
through form elements. Using form elements, customers can create text fields or input lists and list values
based on their individual needs. Once defined, form elements can be placed on a form definition.
Prerequisites
Form elements must exist in the system before you can search for or edit them.
Procedure
To create a new form element, do the following:
1. Choose Administration Budget Forms . In the Detailed Navigation area, choose Form Elements.
2. On the Form Elements screen, in the Enter Form Element box, enter the form element code and click New.
The system displays the Form Elements definition screen.
3. In the Maintain Form Element box, enter information in the following fields:
○ Value Type: enter a value type. The options are value or text. This is a mandatory field that will not be
editable after saving.
○ Description: describe the form element
4. To save the information and create a new form element, click Save.
If the value type is “value”, the system displays the Maintain Values definition screen.
6. On the Maintain Value screen, in the Description field, enter a description of the value and click New.
7. To save the information and create a new form element value, click Save.
To search for a form element, enter a search criteria and click Search. To retrieve all existing form elements,
click Search without entering a search criteria.
To edit a form element, do the following:
1. Search for and select the form element that you want to edit.
The system displays the Form Element definition screen.

2. Select a value to change the description of the form element value.
 Note
You cannot change the value code of a form element value.

8.3.5 Maintaining Stages
Use
The budget formulation process requires the ability to capture budget request changes by formulation stages.
The SAP Budgeting and Planning for Public Sector solution facilitates the creation of budget formulation stages
through stage maintenance. Using stage maintenance, customers can configure stages and link the defined
stages to form definitions based on their individual needs. The stage status can then be used to determine
accessibility of the stage.
Prerequisites
Stages must exist in the system before you can search for or edit them.
Procedure
To create a new stage, do the following:
1. Choose Administration Budget Forms . In the Detailed Navigation area, choose Stage Maintenance.
2. On the Stage Maintenance screen, click New.
The system displays the Stage Details popup.
3. On the Stage Details popup, enter a stage (numeric value between 1 and 999) and a description.
6. Once stages have been defined, click Assign Stages.
The system displays the Assign/Set Stage to Form definition screen.
7. In the Assign/Set Stage to Form definition screen, enter information in the following filter fields:
○ Form Name: enter a form name.
○ Stage: enter a stage.
8. To bring up a list of form-stage combinations already defined, click Submit.
9. To refresh the list of form-stage combinations already defined, click Refresh.
10. To return to the Stage Maintenance screen, click Back.

11. To create a new form-stage combination, click New.
The system displays a blank row in the Combinations list.
12. In the Combinations row, enter information in the following filter fields:
○ Authorization Object: enter a unique code for the form-stage combination.
○ Form Name: enter a form name for the combination.
○ Stage: enter a stage for the combination.
○ Status: select a status for the combination. The options are: 0 (Closed) and 1 (Open).
○ Allow Deletion: Check this box if the form can be deleted at the particular stage.
○ Exclude Re-calculation: Check this box if the forms at the particular stage are not to be recalculated
when the master data changes. The form recalculation implies calculation of position records when the
underlying master data is changed.
13. To save the information and create a new form-stage combination, click Save.
To search for a form-stage combination, enter a search criteria and click Submit. To retrieve all existing form-
stage combinations, click Search without entering a search criteria.
To edit a form-stage combination, do the following:
1. Search for and select the form-stage combination that you want to edit.
 Note
You cannot change the authorization object of a form-stage combination.

 Note
● Stages will not be displayed in the budget form. The displayed stages are controlled by analysis
authorizations (RSECADMIN).
● For more information on analysis authorizations, refer to the SAP Netweaver Security Guide.
Additional Information
Successful selection of a form instance transfers control to the Stage section. The Authorized Stages drop-
down list is filtered by two criteria:
● Stages that are set to status Open and Stages that are greater than or equal to the current stage
● Stages that the user is authorized for (analysis authorizations)
For further information on the setup and maintenance of analysis authorizations, refer to the SAP Netweaver
Security Guide.
Authorization is checked for a combination of form name and stage. The combined value of both stage and
form name is automatically derived.
The stage maintenance configuration is physically stored in DSO /PBFBI/BFS_O01.
InfoObject /PBFBI/SAUTH is defined as authorization object using the analysis authorization (RSECADMIN).
The drop-down list of authorized stages will:
● Determine the current stage of the form

● Check for stages that are set to status Open

● Display only stages that are greater than or equal to the current stage of the form
8.3.6 Stage Advancer
Use
Stage Advancer can be used to advance multiple budget forms at once to a desired stage. It allows skipping
stages and advancing stages of several budget forms to whoever has the Stage Advancer authorization. The
original rule that a budget form stage can’t be moved backwards still applies.
Restrictions
Usage is expected to be limited to few power users with Stage Advancer authorization, since the related
authorization allows the ability to advance several budget forms at once. Budget forms with a current stage
greater than the target stage will not be advanced and will retain their current stage. All the budget forms that
are to be advanced should be available for use – that is, they should not be locked by any other screen,
process, or user. If even one single budget form is locked by any other process, Stage Advancer will not
advance any of the budget forms.
With PBF 8.1, forms that are locked by the Stage Workflow process and are awaiting approval are skipped by
the Stage Advancer and will remain in their existing Stage.
Prerequisites
● You have set up the following master data:

○ FM Area
○ Fund Center
○ Funded Program
○ Grant
○ Functional Area
○ Fund
○ Budget Form Stages
● You have assigned the Stage Advancer object to the user:
○ /PBFBI/MSA

Features
Stage Advancer has two screens. The first screen allows a user to enter selection or filter criteria to bring up a
working set of budget forms that are to be advanced. It accepts the following fields to limit the budget forms
working set:
● Financial management area

● Form name
● Functional area
● Fund
● Fund center
● Funded program
● Grant
Additionally, a Target Stage field is provided to indicate what stage the forms should be advanced to.
Financial Management Area, Form Name, and Target Stage are required fields. A user must, at least, enter these
fields and hit the Search Forms button to go to the next screen, which will display a list of budget forms that
satisfy criteria entered on the first screen.
Value help (like F4 help on traditional SAP screens) is provided for each and every field on this screen. This also
helps to ensure that only valid values can be entered into the fields on this screen.
Depending on the selection criteria entered on the first screen, a list of budget forms will be displayed along
with their current and target stages. Note that budget forms with desired target stages less than the current
stage are indicated with same target stage, since budget form stages are never moved backwards.
Clicking the Advance Forms button on this screen will advance all the budget forms to the indicated stages. The
back button can be used to change selection criteria, if required. Before advancing the budget forms, the
process will attempt to lock each and every form that has a stage value less than the target stage. All the forms
will be advanced only if stage advancer can obtain a lock on each and every budget form. Either all the forms
will be advanced or none.
8.3.7 Form Mass Soft Deletion
Form Mass Soft Deletion screen allows users of SAP Budgeting and Planning for Public Sector to soft delete
multiple budget forms. An Organization can have different number of budget requests in a year. This Feature
mainly helps in deleting multiple budget requests at a time.
Form Mass Soft Deletion helps the user delete the multiple budget requests based on certaincriteria, such as
Form Name (VC name of the form instance), Budget Year, and FM Area. All the budget requests are retrieved
against above mentioned criteria and allows the user to soft delete the multiple budget forms at a time.
You can access the Form Mass Soft Deletion for SAP Budgeting and Planning for Public Sector by choosing
Budget Administration Form Mass Soft Deletion .

Process
The following parameters can be used to search for the list of budget requests:
1. Form Name
2. FM Area
3. Budget Year
Financial Management Area, Budget Year, and Form Name are required fields. You must click the Search button
once the mandatory values are filled.
Each Form ID in the displayed list has a corresponding checkbox. This checkbox determines if the form ID is
selected or not for the deletion.
You can click the Select All button to select all the form IDs for the deletion and click the Deselect All button to
deselect all the form IDs.
You can click the Delete button to temporarily delete the selected form IDs.
8.3.8 Manage Deleted Forms
Use
Use the Manage Deleted Forms screen to manage the forms that were temporarily deleted by users.
Administrators can search for forms based on the various search parameters.
Process
The following parameters can be used to search for the list of deleted forms:
● Form Name
● FM Area
● Fund Center
● Fund
● Grant
● Funded Program
● Functional Area
● Budget Year
● User Name
Financial Management Area and Form Name are required fields. A user must, at least, enter these fields and hit
the Search Forms button to display a list of temporarily deleted budget forms that satisfy criteria entered.
Value help (similar to F4 help on traditional SAP screens) is provided for every field on this screen. This helps
ensure that only valid values can be entered into the fields on this screen.

Each Form ID in the displayed list has a corresponding checkbox . This checkbox determines if the form ID is
selected or not. To select a Form ID, check the respective checkbox. You can select or deselect the entire list
using the Select button or the Deselect Button.
Click the Recover button to restore the selected form IDs in the system – that is, the selected form IDs will no
longer be deleted. If there are any errors while the form is being recovered, they will be written to the log and an
error will be shown. If the recover is successful, an audit log will be saved marking the recover of the selected
forms.
Clicking the Hard Delete button to completely delete the form IDs from the system – that is, the form ID will no
longer be available anywhere in the system. All the corresponding data for the selected forms will be
permanently deleted. If there are any errors while the form is being deleted, the will be written to the log and an
error will be shown . If the deletion is successful, an audit log will be saved marking the deletion of the selected
forms.
8.3.9 Workflow Administration

SAP Budgeting and Planning for Public Sector offers worfklow task functionality for completing Stage
Advances. To take advantage of using workflow tasks for approving and rejecting Stage Advance requests there
are three options available for driving the workflow task assignments and notifications:
1. Custom Business Add-in (BAdI) option

An enhancement spot and Business Add-in (BAdI) has been provided and custom implementations can be
created using the Form Definition (Form Name) as a filter to define custom logic for determining workflow
approver and notification recipients.
2. FM Dimension Hierarchy-Driven option
Configuration is provided on the Form Mapping tab of the SAP Budgeting and Planning for Public Sector
Combo Edit screen, where an InfoObject hierarchy can be selected for a basis to drive the workflow
Aapprovers and notification recipients. If a hierarchy is configured then an assumption is made in relation
to the level of stage advance and the hierarchy node that is used to assign workflow approvers and
notification recipients. The assumption is for each level of stage advance, the same level of nodes upwards
in the hierarchy will be read to determine the target hierarchy node to be used to assign the workflow
approvers and notification recipients.
3. Manual Approver and Notification Maintenance
SAP Budgeting and Planning for Public Sector configuration screens are provided to maintain approvers
and notification recipients at either the Form Definition or Form Instance level.
Not all form definitions need to use the same workflow option. For example, one form definition could use the
custom BAdI logic, another form definition could use the FM Dimension Hierarchy option and yet another form
definition could use the manual approver and notification maintenance. However one form definition cannot
utilize more than one workflow option, and only one workflow option will be used at runtime for the form
definition.
During runtime when a Stage Advancement is requested the following logic occurs:
1. Is there an active BAdI implementation for the form definition? If so, the custom BAdI logic is used to
assign approvers and notification recipients.
2. Are there are no active BAdI implementations and there is a workflow hierarchy configured? If so, the
hierarchy logic is used along with the configured hierarchy to assign approvers and notification recipients.
3. Are there are no active BAdI implementations and there no workflow hierarchy configured? If so, the
manual approver and notification configuration is used to configure approvers and notification recipients.

Note that even though configuration and setup steps are followed, end users will not be able to use the new
Stage Workflow feature in custom forms until the VC models are updated with the APIs.
Custom Business Add-In (BAdI) Option
Enhancement spot /PBFBI/ES_WF_AGENTS_PROVIDER and BAdI /PBFBI/WF_AGENTS_PROVIDER_BADI are

provided to allow custom implementations to define the logic for assigning workflow Approver and Notification
Recipients. A custom implementation using the Form Definition as a Filter is required to use this option. When
stage advancement is requested, if there are any active BAdI Implementations for the Form Definition, then the
custom logic in the implementation will be used to determine Approvers (Method GET_APPROVERS) or
Notification Recipients (method GET_NOTIFICATION_RECIPIENTS).
See the SAP Budgeting and Planning for Public Sector Configuration Guide section Workflow Administration
and Configuration for more details.
FM Dimension Hierarchy-Driven option
There are two prerequisites for the hierarchy-driven option: configuration and hierarchy node master data
attributes.
A configuration screen is provided in the Combo Edit area to select an Info Object and Hierarchy to use for
assigning workflow approvers and notification recipients. When stage advances are requested, the configured
hierarchy will be read and the target hierarchy node will be assigned. For each level of stage advance, the same
level of nodes upwards in the hierarchy will be read to determine the target hierarchy node to be used to assign
the workflow approvers workflow approvers and notification recipients. The Combo Edit configuration for
maintaining the workflow hierarchies can be accessed by navigating to Administration Budget Forms
Combo Edit .
The actual approver and notification recipient user IDs will need to be maintained in the master data for the
hierarchy nodes. The five SAP Budgeting and Planning for Public Sector header dimension InfoObjects (Fund
Center, Fund, Funded Program, Functional Area, and Grant) have five attributes for approvers and five
attributes for Notification Recipients. The user IDsmaintained in those attributes will be assigned as workflow
approvers or notification recipients.
See the SAP Budgeting and Planning for Public Sector Configuration Guide section Workflow Administration
and Configuration for more details.
Manual Approver and Notification Recipient Maintenance
Manual Approver Maintenance
To use a manual approver for workflow, an approver must be maintained, either at the Form Definition level or
the Form Instance level. Form approvers maintained at the Form Instance level take precedence over approvers
maintained at the Form Definition level. The following user interfaces allow users to maintain approvers.

● For Form Definition (Form Level Approval)
The Form-Level Approval screen can be used to maintain Approvers for Form Definition and Stage. Primary
and secondary approvers can be maintained along with an Active field that determines which approver is
active. If the Active field is left blank or 0, then the Primary approver is set by default.
● For Form Instances (Form Instance Approval)
Approvers can be defined at a more granular or form instance level using this screen. The screen functions
are similar to Form Definition.
Manual Notification List Maintenance
This screen can be used to maintain a list of users that should be notified whenever a decision is made on an
approval request. Whether the stage advance request is approved or rejected, a notification is sent to the list of
users maintained at the Form Definition level or the Form Instance level and the user who initiated the stage
advance workflow. A notification list has to be maintained for each stage.
● For Form Definition (Form Level Notification)

The Form Definition Notification List screen can be used to maintain a list of users at the Form Definition-
Stage level.
● For Form Instances (Form Instance Notification)
The Form Instance Notification List screen can be used to a maintain list of users at the Form Definition-
Stage level.
Form – Web Dynpro App Mapping Maintenance (Form Workflow Mapping)
This screen can be used to map the form definition to the corresponding page in the portal. The combination is
used to link an approval request task in the Universal Worklist (UWL) to directly open the form in the
corresponding budget form template. The settings for this table can be obtained by navigating to Portal
Content Administration Portal Content and locating the respective pages related to budget forms. Open
Page Properties and click All to find out the required settings.
● Form Name – the form definition (also known as form name or VC name)
● Role – can be obtained from the Location field in page properties; append text “ROLES://” in front of this
setting
● Web Dynpro Application – a combination of the ID Prefix and ID fields
Example values for standard Budget Form template are:
Form Name DP2009
Role ROLES:// portal_content/com.sap.pct/every_user/com.sap.cdev.pbf.bp_folder/

com.sap.cdev.pbf.pages/com.sap.cdev.pbf.pages.budget_form_template
Web Dynpro Application ● ID Prefix – com.sap.cdev.pbf.pages

● ID – budget_form_template
● Value –com.sap.cdev.pbf.pages.budget_form_template

8.4 Personnel Expenditure Configuration
Use
Personnel expenditure planning (PEP) is the calculation of the cost of each individual employee or vacant
position. Most of the position and employee data is maintained within the HR system. The data will be brought
into the SAP Budgeting and Planning for Public Sector application at specific points in the budget formulation
process. Budget analysts are responsible for recording changes that will be impacted by budgets adopted in
the future.
SAP Budgeting and Planning for Public Sector offers two types of PEP projections: Fiscal Period projections and
Flexible Pay Period projections.
● Fiscal Period Projections were the original type of projections offered by SAP Budgeting and Planning for
Public Sector. Fiscal period projections use the configured Fiscal Year Variant to determine how the results
are to be calculated. For Fiscal Period PEP the lowest level of results are at the fiscal period level.
Additionally What-if projections can be executed on top of Fiscal Period projections. What-if projections
uses a previously executed Fiscal Period projection, known as a Reference projection, and takes additional
selections and input criteria to produce new results based on some specific scenarios. Examples include
adding or removing benefits, changing pay scale/step date criteria, and so on.
● Flexible Pay Period Projections were added to address the requirement to produce results by pay period.
These projections produce results at the fiscal period and pay period levels. For Flexible Pay Period PEP the
lowest level of results are at the pay period level. Flexible Pay Period PEP utilizes the same configuration
and master data as Fiscal period PEP (with some exceptions) and also requires some additional
configuration. The same Employee and Position master data can be used for either Fiscal Period PEP or
Pay Period PEP with one exception. Benefit Rule maintenance requires additional information for pay
period month, year and accumulators to calculate benefits for Pay Period PEP.
Pay Period PEP offers the following additional functionality:
○ Attrition and Backfill projections
Attrition and Backfill projections can be executed on top of Pay Period Projections. Attrition and
Backfill projections uses a previously executed Pay Period projection, known as a Reference projection,
and takes previously configures Attrition and Backfill rules to produce new results based on some
specific scenarios. Attrition and Backfill rules can be configured as Attrition only, Backfill only, or
Attrition and Backfill.
○ Flexible source for Employee and Position master data
Pay Period PEP supports having Employee and Position master data for PEP in DSO objects rather
than the Employee and Position InfoObjects. There are several setup steps and configuration required
to use this options. Details for all Pay Period PEP, Attrition and Backfill and Maintaining Employee and
Position Master Data DSOs can be found in Solution Manager or the PEP Configuration guide.
The following diagram illustrates what functionality each PEP type supports:
PEP type Fiscal Period Re Pay Period Results What-if Scenarios Attrition and Back Employee and Po
sults fill Scenarios sition MD from
DSO
Fiscal Period PEP x x

Flexible Pay Period x x x x
PEP
PEP global configuration, such as parallelization parameters, global table settings and currency conversion
types are utilized by both Fiscal Period and Pay Period PEP. There are additional configuration steps specific for
Fiscal Period PEP and Pay Period PEP. Please refer to Solution Manager for details on the configuration steps.
This document assumes that you have some level of familiarity with the terminology and the functions
associated with SAP Budgeting and Planning for Public Sector PEP. The aim of this document is to provide you
with all the information you need to navigate through and optimize the performance of SAP Budgeting and
Planning for Public Sector PEP. We recommend that you refer to this document whenever necessary during the
hands-on operation of SAP Budgeting and Planning for Public Sector PEP.
1. While there are two types of PEP available, Fiscal Period PEP and Pay Period PEP, it is assumed that
customers will use one type or the other, but not both
2. Fiscal Period PEP allows What-if scenarios and Pay Period PEP allows Attrition and Backfill scenarios.
Fiscal Period PEP will not support Attrition and Backfill scenarios and Pay Period PEP will not support
What-if scenarios.
Prerequisites
The following configuration prerequisites apply to both Fiscal Period PEP and Flexible Pay Period PEP (access
via backend IMG transaction SPRO). Please refer to Solution Manager or PEP Configuration guide for details of
the configuration steps:
● Maintain SAP Budgeting and Planning for Public Sector Global Settings (PEP related settings)
● Maintain SAP Budgeting and Planning for Public Sector Projection types
● Parallelization of Global Settings
The following configuration prerequisite applies only to Fiscal Period PEP:
● Process Chain Configuration
The following configuration prerequisites apply only to Flexible Pay Period PEP (access via backend IMG
transaction SPRO):

● Maintain Pay Period Types
● Upload Pay Period Table from File
● Display Pay Period Table entries
● Maintain Master Data DSO for Employee and Position (optional)
● Business Add-in (BAdI) for Attrition and Backfill (optional)
The following master data prerequisites apply to both Fiscal Period PEP and Flexible Pay Period PEP:
● Country ID
● Pay Scale Type
● Pay Scale Are
● ES Grouping CAP

● Pay Scale Group
● Pay Scale Level
● Promote Date
● Salary Override
● Employee Group
● Employee Sub Group
● Personnel Area
● Personnel Sub-Area
● FM Area
● Fiscal Year Variant
● Fund Center
● Funded Program
● Grant
● Functional Area
● Fund
● Benefit Area
● Benefit Plan
For Flexible Pay Period PEP there is an additional prerequisite:
● Benefit Rules for Pay Periods
For Attrition and Backfill Projections there are additional pre-requisites:
● Attrition Rules
● Attrition and Backfill Group Rules
Features
Most of the data needed for the Fiscal Period and Pay Period PEP calculation will be imported from the HR
system. The information will be imported at the beginning of each budget formulation process. Within SAP
Budgeting and Planning for Public Sector, the Fiscal Period and Flexible Pay Period PEP calculations are based
on data defined for Positions, Employees, Jobs, Benefit Rules and Rates, and Pay Levels. Each of these
elements are defined separately but are related. Due to the relationships between each of the PEP elements,
the components must be defined in a specific order:
1. Pay Levels
2. Benefit Rules
3. Benefit Rates
4. Jobs
5. Positions
6. Employees
Relationships
● Benefits are assigned to jobs, positions, and employees

● Jobs are assigned to positions and employees
● Positions are assigned to employees

SAP Budgeting and Planning for Public Sector supports and also qualifies all the positions and employees that
have different Job Classes maintained for a given position and its corresponding employees.
The PEP calculation will attempt to find the data at the employee level. If an item is not found for the employee,
the calculation will look to the related position and then, if necessary, will look to the job class maintained at the
employee level.
Similarly the PEP calculation will attempt to find the data at the position level. If an item is not found for the
position, the calculation will look to the job class maintained at the position level.
Overfills
A PEP Overfill occurs when the number of Employees assigned to a Position are greater than the Authorized
Count on the Position. Up to PBF Release 8.1 PEP results for Overfills were posted with Negative values and
Negative Vacant Counts, thus reducing the PEP results by the Overfill Amounts and counts. In SAP Budgeting
and Planning for Public Sector 1.0 a configuration setting was added to allow users to specify if Overfill results
should be posted with negative or postitive values and Vacant Counts. For more information on this
configuration refer to Solution Manager or SAP Budgeting and Planning for Public Sector Configuration guide
in the section titled Global Configuration.
Reverse Progression
Reverse Progression in PEP is the process of finding the earlier Pay Scale Levels for Employees if the PEP
Projection includes periods prior to the Employee Extract Date. Up to PBF Release 8.1 PEP results always
included Reverse Progression in certain scenarios. In SAP Budgeting and Planning for Public Sector 1.0 a
configuration setting was added to allow users to specify if PEP should calculate Reverse Progressions or not. .
For more information on this configuration refer to Solution Manager or SAP Budgeting and Planning for Public
Sector Configuration guide in the section titled Global Configuration.
Currency Conversion
8.4.1 Job Maintenance
Use
Job is a structure used to define types of job classes to which positions and employees are assigned. The
public budget formulation process involves forecasting various expense types to arrive at a final budget. Direct
personnel costs such as salaries, taxes, and benefits constitute a large expense area, especially in the public
sector.
Job is used to assign defaults for pay scale details and benefits costs. These defaults are used when elements
are not defined at the employee/position level or when a new position is created in the budget form. The
various features of Job Maintenance help users to arrive at the personnel expense area for the overall budget of
an agency, department, or an organization.

Prerequisites
1. You have setup the following master data:

○ Country ID
○ Pay Scale Type
○ Pay Scale Area
○ ES Grouping CAP
○ Pay Scale Group
○ Pay Scale Level
○ FM Area
○ Commitment Item
○ Benefit Area
○ Benefit Plan
2. You have defined benefit rules. To learn how to maintain benefit rules, see Maintaining Benefit Rules [page
153].
3. Jobs must exist in the system before you can search for or edit them.
Features
The Job Maintenance screen allows you to perform the following actions through the available buttons:
Button Description
New Enables the creation of a new job.
Copy Creates a new job record by copying some information from

the currently selected job.
Search Searches for jobs based on other criteria, such as Job Re
port number
Edit Makes all fields and tables available for changes for the cur
rently selected Job
Save Saves information entered in the respective detail tab.
Cancel Ends edit mode for a position without saving changes
Select Interval Opens a popup with list of intervals (time-dependent data)

that can be loaded
New (Benefits tabs) Creates a new record for maintenance in the respective ta
bles.

Button Description
Copy (Benefits tabs) Copies information from the selected record and creates a
new record for maintenance.
Delete (Benefits tabs) Deletes the selected record from the respective tables.
The Job maintenance screen consists of the following areas:
● Job Selection
This area displays the job selection field and the Interval Start and End Date.
If different intervals exist for the job, pressing the Select Interval button will present the list of defined
intervals that can be selected. The interval selected will influence the data presented in the Detail and
Benefits tabs.
● Details
This area is divided into tabs that group relevant data for job maintenance.
The following tabs are available in the details area.
Job Details
On this tab, you maintain general information for the job in the following fields:
● Job: The job number is automatically generated by the system. You can enter a description for the new job
in the field adjacent to the job number.
● Job RPT No: Specifies the client-defined job number, usually generated in the HR system.
● Country ID: Indicates the country code for the job.
● Pay Scale Type: Defines the pay plan used for basic pay.
● Pay Scale Area: Indicates a specific geographic region. You can use this field to represent local pay or
general area as well.
● ES Grouping CAP: Defines the bargaining unit.
● Pay Scale Group: This field, together with Pay Scale Level, determines the pay level or pay grade of a job.
● Pay Scale Level: Identifies the pay level within the pay scale group.
● FM Area: Refers to the financial management area for the job. This detail determines the fiscal year variant
and currency code for the job. This is a mandatory field.
● Commitment Item: Refers to the commit item to be used when posting salary related costs for this job.
● Distribution Code: Identifies the distribution table to be used when spreading costs across periods in a
fiscal year.
● Performance St. Period: Specifies the starting month of performance for the job when the performance
period is less than 12 months.
● Performance Period: Indicates the number of months for which the job will be funded from the Performance
St. Period.
● FTE Period: Indicates the number of periods within a fiscal year that a job’s costs should be spread over.
Benefits
On this tab, you maintain various benefit plans for the job using the following fields:
● Start Period and End Period: Allows you to maintain the start and end period for a particular benefit.
● Wage Type: (Optional) select the wage type code for this benefit rule.
● Benefit Area: Indicates the benefit area.

● Benefit Plan: Specifies the benefit plan that is associated with the job.
You can maintain the benefit table using the New, Copy, Delete, and Save buttons on the tab.
Activities
In the Job Maintenance screen, you can:
● Edit a job and associated time dependent master data using the Select Interval button. Note that any time
intervals that are completely in the past will not be editable.
● Create a Job [page 132] either through the New or Copy buttons
More Information
● Personnel Expenditure Projection [page 88]

● Position Maintenance [page 133]
● Employee Maintenance [page 141]
8.4.1.1 Creating a New Job
Use
The Job Maintenance screen facilitates the creation of new jobs either by creating a new record or by copying
an existing record and maintaining the necessary information.
Prerequisites

○ Country ID
○ Pay Scale Type
○ Pay Scale Area
○ ES Grouping CAP
○ Pay Scale Group
○ Pay Scale Level
○ FM Area
○ Commitment Item
○ Benefit Area

○ Benefit Plan
153].
3. Jobs must exist in the system before you can search for or edit them.
Procedure
To create a new job, carry out the following steps:
1. Choose Administration PEP Maintenance Personnel Maintenance . In the Detailed Navigation area,
choose Job Maintenance.
2. In the Job Selection area of the Job Maintenance screen, click New. The system creates a new record and
generates a new job number on the Job Details tab. The default Interval Start Date is the current date. The
default Interval End Date is 12/31/9999. Both default dates can be changed as needed.
3. Maintain the necessary information on the following tabs and save the information for each tab:
 Note
To know the function of each field, see Job Maintenance [page 129].
○ Job Details
○ Benefits
To create a new job by copying an existing job, do the following:
1. Using the filter criteria, search for a job. The system displays matching jobs in the List of Jobs area.
2. Select a job from the list and click Copy in the Filter Selection area. The system creates a new job with a
new job number and information from the selected job. All existing date intervals from the source job will
be copied to the new job.
○ Job Details
○ Benefits
8.4.2 Position Maintenance
Use
Position is a structure used to define available slots to which employees can be assigned. The public budget
formulation process involves forecasting various expense types to arrive at a final budget. Direct personnel
costs such as salaries, taxes, and benefits constitute a large expense area, especially in the public sector.
The various features of position maintenance help users to arrive at the personnel expense area for the overall
budget of an agency, department, or an organization.

Prerequisites

○ Country ID
○ Pay Scale Type
○ Pay Scale Area
○ ES Grouping CAP
○ Pay Scale Group
○ Pay Scale Level
○ Promote Date
○ Salary Override
○ Salary
○ Currency
○ Employee Group
○ Employee Sub Group
○ FM Area
○ Fund Center
○ Funded Program
○ Grant
○ Functional Area
○ Fund
○ Benefit Area
○ Benefit Plan
153].
3. Positions must exist in the system before you can search for or edit them.
Features
The Position Maintenance screen allows you to perform the following actions through the available buttons:
Button Description
New Enables the creation of a new position.
Copy Creates a new position record by copying some information

from the currently selected position.
Search Displays a popup that allows you to search for positions

based on attribute values, such as Fund Center

Button Description
rently selected position.
Save Saves information entered in all tabs.
Cancel Ends edit mode for a position without saving changes.
Select Interval Opens a popup with list of intervals (time dependent data)
that can be loaded
New (Allocations and Benefits tabs) Creates a new record for maintenance in the respective ta
bles.
Copy (Allocations and Benefits tabs) Copies information from the selected record and creates a
Delete (Allocations and Benefits tabs) Deletes the selected record from the respective tables.
The position maintenance screen consists of the following areas:
Position Selection
This area displays the position selection field and the Interval Start and End Date.
If different Intervals exist for the position then pressing the Select Interval button will present the list of defined
intervals that can be selected. The Interval selected will influence the data presented in the Detail, Salary,
Home Funding, Benefits, and Allocation tabs.
Position Data
The following tabs are available:
Details
On this tab, you maintain general information for the position in the following fields:
● Job Class: Specifies the job class of the position. The job class provides default characteristics for the
position record.
● Authorization to Fill: Indicates whether the position is approved to be filled.
● Authorized Count: Specifies the number of employees that can fill the position. During a personnel
projection run, the system first calculates the cost of employees assigned to the position, then the
remaining position vacancies are calculated based on the position cost. Should an overfill occur (Position
Authorized Count is less than the number of Employees assigned to the position) the results will be
recorded as per the Overfill Sign setting in the SAP Budgeting and Planning for Public Sector Globals table.
Details for the Overfill Sign can be found in the SAP Budgeting and Planning for Public Sector Configuration
guide in the section titled Global Configuration.
● Salary %: A percentage of salary to be projected. For example, an entry of 50% indicates that assigned
employees are paid half the salary for the position. This field is used to calculate the number of full-time
employees (FTE).
● Benefit %: A percentage of benefit costs to be projected.

● Status: The status must be active in order for the employee costs to be projected. The Active status setting
is maintained in the SAP Budgeting and Planning for Public Sector Globals table. For details see the
Solution Manager or SAP Budgeting and Planning for Public Sector Configuration Guide in the section
titled Global Configuration.
● FTE Period: Indicates the number of periods within a fiscal year that a position’s costs should be spread
over.
● Performance St. Period: Specifies the starting month of performance for the position when the
performance period is less than 12 months.
● Performance Period: Indicates the number of months for which the position will be funded from the
Performance St. Period.
● Report FTE: Indicates a static FTE amount, entered by the user for use in reports. This value does not
impact the projection.
● Employee Group: Indicates the employee group to which the position is assigned.
● Employee Sub Group: Indicates the employee sub-group to which the position is assigned.
● Position Description: Text description of the Position
● Report Position: Specifies the client-defined position number, usually generated in the HR system.
Salary
This tab allows you to maintain salary details. If this tab is left blank, then the system calculates the pay from
the job class code maintained on the Position Details tab. The following fields are available for maintenance on
the Pay Details tab:
● Country ID: Indicates the country code for the position.

● Pay Scale Group: This field, together with Pay Scale Level, determines the pay level or pay grade of an
employee.
● Promote Date: Indicates a date when the position may receive an increased salary either as a percentage
increase or a pay-level promotion. If no date is maintained here then PEP will not calculate any increases
for the position.
● Salary Override: Indicates the salary record that should be considered during a projection.
○ Yes – Denotes that the amount in the Salary field on the Salary Details tab is considered for
projections.
○ No – Indicates that the salary is determined based on the value found in the Pay Level Maintenance
table for the Pay Details values Country ID, Pay Scale Type, Pay Scale Area, ES Grouping for CAP, Pay
Scale Group, and Pay Scale Level.
● Salary: Allows you to enter a salary amount if the Salary Override indicator is set to Yes.
● Currency: The FM area currency will be defaulted as the position currency. A different currency can be
entered if the position currency differs from the FM Area currency.
Home Funding
This tab consists details for the position with regard to financial management. The following fields are available
to maintain the details:
● FM Area: Refers to the financial management area for the position. This detail determines the fiscal year
variant and currency code for the position. This is a mandatory field.

● Fund Center: Defines the fund center associated with the position.
● Funded Program: Indicates the funded program associated with the position.
● Grant: Mentions the grant associated with the position.
● Functional Area: Specifies the functional area associated with the position.
● Fund: Points out the fund that is associated with the position.
Allocations
On this tab, you allocate the position to different FM areas for different time intervals. This tab makes use of all
the fields on the Home Funding tab and the following additional fields:
● Start Period and End Period: Allows you to specify the time interval for a particular allocation.
● Allocation %: Indicates the percentage allocation of a position to a different funding area. During a
personnel projection, personnel cost is calculated and assigned to different funding areas based on
allocation details. If no data is maintained here then PEP will allocate projected costs to the Home Funding
details. If less than 100% is maintained here then PEP will allocate the remaining percentage to the Home
Funding details.
You can maintain the allocation table using the New, Copy, Delete, and Save buttons on the tab.
Benefits
On this tab, you maintain various benefit plans for the position. If no data is maintained here then PEP will apply
any benefits defined in the associated Job for the position. If benefits are maintained here then any Job
benefits will be ignored.
Maintain position benefits using the following fields:
● Benefit Plan: Specifies the benefit plan that is associated with the position.
Activities
In the Position Maintenance screen, you can do the following:
● Search for positions [page 138]

● Edit a position
● Create a position [page 139] either through the New or Copy buttons
More Information
● Personnel Expenditure Planning [page 88]

8.4.2.1 Searching for Positions
Prerequisites

○ Country ID
○ Pay Scale Type
○ Pay Scale Area
○ ES Grouping CAP
○ Pay Scale Group
○ Pay Scale Level
○ Promote Date
○ Salary Override
○ Salary
○ Employee Group
○ FM Area
○ Fund Center
○ Funded Program
○ Grant
○ Functional Area
○ Fund
○ Benefit Area
○ Benefit Plan
153].
3. You have created positions or the positions already exist in the system.
Procedure
To search for existing positions, do the following:
choose Position Maintenance.
2. In the Position Selection section, click Search.
The system displays the Position Search popup.
3. On the Position Search popup, use the following criteria to search for positions:
○ FM Area
○ Fund Center
○ Job Class
○ Report Position
○ Employee Group

○ ES Grouping CAP
○ Position Status
If you know the position number, enter the value using the Position field.
4. Click Search to load the available positions.
5. In the Matching Positions table, select the desired position.
6. In the Interval table, click the row with the desired start and end dates.
7. Click Load to display the position record.
8. Click Cancel to return to the Position Maintenance screen without loading a position.
9. To edit a loaded position, click Edit and make the necessary changes in the Details tabs.
8.4.2.2 Creating a New Position
Use
The Position Maintenance screen facilitates the creation of new positions either by creating a new record or by
copying an existing record and maintaining the necessary information.
Prerequisites

○ Country ID
○ Pay Scale Type
○ Pay Scale Area
○ ES Grouping CAP
○ Pay Scale Group
○ Pay Scale Level
○ Promote Date
○ Salary Override
○ Salary
○ Currency
○ Employee Group
○ FM Area
○ Fund Center
○ Funded Program
○ Grant
○ Functional Area
○ Fund
○ Benefit Area

○ Benefit Plan
153].
Procedure
To create a new position, carry out the following steps:
choose Position Maintenance.
2. In the Filter Selection area of the Position Maintenance screen, click New.
The system creates a new record and generates a new position number. The default Interval Start Date is
the current date. The default Interval End Date is 12/31/9999. Both default dates can be changed as
needed.
 Note
To know the function of each field, see Position Maintenance [page 133].
○ Position Details
○ Pay Details
○ Organization
○ Home Funding
○ Allocations
○ Benefits
To create a new position by copying an existing position, do the following:
1. Using the Position Search popup filter criteria, search and load an existing position.
The system displays the loaded position in the Position Maintenance screen header.
2. Click Copy in the Position Maintenance screen header.
The system creates a new position with a new position number and information from the loaded position.
All existing date intervals from the source job will be copied to the new job.
○ Details
○ Salary
○ Home Funding
○ Allocations
○ Benefits

8.4.3 Employee Maintenance
Use
Employee is a structure used to define people employed by the organization which are assigned to positions.
The public budget formulation process involves forecasting various expense types to arrive at a final budget.
Direct personnel costs such as salaries, taxes, and benefits constitute a large expense area, especially in the
public sector.
The various features of Employee Maintenance help users to arrive at the personnel expense area for the overall
budget of an agency, department, or an organization.
Prerequisites

○ Country ID
○ Pay Scale Type
○ Pay Scale Area
○ ES Grouping CAP
○ Pay Scale Group
○ Pay Scale Level
○ Promote Date
○ Salary Override
○ Salary
○ Currency
○ Employee Group
○ Personnel Area
○ Personnel Sub Area
○ FM Area
○ Fund Center
○ Funded Program
○ Grant
○ Functional Area
○ Fund
○ Benefit Area
○ Benefit Plan
○ Position
153].
3. Employees must exist in the system before you can search for or edit them.

Features
The Employee Maintenance screen allows you to perform the following actions through the available buttons:
Button Description
New Enables the creation of a new employee.
Copy Creates a new employee record by copying some informa

tion from the currently selected employee.
Search Displays a popup that allows you to search for positions

based on attribute values, such as Fund Center
rently loaded employee.
Save Saves information entered in all tabs.
Cancel Ends edit mode for a position without saving changes.
Select Interval Opens a popup with list of Intervals (time-dependent data)

that can be loaded
New (Allocations and Benefits tabs) Creates a new record for maintenance in the respective ta
bles.
Copy (Allocations and Benefits tabs) Copies information from the selected record and creates a
Delete (Allocations and Benefits tabs) Deletes the selected record from the respective tables.
The Employee Maintenance screen consists of the following areas:
Employee Selection
This area displays the employee selection field and the Interval Start and End Date.
If different Intervals exist for the employee then pressing the Select Interval button will present the list of
defined intervals that can be selected. The interval selected will influence the data presented in the Detail,
Salary, Home Funding, Benefits, and Allocation tabs.
Employee Data
The following tabs are available:
Details
On this tab, you maintain general information for the employee in the following fields:
● Entry Date: Specifies the date the employee record was created.
● Job Class: Specifies the job class of the employee. The job class provides default characteristics for the
employee record.
● FM Area: Refers to the financial management area for the employee. This detail determines the fiscal year
variant and currency code for the employee. This is a mandatory field.

● Reporting Job Class: Specifies the client-defined job number, usually generated in the HR system.
● Position: Indicates the employee’s assigned Position Number.
● Performance St. Period: Specifies the starting month of performance for the employee when the
performance period is less than 12 months.
● Performance Period: Indicates the number of months for which the employee will be funded from the
Performance St. Period.
● Status: Indicates the current status of the employee. The status must be 3 (Active) in order for the
employee costs to be projected.
● FTE Period: Indicates the number of periods within a fiscal year that a employee’s costs should be spread
over.
● Extraction Date: Indicates the date the employee record was extracted from the HR system and loaded into
● MI: Specifies the middle initial of the employee.
● First Name: Specifies the first name of the employee.
● Last Name: Specifies the last name of the employee.
● Salary %: A percentage of salary to be projected. For example, an entry of 50% indicates that assigned
employees are paid half the salary for the employee. This field is used to calculate the number of full-time
employees (FTE).
● Benefit %: A percentage of benefit costs to be projected.
● Report FTE: Indicates a static FTE amount, entered by the user for use in reports. This value does not
impact the projection.
● Employee Group: Indicates the employee group to which the employee is assigned
● Employee Sub Group: Indicates the employee sub-group to which the employee is assigned
● Personnel Group: Indicates the personnel group to which the employee is assigned
● Personnel Sub Group: Indicates the personnel sub-group to which the employee is assigned
● Description: Text description of the Employee
● Report Number: Specifies the client-defined employee number, usually generated in the HR system
Salary
This tab allows you to maintain salary details. If this tab is left blank, then the system calculates the pay from
the employee's position job class code maintained on the Position Details tab. The following fields are available
for maintenance on the Pay Details tab:
● Country ID: Indicates the country code for the employee.

● Pay Scale Group: This field, together with Pay Scale Level, determines the pay level or pay grade of an
employee.
● Promote Date: Indicates a date when the employee may receive an increased salary either as a percentage
increase or a pay-level promotion.
● Longevity Date: Indicates a date when the employee may receive a one-time benefit associated with
longevity.
● Salary Override: Indicates the salary record that should be considered during a projection.

○ Yes – Denotes that the amount in the Salary field on the Salary Details tab is considered for
projections.
○ No – Indicates that the salary is determined based on the value found in the Pay Level Maintenance
table for the Pay Details values Country ID, Pay Scale Type, Pay Scale Area, ES Grouping for CAP, Pay
Scale Group, and Pay Scale Level.
● Salary: Allows you to enter a salary amount if the Salary Override indicator is set to Yes.
● Currency: The FM area currency will be defaulted as the position currency. A different currency can be
entered if the position currency differs from the FM Area currency.
Home Funding
This tab consists of fields that provide details for the employee with regard to financial management. The
following fields are available to maintain the details:
● FM Area: Refers to the financial management area for the employee. This detail determines the fiscal year
variant and currency code for the employee. This is a mandatory field.
● Fund Center: Defines the fund center associated with the employee.
● Funded Program: Indicates the funded program associated with the employee.
● Grant: Mentions the grant associated with the employee.
● Functional Area: Specifies the functional area associated with the employee.
● Fund: Points out the fund that is associated with the employee.
Allocations
On this tab, you allocate the employee to different FM areas for different time intervals. This tab makes use of
all the fields on the Home Funding tab and the following additional fields:
● Start Period and End Period: Allows you to specify the time interval for a particular allocation.
● Allocation %: Indicates the percentage allocation of a employee to a different funding area. During a
personnel projection, personnel cost is calculated and assigned to different funding areas based on
allocation details.
You can maintain the allocation table using the New, Copy, Delete, and Save buttons on the tab.
Benefits
On this tab, you maintain various benefit plans for the employee using the following fields:
● Benefit Plan: Specifies the benefit plan that is associated with the employee.
Activities
In the Employee Maintenance screen, you can:
● Search for Employees [page 145]

● Edit an Employee
● Create an Employee [page 146] either through the New or Copy buttons

More Information
● Personnel Expenditure Projection [page 88]

● Position Maintenance [page 133]
8.4.3.1 Searching for Employees
Prerequisites

○ Country ID
○ Pay Scale Type
○ Pay Scale Area
○ ES Grouping CAP
○ Pay Scale Group
○ Pay Scale Level
○ Promote Date
○ Salary Override
○ Salary
○ Currency
○ Employee Group
○ Personnel Area
○ FM Area
○ Fund Center
○ Funded Program
○ Grant
○ Functional Area
○ Fund
○ Benefit Area
○ Benefit Plan
153].
3. You have created employee records or they already exist in the system.

Procedure
To search for existing employees, do the following:
1. Choose Administration PEP Maintenance Personnel Maintenance .In the Detailed Navigation area,
choose Employee Maintenance.
2. In the Employee Selection section, click Search.
The system displays the Employee Search popup.
3. On the Employee Search popup, use the following criteria to search for positions:
○ FM Area
○ Fund Center
○ Job Class
○ Position
○ Status
○ First Name
○ Report Number
○ Employee Group
○ ES Grouping CAP
○ Last Name
4. Click Search to load the matching employees.
5. In the Matching Employees table, select the desired employee.
6. In the Interval table, click the row with the desired start and end dates.
7. Click Load to display the employee record.
8. Click Cancel to return to the Employee Maintenance screen without loading an employee.
9. To edit a loaded employee, click Edit and make the necessary changes in the Details tabs.
8.4.3.2 Creating an Employee
Use
The Employee Maintenance screen facilitates the creation of new employees either by creating a new record or
by copying an existing record and maintaining the necessary information.
Prerequisites

○ Country ID
○ Pay Scale Type
○ Pay Scale Area
○ ES Grouping CAP

○ Pay Scale Group
○ Pay Scale Level
○ Promote Date
○ Salary Override
○ Salary
○ Currency
○ Employee Group
○ Personnel Area
○ FM Area
○ Fund Center
○ Funded Program
○ Grant
○ Functional Area
○ Fund
○ Benefit Area
○ Benefit Plan
○ Position
153].
3. Employee records must exist in the system before you can search for or edit them.
Procedure
To create a new employee, carry out the following steps:
choose Employee Maintenance.
2. In the Filter Selection area of the Employee Maintenance screen, click New.
The system creates a new record and generates a new employee number. The default Interval Start Date is
the current date. The default Interval End Date is 12/31/9999. Both default dates can be changed as
needed.
3. Click Edit and maintain the necessary information on the following tabs:
 Note
To know the function of each field, see Employee Maintenance [page 141].
○ Employee Details
○ Pay Details
○ Organization
○ Home Funding
○ Allocations

○ Benefits
4. Click Save.
To create a new employee by copying an existing employee record, do the following:
1. Using the Employee Search popup filter criteria, search and load an existing employee.
The system displays the loaded employee in the Employee Maintenance screen.
2. Click Copy in the Employee Maintenance screen header.
The system creates a new employee with a new employee number and information from the loaded
position.
3. Maintain the necessary information on the following tabs and save the information:
○ Details
○ Salary
○ Home Funding
○ Allocations
○ Benefits
8.4.4 Employee and Position Comparison
Use
As the name suggests, this is used to compare employee and position master data for two reference
projections. The user can enter two reference projections, and the report will display master data that is unique
to each projection.
Additional filter options are also provided to compare specific attributes of the master data such as employee,
position, employee group, and subgroup.
Restrictions
The projections displayed in value help for projection IDs are only reference projections to which the user has
authorization.
Prerequisites
All the master data and projections should be set up in the back end.
Features
Depending upon the type of comparison – that is, employee or position – the user can select the appropriate
tab to access the comparison screen.
In order to compare two reference projections, user must enter them on the input fields provided on the
screen. A value help is provided for assistance that allows the user to pick a reference projection from the list of
reference projections available in the system.

After selecting two reference projections for comparison, the user can hit the submit button to display the
comparison.
The report can be further filtered by specifying additional optional parameters on the selection screen such as:
● Employee group, subgroup, or employee ID for employee master data comparison

● Employee group, subgroup, or position ID for position master data comparison
Value help is also provided for each of these additional parameters.
8.4.5 Creating Pay Levels
Use
Pay levels define annual salary amounts, step duration and promotion information, and percentage increase for
fixed salaries by predefined combinations of pay scale elements. Pay scale elements in SAP Budgeting and
Planning for Public Sector include Country ID, Pay Scale Type, Pay Scale Area, ES Grouping for CAP, Pay Scale
Group, and Pay Scale Level.
For employees or positions with a Salary Override value of No, the personnel expenditure projection (PEP)
calculation will consider the annual salary amount that is maintained in the pay level table. The step duration
value determines the number of periods the employee or position should remain at the designated annual
salary amount. The New Level and New Group values are then used to identify the next annual salary amount to
be used after the step duration period.
For employees or positions with a Salary Override value of Yes, the PEP calculation will consider the percentage
increase to be applied to the salary amount defined on the master data record. This percentage will be applied
every 12 periods starting from the Promotion Date, which is also found on the master data record.
Prerequisites
You have defined the master data that relates to a pay level including:
● Country ID
● Pay Scale Type
● Pay Scale Area
● ES Grouping CAP
● Pay Scale Group
● Pay Scale Level
Procedure
You can search, edit, or copy pay levels on the Pay Level Maintenance screen. Choose Administration
Personnel Maintenance . In the Detailed Navigation area, choose Pay Level Maintenance

To search for a pay level, enter a search criteria and click Submit. To retrieve all existing pay levels, click Submit
without entering a search criteria.
To edit a pay level, do the following:
1. Search for and select the pay level that you want to edit.
The system displays the Salary Details screen.
2. In the Pay Level layout, select a pay level row to edit.
The system highlights the selected row.
 Note
You cannot change the pay scale element compound key.
3. In the Pay Level Details tab, enter all changes to existing values. The options are:
○ Starting Date: enter the date indicating when the row on the pay level table is valid.
○ End Date: the system will calculate the end date.
○ Currency code: enter the valid currency to be used for the pay level.
○ Amount: enter the annual amount for the pay level (with the compound key values). The amount is
used in the projection when there is no override of the salary.
○ Step Months: enter the number of periods that an employee and/or position is on the current pay level
before being moved to the new pay level and group. This is also used when projecting back in time to
get historic pay information.
○ New Level: enter the next pay scale level for a position or employee once the step duration has expired
at the current level.
○ New Group: enter the next pay scale group for a position or employee once the step duration has
expired at the current pay level.
○ Fixed Salary Increase %: enter the percentage of salary increase given to positions or employees on the
pay level when Salary Override is set to Yes in the position or employee maintenance record.
○ Description: enter a text description for the pay level record.
5. To exit without saving the changes, refresh the screen without saving.
To copy a pay level, do the following:
1. Search for and select the pay level that you want to edit.
The system displays the Salary Details screen.
2. In the Pay Level layout, select a pay level row to edit the to date, amount, step months, new group, new
level, fixed salary increase % and/or description.
 Note
You cannot change the pay scale element combination or end date.


8.4.6 Creating Projection Distributions
Use
Projection distributions are used in the PEP projection to redistribute the salary and percentage based benefit
costs for a fiscal year according to percentages defined by projection period. Without a projection distribution,
the PEP projection will distribute the salary and percentage based benefit costs evenly over the periods of a
fiscal year. Projection distributions allow the PEP projection to distribute the costs to more accurately reflect
when the costs will occur.
For example, when an entity is on a bi-weekly pay cycle, two of the 12 months will have three pays and the
remaining months will have only two pays for a total of 26 pays. The projection distribution percentages would
be larger for the two months with three pays (.115385 or 3/26) to the remaining period’s two pays (.076923 or
2/26)
Procedure
You can edit an existing or create a new projection distribution on the Projection Distribution screen. Choose
Administration PEP Maintenance Fiscal Period PEP .In the Detailed Navigation area, choose Projection
Distributions.
To edit a projection distribution, do the following:
1. Select the projection distribution that you want to edit.

The system lists the Projection Distribution Details table.
2. In the Details table, select a row to edit.
3. In the row, enter all changes to existing values. The options are:
○ Fiscal Period: enter the fiscal period (YYYYPPP) that is valid for the row.
○ Percentage: enter the percentage to be used for the fiscal period.
To create a new projection distribution, do the following:
1. On the Projection Distribution screen, click New.

The system displays the New Projection Distribution popup.
2. In the New Projection Distribution popup, enter a projection distribution code.
3. To save the information and create a new projection distribution, click Create.
5. To add projection distribution detail rows, click Add
on the Details table.
The system displays a new row in the Details table.
6. Select a fiscal period and enter a percentage.
7. Repeat step 6 until all projection distribution rows are entered.
8. To save the information, click Create.

To delete a projection distribution row, do the following:
1. Select a row in the Details tab on the Projection Scenario screen.

2. Click Delete.
3. To save the changes, click Create.
8.4.7 Maintaining Benefit Rates
Use
The personnel expenditure projection (PEP) requires benefit rates to be defined for combinations of benefit
area and benefit plans. The SAP Budgeting and Planning for Public Sector solution facilitates the creation of
benefit rates through the Benefit Rate maintenance screen. Using benefit rates, customers can configure rates
based on their individual needs.
Prerequisites
The following master data exists in the system:
● Benefit Areas
● Benefit Plans
● Benefit Rules
Procedure
To create a new benefit rate, do the following:
1. Choose Administration PEP Maintenance Personnel Maintenance .In the Detailed Navigation area,
choose Benefit Rates Benefit Rates .
2. On the Benefit Rates Detail tab, click New.
3. In the Details table, enter information in the following fields:
○ Benefit Area: select a benefit area code.
This selection will limit the available benefit plans.
○ Benefit Plan: select a benefit plan code.
○ Benefit Range Step: select a benefit range step.
The benefit range step can be any whole number. The benefit range step allows differing minimum
amount and maximum amount values within the same benefit area, benefit plan, and effective date
combination.
○ Start Date: enter the effective start date for this benefit rate row.

○ End Date: enter the effective end date for this benefit rate row.
○ Longevity Months: enter the number of months needed to qualify for the benefit rate row.
The system will determine the current longevity months for each position or employee based on the
position or employee longevity date.
○ Min Amount: enter the minimum amount of annual salary needed to qualify for this benefit rate row.
○ Max Amount: enter the maximum amount of salary that qualifies for this benefit rate row.
○ Amount: enter the annual amount associated with this benefit rate row.
○ Benefit Rate: enter the benefit rate or percentage value associated with this benefit rate row.
4. To save the information, click Save.
5. To exit without saving the information, refresh the screen without saving.
To search for a benefit rate, enter a search criteria and click Search. To retrieve all existing benefit rates, click
Search without entering a search criteria.
To edit a benefit rate, do the following:
1. Search for and select the benefit rate that you want to edit.
The system displays the Details screen.
2. Click Edit to change the start date, longevity months, min amount, max amount, amount or benefit rate of
the benefit rate.
 Note
You cannot change benefit area, benefit plan, benefit range step, and end date of a benefit rule.

4. To exit without saving the changes, refresh the screen without saving.
To delete a benefit rate, do the following:
1. Search for and select the benefit rate that you want to delete.
The system displays the Details screen.
2. Click Delete.
8.4.8 Maintaining Benefit Rules
Use
The personnel expenditure planning (PEP) requires benefit rates to be defined for combinations of benefit area
and benefit plans. The combinations of benefit area and benefit plans are created through benefit rules. The
SAP Budgeting and Planning for Public Sector solution facilitates the creation of benefit rules through the
Benefit Rules Maintenance screen. Using benefit rules, customers can create benefit area/benefit plan
combinations and assign attributes needed to calculate the cost of the benefits in the PEP projections.
In the previous releases, benefits were configured for the fiscal period. Fiscal feriod PEP projections use the
monthly benefit rules. To execute pay period PEP projections, the benefit rules need to be configured for pay
periods and pay years. An additional Pay Periods tab has been added to the Benefit Rules Maintenance for
maintaining the pay periods and pay years.

Prerequisites
You have defined the following master data:
● Benefit Area
● Benefit Plan
● Wage Type
● Accumulators
● Commitment Items
Procedure
To create a new benefit rule, do the following:
1. Choose PBF Administration PEP Maintenance Personnel Maintenance .In the Detailed Navigation
area, choose Benefit Rules .
2. In the Benefit Area screen, click Edit.
The Benefit Area table becomes editable.
3. In the Benefit Area table, click New.
The system displays the New Benefit Area popup.
4. In the New Benefit Area popup, select a benefit area.
5. To add the new benefit areas to the benefit rule, click OK.
6. To return to the Benefit Area screen without adding a benefit area, click Cancel.
7. To add benefit plans to the benefit area, click Next.
The system displays the Benefit Plan screen.
8. In the Benefit Plan screen, click Add.
The system displays the New Benefit Plan popup.
9. In the New Benefit Plan popup, enter information in the following fields:
○ Benefit Plan: select the benefit plan code associated with the selected benefit area.
○ Wage Type: select the wage type code for this benefit rule.
○ Calculation Basis: select the accumulator that is used as the basis of the calculation for this benefit
rule.
○ Calculation Order: enter the calculation order for the benefit rule to establish the sequence in which the
benefit rules should be calculated.
○ Benefit Start Period: enter the period in which the benefit costs for this benefit rule can begin to be
calculated in the PEP projection.
○ Commitment Item: select the commitment item code assigned to the benefit rule that will be posted by
the projection scenarios.
There is no limit to the number of benefit plans per benefit area.
10. To add the new benefit plan to the benefit rule for the selected benefit area, click OK.
11. To return to the Benefit Plan screen without adding a benefit area, click Cancel.
12. To add benefit months and accumulators to the benefit area/benefit plan rule, click Next. The next steps
depend on whether Fiscal Period PEP or Pay Period PEP is utilized.
○ For Fiscal Period PEP
1. To add the benefit months and accumulators for Fiscal Period PEP, select the Months tab. The
system displays the Benefit Months and Accumulator screen.

2. In the Months table on the Benefit Months and Accumulator screen, click Add.
The system displays a new row in the Months table.
3. Enter a number between 1-12 in the highlighted row.
4. In the Accumulator table on the Benefit Months and Accumulator screen, click Add.
The system displays a new row in the accumulator table.
○ For Pay Period PEP
1. To add the benefit pay periods and years and accumulators for Pay Period PEP, select the Pay
Periods tab. The system displays the Benefit Pay Periods and Accumulator screen.
2. In the Pay Periods table on the Benefit Months and Accumulator screen, click Add. The system
displays a new row in the Pay Periods table.
3. Enter the appropriate Pay Type, such as monthly, weekly, bi-weekly, and so on.
4. Enter the pay periods and pay years for which the benefit should be included in PEP calculations.
5. In the Accumulator table on the Benefit Pay Periods and Accumulator screen, click Add. The
system displays a new row in the Accumulator table.
13. Select an accumulator code.
14. To return from the Benefit Months and Accumulator screen to the Benefit Plan screen and from the Benefit
Plan screen to the Benefit Area screen, click Back.
15. To save the entries in all three Benefit Rules screens, click Save.
16. To return the Benefit Rules screens to a non-editable state without saving any changes, click Cancel.
To edit a benefit rule, do the following:
1. Select the benefit area that you want to edit, and click Next.
The system displays the Benefit Plan screen.
2. Select the benefit plan you want to edit and click Edit.
The system makes all fields in the Benefit Rule screens editable.
3. Enter changes in the wage type, calculation basis, calculation order, benefit start period, or commitment
item. Choose the Months tab to edit the benefit plan months or benefit accumulators for Fiscal Period PEP.
 Note
You cannot change benefit area or benefit plan.
4. To edit the months and accumulators for a benefit plan, select the benefit plan row, click Next.
The system displays the Months and Accumulators screen.
5. Make changes to either the Months and/or Accumulator tables.
8. Choose the Pay Periods tab to edit benefit pay type, pay periods, pay years, or benefit accumulators for Pay
Period PEP. You cannot change benefit area or benefit plan.
9. To edit the pay type, pay periods, pay years, and accumulators for a benefit plan, select the benefit plan
row and click Next. The system displays the Pay Periods and Accumulators screen.
10. Make changes to the pay periods or accumulator tables.
11. To save the changes, click Save. To exit without saving the changes, click Cancel.
To delete a benefit rule, do the following:
1. Select the benefit rule that you want to delete.

The system displays a popup seeking a confirmation.
○ To delete the benefit area and all related benefit plans, click Yes.

○ To not delete the benefit area and all related benefit plans, click No.
2. To delete a specific benefit plan, select the benefit area and click Next.
3. Select the benefit plan row, click Delete.
The system displays a popup seeking confirmation.
○ To delete the benefit plan and all related months and accumulators or pay periods and accumulators,
click Yes.
○ To not delete the benefit plan and all related months and accumulators, click No.
4. To delete a benefit plan month, select the benefit plan, click Next.
5. Select the Months tab.
6. Select the month to be deleted, click Delete.
7. To delete a benefit plan accumulator, select the benefit plan, click Next.
8. Select the accumulator to be deleted, click Delete.
10. To delete a benefit plan pay period, select the benefit plan and click Next.
11. Select the Pay Periods tab.
12. Select the row with the pay type, pay period, and pay year to be deleted and click Delete.
13. To delete a benefit plan accumulator, select the benefit plan and click Next.
14. Select the accumulator to be deleted and click Delete.
8.4.9 PEP Attrition and Backfill Projections
Use
There are some required and optional configurations needed in order to execute attrition and backfill
scenarios. An attrition and backfill projection has a required first step of executing a pay period projection. The
pay period projection is used as a reference projection for the attrition and backfill projection. The attrition and
backfill projection will then attrition employees as per the configured attrition and nackfill group rule that is
entered on the Attrition and Backfill Projection screen. Note that the pay period projection, the attrition and
backfill group rule, and the attrition and backfill projection all need to be based on the same pay type (weekly,
monthly, bi-monthly, and so on). The results will calculate the attrtioned employees and add backfill positions
that will be posted to the Attrition and Backfill InfoCube. Only attrition and backfill delta records will be posted
to the InfoCube. For reporting, a multiprovider has been provided, and users can create queries to combine the
pay period projection and the attrition and backfill projection to get the complete projection results. Several
attrition and backfill projections can be executed on top of the same pay period projection.
Process
The configuration of Attrition and Backfill Rules is a two-step process:
1. Maintain Attrition Rules

The attrition rule consists of selection criteria, such as the desired FM dimensions, Employee Group,
Personnel Group, Pay Scale Group, Job, and so on. Once the selection criteria are complete then the pay
year and period and attrition rate is entered. This combination of data represents an attrition rule.

See Attrition Rule Maintenance [page 157].
2. Maintain Attrition and Backfill Group Rules
The Attrition and Backfill Group Rule incorporates the Attrition Rules configured in the first step and allows
backfill rules to be created. Each Attrition Rule can be added to one or more Attrition and Backfill Group
rule. Backfill rules require a Backfill Position which can be any Position defined in Master Data, or new
Positions can be created specifically for backfill purposes. The Backfill Position entered in the Group Rule
will be used to generate a new backfill position during the Attrition and Backfill Projection calculation. The
new positions will have a different employment status so that it won’t be considered for other PEP
projection calculations. There are three types of group rules allowed:
○ Attrition only.
These are attrition rules without any type of backfill. The type of rule can be used to represent work
force reductions.
○ Attrition and backfill
These are attrition rules with a dependent backfill rule. This type of rule can be used to represent work
force reductions followed by some percentage of backfilling (positions) based on a percentage of those
employees that were subject to attrition.
○ Backfill only
These are independent backfill rules with no associated attrition and represent a workforce increase
which could represent a hiring event. Backfill only rules require an actual number (head count) used
rather than based on a percentage of an attrition rule.
See Attrition and Backfill Group Rule Maintenance [page 158].
Once the attrition and backfill group rules have been configured and the pay period reference projection has
run successfully then users can execute attrition and backfill projection and enter the group rule in the Attrition
and Backfill Projection screen. When the attrition and backfill projection executes, it will apply the attrition and
backfill group rule that was entered when the user creates the attrition and backfill projection. The PEP engine
will read the attrition rule to determine the number of employees to be attritioned using the selection criteria of
the attrition rule and then apply the attrition rates to the pay periods indicated in the attrition rule. It is
important to note that:
● Only employees can be attritioned; positions are not attritioned.

● Once an employee has been attritioned, he or she is attritioned for the duration of the projection.
● Several attrition rules can be used in one attrition and backfill group rule. There are no checks or warnings
for attrition rules that may have overlapping selection criteria. If there is overlap, the attritions will be
calculated as per the configured group rules and attrition rules.
● Only positions are created for backfills; employees are not used for backfills.
● Once a backfill position is created, it is included for the duration of the projection.
8.4.9.1 Attrition Rule Maintenance
Use
Attrition and backfill group rules and, ultimately attrition and backfill projections, utilize attrition rules. Attrition
rule data consists of selection criteria that the PEP engine will use to determine which selection of employees
should be attritioned. Additionally, the pay year and period and attrition rate are used to determine how many
employees are to be attritioned and in which pay periods.

Procedure
Use the following portal menu path to access the Attrition Rule Maintenance screen: Administration PEP
Maintenance Flexible Pay Period PEP Attrition Rules Maintenance .
To create a new attrition rule:
1. Click New.
2. In the popup screen, enter the:
○ FM area
○ Pay type (monthly, weekly, bi-,monthly, and so on)
The pay type needs to be consistent with the pay period reference projection and the attrition and
backfill group rule to be used in the projection
○ Description
3. Click Create.
4. On the Dimensions tab, enter all the applicable selection criteria for which the rule is being created. All six
FM dimension fields are available, as well as Employee Group, Employee Subgroup, Personnel Area,
Personnel Subarea, Pay Scale Group, Pay Scale Level, ES Grouping, Job, and Position. Each field containing
data will be used by the PEP engine to filter which employees are considered for the attrition rule.
5. On the Pay Period Attrition Rate tab, enter the pay year, pay period, and attrition rate that should be applied
to the group of employees selected after the filtering logic has completed. Note that default entries are
created for each pay year and pay period based on the pay period table for the pay type selected in the
previous step. The attrition rate is defaulted to 0. Valid attrition rates are from 0 to 100. Enter the attrition
rate in the starting pay year and pay period desired. The attrition rates accumulate, so each rate entered in
a subsequent pay period is an additional rate of attrition.
6. It is possible to export the attrition rates to a spreadsheet, modify the spreadsheet, and then upload the
changed values back to the screen. To do this:
1. Click the Export button and choose Excel from the dropdown. Select Save from the Excel popup and
enter a file path and name.
2. Make changes to the spreadsheet and save the file as a .CSV (comma delimited) file.
3. Return to the screen and click the Replace Data button. Use the Browse feature in the popup to locate
the file saved in the previous step. Click the Upload button.
4. If the spreadsheet changes are no longer desired, the previous rates can be retrieved by clicking the
Revert Changes button.
7. When changes are complete, click the Save button.
8.4.9.2 Attrition and Backfill Group Rule Maintenance
Use
Attrition and backfill group rules are utilized in and attrition and backfill projections to determine what
employees are to be attritioned and what backfill positions are to be created. Attrition group rules combine
attrition rules (created in the previous step) and allow backfill criteria to be added, based on a percentage of
the attrition rule. For example, maybe only 50% of the attritioned employees would be added back in a future
pay period as a vacant backfilled position. Group rules also allow independent backfill rules, which are not
based on any attrition, and would represent a hiring event.

Procedure
Use the following portal menu path to access the Attrition and Backfill Group Rule Maintenance screen:
Administration PEP Maintenance Flexible Pay Period PEP Attrition and Backfill Group Rules
Maintenance .
To create a new attrition and backfill group rule:
1. Click New.
○ In the popup screen, enter pay type (monthly, weekly, bi-monthly, and so on). The pay type needs to be
consistent with the pay period reference projection and the attrition and backfill group rule to be used
in the projection
○ Enter a description.
2. Click Create.
3. Click Add.
4. Select the attrition and backfill rule type:
○ Only Attrition, workforce reduction with no backfill:
○ Attrition Rule: Enter the desired attrition rule created in the previous step, Attrition Rule
Maintenance [page 157]. Note that only attrition rules of the same pay type are available for
selection
○ View Attrition Rule: Click the View button to have the attrition rule details presented in a popup
screen (display only).
○ Only Backfill, workforce increase not associated with any attrition rule:
○ The Attrition Rule and View Attrition Rule fields do not apply and are display only.
○ Backfill Position: Enter the desired backfill position. When the attrition and backfill projection runs,
the backfill position will be created as per the master data associated with the backfill position
selected.
○ Attrition Start Pay Year, Attrition Start Pay Period, Attrition End Pay Year, and Attrition End Pay
Period do not apply and are display only.
○ Backfill Start Pay Year: Enter the pay year in which the backfill position will begin.
○ Backfill Start Pay Period: Enter the pay period in which the backfill position will begin.
○ Backfill Rate does not apply and is display only.
○ Backfill Count: Enter the number of vacant backfill positions to be calculated.
○ Attrition and Backfill, workforce reduction with workforce increase based on a percentage of the
reduction:
○ Attrition Rule: Enter the desired attrition rule created in the previous step, Attrition Rule
Maintenance [page 157]. Note that only attrition rules of the same pay type are available for
selection
○ View Attrition Rule: Click the View button to have the attrition rule details
○ Backfill Position: Enter the desired backfill position. When the Attrition and Backfill projection runs
and the backfill position will be created as per the master data associated with the backfill position
selected.
○ Attrition Start Pay Year and Attrition Start Pay Period: Enter the starting point of when attrition
should be calculated for backfill purposes.
○ Attrition End Pay Year and Attrition End Pay Period: Enter the ending point of when attrition should
be calculated for backfill purposes.
○ Backfill Start Pay Year: Enter the pay year in which the backfill position will begin.

○ Backfill Start Pay Period: Enter the pay period in which the backfill position will begin.
○ Backfill Rate: The PEP calculation will use the backfill rate as a percentage of the number of
attritioned employees during the attrition pay period or year start and end range to determine how
many vacant backfill positions to create.
○ Backfill Count does not apply and is display only.
5. When the data is complete, click Save.
8.4.10 Business Add-in (BAdI) for Attrition and Backfill

(Optional)
PEP calculations have a fundamental algorithm to calculate vacant position count. The PEP calculation engine
first determines the number of employees for a position. It then determines the number of vacant positions as
follows:
Position Vacant Count = Authorized Count (Position Master Data) – number of employees
When applying attrition rules to PEP results, employees are always attritioned. Therefore, while the attrition
rule would reduce the number of employees, it would also increase the number of vacation positions as per the
PEP algorithm.
 Example
if there were an authorized count of 10 and there are 5 employees, then there are 5 vacant positions. Using
the PEP algorithm, if 2 employees are attritioned, then the vacant count would become 7. This behavior
may not be desired, especially if Backfill rules are provided to determine if/when backfill positions would be
planned.
See Solution Manager for steps to activate and deactivate the BAdI.

9 Reports
Use
The current version of SAP Budgeting and Planning for Public Sector supports reporting from all InfoProviders
in SAP Business Information Warehouse (BW) and an RFC to access long text stored in the database.
Reports on decision packages provide individuals in the budget planning departments with an updated account
of budget requests for future planning and implementation.
Integration
Reporting is based on data stored in SAP BW. Integration with products and solutions such as SAP
BusinessObjects provides analytics and reporting capability, including reports that can later be used to create
and print budget books. For more information about SAP BusinessObjects products and solutions, see the SAP
Library at http://help.sap.com SAP BusinessObjects .
Prerequisites
The following activities are completed in the system:
● Integration of reporting tools (for example, SAP BusinessObjects)

● Creation of report queries
● Designing of report layouts and formats

Reports INTERNAL 161
10 Portal Content for SAP Budgeting and
Planning for Public Sector
SAP Budgeting and Planning for Public Sector is an application based on SAP NetWeaver that supports end-to-
end budgeting and performance management processes for public sector organizations. This application
incorporates SAP Business Information Warehouse (SAP BW) to help organizations plan their budgets for
various processes including personnel planning, operating (base and incremental), strategic planning, capital,
and budget execution activities. Each type of request can contain expenditures, revenue sources, personnel
costs, and related text justification.
This application provides role-based access to various aspects of the application’s portal content. Depending
on assigned roles:
● In the Budget Formulation role, you can create, edit or review budget form requests for budget formulation
and budget execution activities; compare, prioritize, and establish funding levels; and/or create
performance management text and plan/define performance measurement targets which can later be
used to measure the outcome of approved programs and initiatives. This role will be assigned to End Users,
Super Users and System Administration users.
● In the PEP Maintenance role, you can maintain position and employee records including assigned funding
stream allocations and benefit data or run projection scenarios to establish the impacts of funding or cost
change alternatives. This role will be assigned to Super Users and System Administration users.
● In the PBF Administration role, you can maintain all master data; maintain budget form components such
as comment boxes, form elements, and combo edit; run PEP projections; and maintain the spell check
dictionary and application help links. This role will be assigned to System Administration users.
The portal content for SAP Budgeting and Planning for Public Sector is meant for end users of the application
based on the roles assigned to the individual.
Technical Data
Availability SAP NetWeaver 7.31
Languages Available English, German, Spanish, Portuguese, and Arabic
10.1 Budget Formulation
pcd:portal_content/com.sap.pct/every_user/com.sap.cdev.pbf.bp_folder/
com.sap.cdev.pbf.roles/com.sap.cdev.pbf.roles.budget_formulation
Use
If you wish to use SAP Budgeting and Planning for Public Sector, activate this role.

162 INTERNAL Portal Content for SAP Budgeting and Planning for Public Sector
Budget analysts and reviewers responsible for formulating an organization's budget work with budget forms,
planning forms, and ranking forms for multi-level budget planning, evaluation of budget requests, strategic
planning for organizational units, and setting the priority for different expenditures.
A budget analyst creates various budget requests (budget form instances) to present different budget
proposals. Reviewers at each approval level use ranking forms to evaluate budget proposals. Budget requests
are ranked and re-ranked as the budget formulation process moves through the organization, till the budget is
adopted.
This role provides access to the creation of budget forms, planning forms, ranking forms, and the maintenance
of application master data.
Integration
This role is integrated with the Budget Formulation [page 163] workset. On the Reports menu, you can
integrate appropriate reports that you develop in the reporting tool of your choice.
Depending on the business need, users of this role may also need the PEP Maintenance role to maintain
position or employee information and/or the PBF Administration role to configure different attributes for
budget forms or PEP master data.
10.1.1 Budget Formulation
Technical Data
Technical Name pcd:portal_content/com.sap.pct/every_user/

com.sap.cdev.pbf.bp_folder/
com.sap.cdev.pbf.worksets/
com.sap.cdev.pbf.worksets.budget_formulation
Use
You can use this workset to:
● Create budget form instances

● Compare budget form instances and rank individual budget requests
● Create planning forms that help define the strategic planning elements including mission, goals, objectives,
and performance measures
● Maintain application-level master data
● Integrate reports (if a suitable reporting tool is integrated)

Portal Content for SAP Budgeting and Planning for Public Sector INTERNAL 163
Features
This workset is integrated with the following pages:
Pages in Budget Formulation Workset
Page Technical Name
Budget Form pcd:portal_content/com.sap.pct/every_user/

com.sap.cdev.pbf.bp_folder/com.sap.cdev.pbf.pages/
com.sap.cdev.pbf.pages.budget_form
Ranking Form pcd:portal_content/com.sap.pct/every_user/

com.sap.cdev.pbf.pages.ranking_form
Fund Center Planning pcd:portal_content/com.sap.pct/every_user/

com.sap.cdev.pbf.pages.fc_planning
Master Data Maintenance pcd:portal_content/com.sap.pct/every_user/

com.sap.cdev.pbf.pages.masterdata_maintenance
10.2 PEP Maintenance
com.sap.cdev.pbf.roles/com.sap.cdev.pbf.roles.pep_maintenance
Use
If you wish to use SAP Budgeting and Planning for Public Sector PEP functionality, activate this role.
This role provides users with the ability to maintain position and employee details. The user can also compare
the master data between two reference projections, run projection scenarios (fiscal period or pay period
projections) to calculate personnel expenditures including salaries, benefits, statutory costs, and supplemental
pays for varying time periods by employee, position, job, and FM dimensions, run what-if projections on top of
the fiscal period reference projection or attrition and backfill projections on top of pay period reference
projections. It is also possible for the user to delete the projection and its corresponding results from the
respective targets.

Integration
This role is integrated with the PEP Maintenance [page 165] workset. Role users may also be granted access to
some reports, provided adequate reporting features are available with the integration of a suitable reporting
tool.
Depending on business needs, users of this role may also require some features of the PBF Administration role,
for example, to maintain jobs, pay levels, and benefits.
10.2.1 PEP Maintenance
Technical Data

com.sap.cdev.pbf.worksets.pep_maintenance
Use
● Create and maintain position details

● Create and maintain employee details
● Do employee and position master data comparison between two reference projection IDs
● Run fiscal period or pay period projection scenarios and update projection cubes
● Run what-if scenarios on top of the fiscal period projection IDs that were flagged as reference projection
IDs in the run projection screen.
● Run attrition and backfill scenarios on top of the pay period projection IDs that wereflagged as reference
projection IDs in the run projection screen.
● Monitor the projection ID being processed in the background and check the statistics and history of the
projections that are already processed
● Delete a projection ID and its resultant records from the respective targets
● Generate reports (if a suitable reporting tool is integrated)

Features
Pages in PEP Maintenance Workset
Page Technical Name
Position Maintenance pcd:portal_content/com.sap.pct/every_user/com.sap.cdev.pbf.bp_folder/

com.sap.cdev.pbf.pages/com.sap.cdev.pbf.pages.position_maintenance
Employee Maintenance pcd:portal_content/com.sap.pct/every_user/com.sap.cdev.pbf.bp_folder/

com.sap.cdev.pbf.pages/com.sap.cdev.pbf.pages.employee_maintenance
Run Projection Scenarios pcd:portal_content/com.sap.pct/every_user/com.sap.cdev.pbf.bp_folder/

com.sap.cdev.pbf.pages/com.sap.cdev.pbf.pages.projection_scenarios
10.3 PBF Administration
com.sap.cdev.pbf.roles/com.sap.cdev.pbf.roles.pbf_admin
Use
If you wish to use SAP Budgeting and Planning for Public Sector, activate this role.
The PBF administrator is one who is familiar with the budgeting process and understands the requirements of
the different forms. A person in this role is mostly responsible for maintaining personnel data, defining various
aspects of budget forms, maintaining the attributes of application specific master data, and running various
projections. Administrative tasks such as managing a dictionary of terms and creating context-sensitive links
between application screens and the help are some of the other responsibilities of this role.
Integration
The various functions of this role are possible with the integration of the PBF Administration [page 167]
workset.

10.3.1 PBF Administration
Technical Data

com.sap.cdev.pbf.worksets.pbf_admin
Use
● Maintain master data

● Set up budget form attributes such as comment structures, define editing rules for budget forms, create
new form elements and define values, manage the list of stages for use during budget formulation, and
maintain notification lists and workflow approval lists for stage advances
● Manage data for personnel expenditure planning
● Run fiscal period projection scenarios and what-if scenarios or pay period projections and attrition and
backfill scenarios to update planning cubes; also, you can delete the projection and its results from the BW
targets
● Manage a dictionary of terms
● Configure context-based navigation to application help
Features
Pages in PBF Administration Workset
Page Technical Name
Master Data Maintenance pcd:portal_content/com.sap.pct/every_user/

com.sap.cdev.pbf.pages.masterdata_maintenance
Comment Types pcd:portal_content/com.sap.pct/every_user/

com.sap.cdev.pbf.pages.comment_types
Comment Type Trees pcd:portal_content/com.sap.pct/every_user/

com.sap.cdev.pbf.pages.comment_type_trees

Page Technical Name
Combo Edit pcd:portal_content/com.sap.pct/every_user/

com.sap.cdev.pbf.pages.combo_edit
Form Elements pcd:portal_content/com.sap.pct/every_user/

com.sap.cdev.pbf.pages.form_elements
Stage Maintenance pcd:portal_content/com.sap.pct/every_user/

com.sap.cdev.pbf.pages.stage_maintenance
Position Maintenance pcd:portal_content/com.sap.pct/every_user/

com.sap.cdev.pbf.pages.position_maintenance
Employee Maintenance pcd:portal_content/com.sap.pct/every_user/

com.sap.cdev.pbf.pages.employee_maintenance
Job Maintenance pcd:portal_content/com.sap.pct/every_user/

com.sap.cdev.pbf.pages.job_maintenance
Pay Level Maintenance pcd:portal_content/com.sap.pct/every_user/

com.sap.cdev.pbf.pages.pay_level_maintenance
Benefit Rules pcd:portal_content/com.sap.pct/every_user/

com.sap.cdev.pbf.pages.benefit_rules
Benefit Rates pcd:portal_content/com.sap.pct/every_user/

com.sap.cdev.pbf.pages.benefit_rates
Projection Distributions pcd:portal_content/com.sap.pct/every_user/

com.sap.cdev.pbf.pages.projection_distributions
Run Projection Scenarios pcd:portal_content/com.sap.pct/every_user/

com.sap.cdev.pbf.pages.projection_scenarios
Dictionary Management pcd:portal_content/com.sap.pct/every_user/

com.sap.cdev.pbf.pages.dictionary_management

Page Technical Name
Application Help pcd:portal_content/com.sap.pct/every_user/

com.sap.cdev.pbf.pages.app_help

11 BI Content for SAP Budgeting and
Planning for Public Sector
The BI content for SAP Budgeting and Planning for Public Sector is an add-on to the standard SAP BI Content
7.04. The BI content is categorized into the following InfoAreas:
● Public Sector Budgeting [page 170]

○ PEP Maintenance [page 269]
○ Projection Scenario — Queue and Statistics [page 300]
○ Public Budget Formulation — Master Data [page 355]
○ Budget Forms [page 375]
○ Combo Edit Authorization Objects [page 375]
○ Ranking [page 380]
11.1 Public Sector Budgeting
11.1.1 InfoCubes
11.1.1.1 Performance Measure Cube
/PBFBI/PM_R01
Use
Characteristics
InfoObject Description
/PBFBI/BDGT_YR Budget Year
/PBFBI/COMMENT Comment Instance

170 INTERNAL BI Content for SAP Budgeting and Planning for Public Sector
/PBFBI/FM_AREA Financial Management Area
/PBFBI/FORM_ID Form Instance ID
/PBFBI/FUND Fund
/PBFBI/FUNDPGM Funded Program
/PBFBI/FUND_CT Funds Center
/PBFBI/GRANT Grant
/PBFBI/PRFMEAS Performance Measure
0VTYPE Value Type for Reporting
Key Figures
PBFBI/PM_KPI Performance Measure
Time Characteristics
0FISCYEAR Fiscal Year
0FISCVARNT Fiscal Year Variant
11.1.1.2 Budget Form Positions Cube
/PBFBI/HRPJ_R01
Use

BI Content for SAP Budgeting and Planning for Public Sector INTERNAL 171
0FISCPER Fiscal Year / Period
0FISCPER3 Posting Period
Unit
0FM_CURR Currency key for FM area currency
/PBFBI/ALT_CUR Alternate Currency
Characteristics
/PBFBI/GRANT Grant
/PBFBI/FUND Fund
/PBFBI/FUNCARA Functional Area
/PBFBI/CMMT_IT Commitment item
/PBFBI/PYSCLAR Pay Scale Area
/PBFBI/PYSLCGP Pay Scale Group
/PBFBI/PYSCLTY Pay Scale Type
/PBFBI/PYSCLVL Pay Scale Level
/PBFBI/CTRY_ID Country Grouping
/PBFBI/ESGCAP Employee Subgrp Grouping for Collective Agreement Provi

sions
/PBFBI/BEN_ARE Benefit Area

/PBFBI/BEN_PLN Benefit Plan
/PBFBI/EMPLOYE Employee
/PBFBI/POSTN Position
/PBFBI/JOB Job
/PBFBI/SAL_OVD Salary Override
/PBFBI/FTEPERD FTE Periods
/PBFBI/VCNAME Form Definition / VC Model Name
/PBFBI/PROJID Projection ID
/PBFBI/VCNT_FL Vacant Selections
/PBFBI/STAGE Budget Stage
/PBFBI/PROJTYP Projection Type
0EMPLGROUP Employee Group
0EMPLSGROUP Employee Subgroup
0PERS_AREA Personnel Area
0PERS_SAREA Personnel Subarea
/PBFBI/FRM_TYP Form Type
/PBFBI/TRANSTY Transaction Type
/PBFBI/TRANSID GUID for Transaction
/PBFBI/PUVALTP Budgeting Value Type
/PBFBI/DELETE Deletion Indicator
/PBFBI/GENDIM1 Generic Header Dimension1

Key Figures
/PBFBI/FM_AMT1 Amount in FM Area Currency
/PBFBI/ALT_AMT Amount in Alternate Currency
/PBFBI/RPT_FTE Report FTE
/PBFBI/CALCFTE Calculated FTE
/PBFBI/EMP_CNT Employee Count
/PBFBI/ATH_CTR Authorized Count
/PBFBI/VAC_CTR Vacant Counter
/PBFBI/FIL_CTR Filled Count
/PBFBI/SAL_PCT Salary %
/PBFBI/BNT_PCT Benefit %
11.1.2 MultiProviders
11.1.2.1 Budget / Projection MultiProvider
/PBFBI/BFHR_M01
Use
This MultiProvider consists of the following InfoCubes:
/PBFBI/HRPJ_R01 Projection Cube [page 171]
/PBFBI/BF_CUBE Budget Forms [page 383]

11.1.3 Key Figures
11.1.3.1 Amount in FM Area Currency
/PBFBI/FM_AMT1
Use
This key figure displays an amount in FM area currency. The type of amount (such as, invoices in the payment
budget) is first made up of the combination with other characteristic values.
Technical Data
Exchange Available as of Release SAP Public Budget Formulation 7.1
Aggregation Summation
Exception Aggregation Summation
Calculation No
Value Restriction / Calculation No
11.1.3.2 Amount in Alternate Currency
/PBFBI/ALT_AMT
Use
This key figure displays an amount in alternate currency.

Technical Data
Calculation No
11.1.3.3 Annualization
/PBFBI/ANUALZ1
Use
This key figure displays the annualization amount in FM area currency.
Technical Data
Calculation No
11.1.3.4 Authorized Count
/PBFBI/ATH_CTR
Use
This key figure displays the authorized count of employees for a position.

Technical Data
Calculation No
11.1.3.5 Benefit %
/PBFBI/BNT_PCT
Use
This key figure displays the percentage representing the employer’s share of fixed cost benefits.
Technical Data
Calculation No
11.1.3.6 Benefit Amount
/PBFBI/BEN_AMT
Use
This key figure shows the amount for benefit plans such as health, insurance, and miscellaneous plans.

Technical Data
Calculation No
11.1.3.7 Benefit Maximum Amount
/PBFBI/BENMXAM
Use
This key figure shows the maximum amount for a benefit plan.
Technical Data
Calculation No
11.1.3.8 Benefit Minimum Amount
/PBFBI/BENMNAM
Use
This key figure shows the minimum amount for a benefit plan.

Technical Data
Calculation No
11.1.3.9 Benefit Rate
/PBFBI/BEN_RT
Use
This key figure shows the rate for a benefit plan.
Technical Data
Calculation No
11.1.3.10 Calculated FTE
/PBFBI/CALCFTE
Use
This key figure shows the calculation factor for FTE.

Technical Data
Calculation No
11.1.3.11 Calculation Basis Amount
/PBFBI/BAS_AMT
Use
This key figure shows the base amount on which the benefit is applicable.
Technical Data
Calculation No
11.1.3.12 Current Rank
/PBFBI/CURRANK
Use
This key figure shows the current rank of the budget form.

Technical Data
Calculation No
11.1.3.13 Distribution Percentage
/PBFBI/DIS_PCT
Use
This key figure holds the distribution percentage maintained for the distribution code.
Technical Data
Exchange Available as of Release SAP Public Budget Formulation 7.1 SP 01
Calculation No
11.1.3.14 Employee Count
/PBFBI/EMP_CNT
Use
This key figure is used to distinguish an employee record. It is always 1 for employee records in the projection
cube.

Technical Data
Calculation No
11.1.3.15 Filled Count
/PBFBI/FIL_CTR
Use
This key figure shows the yearly count of employees assigned to a position.
Technical Data
Calculation No
11.1.3.16 Funding Percentage
/PBFBI/FND_PCT
Use
This key figure shows the percentage of fund allocated to each fund center. This is used in employee and
position fund center allocations.

Technical Data
Exchange Available as of Release SAP NW 7.01 BI Content Add-On 7.04
Calculation No
11.1.3.17 Funded Flag for Ranking
/PBFBI/FUNDFLG
Use
This key figure indicates the funded flag for ranking
Technical Data
Calculation No
11.1.3.18 Initial Base Budget
/PBFBI/INITBB1
Use
This key figure displays the current budget.

Technical Data
Calculation No
11.1.3.19 Key
/PBFBI/KEY01
Use
This characteristic display the key of the combo edit.
Technical Data
Aggregation Maximum
Exception Aggregation Maximum
Calculation No
11.1.3.20 Number of Days in a Month
/PBFBI/DAYS
Use
This key figure displays the number of days in a month.

Technical Data
Calculation No
11.1.3.21 Number of Positions
/PBFBI/NUMPST
Use
This key figure shows the count of vacant positions. This is used in the budget form's Position screen.
Technical Data
Calculation No
11.1.3.22 One Time Adjustment
/PBFBI/OTADJT1
Use
One Time Adjustment

Technical Data
Calculation No
11.1.3.23 Pay Level Amount
/PBFBI/PYLVAMT
Use
This key figure displays the amount specific to the pay scale level.
Technical Data
Exception Aggregation Last Value
Calculation No
Value Restriction / Calculation 0CALDAY
11.1.3.24 Percentage Capitalization Amount
/PBFBI/CAP_AMT
Use
This key figure displays the maximum amount applied to an accumulator for percentage based benefits.

Technical Data
Calculation No
11.1.3.25 Performance KPI Measures
/PBFBI/PRF_KPI
Use
Performance KPI Measures
Technical Data
Calculation No
11.1.3.26 Performance Measure
/PBFBI/PRF_KPI
Use
Performance Measure

Technical Data
Calculation No
11.1.3.27 Position Allocation
/PBFBI/POS_ALL
Use
This key figure displays percentage allocation of an employee to a position.
Technical Data
Calculation No
11.1.3.28 Prior Rank
/PBFBI/PR_RANK
Use
This key figure displays the previous rank.

Technical Data
Calculation No
11.1.3.29 Rank Amount
/PBFBI/RANKAM1
Use
This key figure displays the ranking amount in FM area currency.
Technical Data
Calculation No
11.1.3.30 Ranking Version ID
/PBFBI/RANKVRS
Use
This key figure displays the version ID.

Technical Data
Calculation No
11.1.3.31 Rate
/PBFBI/RATE
Use
This key figure displays the supplementary rate for salary or benefit for a projection run.
Technical Data
Calculation No
11.1.3.32 Rate for Annual Fixed Salary Increase
/PBFBI/FXRATE
Use
This key figure displays the rate for annual fixed salary increases.

Technical Data
Exchange Available as of Release SAP NW 7.01 BI Content Add-On 7.04
Calculation No
11.1.3.33 Report FTE
/PBFBI/RPT_FTE
Use
This key figure displays the reporting FTE for employee and position.
Technical Data
Calculation No
11.1.3.34 Salary
/PBFBI/SALARY1
Use
This key figure displays the annual salary for budget form positions.

Technical Data
Calculation No
11.1.3.35 Salary %
/PBFBI/SAL_PCT
Use
This key figure displays the percentage of full-time employment.
Technical Data
Calculation No
11.1.3.36 Step Date
/PBFBI/STEPDT
Use
This characteristic displays the next pay scale level change date.

Technical Data
Aggregation Maximum
Exception Aggregation Maximum
Calculation No
11.1.3.37 Unique Ranking Instance ID
/PBFBI/RNK_ID
Use
This key figure shows the unique ranking instance ID.
Technical Data
Calculation NoDescription of the calculation or No / Nein
11.1.3.38 Vacant Counter
/PBFBI/VAC_CTR
Use
This key figure displays the number of vacancies for each position.

Technical Data
Calculation No
11.1.3.39 Working Rank
/PBFBI/WRKRANK
Use
This key figure displays the working rank.
Technical Data
Calculation No
11.1.4 Characteristics
11.1.4.1 Allocate Flag
/PBFBI/ALL_FLG

Use
This characteristic displays the allocation flag.
Technical Data
External Hierarchy
11.1.4.2 Attribute
/PBFBI/ATTR
Use
This characteristic displays the attribute of an audit item.
Technical Data
External Hierarchy
11.1.4.3 Audit: Change Type
/PBFBI/CHGTYPE
Use
This characteristic displays the change type of an audit item.

Technical Data
External Hierarchy
11.1.4.4 Authorization for Fill
/PBFBI/ATH_FIL
Use
This characteristic displays Yes/No field. If yes, the cost of this position is projected if the employee is vacant. If
no, this position is only projected if filled.
Technical Data
External Hierarchy
11.1.4.5 Authorization Object for Stage
/PBFBI/SAUTH
Use
Technical Data
External Hierarchy

11.1.4.6 Benefit Accumulator
/PBFBI/ACCUM
Use
An area where costs can be stored.
Technical Data
External Hierarchy
11.1.4.7 Benefit Area
/PBFBI/BEN_ARE
Use
You can use this characteristic to break key figures down by benefit area.
Technical Data
External Hierarchy
11.1.4.8 Benefit Cost Group
/PBFBI/BEN_CGP

Use
This characteristic displays the benefit cost group.
Technical Data
External Hierarchy
11.1.4.9 Benefit Cost Variant Rule
/PBFBI/BEN_CVR
Use
This characteristic displays the benefit cost variant rule.
Technical Data
External Hierarchy
11.1.4.10 Benefit Months Count
/PBFBI/BEN_CNT
Use
This characteristic displays the number of benefit months.

Technical Data
External Hierarchy
11.1.4.11 Benefit Plan
/PBFBI/BEN_PLN
Use
You can use this characteristic to break key figures down by benefit plan.
Technical Data
External Hierarchy
11.1.4.12 Benefit Range Step
/PBFBI/BENRGST
Use
This characteristic displays the number of records in the Benefit Rates screen.
Technical Data
External Hierarchy

11.1.4.13 Benefits Record Counter (Employee)
/PBFBI/RECORD3
Use
This characteristic displays the number of records in the employee benefits.
Technical Data
External Hierarchy
11.1.4.14 Benefit Start Period
/PBFBI/BNSTPER
Use
This characteristic displays the benefit start period.
Technical Data
External Hierarchy
11.1.4.15 Budget Stage
/PBFBI/STAGE

Use
Technical Data
External Hierarchy
11.1.4.16 Budget Year
/PBFBI/BDGT_YR
Use
This characteristic displays the budget year.
Technical Data
External Hierarchy
11.1.4.17 Budgeting Value Type
/PBFBI/PUVALTP
Use

Technical Data
External Hierarchy
11.1.4.18 Calculation Basis
/PBFBI/CALCBAS
Use
This characteristic displays the calculation basis.
Technical Data
External Hierarchy
11.1.4.19 Calculation Order
/PBFBI/CALC_OR
Use
This characteristic displays the order when projecting personnel compensation within the calculation engine.
Technical Data
External Hierarchy

11.1.4.20 Change Number
/PBFBI/CHGNR
Use
This characteristic displays the change number of an audit item.
Technical Data
External Hierarchy
11.1.4.21 Combo Edit — Fund Center Hierarchy Level
/PBFBI/FCLEVEL
Use
This characteristic displays the fund centre hierarchy level.
Technical Data
External Hierarchy
11.1.4.22 Combo Edit Rule for Budget Forms
/PBFBI/RULE

Use
Technical Data
External Hierarchy
11.1.4.23 Comment Instance
/PBFBI/COMMENT
Use
This characteristic displays the comment instance.
Technical Data
External Hierarchy
11.1.4.24 Commitment Item
/PBFBI/CMMT_IT
Use
This characteristic displays the commitment item.

Technical Data
External Hierarchy
11.1.4.25 Commitment Item Category
/PBFBI/CI_TYPE
Use
This characteristic displays the commitment item category.
Technical Data
External Hierarchy
11.1.4.26 Commitment Item Group
/PBFBI/CIGRP
Use
This characteristic displays the commitment item group.
Technical Data
External Hierarchy

11.1.4.27 Commodity
/PBFBI/COMDTY
Use
This characteristic displays commodity.
Technical Data
External Hierarchy
11.1.4.28 Counter - Job Benefits
/PBFBI/RECORD6
Use
This characteristic displays the number of records in the job benefits.
Technical Data
External Hierarchy
11.1.4.29 Country Grouping
/PBFBI/CTRY_ID

Use
The Country Grouping characteristic enables you to display key figures in accordance with country criteria.
Technical Data
External Hierarchy
11.1.4.30 Created
/PBFBI/CREATED
Use
Technical Data
External Hierarchy
11.1.4.31 Date From
/PBFBI/DATEFR
Use
This characteristic displays the validity start date.

Technical Data
External Hierarchy
11.1.4.32 Date To
/PBFBI/DATETO
Use
This characteristic displays the validity end date.
Technical Data
External Hierarchy
11.1.4.33 Decision Package Position
/PBFBI/DP_POS
Use
This characteristic indicates the decision package position.
Technical Data
External Hierarchy

11.1.4.34 Deletion Indicator
/PBFBI/DELETE
Use
This characteristic displays the deletion indicator.
Technical Data
External Hierarchy
11.1.4.35 Delete Monthwise DSO Data Flag
/PBFBI/DLT_DSO
Use
This characteristic displays the delete monthwise DSO data flag. If the characteristic contains the value “X” for
a projection ID, then the resultant data for the projection ID will be loaded only in the infocube and the same will
be deleted from teh monthwise DSOs upon loading to the infocube.
Technical Data
External Hierarchy
11.1.4.36 Dependent Coverage
/PBFBI/BEN_DEP

Use
This characteristic displays the dependent coverage.
Technical Data
External Hierarchy
11.1.4.37 Detailing of Commitment and Actual in Funds

Management
/PBFBI/FMACTDT
Use
Technical Data
External Hierarchy
11.1.4.38 Distribution Code
/PBFBI/DIS_CDE
Use
This characteristic displays the distribution code.

Technical Data
External Hierarchy
11.1.4.39 Employee
/PBFBI/EMPLOYE
Use
This characteristic enables you to display key figures based on employee criteria.
Technical Data
External Hierarchy
11.1.4.40 Employee Group
0EMPLGROUP
Use
This characteristic displays the employee group.
Technical Data
External Hierarchy

11.1.4.41 Employee Report Number
/PBFBI/RPT_EMP
Use
Technical Data
External Hierarchy
11.1.4.42 Employee SubGroup
0EMPLSGROUP
Use
This characteristic displays the employee subgroup.
Technical Data
External Hierarchy
11.1.4.43 Employee Subgrp Grouping for Collective

Agreement Provisions
/PBFBI/ESGCAP

Use
This characteristic enables you to display key figures at the level of employee subgroup groupings for collective
agreement provisions.
Technical Data
External Hierarchy
11.1.4.44 Employment Status
0EMPLSTATUS
Use
This characteristic displays the employment status.
Technical Data
External Hierarchy
11.1.4.45 End Date
/PBFBI/END_DTE
Use
This characteristic displays the end date.

Technical Data
External Hierarchy
11.1.4.46 Extraction Date
/PBFBI/EXT_DTE
Use
Technical Data
External Hierarchy
11.1.4.47 Functional Area Node Name
/PBFBI/FAHNAME
Use
This characteristic displays the functional area node name.
Technical Data
External Hierarchy

11.1.4.48 Fund Centre Node Name
/PBFBI/FCHNAME
Use
This characteristic displays the fund centre node name.
Technical Data
External Hierarchy
11.1.4.49 Fund Node Name
/PBFBI/FUHNAME
Use
Technical Data
External Hierarchy
11.1.4.50 Funded Program Node Name
/PBFBI/FPHNAME

Use
Technical Data
External Hierarchy
11.1.4.51 Grant Node Name
/PBFBI/GHNAME
Use
Technical Data
External Hierarchy
11.1.4.52 Financial Management Area
/PBFBI/FM_AREA
Use
This characteristic displays Financial Management Area

Technical Data
External Hierarchy
11.1.4.53 First Name
/PBFBI/FST_NME
Use
Technical Data
External Hierarchy
11.1.4.54 Flag for Correction
/PBFBI/FLAG
Use
This characteristic displays the indicator for correction.
Technical Data
External Hierarchy

11.1.4.55 Form Definition / VC Form Name
/PBFBI/VCNAME
Use
Technical Data
External Hierarchy
11.1.4.56 Form Instance ID
/PBFBI/FORM_ID
Use
Technical Data
External Hierarchy
11.1.4.57 Form Type
/PBFBI/FRM_TYP

Use
Technical Data
External Hierarchy
11.1.4.58 FTE Periods
/PBFBI/FTEPERD
Use
Technical Data
External Hierarchy
11.1.4.59 Functional Area
/PBFBI/FUNCARA
Use

Technical Data
External Hierarchy
11.1.4.60 Functional Area Node Type
/PBFBI/FA_NODE
Use
This characteristic displays the functional area node type.
Technical Data
External Hierarchy
11.1.4.61 Fund
/PBFBI/FUND
Use
Technical Data
External Hierarchy

11.1.4.62 Fund Group
/PBFBI/FUNDGRP
Use
Technical Data
External Hierarchy
11.1.4.63 Fund Node Type
/PBFBI/FU_NODE
Use
Technical Data
External Hierarchy
11.1.4.64 Fund Type
/PBFBI/FUNDTYP

Use
Technical Data
External Hierarchy
11.1.4.65 Funded Program
/PBFBI/FUNDPGM
Use
Technical Data
External Hierarchy
11.1.4.66 Funded Program Node Type
/PBFBI/FP_NODE
Use

Technical Data
External Hierarchy
11.1.4.67 Funding Allocation Override
/PBFBI/FUND_OV
Use
Technical Data
External Hierarchy
11.1.4.68 Funding Flag
/PBFBI/FUNDED
Use
Technical Data
External Hierarchy

11.1.4.69 Funds Center
/PBFBI/FUND_CT
Use
Technical Data
External Hierarchy
11.1.4.70 Funds Center Node Type
/PBFBI/FC_NODE
Use
This characteristic displays the funds center node type.
Technical Data
External Hierarchy
11.1.4.71 Funds Center Manager in Organization Model
/PBFBI/FMRESPO

Use
Technical Data
External Hierarchy
11.1.4.72 GUID
/PBFBI/GUID
Use
Technical Data
External Hierarchy
11.1.4.73 GUID for Budget Form Texts
/PBFBI/TXTGUID
Use

Technical Data
External Hierarchy
11.1.4.74 Grant
/PBFBI/GRANT
Use
Technical Data
External Hierarchy
11.1.4.75 Grant Node Type
/PBFBI/GR_NODE
Use
Technical Data
External Hierarchy

11.1.4.76 Health Plan Option
/PBFBI/BEN_HPO
Use
Technical Data
External Hierarchy
11.1.4.77 Hierarchy Item Selector
/PBFBI/HRITNDS
Use
This characteristic displays the hierarchy item selector.
Technical Data
External Hierarchy
11.1.4.78 Hierarchy Item Level
/PBFBI/HRITLVL

Use
This characteristic displays the hierarchy item level.
Technical Data
External Hierarchy
11.1.4.79 Hierarchy Level - Nodes Below (Auth)
/PBFBI/ALLNODE
Use
This characteristic indicates the hierarchy level authorization for nodes below a certain level.
Technical Data
External Hierarchy
11.1.4.80 Hierarchy Level for Authorization
/PBFBI/LEVEL
Use

Technical Data
External Hierarchy
11.1.4.81 Hierarchy Value for Budget Form Combo Edit
/PBFBI/HIER1
Use
Technical Data
External Hierarchy
11.1.4.82 InfoObject
/PBFBI/IOBJNM
Use
Technical Data
External Hierarchy

11.1.4.83 InfoObject for Authorization
/PBFBI/IOBJ
Use
Technical Data
External Hierarchy
11.1.4.84 InfoObject Key Value
/PBFBI/IOBJVAL
Use
Technical Data
External Hierarchy
11.1.4.85 InfoProvider for Authorization
/PBFBI/INFPROV

Use
Technical Data
External Hierarchy
11.1.4.86 InfoProvider PBF
/PBFBI/INFOPR
Use
This characteristic displays the InfoProvider PBF.
Technical Data
External Hierarchy
11.1.4.87 Job
/PBFBI/JOB
Use

Technical Data
External Hierarchy
11.1.4.88 Job Report No.
/PBFBI/RPT_JOB
Use
Technical Data
External Hierarchy
11.1.4.89 Last Executed
/PBFBI/LST_EXE
Use
Technical Data
External Hierarchy

11.1.4.90 Last Execution Date With Projection Posting
/PBFBI/PPJ_LDT
Use
Technical Data
External Hierarchy
11.1.4.91 Last Execution Time With Projection Posting
/PBFBI/PPJ_LTM
Use
Technical Data
External Hierarchy
11.1.4.92 Last Name
/PBFBI/LNAME

Use
Technical Data
External Hierarchy
11.1.4.93 Last Time Executed
/PNFBI/LST_TIM
Use
Technical Data
External Hierarchy
11.1.4.94 Longevity Date
/PBFBI/LONG_DT
Use

Technical Data
External Hierarchy
11.1.4.95 Longevity Date
/PBFBI/LNGE_DT
Use
Technical Data
External Hierarchy
11.1.4.96 Longevity Month
/PBFBI/LONGMTH
Use
Technical Data
External Hierarchy

11.1.4.97 Mandatory Job Benefit — Always Calculate Flag
/PBFBI/MDT_BEN
Use
This characteristic displays the mandatory job benefit.
Technical Data
External Hierarchy
11.1.4.98 MD End Date
/PBFBI/TO_DTE
Use
Technical Data
External Hierarchy
11.1.4.99 Middle Initials
/PBFBI/MDL_NME

Use
Technical Data
External Hierarchy
11.1.4.100 Master Data Copy Run
/PBFBI/COPY
Use
This characteristic displays the master data copy run.
Technical Data
External Hierarchy
11.1.4.101 Modified
/PNFBI/MODIFD
Use

Technical Data
External Hierarchy
11.1.4.102 Name of Person Responsible for Funds Center
/PBFBI/RESPNAM
Use
Technical Data
External Hierarchy
11.1.4.103 New Unit
/PBFBI/UNT_NEWTechnical name
Use
This characteristic displays the new unit.
Technical Data
External Hierarchy

11.1.4.104 New Value
/PBFBI/VAL_NEW
Use
Technical Data
External Hierarchy
11.1.4.105 Node Type for Derivation
/PBFBI/NODETYP
Use
Technical Data
External Hierarchy
11.1.4.106 Number for Stats
/PBFBI/NUMBERTechnical name

Use
This characteristic displays the number for stats.
Technical Data
External Hierarchy
11.1.4.107 Object Hierarchy Name
/PBFBI/HIER
Use
Technical Data
External Hierarchy
11.1.4.108 Objective
/PBFBI/OBJECTV
Use

Technical Data
External Hierarchy
11.1.4.109 Object Type for PCP
/PBFBI/OBJ_TYP
Use
Technical Data
External Hierarchy
11.1.4.110 Old Unit
/PBFBI/UNT_OLD
Use
This characteristic displays the old unit.
Technical Data
External Hierarchy

11.1.4.111 Old Value
/PBFBI/VAL_OLD
Use
Technical Data
External Hierarchy
11.1.4.112 PCP Processed
/PBFBI/PROCSD
Use
Technical Data
External Hierarchy
11.1.4.113 Deletion Indicator
Technical name

Use
This characteristic displays the deletion indicator.
Technical Data
Exchange Available as of Release Backend start release
External Hierarchy
11.1.4.114 PEP Projection Master Data Save Flag
/PBFBI/SAVE_MD
Use
This characteristic displays the PEP projection master data save flag to save the MD of reference projection for
further analysis in what-if projections.
Technical Data
External Hierarchy
11.1.4.115 PM Unit of Measure
/PBFBI/UNIT
Use

Technical Data
External Hierarchy
11.1.4.116 Pay Scale Area
/PBFBI/PYSCLAR
Use
Technical Data
External Hierarchy
11.1.4.117 Pay Scale Group
/PBFBI/PYSCLGP
Use
Technical Data
External Hierarchy

11.1.4.118 Pay Sacle Group — New
/PBFBI/PYSCNGP
Use
Technical Data
External Hierarchy
11.1.4.119 Pay Scale Level
/PBFBI/PYSCLVL
Use
Technical Data
External Hierarchy
11.1.4.120 Pay Scale Level — New
/PBFBI/PYSCNLV

Use
Technical Data
External Hierarchy
11.1.4.121 Pay Scale Type
/PBFBI/PYSCLTY
Use
Technical Data
External Hierarchy
11.1.4.122 Performance Measure
/PBFBI/PRFMEAS
Use

Technical Data
External Hierarchy
11.1.4.123 Performance Period
/PBFBI/PPERIOD
Use
Technical Data
External Hierarchy
11.1.4.124 Performance Start Period
/PBFBI/STPERD
Use
Technical Data
External Hierarchy

11.1.4.125 Personnel Area
0PERS_AREA
Use
This characteristic displays the personal area.
Technical Data
External Hierarchy
11.1.4.126 Planning Function Projection Type
/PBFBI/PRJ_TYP
Use
This characteristic displays the projection type.
Technical Data
External Hierarchy
11.1.4.127 Position
/PBFBI/POSTN

Use
Technical Data
External Hierarchy
11.1.4.128 Position Benefits Counter
/PBFBI/RECORD5
Use
Technical Data
External Hierarchy
11.1.4.129 Positions Record Counter (Employee)
/PBFBI/RECORD4
Use
This characteristic displays the number of records in the employee positions.

Technical Data
External Hierarchy
11.1.4.130 Post Budget Form Cube
/PBFBI/PBF_FLG
Use
Technical Data
External Hierarchy
11.1.4.131 Post Projection Flag
/PBFBI/PPJ_FLG
Use
Technical Data
External Hierarchy

11.1.4.132 Projection End Date
/PBFBI/PRJEDTE
Use
Technical Data
External Hierarchy
11.1.4.133 Projection End Period
/PBFBI/PRJ_EN
Use
Technical Data
External Hierarchy
11.1.4.134 Projection ID
/PBFBI/PROJID

Use
Technical Data
External Hierarchy
11.1.4.135 Projection Scenario Activity
/PBFBI/ACT_VTY
Use
This characteristic displays the projection scenario activity.
Technical Data
External Hierarchy
11.1.4.136 Projection Scenario Header Flag
/PBFBI/HED_FLG
Use
This characteristic displays the projection scenario header flag that is used to dientify the projections that are
added in what-if projections screens.

Technical Data
External Hierarchy
11.1.4.137 Projection: Last Execution Date with Allocation
/PBFBI/ALL_LDT
Use
This characteristic displays the allocation date.
Technical Data
External Hierarchy
11.1.4.138 Projection: Last Execution Time with Allocation
/PBFBI/ALL_LTM
Use
This characteristic displays the last execution time with allocate.
Technical Data
External Hierarchy

11.1.4.139 Projection Last Execution Date With BF Posting
/PBFBI/PBF_LDT
Use
Technical Data
External Hierarchy
11.1.4.140 Projection Last Execution Time With BF Posting
/PBFBI/PBF_LTM
Use
Technical Data
External Hierarchy
11.1.4.141 Projection Start Date
/PBFBI/PRJSDTE

Use
Technical Data
External Hierarchy
11.1.4.142 Projection Start Period
/PBFBI/PRJ_ST
Use
Technical Data
External Hierarchy
11.1.4.143 Projection Status
/PBFBI/PRJSTAT
Use
This characteristic displays the projection status.

Technical Data
Exchange Available as of Release SAP Public Budget Formulation 7.1 SP 01Start release
External Hierarchy
11.1.4.144 Projection Type
/PBFBI/PRJ_TYP
Use
Technical Data
External Hierarchy
11.1.4.145 Query Name for Authorization
/PBFBI/QUERY
Use
Technical Data
External Hierarchy

11.1.4.146 Ranking ID
/PBFBI/RANK_ID
Use
Technical Data
External Hierarchy
11.1.4.147 Ranking Stage
/PBFBI/RSTAGE
Use
Technical Data
External Hierarchy
11.1.4.148 Reason Change Text GUID
/PBFBI/RCGUID

Use
Technical Data
External Hierarchy
11.1.4.149 Record Counter (Employee)
/PBFBI/RECORD2
Use
This characteristic displays the number of records in the employee allocation.
Technical Data
External Hierarchy
11.1.4.150 Record Counter (Position)
/PBFBI/RECORD
Use
This characteristic displays the number of records in the position allocations.

Technical Data
External Hierarchy
11.1.4.151 Reference Projection ID
/PBFBI/RFPRJID
Use
This characteristic displays the reference projection ID. All what-if IDs will be generated on top of reference
projection IDs. For such what-if IDs, this characteristic displays their reference/parent projection ID.
Technical Data
External Hierarchy
11.1.4.152 Reporting Job Class
/PBFBI/JOB_CLS
Use
Technical Data
External Hierarchy

11.1.4.153 Reporting Position
/PBFBI/RPT_POS
Use
Technical Data
External Hierarchy
11.1.4.154 Salary Override
/PBFBI/SAL_OVD
Use
Technical Data
External Hierarchy
11.1.4.155 Shared Memory Instance Name
/PBFBI/SOMINST

Use
Technical Data
External Hierarchy
11.1.4.156 Start Date
/PBFBI/ST_DATE
Use
Technical Data
External Hierarchy
11.1.4.157 Status
/PBFBI/STATUS
Use

Technical Data
External Hierarchy
11.1.4.158 Status of Form
/PBFBI/STFRM
Use
Technical Data
External Hierarchy
11.1.4.159 Step Date
/PBFBI/STP_DTE
Use
Technical Data
External Hierarchy

11.1.4.160 Step Months
/PBFBI/STPMTHS
Use
Technical Data
External Hierarchy
11.1.4.161 Text ID
/PBFBI/TXTID
Use
This characteristic displays the text ID.
Technical Data
External Hierarchy
11.1.4.162 Text Status
/PBFBI/TXTSTAT

Use
Technical Data
External Hierarchy
11.1.4.163 Total No. of Records Written
/PBFBI/NO_REC
Use
This characteristic displays the total number of records written.
Technical Data
External Hierarchy
11.1.4.164 Truth Value
/PBFBI/BOOL
Use
This characteristic displays the truth value.

Technical Data
External Hierarchy
11.1.4.165 Transaction Type
/PBFBI/TRANSTY
Use
This characteristic displays the transaction type.
Technical Data
External Hierarchy
11.1.4.166 GUID for Transaction
/PBFBI/TRANSID
Use
This characteristic displays the GUID for a transaction. In Reallocations, each transaction is identified by a
unique GUID.
Technical Data
Exchange Available as of Release SAP PUBLIC BUDGET FORMULATION 7.1 SP01
External Hierarchy

11.1.4.167 Update Time Stamp
/PBFBI/UPDTMST
Use
Technical Data
External Hierarchy
11.1.4.168 User Name
/PBFBI/UNAME
Use
Technical Data
External Hierarchy
11.1.4.169 User Name
/PBFBI/USERNAM

Use
Technical Data
External Hierarchy
11.1.4.170 Vacant Counts
/PBFBI/VAC_CNT
Use
Technical Data
External Hierarchy
11.1.4.171 Vacant Lag Months
/PBFBI/VCT_LGM
Use

Technical Data
External Hierarchy
11.1.4.172 Vacant Selections
/PBFBI/VCNT_FL
Use
Technical Data
External Hierarchy
11.1.4.173 Value type in Funds Management
/PBFBI/FMVTYPE
Use
Technical Data
External Hierarchy

11.1.4.174 Version
/PBFBI/VERSION
Use
Technical Data
External Hierarchy
11.1.4.175 Wage Type
/PBFBI/WAGETYP
Use
Technical Data
External Hierarchy
11.1.5 PEP Maintenance
Projection Scenario — Queue and Statistics [page 300] is the other InfoArea within PCP Maintenance.

11.1.5.1 DataStore Objects
11.1.5.1.1 Audit Header
/PBFBI/AUD_O01
Use
This DataStore object is required to keep track of the changes made to the master data. It stores information
such as who made the changes and at what time. It stores the header level information only.
Key Fields
InfoObject Description Comment
/PBFBI/GUID GUID A new GUID is generated for every session.
Data Fields
0DATE Date
/PBFBI/IOBJNM InfoObject
/PBFBI/OBJVAL InfoObject Key Val
0TIME Time
/PBFBI/UPDTMST Update Time Stamp
/PBFBI/USERNAM User Name
Structure
Delta Update
Delta update is not supported for this DataStore object.

11.1.5.1.2 Audit Item
/PBFBI/AUD_O02
Use
This DataStore object is required to keep item level information about the fields which were changed.
Key Fields
/PBFBI/GUID GUID
/PBFBI/CHGNR Change Number
Data Fields
/PBFBI/ATTR Attribute
/PBFBI/CHGTYPE Audit: Change Type
/PBFBI/VAL_NEW New Value
/PBFBI/VAL_OLD Old Value
Structure
Delta Update
11.1.5.1.3 Benefit Rates
/PBFBI/PHR_O10

Use
This DataStore object is required for the maintenance of benefit rates corresponding to a benefit area and
benefit plan.
Key Fields
/PBFBI/BENRGST Benefit Range
/PBFBI/DATETO Step Date To
Data Fields
/PBFBI/DATEFR Date From
/PBFBI/BEN_AMT Benefit Amount
0CURRENCY Currency
/PBFBI/BEN_RT Key Benefit Rate
0RECORDMODE BW Delta Process: Update Mode
/PBFBI/BENMNAM Benefit Minimum Amount
/PBFBI/BENMXAM Benefit Maximum Amount
/PBFBI/LONGMTH Longevity Months
Structure
Delta Update
11.1.5.1.4 Benefit Rates — Staging
/PBFBI/HRSTO10

Use
This DataStore object is required for the maintenance of benefit rates corresponding to a benefit area and
benefit plan. This DSO is a staging DSO for the ETL process while loading data from the source system and
subsequently pushes the data to DSO /PBFBI/HRPAO06.
Key Figures
/PBFBI/BENRGST Benefit Range Step
/PBFBI/DATETO Date To
Data Fields
/PBFBI/DATEFR Date From
0CURRENCY Currency
/PBFBI/BEN_RT Key Benefit Rate
/PBFBI/BENMNAM Benefit Minimum Amount
/PBFBI/BENMXAM Benefit Maximum Amount
/PBFBI/LONGMTH Longevity Months
Structure
Delta Update
11.1.5.1.5 Employee Allocations
/PBFBI/HRPAO02

Use
This DataStore object stores the percentage allocation of a employee across Fund Centers. Data for this DSO
comes from the Employee Maintenance screen.
Key Fields
/PBFBI/RECORD2 Record Counter (Employee)
/PBFBI/EMPLOYE Employee MD
/PBFBI/TO_DTE End Date
Data Fields
/PBFBI/FUND Fund
/PBFBI/GRANT Grant
/PBFBI/FND_PCT Funding Percentage
/PBFBI/ST_DATE Start Date
/PBFBI/END_DTE End Date
/PBFBI/STATUS Status
/PBFBI/CMMT_IT Commitment Item
Structure
Delta Update

11.1.5.1.6 Employee Allocation — Staging
/PBFBI/HRSTO02
Use
This DataStore object stores the percentage allocation of a employee across Fund Centers. This DSO is a
staging DSO for the ETL process while loading data from the source system and eventually pushes the data to
DSO /PBFBI/HRPAO02.
Key Fields
/PBFBI/EMPLOYE Employee MD
/PBFBI/TO_DTE End Date
Data Fields
/PBFBI/FUND Fund
/PBFBI/GRANT Grant

Structure
Delta Update
11.1.5.1.7 Employee Benefits
/PBFBI/HRPAO03
Use
This DataStore object is required for the mapping of an employee to a valid combination of benefit area and
benefit plan (employee benefits) . The Employee Maintenance screen provides the data for this DSO.
Key Fields
0FISCVARNT Fiscal Variant
/PBFBI/TO_DTE MD End Date
/PBFBI/RECORD3 Benefit Record Counter (Employee)
Data Fields
/PBFBI/WAGETYP Wage Type

Structure
Delta Update
11.1.5.1.8 Employee Benefits — Staging
/PBFBI/HRSTO03
Use
This DataStore object is required for the mapping of an employee to a valid combination of benefit area and
benefit plan (employee benefits) . This DSO is a staging DSO for the ETL process while loading data from the
source system and eventually pushes the data to DSO /PBFBI/HRPAO03.
Key Fields
/PBFBI/RECORD3 Benefit Record Counter (Employee)
Data Fields

Structure
Delta Update
11.1.5.1.9 Employee Positions
/PBFBI/HRPAO04
Use
This DataStore object is required for the mapping of employee allocations with different positions.
Key Fields

/PBFBI/RECORD4 Positions Record Counter (Employee)
Data Fields
/PBFBI/POS_ALL Position Allocation
Structure
Delta Update
11.1.5.1.10 Position Benefits
/PBFBI/HRPAO05
Use
This DataStore object is required for the mapping of a position to a valid combination of benefit area and
benefit plan (position benefits). Position Maintenance screen provides the data for this DSO.
Key Fields
/PBFBI/RECORD5 Position Benefits Counter

Data Fields
Structure
Delta Update
11.1.5.1.11 Position Benefits — Staging
/PBFBI/HRSTO05
Use
benefit plan (position benefits). This DSO is a staging DSO for the ETL process while loading data from the
source system and pushes the data to DSO /PBFBI/HRPAO05.
Key Fields

/PBFBI/RECORD5 Position Benefit Counter
Data Fields
Structure
Delta Update
11.1.5.1.12 Job Benefits
/PBFBI/HRPAO06
Use
This DataStore object is required for the mapping of a job to a valid combination of benefit area and benefit
plan (job benefits). Job Maintenance screen provides the data for this DSO.
Key Fields

/PBFBI/JOB Job
/PBFBI/RECORD6 Counter — Job Benefits
Data Fields
Structure
Delta Update
11.1.5.1.13 Job Benefits — Staging

/PBFBI/HRSTO06
Use
This DataStore object is required for the mapping of a job to a valid combination of benefit area and benefit
plan (job benefits). This DSO is a staging DSO for the ETL process while loading data from the source system
and pushes the data to DSO /PBFBI/HRPAO06.

Key Fields
/PBFBI/JOB Job
Data Fields
Structure
Delta Update
11.1.5.1.14 Position Allocations
/PBFBI/HRPAO01

Use
This DataStore object stores the percentage allocation of a position across fund centers. Position Maintenance
screen provides the data for this DSO.
Key Fields
/PBFBI/RECORD Record Counter (Position)
Data Fields
/PBFBI/FUND Fund
/PBFBI/GRANT Grant

Structure
Delta Update
11.1.5.1.15 Position Allocations — Staging
/PBFBI/HRSTO01
Use
This DataStore object stores the percentage allocation of a position across fund centers. This DSO is a staging
DSO for the ETL process while loading data from the source system and pushes the data to DSO /PBFBI/
HRPAO01.
Key Fields
Data Fields
/PBFBI/FUND Fund
/PBFBI/GRANT Grant

Structure
Delta Update
11.1.5.1.16 Position Benefits
/PBFBI/HRPAO05
Use
benefit plan (position benefits). Position Maintenance screen provides the data for this DSO.
Key Fields
/PBFBI/RECORD5 Position Benefits Counter
Data Fields

Structure
Delta Update
11.1.5.1.17 Position Benefits — Staging
/PBFBI/HRSTO05
Use
benefit plan (position benefits). This DSO is a staging DSO for the ETL process while loading data from the
source system and pushes the data to DSO /PBFBI/HRPAO05.
Key Fields

/PBFBI/RECORD5 Position Benefit Counter
Data Fields
Structure
Delta Update
11.1.5.1.18 Postion MD for Proj Scenarios
/PBFBI/OPOSTON
Use
This DataStore object is required for storing the data of an position’s monthwise records after performing PEP
calculation for salary and benefits for a projection scenario. This acts as a staging area while pushing the data
to the projection cube.
Key Fields

0USERNAME User Name
0DATE Date
/PBFBI/COPY PBF Master Data Copy Run
0FISCVARNT Fiscal year variant
Data Fields
/PBFBI/FUND Fund
/PBFBI/GRANT Grant
/PBFBI/JOB Job
/PBFBI/CREATED Created (System Field)
/PBFBI/DP_POS Decision Package Position

sions
/PBFBI/MODIFD Modified (System Field)
/PBFBI/PPERIOD Performance Period
/PBFBI/PROCSD PCP Processed
/PBFBI/PYSCLGP Pay Scale Group

/PBFBI/ATH_FIL Authorization to Fill
0EMPLSTATUS Employment Status
0LOGSYS Source System
/PBFBI/RPT_POS Reporting Position
/PBFBI/STPERD Performance St. Period
/PBFBI/STP_DTE Step Date
/PBFBI/UPDTMST Update Time Stamp
/PBFBI/ATH_CTR Authorised Count
0POS_FTE Position FTE
0ANSALARY Annual Salary
0CURRENCY Annual Salary
Structure
Delta Update

11.1.5.1.19 Projection Benefit Parameters
/PBFBI/PHR_O12
Use
This DataStore stores the supplementary benefit amounts and rate for the projection scenario.
Key Fields
Data Fields
/PBFBI/RATE Rate
0FM_CURR Currency Key for FM Area Currency
Structure
Delta Update

11.1.5.1.20 Projection Pay Parameters
/PBFBI/PHR_O11
Use
This DataStore stores the supplementary salary amounts and rate for the projection scenario.
Key Fields

sions
Data Fields
/PBFBI/RATE Rate

Structure
Delta Update
11.1.5.1.21 Projection Selection Parameters
/PBFBI/PHR_O14
Use
This DataStore object stores the Projection Screen parameter header details which is used as a filter for the
projection scenarios.
Key Fields
/PBFBI/HED_FLG Projection Scenario Header Flag
Data Fields
/PBFBI/UNAME User Name
/PBFBI/LST_EXE Last Executed
/PBFBI/LST_TIM Last Time Executed
/PBFBI/PRJ_ST Projection Start Period
/PBFBI/PRJ_EN Projection End Period
/PBFBI/ALL_FLG Allocate Flag
/PBFBI/VCT_LGM Vacant Lag Months

/PBFBI/FUND Fund
/PBFBI/GRANT Grant
/PBFBI/PPJ_FLG Post Projection flag
/PBFBI/PBF_FLG Post Budget Form Cube
/PBFBI/ALL_LDT Projection: Last Exec Date w Allocate
/PBFBI/ALL_LTM Projection: Last Exec Time w Allocate
/PBFBI/PPJ_LDT Projection: Last Exec Date w Prj Posting
/PBFBI/PPJ_LTM Projection: Last Exec Time w Proj Posting
/PBFBI/PBF_LDT Projection: Last Exec Date w BF Posting
/PBFBI/PBF_LTM Projection: Last Exec Time w BF Posting
/PBFBI/PRJSDTE Projection Start Date
/PBFBI/PRJEDTE Projection End Date

sions
/PBFBI/JOB Job

/PBFBI/RFPRJID Reference Projection ID
/PBFBI/SAVE_MD PEP Projection Master Data Save Flag
/PBFBI/DLT_DSO Delete Monthwise DSO Data Flag
OFM_CURR Currency key for FM area currency
Structure
Delta Update
11.1.5.1.22 Projection — Distributions
/PBFBI/PRJ_O15
Use
This DataStore object stores the periodic distribution percentages for the distribution code maintained in the
job class.
Key Fields
/PBFBI/DIS_CDE Distribution Code
0FISCPER Fiscal year / period
Data Fields

/PBFBI/DIS_PCT Distribution Percentage
Structure
Delta Update
11.1.5.1.23 Salary Amounts
/PBFBI/PHR_O09
Use
This DataStore object is required for storing salary data such as pay scale area, pay scale type, pay scale group,
pay scale level, and employee subgroup.
Key Fields
Data Fields

sions

0CURRENCY Currency Key
Structure
Delta Update
11.1.5.1.24 Store the Emp. Assignment to Pos. Monthwise
/PBFBI/EMPCNT
Use
This DataStore object stores employee assignment to positions on a periodic basis.
Key Fields
0FISCYEAR Fiscal year
Data Fields


sions
/PBFBI/JOB Job
/PBFBI/GRANT Grant
/PBFBI/FUND Fund
Structure
Delta Update
11.1.5.2 MultiProviders

11.1.5.2.1 Employee Position Monthwise
/PBFBI/HR_M02
Use
This MultiProvider contains the DataStore objects /PBFBI/HRPAO07 [page 305] and /PBFBI/HRPAO08 [page
311].
11.1.5.2.2 MultiProvider for Projection Cubes
/PBFBI/HR_M04
Use
InfoCubes
/PBFBI/HRPJ_R01 Projection Cube
/PBFBI/PROJ_1 – Budget Form Positions Cube Projection Cube 1 [page 300]
/PBFBI/PROJ_2 – Reference-based Projection Cube Projection Cube 2 [page 302]
11.1.5.2.3 Update Projection Calculations
/PBFBI/HR_M03
Use
This MultiProvider consists of the following InfoCubes and DataStore objects.
InfoCubes

DataStore Objects
/PBFBI/HRPAO07 Employee Monthwise [page 305]
/PBFBI/HRPAO08 Position Monthwise [page 311]
11.1.5.3 Projection Scenario — Queue and Statistics
11.1.5.3.1 Projection Cube 1
/PBFBI/PROJ_1
Use
Unit
Characteristics

/PBFBI/GRANT Grant
/PBFBI/FUND Fund

sions
/PBFBI/JOB Job

Key Figures
11.1.5.3.2 Projection Cube 2
/PBFBI/PROJ_2
Use

Unit
Characteristics
/PBFBI/GRANT Grant
/PBFBI/FUND Fund

sions

/PBFBI/JOB Job
Key Figures

11.1.5.3.3 Combined Dimension — Reporting
/PBFBI/BF_PRJ
Use
InfoCubes
InfoObject InfoCube
/PBFBI/PM_R01 Performance Measure Cube [page 170]
/PBFBI/PROJ_1 Projection Cube 1 [page 300]
/PBFBI/PROJ_2 Projection Cube 2 [page 302]
11.1.5.3.4 DataStore Objects
11.1.5.3.4.1 Employee Monthwise
/PBFBI/HRPAO07

Use
This DataStore object is required for storing the data of an employee’s monthwise records after performing
PEP calculation for salary and benefits for a projection scenario. This acts as a staging area while pushing the
data to the projection cube.
Key Fields
/PBFBI/GUID GUID
Data Fields
/PBFBI/FUND Fund
/PBFBI/ACCUM Benefit Accumulator
0DATETO Valid To
0DATEFROM Valid From
0CALMONTH Calendar Year/Month
/PBFBI/JOB Job


sions
/PBFBI/FUND_OV Funding Allocation Override
/PBFBI/GRANT Grant
/PBFBI/CALC_OR Calculation Order
/PBFBI/BAS_AMT Calculation Basis Amount
/PBFBI/CAP_AMT Percentage Capitalization Amount
0FISCPER Fiscal Year/Period

Structure
Delta Update
11.1.5.3.4.2 Employee Monthwise Kit 2
/PBFBI/HRPAO09
Use
This DataStore object is required for storing the data of an employee’s monthwise records after performing
PEP calculation for salary and benefits for a projection scenario. This acts as a staging area while pushing the
data to the projection cube.
Key Fields
/PBFBI/GUID GUID

Data Fields
/PBFBI/FUND Fund
0DATETO Valid To
/PBFBI/JOB Job

sions

/PBFBI/GRANT Grant

Structure
Delta Update
11.1.5.3.4.3 Position Monthwise
/PBFBI/HRPAO08
Use
This DataStore object is required for storing the data of an position’s monthwise records after performing PEP
Calculation for salary and benefits for a Projection Scenario. This acts as a staging area while pushing the data
Key Fields
/PBFBI/GUID GUID
Data Fields

0DATETO Valid To
/PBFBI/JOB Job

sions
/PBFBI/GRANT Grant

/PBFBI/FUND Fund
0FISCPER3 Posting
/PBFBI/FIL_CTR Filled Counter

Structure
Delta Update
11.1.5.3.4.4 Position Monthwise Kit 2 (Direct Update)
/PBFBI/HRPAO10
Use
This DataStore object is required for storing the data of a position’s monthwise records after performing PEP
calculation for salary and benefits for a projection scenario. This acts as a staging area while pushing the data
Key Fields
/PBFBI/GUID GUID
Data Fields
0DATETO Valid To

/PBFBI/JOB Job

sions
/PBFBI/GRANT Grant
/PBFBI/FUND Fund
0FISCPER3 Posting

Structure
Delta Update
11.1.5.4 Reference-Based Projections and PDP Master Data

Versioning

Structure
Use
DataStore Objects
11.1.5.4.1.1 Employee – PEP Analysis Data & Master Data

Version
/PBFBI/RBPSO01
Use
This DataStore object is required for storing the data of an Employee's Master Data Records after inheriting the
missing information such as Pay Scale Details, FTE Period, Distribution Code, Commitment Item, and so on for
a Projection Scenario. This DSO will also hold the Employee Records split based on STEPs after STEP
Calculation. This acts as a reference data for what-if projection scenarios.
Key Fields
/PBFBI/GUID GUID
Data Fields
0DATETO Valid to
0DATEFROM Valid from
/PBFBI/JOB Job


sions
/PBFBI/FUND Fund
/PBFBI/GRANT Grant
/PBFBI/FUND_OV Funding Allocation Overide

/PBFBI/EXT_DTE Extraction Date
/PBFBI/LONG_DT Longevity Date
/PBFBI/MD_FLG Master Data Flag
/PBFBI/PCT_CAP Percentage Capitalization Flag
Structure
Delta Update
The following delta update is supported for this DataStore object:
● Delta update:
● DataSource:
11.1.5.4.1.2 Employee Projection Allcations
/PBFBI/RBPSO05
Use
This DataStore object is required for storing the data snap shot of an Allocation Details of all the Employees
qualified for the Reference Projection Run. This acts as a reference data for What-IF projection Scenarios.
Key Fields

Data Fields
/PBFBI/FUND Fund
/PBFBI/GRANT Grant
Structure
Delta Update
● Delta update:
● DataSource:
11.1.5.4.1.3 Employee Projection Benefits
/PBFBI/RBPSO07

Use
This DataStore object is required for storing the data snap shopt of the Benefit Details of all the Employees
qualified for the Reference Projection Run. This acts as a reference data for What-IF projection Scenarios. This
DSO also holds Add on Projection Specific Employee Benefits entered by the user on What If Projection Screen.
Key Fields
/PBFBI/RECORD3 Benefits Record Counter (Employee)
Data Fields
/PBFBI/IF_FLG Inherited From Flag
/PBFBI/EXCLUDE Exclude Flag
Structure
Delta Update
● Delta update:

● DataSource:
11.1.5.4.1.4 Job Benefits Inherited
/PBFBI/RBPSO09
Use
This DataStore object is required for storing the data snap shopt of the Benefit Details of all the Jobs used for
inheriting missing Employee and Position’s Benefit qualified for the Reference Projection Run. This acts as a
reference data for What-IF projection Scenarios.
Key Fields
/PBFBI/JOB Job
Data Fields

Structure
Delta Update
● Delta update:
● DataSource:
11.1.5.4.1.5 Position — PEP Analysis Data & Master Data

Version
/PBFBI/RBPSO02
Use
This DataStore object is required for storing the data of an Position’s Master Data Records after inheriting the
missing information such as Pay Scale Details, FTE Period, Distribution Code, Commitment Item, etc. for a
Projection Scenario. This DSO will also hold the Position Records splitted based on STEPs after STEP
Calculation. This acts as a reference data for What-IF projection Scenarios.
Key Fields
InfoObjects Description
/PBFBI/GUID GUID
Data Fields
0DATETO Valid to
/PBFBI/JOB Job


sions
/PBFBI/PYSCLGP Payscale Group
/PBFBI/FUND Fund
/PBFBI/GRANT Grant
/PBFBI/PPERIOD Perforance Period

/PBFBI/LONG_DT Longevity Date
/PBFBI/RPT_POS Reporting Position
/PBFBI/ATH_FIL Authorization to Fill
0POS_FTE Position FTE
/PBFBI/ATH_CTR Authorized Content
/PBFBI/MD_FLG Master Data Flag
/PBFBI/PCT_CAP Percentage Capitalization Flag
Structure
Delta Update
● Delta update:
● DataSource:
11.1.5.4.1.6 Position Projection Allocations
/PBFBI/RBPSO06
Use
This DataStore object is required for storing the data snap shopt of an Allocation Details of all the Positions
qualified for the Reference Projection Run. This acts as a reference data for What-IF projection Scenarios.
Key Fields

Data Fields
/PBFBI/FUND Fund
/PBFBI/GRANT Grant
/PBFBI/STATUS status
Structure
Delta Update
● Delta update:
● DataSource:
11.1.5.4.1.7 Position Projection Benefits
/PBFBI/RBPSO08

Use
This DataStore object is required for storing the data snap shopt of the Benefit Details of all the Positions
qualified for the Reference Projection Run. This acts as a reference data for What-IF projection Scenarios. This
DSO also holds Add on Projection Specific Position Benefits entered by the user on What If Projection Screen.
Key Fields
/PBFBI/RECORD3 Benefits Record Counter (Employee
Data Fields
/PBFBI/CTRY_ID country Grouping
/PBFBI/END_DTE End date
/PBFBI/IF_FLG Inherited from flag
/PBFBI/EXCLUDE Exclude flag
Structure
Delta Update
● Delta update:
● DataSource:

11.1.5.4.1.8 Position's Employee Count
/PBFBI/RBPSO03
Use
This DataStore object is required for storing the data snap shopt of Employee’s Annual Count Details of all the
Positions qualified for the Reference Projection Run. This acts as a reference data for What-IF projection
Scenarios.
Key Fields
/PBFBI/POSTN Postion
Data Fields
Structure
Delta Update
● Delta update:
● DataSource:

11.1.5.4.1.9 Projection-Specific Pay Scale Level
/PBFBI/RBPSO04
Use
This DataStore object is required for storing the Pay Table Details entered by the user on a What IF Projection
Screen while executing What IF Projection Run.
Key Fields

sions
0DATETO Valid to
Data Fields
0CURRENCY Currency key
/PBFBI/PYLVAMT Pay level amount
/PBFBI/STPMTHS Step Months
/PBFBI/PYSCNLV Pay Scale Level — New
/PBFBI/PYSCNGP Pay Scale Group — New
/PBFBI/FXRATE Rate for annual fixed salary increases

Structure
Delta Update
● Delta update:
● DataSource:
11.1.5.5 Projection Kit for Reference-based Projection

Scenarios
11.1.5.5.1 Reference-Based Projection Cube 1
/PBFBI/RPRJ_1
Use
Unit
Characteristics

/PBFBI/CTRY_ID Country grouping
0EMPLGROUP Employee group

sions
/PBFBI/FTEPERD FTE periods
/PBFBI/FM_AREA financial Management Area
/PBFBI/VC_NAME Form Definition / VC Model name
/PBFBI/FUNCARA functional Area
/PBFBI/FUND Fund
/PBFBI/GRANT Grant
/PBFBI/JOB Job

/PBFBI/RFPRJID Reference Projection ID
Key Figures
11.1.5.6 Pay Period Projection
Pay Period Projection
11.1.5.6.1 Pay Period Projection Attrition and Backfill Kit

11.1.5.6.1.1 Attrition and Backfill Projection Cube
/PBFBI/PPRD_C4
Use
Unit
Characteristics
/PBFBI/GRANT Grant
/PBFBI/FUND Fund


sions
/PBFBI/JOB Job
/PBFBI/PAY_PER Pay Period
/PBFBI/PAY_YR Pay Year
/PBFBI/PAY_TYP Pay Period Type
Key Figures

11.1.5.6.1.2 Attrition and Backfill Employee DSO
/PBFBI/PPRDOE4
Use
Key Fields
/PBFBI/GUID GUID
Data Fields
/PBFBI/FUND Fund

0DATETO Valid To
/PBFBI/JOB Job

sions

/PBFBI/GRANT Grant

/PBFBI/PAYPERD Pay Year / Period
Structure
Delta Update
11.1.5.6.1.3 Attrition and Backfill Position DSO
/PBFBI/PPRDOP4
Use
Key Fields
/PBFBI/GUID GUID
Data Fields
/PBFBI/FUND Fund

0DATETO Valid To
/PBFBI/JOB Job

sions
/PBFBI/GRANT Grant


Structure
Delta Update
11.1.5.6.2 Pay Period Projection Kit
11.1.5.6.2.1 Pay Period Projection Cubes
/PBFBI/PPRD_C1 - Pay Period Projection Cube1, /PBFBI/PPRD_C2 - Pay Period

Projection Cube2, /PBFBI/PPRD_C3 - Pay Period Projection Cube3
Use
Unit
Characteristics

/PBFBI/GRANT Grant
/PBFBI/FUND Fund

sions
/PBFBI/JOB Job

Key Figures
11.1.5.6.2.2 Employee Pay Periodwise Records
/PBFBI/PPRDOE1 - Employee Pay Periodwise Records-1, /PBFBI/PPRDOE2 - Employee Pay

Periodwise Records-2, /PBFBI/PPRDOE3 - Employee Pay Periodwise Records-3

Use
Key Fields
/PBFBI/GUID GUID
Data Fields
/PBFBI/FUND Fund
0DATETO Valid To
/PBFBI/JOB Job


sions
/PBFBI/GRANT Grant

Structure
Delta Update
11.1.5.6.2.3 Position Pay Periodwise Records
/PBFBI/PPRDOP1 - Position Pay Periodwise Records-1, /PBFBI/PPRDOP2 - Position Pay

Periodwise Records-2, /PBFBI/PPRDOP3 - Position Pay Periodwise Records-3
Use
Key Fields

/PBFBI/GUID GUID
Data Fields
/PBFBI/FUND Fund
0DATETO Valid To
/PBFBI/JOB Job

sions

/PBFBI/GRANT Grant
0FISCPER3 Posting

/PBFBI/FUND Fund
0DATETO Valid To
/PBFBI/JOB Job


sions
/PBFBI/GRANT Grant
0FISCPER3 Posting

Structure
Delta Update
11.1.5.6.3 MultiProvider for Pay Period Projection Cubes
/PBFBI/PPRD_M1

Use
/PBFBI/PPRD_C1 Pay Period Projection Cube1 Pay Period Projection Cubes [page 341]
/PBFBI/PPRD_C2 Pay Period Projection Cube2 Pay Period Projection Cubes [page 341]
PBFBI/PPRD_C3 Pay Period Projection Cube3 Pay Period Projection Cubes [page 341]
/PBFBI/PPRD_C4 Attrition and Backfill Projection Cube Attrition and Backfill Projection Cube
[page 333]
11.1.5.7 Attrition and Backfill Master Data
Attrition and Backfill Master Data
11.1.5.7.1 Attrition Rule Detail
/PBFBI/PPRD_AD
Use
Key Fields
/PBFBI/ATR_RUL Attrition Rule
Data Fields
/PBFBI/ATT_RT Attrition Rate

Structure
Delta Update
11.1.5.7.2 Attrition Rule Header
/PBFBI/PPRD_AH
Use
Key Fields
Data Fields
/PBFBI/FUND Fund
/PBFBI/GRANT Grant
/PBFBI/JOB Job


sions
Structure
Delta Update
11.1.5.7.3 Attrition and Backfill Rule
/PBFBI/PPRD_AB
Use
Key Fields
/PBFBI/ANB_GRP Attrition and Backfill Group ID
/PBFBI/ANB_RUL Attrition and Backfill Rule
Data Fields

/PBFBI/ANB_TYP A & B Rule type
/PBFBI/ATR_SPP Backfill determination: Attrition Start Pay Period
/PBFBI/ATR_SPY Backfill determination: Attrition Start Pay Year
/PBFBI/ATR_EPP Backfill determination: Attrition End Pay Period
/PBFBI/ATR_EPY Backfill determination: Attrition End Pay Year
/PBFBI/BFL_SPP Backfill Start Pay Period
/PBFBI/BFL_SPY Backfill Start Pay Year
/PBFBI/BFL_RT Backfill Rate
/PBFBI/BFL_CT Backfill Count (Headcount)
Structure
Delta Update
11.1.6 Public Budget Formulation — Master Data
This InfoArea consists of the following InfoObjects:
/PBFBI/BEN_ARE Benefit Area [page 197]
/PBFBI/BEN_PLN Benefit Plan [page 199]
/PBFBI/STAGE Budget Stage [page 200]
/PBFBI/PUVALTP Budgeting Value Type [page 201]
/PBFBI/CI_TYPE Commitment Item Category [page 205]

/PBFBI/CIGRP Commitment Item Group [page 205]
/PBFBI/CMMT_IT Commitment Item [page 204]
/PBFBI/DIS_CDE Distribution Code [page 210]
/PBFBI/EMPLOYE Employee [page 211]
/PBFBI/ESGCAP Employee Subgrp Grouping for Collective Agreement

Provisions [page 212]
/PBFBI/FM_AREA Financial Management Area [page 216]
/PBFBI/FA_NODE Functional Area Node Type [page 220]
/PBFBI/FUND Fund [page 220]
/PBFBI/FUNDGRP Fund Group [page 221]
/PBFBI/FU_NODE Fund Node Type [page 221]
/PBFBI/FUNDTYP Fund Type [page 221]
/PBFBI/FUNDPGM Funded Program [page 222]
/PBFBI/FP_NODE Funded Program Node Type [page 222]
/PBFBI/FUND_CT Funds Center [page 224]
/PBFBI/FC_NODE Funds Center Node Type [page 224]
/PBFBI/GRANT Grant [page 226]
/PBFBI/GR_NODE Grant Node Type [page 226]
/PBFBI/JOB Job [page 231]
/PBFBI/NODETYP Node Type for Derivation [page 239]
/PBFBI/PYSCLAR Pay Scale Area [page 244]
/PBFBI/PYSCLGP Pay Scale Group [page 244]
/PBFBI/PYSCNGP Pay Scale Group – New [page 370]
/PBFBI/PYSCLVL Pay Scale Level [page 245]
/PBFBI/PYSCNLV Pay Scale Level – New [page 245]
/PBFBI/PYSCLTY Pay Scale Type [page 246]

/PBFBI/POSTN Position [page 248]
/PBFBI/RSTAGE Ranking Stage [page 257]
/PBFBI/JOB_CLS Reporting Job Class [page 259]
/PBFBI/FMVTYPE Value Type in Funds Management [page 268]
/PBFBI/VERSION Version [page 269]
/PBFBI/WAGETYP Wage Type [page 269]
11.1.6.1 Benefit Area
/PBFBI/BEN_ARE
Use
You can use this characteristic to break key figures down by benefit area.
Technical Data
External Hierarchy
11.1.6.2 Benefit Plan
/PBFBI/BEN_PLN
Use
You can use this characteristic to break key figures down by benefit plan.

Technical Data
External Hierarchy
11.1.6.3 Budget Stage
/PBFBI/STAGE
Use
Technical Data
External Hierarchy
11.1.6.4 Budgeting Value Type
/PBFBI/PUVALTP
Use
Technical Data
External Hierarchy

11.1.6.5 Commitment Item Category
/PBFBI/CI_TYPE
Use
This characteristic displays the commitment item category.
Technical Data
External Hierarchy
11.1.6.6 Commitment Item Group
/PBFBI/CIGRP
Use
This characteristic displays the commitment item group.
Technical Data
External Hierarchy
11.1.6.7 Commitment Item
/PBFBI/CMMT_IT

Use
This characteristic displays the commitment item.
Technical Data
External Hierarchy
11.1.6.8 Distribution Code
/PBFBI/DIS_CDE
Use
This characteristic displays the distribution code.
Technical Data
External Hierarchy
11.1.6.9 Employee
/PBFBI/EMPLOYE
Use

Technical Data
External Hierarchy
11.1.6.10 Employee Subgrp Grouping for Collective

Agreement Provisions
/PBFBI/ESGCAP
Use
This characteristic enables you to display key figures at the level of employee subgroup groupings for collective
agreement provisions.
Technical Data
External Hierarchy
11.1.6.11 Financial Management Area
/PBFBI/FM_AREA
Use
This characteristic displays Financial Management Area
Technical Data

External Hierarchy
11.1.6.12 Functional Area Node Type
/PBFBI/FA_NODE
Use
This characteristic displays the functional area node type.
Technical Data
External Hierarchy
11.1.6.13 Fund
/PBFBI/FUND
Use
Technical Data
External Hierarchy

11.1.6.14 Fund Group
/PBFBI/FUNDGRP
Use
Technical Data
External Hierarchy
11.1.6.15 Fund Node Type
/PBFBI/FU_NODE
Use
Technical Data
External Hierarchy
11.1.6.16 Fund Type
/PBFBI/FUNDTYP

Use
Technical Data
External Hierarchy
11.1.6.17 Funded Program
/PBFBI/FUNDPGM
Use
Technical Data
External Hierarchy
11.1.6.18 Funded Program Node Type
/PBFBI/FP_NODE
Use

Technical Data
External Hierarchy
11.1.6.19 Funds Center
/PBFBI/FUND_CT
Use
Technical Data
External Hierarchy
11.1.6.20 Funds Center Node Type
/PBFBI/FC_NODE
Use
This characteristic displays the funds center node type.
Technical Data
External Hierarchy

11.1.6.21 Grant
/PBFBI/GRANT
Use
Technical Data
External Hierarchy
11.1.6.22 Grant Node Type
/PBFBI/GR_NODE
Use
Technical Data
External Hierarchy
11.1.6.23 Generic Dimension1
/PBFBI/GEN_DIM1

Use
Technical Data
Exchange Available as of Release SAP Public Budget Formulation 1.0 FP03
External Hierarchy
/PBFBI/GEN_DIM2
Use
Technical Data
External Hierarchy
/PBFBI/GEN_DIM3
Use

Technical Data
External Hierarchy
/PBFBI/GEN_DIM4
Use
Technical Data
External Hierarchy
/PBFBI/GEN_DIM5
Use
Technical Data
External Hierarchy

11.1.6.28 Job
/PBFBI/JOB
Use
Technical Data
External Hierarchy
11.1.6.29 Node Type for Derivation
/PBFBI/NODETYP
Use
Technical Data
External Hierarchy
11.1.6.30 Pay Scale Area
/PBFBI/PYSCLAR

Use
Technical Data
External Hierarchy
11.1.6.31 Pay Scale Group
/PBFBI/PYSCLGP
Use
Technical Data
External Hierarchy
11.1.6.32 Pay Scale Group — New
/PBFBI/PYSCNGP
Use

Technical Data
External Hierarchy
11.1.6.33 Pay Scale Level
/PBFBI/PYSCLVL
Use
Technical Data
External Hierarchy
11.1.6.34 Pay Scale Level — New
/PBFBI/PYSCNLV
Use
Technical Data
External Hierarchy

11.1.6.35 Pay Scale Type
/PBFBI/PYSCLTY
Use
Technical Data
External Hierarchy
11.1.6.36 Position
/PBFBI/POSTN
Use
Technical Data
External Hierarchy
11.1.6.37 Ranking Stage
/PBFBI/RSTAGE

Use
Technical Data
External Hierarchy
11.1.6.38 Reporting Job Class
/PBFBI/JOB_CLS
Use
Technical Data
External Hierarchy
11.1.6.39 Value type in Funds Management
/PBFBI/FMVTYPE
Use

Technical Data
External Hierarchy
11.1.6.40 Version
/PBFBI/VERSION
Use
Technical Data
External Hierarchy
11.1.6.41 Wage Type
/PBFBI/WAGETYP
Use
Technical Data
External Hierarchy

11.1.7 Budget Forms
Definition
Use
This InfoArea contains the following InfoAreas:
● Combo Edit Authorization Objects [page 375]

● Ranking [page 380]
11.1.7.1 Combo Edit Authorization Objects
11.1.7.1.1.1 Combo Edit — Node Table
/PBFBI/CE_ON01
Use
This DataStore object is required for the mapping of rule with the hierarchies for all the major dimensions
mapped with the rule.
Key Fields

Data Fields
/PBFBI/FUND Fund
/PBFBI/GRANT Grant
/PBFBI/FCHNAME PBF Fund Centre Node Name
/PBFBI/FUHNAME PBF Fund Node Name
/PBFBI/FPHNAME PBF Funded Program Node Name
/PBFBI/GHNAME PBF Grant Node Name
/PBFBI/FAHNAME PBF Functional Area Node Name
/PBFBI/FA_NODE Functional Area Node Type
/PBFBI/FU_NODE Fund Node Type
/PBFBI/FC_NODE Funds Center Node Type
/PBFBI/FP_NODE Funded Program Node Type
/PBFBI/GR_NODE Grant Node Type
Structure
Delta Update
11.1.7.1.1.2 ComboEdit Leaf Maintenance
/PBFBI/CE_OLF1

Use
This DataStore object is required for the mapping of rule, InfoProvider, and query with the values for all the
major dimensions configured against the rule in the DSO /PBFBI/CE_OH01.
Key Fields
/PBFBI/RULE Flag for Correction
/PBFBI/INFPROV PBF Info Provider for Auth
/PBFBI/QUERY PBF Query Name for Auth
/PBFBI/FUND Fund
/PBFBI/GRANT Grant
0DATETO Valid To
/PBFBI/FLAG Combo Edit Rule for Budget Forms
Structure
Delta Update
11.1.7.1.1.3 Combo Edit Rule <> Form Mapping
/PBFBI/CE_OH02

Use
This DataStore object is required for the mapping of rule with a form name.
Key Fields
/PBFBI/RULE ComboEdit Rule for Budget Forms
Data Fields
/PBFBI/KEY01 Key
Structure
Delta Update
11.1.7.1.1.4 Combo Edit Hierarchy Header Config
/PBFBI/CE_OH01
Use
This DataStore object is required for the mapping of rule with the InfoObject and hierarchy. It also maintains
the value for the default node, level, and level indicator.
Key Fields
/PBFBI/RULE ComboEdit Rule for Budget Forms
/PBFBI/IOBJ PBF InfoObject for Authorization
/PBFBI/HIER PBF Object Hierarchy Name

Data Fields
/PBFBI/HIER1 Hierarchy Value for Budget Form Combo Edit
/PBFBI/LEVEL PBF Hierarchy Level for Auth
/PBFBI/ALLNODE PBF Hierarchy Level - Nodes Below (Auth)
/PBFBI/NODETYP Node Type for Derivation
/PBFBI/HRITND Hierarchy Item Selector
/PBFBI/HRITLVL Hierarchy Item level
Structure
Delta Update
11.1.7.1.2 MultiProviders
11.1.7.1.2.1 Combo Edit Config. Reporting
/PBFBI/CE_M01
Use
This MultiProvider contains the following two DataStore objects:
/PBFBI/CE_OH02 Combo Edit Rule <> Form Mapping [page 377]
/PBFBI/CE_ON01 Combo Edit — Node Table [page 375]

11.1.7.2 Ranking
11.1.7.2.1 Ranking Cube
/PBFBI/RANKING
Use
Characteristics
/PBFBI/VERSION Version
Key Figures
/PBFBI/CURRANK Current Rank
/PBFBI/FUNDFLG Funded Flag for Ranking

11.1.7.3 Budget Form Positions Cube
/PBFBI/HRPJ_R01
Use
Unit
Characteristics
/PBFBI/GRANT Grant
/PBFBI/FUND Fund


sions
/PBFBI/JOB Job

Key Figures
11.1.7.4 Budget Forms
/PBFBI/BF_CUBE
Use
This InfoCube is used in budget forms.

Characteristics
/PBFBI/FMACTDT Detailing of Funding and Actual in Funds Management
/PBFBI/ESGCAP Employee Subgrp Grouping for Collective Agreement Provisions
/PBFBI/FUND Fund
/PBFBI/FUNDED Funding Flag
/PBFBI/GRANT Grant
/PBFBI/JOB Job
/PBFBI/OBJECTV Objective
/PBFBI/TXTGUID PBF GUID for Budget Form Texts

/PBFBI/FMVTYPE Value Type in Funds Manangement
/PBFBI/TRANSID GUIDE for Transaction
/PBFBI/DETELE Deletion Indicator
Key Figures
/PBFBI/ANUALZ1 Annualization

/PBFBI/INITBB1 Initial Base Budget
/PBFBI/NUMPST Number of Positions
/PBFBI/OTADJT1 One Time Adjustment
/PBFBI/PR_RANK Prior Rank
/PBFBI/SALARY1 Salary
/PBFBI/WRKRANK Working Rank
0CALQUART1 Quarter
11.1.7.5 BF Ranking MultiProvider
/PBFBI/BF_RANK

Use
InfoObject InfoCube
/PBFBI/RANKING Ranking Cube [page 380]
11.1.7.6 Audit Trail for /PBFBI/BF_CUBE
/PBFBI/BF_CUBA
Use
Key Fields
/PBFBI/GUID GUID
Data Fields
0USERNAME User Name
0DATE Date
0TIME Time
/PBFBI/FUND Fund
/PBFBI/GRANT Grant

/PBFBI/JOB Job
/PBFBI/_END_DTE End Date
/PBFBI/FMVTYPE Value Type in Funds Management
/PBFBI/FMACTDT Detailing of Funding and Actual in Funds Management
/PBFBI/RANK_ID Ranking ID
/PBFBI/RSTAGE Ranking Stage
/PBFBI/PRF_KPI Performance KPI Measures
0UNIT Unit of Measure

/PBFBI/RANKAM1 Rank Amount

sions
/PBFBI/STPERD Performance Start Period
/PBFBI/STAGE Stage
/PBFBI/RCGUID Reason Change Text GUID

Structure
Delta Update
11.1.7.7 Budget Form Stages
/PBFBI/BFS_O01
Use
This DataStore object maps the stage authorization object and stages with the form ID.
Key Fields
/PBFBI/SAUTH Authorization Object for Stage
Data Fields
/PBFBI/STFRM Status of Form
/PBFBI/BOOL Truth Value
/PBFBI/MA_CALC Budget Form Mass Calculation

Structure
Delta Update
11.1.7.8 Line Item Text GUIDs
/PBFBI/LINETXT
Use
This DataStore Object stores the line item text being entered for every expense and revenue entry of a budget
form ID.
Key Fields
/PBFBI/VCNAME Form Definition/VC Model Name
/PBFBI/BUDG_YR Budget Year
/PBFBI/GRANT Grant
/PBFBI/FUND Fund
Data Fields

/PBFBI/TXTGUID GUID for budget form texts
Structure
Delta Update
11.1.8 Budget Development Objects
Budget Development Objects
11.1.8.1 MultiProviders
11.1.8.1.1 MultiProvider for Budget without Positions
/PBFBI/SL_M01
Use
/PBFBI/SL_C02 Annualized Aggregated Projection Scenario Data [page 394]

/PBFBI/SL_C01 Budget Forms: Actual/Previous Year Budget [page 396]
/PBFBI/SL_C03 Budget Forms Historical: Preivous Year Budget Data [page

399]
11.1.8.1.2 MultiProvider for Budget Development Content
/PBFBI/SL_M02
Use
The MultiProvider contains the following two infocubes:
/PBFBI/RANKING Ranking Cube [page 380]
11.1.8.1.3 Ranking MultiProvider for Budget Development
/PBFBI/SL_RANK
Use
The MultiProvider contains the following InfoCubes:
/PBFBI/BF_CUBE Budget Forms [Page 280]
/PBFBI/RANKING Ranking Cube [Page 277]

11.1.8.2 InfoCubes for Budget Development
11.1.8.2.1 Annualized Aggregated Projection Scenario Data
/PBFBI/SL_C02
Use
Characteristics
/PBFBI/GRANT Grant
/PBFBI/FUND Fund
/PBFBI/VCNAME Form Definition / VC Model name
/PBFBI/JOB Job
/PBFBI/END_DTE End Period

/PBFBI/ST_DATE Start Period

sions
/PBFBI/FMACTDT Detailing of Commitment and Actual in Funds Management
/PBFBI/FMVTYPE Value type in Funds Management
Key Figures

/PBFBI/FM_AMT1 Amount in FM area currency
0FISCPER3 Posting period
0CALQUART1 Quarter
11.1.8.2.2 Budget Forms: Actual/Previous Year Budget
/PBFBI/SL_C01

Use
Characteristics
/PBFBI/GRANT Grant
/PBFBI/FUND Fund
/PBFBI/JOB Job


sions
Key Figures

0CALQUART1 Quarter
11.1.8.2.3 Budget Forms Historical: Preivous Year Budget

Data
/PBFBI/SL_C03
Use
Characteristics

/PBFBI/GRANT Grant
/PBFBI/FUND Fund
/PBFBI/JOB Job

sions

Key Figures

Time Characteristices
0CALQUART1 Quarter
11.1.8.2.4 Resource Planning Forms
/PBFBI/RP_CUBE
Use
Characteristics
/PBFBI/GRANT Grant

/PBFBI/FUND Fund
/PBFBI/JOB Job
/PBFBI/RT_TYPE Rate Type

/PBFBI/ACTYPE PBF Activity Type
/PBFBI/ACT_GRP Activity Pricing Group
/PBFBI/CMD_TY PBF Commodity
/PBFBI/CMDTYP PBF Commodity Type
/PBFBI/CMDPI PBF Price Indicator
/PBFBI/LOCN PBF Commodity Location
Key Figures
/PBFBI/QTY PBF Quantity
/PBFBI/NUMDYS Number of Days
0CALQUART1 Quarter
11.1.8.3 DSOs for Budget Development

11.1.8.3.1 Committment Item — Commodity Mapping
/PBFBI/BFCITEM
Use
This DataStore object is used for the mapping of commodity and commitment item.
Key Fields
/PBFBI/COMDTY Commodity
Structure
Delta Update
11.1.8.3.2 Commodity Rate Maintenance
/PBFBI/CM_RATE
Use
Key Fields
/PBFBI/LOCN PBF Commodity Location
/PBFBI/COMDTY Commodity

/PBFBI/CMDPI PBF Price Indicator
/PBFBI/CMD_TY PBF Commodity
Data Fields
/PBFBI/PRICE PBF Unit Price
/PBFBI/MD_CURR Master Data Currency
Structure
Delta Update
11.1.8.3.3 Forms: Budget Type
/PBFBI/SL_O04
Use
Key Fields

Data Fields
/PBFBI/BUDGTYP Budget Type
Structure
Delta Update
11.1.8.3.4 Multi-Year Projection Inflaitonary Rate
/PBFBI/SL_O05
Use
Key Fields

Data Fields
/PBFBI/DIS_PCT Distribution Percentage
Structure
Delta Update
11.1.8.3.5 PBF Activity Price Maintenance DSO
/PBFBI/SL_RTE
Use
Key Fields
/PBFBI/ACT_GRP Activity Pricing Group
/PBFBI/ACTYPE PBF Activity Type
Data Fields

Structure
Delta Update
11.1.8.3.6 PBF Value Types
/PBFBI/SL_O01
Use
Key Fields

Data Fields
Structure
Delta Update
11.1.8.3.7 Resource Planning Rate Type
/PBFBI/RP_O01
Use
Key Fields
/PBFBI/RT_TYPE Rate Type
/PBFBI/JOB Job /PBFBI/JOB NUMC 08 /PBFBI/JOB
/PBFBI/POSTN Position /PBFBI/POSTN NUMC 08 /PBFBI/POSTN
Data Fields

Structure
Delta Update

Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:
● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.
Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.
Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.

412 INTERNAL Important Disclaimers and Legal Information
Important Disclaimers and Legal Information INTERNAL 413
www.sap.com/contactsap
© 2020 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.
Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.
THE BEST RUN

SAP Budgeting and Planning For Public Sector

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP Budgeting and Planning For Public Sector

Uploaded by

Copyright:

Available Formats

USER GUIDE | INTERNAL

Document Version: 1.0 – 2020-06-12

SAP Budgeting and Planning for Public Sector

THE BEST RUN

1 SAP Budgeting and Planning for Public Sector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

SAP Budgeting and Planning for Public Sector

6 Personnel Expenditure Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

7 Additional Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106

8 SAP Budgeting and Planning for Public Sector Administration. . . . . . . . . . . . . . . . . . . . . . . . 109

SAP Budgeting and Planning for Public Sector

SAP Budgeting and Planning for Public Sector

Product SAP Budgeting and Planning for Public Sector

Release 1.0 FP03

Based On SAP NetWeaver 7.4

Documentation Published July 2017

SAP Budgeting and Planning for Public Sector

1. Master Data Maintenance [page 109]

SAP Budgeting and Planning for Public Sector

SAP Budgeting and Planning for Public Sector

Personal expenditure projection (PEP) scenarios with budget form positions

Function Type of Chnage Description

SAP Budgeting and Planning for Public Sector

Function Type Description

Optional workflow settings New The Form Designer configuration tool

Mass form delete utility

Function Type Description

SAP Budgeting and Planning for Public Sector

Function Type Description

SAP Budgeting and Planning for Public Sector

● Creating Form Templates [page 12]

3.1 Connecting to Budgeting and Planning for Public

SAP Budgeting and Planning for Public Sector

● Creating Forms [page 12]

3.2 Creating Forms

SAP Budgeting and Planning for Public Sector

SAP Budgeting and Planning for Public Sector

Sheet Type Details

Funding For the entire sheet:

○ Set the Number of Layout-Columns field to specify the number of lay­

SAP Budgeting and Planning for Public Sector

For the entire sheet:

○ Set the Number of Layout-Columns field to specify the number of lay­

Label The name of the group.

Tooltip This sets the tooltip of the group

SAP Budgeting and Planning for Public Sector

Load Status True If a Group needs to be visible

False If a Group needs to be visible

All Group will always be visible.

Edit Status True If a Group needs to be visible

False If a group needs to be visible

All If a Group needs to visible al­

Sheet Name This dropdown becomes visible only when “UserDefined” or

Label Label: This sets the name of the button created.

Image This sets the icon of the button.

See Group Configuration, above, for detailed information on these properties.

SAP Budgeting and Planning for Public Sector

SAP Budgeting and Planning for Public Sector

3.3 Using Forms

3. In the Open Document dialog that appears:

Query A worksheet that displays the results of a given query.

SAP Budgeting and Planning for Public Sector

6. At any time after you have loaded a form, you can:

○ Set the Number of Layout-Columns field to specify the number of lay

○ Set the Number of Layout-Columns field to specify the number of lay

All If a Group needs to visible al

Info Object /PBFBI/FRM_TYP FI Form type for Resource Plan

Info Object /PBFBI/VCNAME DP2009 Form Name Resource Plan

/PBFBI/UPDATE_FORM_DESCRIP Form Header Updates the form description for a given