BPC Embebido PDF

PUBLIC
SAP Business Planning and Consolidation, version for SAP BW/4HANA

Document Version: 11.0 SPS03 – 2017-07-31
Application Help - SAP Business Planning and

Consolidation, version for SAP BW/4HANA
(Embedded configuration)
© 2018 SAP SE or an SAP affiliate company. All rights reserved.
THE BEST RUN

Content
1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.1 Preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2 Change Company Logo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.3 Grid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
2.4 Favorites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.5 Home Page and Navigation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3 Business Process Flows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

3.1 My Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4 Process Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
5 Run Consolidation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

5.1 Consolidation Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Run a Currency Translation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Run a Consolidation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Working with Periodic Consolidations and Currency Translations. . . . . . . . . . . . . . . . . . . . . . . . 21
5.2 Controls Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Execute a Control Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Control Set Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.3 Journals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Journal Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Journal Entry Form. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Journal Postings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Journal Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Journal Queries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Reopen Journal Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Print Journal Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.4 Ownership Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Create Ownership-based Hierarchies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
6 System Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.1 Reporting on Business Process Flows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
6.2 Reporting on Data Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
6.3 Reporting on Work Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
7 Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
2 PUBLIC Content
7.1 Environment Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
New Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
7.2 Dimension Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Dimension Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Dimension Member Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Dimension Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Hierarchy Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Dimension Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Creating Local Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
7.3 Model Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Planning and Consolidation Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
Working with Local Providers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
7.4 Consolidation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
Create an Embedded Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Set up a Consolidation Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Set Task Sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Preparations for Executing Consolidation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Load Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
7.5 Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Business Rules Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Controls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
7.6 Business Process Flow Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Creating New Process Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Creating Process Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Setup of E-mail Notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
External Process Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
7.7 Work Status Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
7.8 Journal Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Journal Template Creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Delete All Journal Entries from Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Limits to Dimension Members for Journal Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
BAdI for Generating Calculated Amounts When Saving a Journal. . . . . . . . . . . . . . . . . . . . . . . 145
7.9 Auditing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Data Auditing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
7.10 Supported BAdIs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149
7.11 Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
User Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Integration into Single Sign-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151
Setting Up Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Setting Up Teams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Role Assignment Based on Authorization Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Content PUBLIC 3
Data Access Profile Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
4 PUBLIC Content
1 Overview
Application help for an embedded configuration of SAP Business Planning and Consolidation, version for SAP
BW/4HANA.
Product Information
SAP Business Planning and Consolidation provides everything you need to meet your bottom-up and top-down
financial and operational planning requirements through a single application and user interface.
SAP Business Planning and Consolidation 11.0, version for SAP BW/4HANA is a new product based on SAP
BW/4HANA. The product supports the HANA database and uses SAPUI5 user interface technology. The SAP
UI5 user interface is based on standard HTML5, which provides all the benefits of HTML5 and supports
languages such as Hebrew and Arabic that are written and read from right to left. BW/4HANA is a new, next-
generation data warehouse product that is optimized for the SAP HANA platform, delivering real-time,
enterprise-wide analytics that minimizes the movement of data and connecting all the data in an organization
into a single logical view.
SAP Business Planning and Consolidation 11.0, version for BW/4HANA also introduces the new SAP Belize user
interface that has a clean and consistent layout. Belize is the refined SAP Fiori visual language whose calm
color tones help users stay focused on daily business tasks and content. With delightful visual details and
typography, Belize conveys content with clarity and makes the user experience richer.
Administrators can configure the installation of SAP Business Planning and Consolidation in one of two ways:
● In an embedded configuration, Business Planning and Consolidation is integrated with SAP HANA-
optimized processing, through which you can perform SAP HANA-optimized planning. For details about
SAP HANA-optimized processing and the BW planning processor, refer to Planning Concepts.
● In a standard configuration, you can use all the functionality that is available in the standard configuration
of SAP Business Planning and Consolidation, version for SAP NetWeaver.
 Note
Information within a single topic that differs between the configuration types is clearly explained within the
relevant content.
Integration
HTML5-based web client
The HTML5-based web client offers an integrated view for both business users and administrative users.
Overview PUBLIC 5
SAP BusinessObjects Analysis, Edition for Microsoft Office
There is a separate installation for business users who are power users - the SAP BusinessObjects Analysis,
Edition for Microsoft Office. For more information, see the SAP BusinessObjects Analysis, Edition for Microsoft
Office help available on the SAP Help Portal.
SAP Analytics Cloud

SAP Analytics Cloud is an all-in-one analytics platform for organizational planning, predictive analytics, and
visualized business intelligence. Now the data integration between SAP Analytics Cloud and SAP BPC has been
enhanced: models of periodic storage type can be consumed by SAP Analytics Cloud in write-back mode with
significantly enhanced performance.
 Recommendation
We recommend that you keep the SAP Analytics Cloud model based on BPC as small as possible by
filtering in the mapping screen and synchronize frequently with your BPC data source. If you want to import
BPC delta data into SAP Analytics Cloud all at once, we recommend that you keep the data volume to less
than 1.5 GB and the number of records to less than 450,000.
Features
Security
The Security Guide provides thorough security-relevant information for this release of Business Planning and
Consolidation. The guide is available on the SAP Help Portal.
Starting the Web Client
To start the Planning and Consolidation Web Client, do the following:
Open a browser and connect to the URL http://<PC_server:port>/sap/epm/bpc/web/, where

<PC_server:port> is the server name or IP address and port number of the Business Planning and
Consolidation application location.
To log on directly to a specific environment, enter http://<PC_server:port>/sap/epm/bpc/web/

#<environment type>/<environment ID>, where <environment type> is pak for Business Planning
and Consolidation environments in an embedded configuration..
 Note
Logging on directly to an environment works only when the authentication is done automatically. For
example, the direct log on works when you have a logon ticket that was issued during a previous log on.
6 PUBLIC Overview
2 Getting Started
The following features are available to help you get started using SAP Business Planning and Consolidation:
● You can change the user preferences to customize the display of your UI. See Preferences [page 7].
● You can replace the SAP logo with your company logo, See Change Company Logo [page 8].
● You can change the way data displays in table format on various pages within the application. See Grid
[page 8].
● You can customize your own home page and navigation to different functions through the main navigation
panel. See Home Page and Navigation [page 9].
2.1 Preferences
You can change user preferences to customize the display of your user interface. You can make changes to the
language, date format, and others settings.
You can change the following settings:
My Preferences
Feature Description
Theme The theme that you want to use for the application UI
Language The language in which you want the UI texts to appear
Time The time zone that you want to use in the application
Date Format The format in which the date appears
Number Format The format in which the numbers appear
Name Format The format in which the logged in user's name appears
You can also upload a photo to customize your profile.
Activities
To view and edit user preferences, in the upper right part of the screen, click your user name and choose
Preferences.
● To change the settings, choose Save.

● To restore the original settings, choose Restore Default.
 Note
Your changes will take effect upon your next logon. If you want to apply the changes immediately, you must
restart the application.
Getting Started PUBLIC 7
2.2 Change Company Logo
You can replace the SAP logo in the upper left corner of Business Planng and Consolidation with your company
logo.
To replace the SAP logo with your company logo, follow these steps:
1. Enter transaction code se38.

2. Execute program RSBPC_CUSTOM_LOGO.
3. In the company logo field, upload the picture of your company’s logo. The default SAP logo is 50*26. We
recommend you use a png file and limit the image size to 32*32.
4. In the product name field, enter the name of your company.
To directly change your company logo back to the default SAP logo, follow these steps:
1. Enter transaction code se38 and execute program RSBPC_CUSTOM_LOGO

2. Select the option Clear Values and choose Execute.
2.3 Grid
A grid is a table that displays data and allows you to alter the display of that data.
● Where available, you can filter the data displayed in a table. Click the column header tab and then in the
drop down list enter a value in the Filter field.
By entering a specific value, you can narrow the data displayed to include only the ones with that value.
● Display or hide certain columns using the (View Settings) button in the upper right corner of a table,
where available.
All columns are displayed by default. To hide a particular column, deselect the checkbox for that column.
● Sort the data in the table according to a particular column by clicking the column header tab.
In the drop down list, the data can be sorted in ascending or descending order.
2.4 Favorites
You can add any important pages you want to bookmark to Favorites.
To reserve a page as favorites, click the button to the upper right corner of corresponding page
and name it as you wish. Then the pages marked as favorites are displayed in the Favorites tile in the home
page.
If you want to edit these favorite pages, click the Edit Favorites button in the Favorites tile, or go to the
navigation panel by clicking and choose Favorites to enter the Favorite editing page. On this page, you can
change the sequence of the pages or remove any pages from the favorite list.
8 PUBLIC Getting Started
Related Information
Home Page and Navigation [page 9]
2.5 Home Page and Navigation
When you log in to the web client of Business Planning and Consolidation, you can use the main navigation
panel on the left side to navigate to the functionality that you want to access.
The main navigation panel is composed of the following categories:
● Home - Displays your favorite pages and snapshots of charts, and reminds you of the activities
approaching a deadline. For more information, see the Home Page section below.
● My Activities - Displays the activities requiring action by you as the currently logged-on user. For more
information, see My Activities [page 12].
● Process Monitor - Displays a complete list of the process instances for you as the process owner of
corresponding process templates to monitor. See Process Monitor [page 14].
● Consolidation - Provides information about generating and managing consolidated data to give you an
accurate view of the financial situation of your organization. See Run Consolidation [page 15].
● Administration - Enables administrators to perform setup and maintenance tasks for Business Planning
and Consolidation. See Administration [page 49].
● System Reports - Provides information about reporting on system information and activity. See System
Reports [page 44].
Home Page
You can navigate to home page from the main navigation panel. The home page is composed of the following
tiles:
Favorites - provides direct links to specific Business Planning and Consolidation web pages that you
bookmarked as favorites.
Timeline - provides the activities requiring action by you as the currently logged-on user in deadline order
Charts - provides a snapshot of charts that you pinned to the home page
Navigation
This release of Business Planning and Consolidation is a single page application. You can jump to a certain page
in two ways:
● From the main navigation panel – To jump to a new page, click the icon from the upper left corner and
choose a page.
Getting Started PUBLIC 9
● From the breadcrumb bar – The navigation path in the breadcrumb bar indicates the position of a page in
the application. By clicking the Drill Down button, you can jump to other relevant pages at the same level.
To go back to the previous page, we recommend you use the button inside the application other than the
back button on your web browser as we make some customized enhancement to the back button inside the
application.
Changing the Environment
Click the button from the upper right corner of the screen and your current environment displays. Click on
the environment name to change to another environment. For detailed information, refer to Environment
Management [page 49].
Context Sensitive Help
You can view help for each feature directly from BPC web client instead of searching it on SAP Help Portal. To
open a context sensitive help, click the button from the upper right corner of each page and choose About
This Feature.
Setting Preferences
To set individual preferences, click on your name in the upper right corner of the screen and choose
Preferences. For more information, see Preferences [page 7].
10 PUBLIC Getting Started
3 Business Process Flows
Business process flows (BPFs) guide you through a sequence of tasks within a defined business process.
Depending on your role, the activities available to you can involve completing actions as an activity performer
or reviewing actions submitted by other users as an activity reviewer.
Features
A process instance, or simply a process, is an iteration of a process template that is in active use. For example,
an authorized administrative user creates a process template called “Monthly Reporting” to coordinate the
monthly reporting activities of various personnel. Then that user or another authorized user can create a
process for a specific period such as November 2009 based on the “Monthly Reporting” template.
As a business user, you can utilize the following features related to business processes:
● Activities
Activities list the processes that you as the currently logged on user can access to perform or review
actions.
For more information, see My Activities [page 12].
● Process Monitor
Process monitor displays a complete list of the processes that you as the process owner of corresponding
process templates can access. If meanwhile you are the owner of the process instances, you can also
finalize them once they have been completed.
For more information, see Process Monitor [page 14].
● E-mail notifications
The system automatically generates e-mail notifications to the people who are involved in a process or
activity to keep them informed of its progress and of tasks that need to be performed. The e-mail
notifications automatically sent to users contain a link to bring them directly to the activity or process
monitor, or to navigate to external applications to perform further actions.
E-mail notifications occur in the following situations:
○ Process monitors are the users who can monitor all the instances created from a process template.
Process monitors receive an e-mail notification when a new process instance is:
○ Created
○ Suspended
○ Resumed
○ Reset
○ Ready to be finalized
○ The owner of an activity receives an e-mail notification when the activity is:
○ Opened to be performed
○ Approved or rejected by a reviewer
○ Reopened
○ When a deadline is changed
○ The responsible reviewer of an activity receives an e-mail notification when an activity is ready for
review or when a deadline is changed.
Business Process Flows PUBLIC 11
For information on how system administrators configure e-mail notifications, see Setup of E-mail Notifications
[page 131].
3.1 My Activities
My Activities displays the activities requiring action by you as the currently logged-on user. The actions might
include performing activities assigned to you or reviewing activities submitted by others.
Features
By clicking an activity, you can open the associated activity workspace to perform or review your activity. The
activity workspace contains hyperlinks to begin executing your tasks.
Before any action is taken, activities can have the following statuses:
● Open-To perform: The new activity is waiting for completion or to be submitted.

● Pending: The activity is waiting for another activity to be completed. You cannot take any action on a
pending activity.
Activities that need to be reviewed after submission can have the following statuses:
● Submitted: Action has been taken and the activity is waiting for review.
● Rejected: A reviewer has rejected the activity and the activity is open again to be performed.
● Completed: The activity is approved and fully completed.
If no review action is required, a performer can directly change the status to Completed after taking all the
required actions.
An activity can be reopened for performing actions once again after it has been completed. Activities that are
reopened can have the following statuses:
● Reopened: The completed activity has been reopened.

● Delayed: Completion of the activity has been delayed due to the previous activity being reopened. It is not
possible to take any action on a delayed activity.
The performer of an activity is the person responsible for completing the activity. A reviewer is the person who
must verify the actions taken by a performer in a particular activity context. Performers and reviewers can be
one or more users or a team. For multiple users to be involved in the completion of an activity simultaneously,
two or more users can concurrently work at the same activity.
Activities
The left side of the My Activities view displays all the processes whose activities require your action. The
activities you see are those for which you are a performer or a reviewer.
12 PUBLIC Business Process Flows
In the upper portion of the panel, you can choose to display finalized or active processes, or display processes
by ID, description, or both. The search box in the upper right corner supports cross-column searching, which
means anything in the page that matches your input will be displayed and highlighted.
Using (View Settings), you can choose the columns to display for all activities, as well as sort and group
activities on your own, which enables you to manage activities in a more organized way.
Numbers such as in each process show the total number of open activities that require you as the current
reviewer or performer to take actions in this process. Click See more to view the detailed activity numbers for
each status.
Performing or Reviewing Activities
Choose a process and the Details window displays all the activities of that process requiring your action. Then,
if you the assigned performer of an activity, you can click the activity names to open the activity workspace
where you perform any required tasks. When you have completed the required actions, choose Complete in the
activity workspace. The status in the My Activities view automatically updates; if any further reviews are
required, the status will change to Submitted. Otherwise, the activity status will be directly changed to
Completed.
You can enter and review comments when changing the status of a BPF activity.
If you are the assigned reviewer of an activity, you can approve or reject the activity. Approve changes the
status of the activity to Completed. Reject changes the status of the activity to Rejected and the responsible
user may resubmit the activity for approval.
Reopening Activities
You can reopen a completed activity or specific activities for which reopening criteria have been met. For more
information, see Criteria for Reopening Activities [page 124]. If you are a process instance owner, you can
reopen activities of the processes you own without any limitations. To reopen an activity, go to the process
instance and click See more. Then choose the Reopen button to select activities.
Work Status Integration
Work status is a very commonly used feature within Business Planning and Consolidation for planning process
control. The state of work status can be automatically changed with the changing of BPF activity status if the
integration of work status with BPF has been set up by an administrator. For example, if the administrator
defined for a certain data region that when the activity is completed the work state of this region will be
automatically changed to Locked, then once you as the activity performer submits a region of planning data in
an activity and changes the status of the activity to Complete, the pertinent data region by work status is
automatically locked.
Business Process Flows PUBLIC 13
4 Process Monitor
Use
Process monitor displays a complete list of the process instances that you as the process owner of
corresponding process templates can access. In the process monitor, you can see a complete list of processes
and display the full set of information available for individual process instances. The process instance owner
can finalize a completed process instance.
Prerequisites
Process Monitor does not display by default. To view the process monitor, you must have been assigned access
as a process owner during process template creation.
Features
When you open the process monitor, it displays the process name, process context, status (completion
progress, number of activities completed, in progress, pending), start date, and owners for each process
instance. You can filter the processes choosing Process and All. By choosing Process, you can display processes
by process templates. By choosing All, you can choose to display either active processes, which are processes
not yet finalized. or finalized processes.
When you click the name of a process from the list, a detailed view is displayed in which you can see the status
of activities in the process instance. You can view them using Group By to group by activity, context, status, and
action required. You can also filter using Show Activities.
The detailed view shows the performer deadline and reviewer deadline for the activities. In case a planning
cycle needs to be adjusted due to special circumstances, a process template owner can change deadlines for
uncompleted activities by choosing Change Deadlines. In the detailed view, the process instance owner can
also choose to reopen completed activities by choosing Reopen without any limitations.
Only the process instance owner can finalize a completed process instance from the process monitor.
14 PUBLIC Process Monitor
5 Run Consolidation
The Consolidation module in SAP Business Planning and Consolidation enables you to generate and manage
consolidated data, giving you an accurate view of the status of the collected and consolidated data within your
organization as well as a unified environment to perform consolidation tasks over the web.
Features
The following Consolidation features are available:
● Consolidation Monitor: generate and monitor consolidated data from data reported by Group and Entity
members
● Controls Monitor: execute and monitor controls used to validate the reported data
● Journals: create and manage journal entries containing adjustments used for correcting collected and
consolidated data
● Ownership Manager: create and manage ownership-based hierarchies used for performing statutory
consolidations
Related Information
Consolidation Monitor [page 15]

Controls Monitor [page 22]
Journals [page 28]
Ownership Manager [page 39]
5.1 Consolidation Monitor
The Consolidation Monitor is a global dashboard for monitoring the consolidation progress of a specific
consolidation scope, which is made up of a category, period, group, or sub-group.
The Consolidation Monitor is a key component in executing consolidations since it communicates to the
consolidation engine about the entities on which to execute business rules. For more information about setting
up your consolidation environment with dimension properties, model settings, and journal definitions, see
Consolidation [page 64].
The Consolidation Monitor displays the Group/Entity hierarchy created in the Ownership Manager (only
Consolidation type models). For information on configuring an ownership-based hierarchy, see Ownership
Manager [page 39].
Run Consolidation PUBLIC 15
The scope context area displays the selected dimension members: Time (T-type), Category (C-type) and
Group (G-type).
Prerequisites
An administrator has assigned relevant authorization objects to you for managing Consolidation Monitor and
executing business rules. To perform control type tasks, you also need to be assigned the relevant
authorization objects. For detailed information about how to assign the authorization objects, see the topic
“Authorization for Performing Consolidation Tasks” in the Security Guide available on the SAP Help Portal.
Before running relevant business rule tasks, corresponding dimensions and attributes must be maintained by
your administrator. For detailed information, see Business Rules Management [page 83].
Since Consolidation Monitor is the central place to trigger tasks defined by certain business rules on different
consolidation models, before you perform any tasks in Consolidation Monitor, your administrator is expected
to have defined business rule types for the consolidation model in Rules Business Rules and chosen the
tasks to be run on the model in Rules Task Sequences . For detailed information, refer to Business Rules
Management [page 83] and Set Task Sequence [page 80].
Features
In the Consolidation Monitor you can do the following:
● Execute consolidation tasks

The types of business rules you can execute in Consolidation Monitor include:
○ Run Currency Translation
○ Account-Based Calculation
○ Intercompany Booking
○ Carry Forward
○ Elimination and Adjustment
○ US Elimination
○ Change work status
○ Run control
For more information, see Run a Consolidation [page 18].
You can trigger any of these tasks based on your business needs. The task status for business rules is by
default To Be Executed. After you execute a task, the status will change to Running and automatically
turned into Done orFailed upon the completion of the task. If the task is not valid, the status will display the
icon of Not Applicable.
● Display the running processes
All the processes for business rule type tasks can be viewed through Display Running Process. You can
display processes only for groups to which you have Read access.
● Reset the consolidation status
You can reset a Done or Failed status of a business rule type task to To Be Executed, in which case you
would then need to run a full consolidation. If an administrator enables task dependency when defining
task sequences, all the consolidation tasks after that task also need to be re-executed.
16 PUBLIC Run Consolidation
Activities
1. In Consolidation Consolidation Monitor , select corresponding dimension members for dimensions in

the scope context area.
2. Choose the task and the entity/group on which you want to run consolidation and click the Execute button.
 Example
If you want to run currency translation on Entity 1, you first select the intersection cell of the Currency
Translation task type and Entity 1 and then click Execute on the tool bar.
Related Information
Run a Consolidation [page 18]
5.1.1 Run a Currency Translation
You can convert amounts from their source currency to a target currency.
Available currencies are those specified in the Group dimension or group members. Currency translation can
be executed at any group/entity level. When you select a base entity and run the currency translation for this
entity, you can select the reporting currency in which to run the translation and convert amounts from their
source currency to a target currency. When you select a group or sub-group, the currency translation is run on
the currencies defined for the selected group.
You perform currency translations in the Consolidation Central module of SAP Business Planning and
Consolidation.
Prerequisites
You can perform currency translation on an entity if you have Write access to this entity.
Features
If you execute currency translation on an entity, a currency conversion dialogue boc appears with the following
dimension types and corresponding default members:
● C – Category
Default member: category member on the context bar.
● T – Time periods
Default member: time period on the context bar.
● E – Entity
Default member: the selected entity
● R – Currency
Default member: the first member in the currency dimension of the CONSOLIDATION InfoProvider.
● Currency Rate Entities
Default member: Global. If Global is not defined, then the first member of Entity in the RATE InfoProvider
displays.
You should be able to select multiple entities, currencies and time periods.
After defining all the members for these dimension types, click OK and execute a currency translation by
following the steps in Consolidation Monitor [page 15].
If you execute currency translation on a group, then a currency conversion dialogue appears with the following
● C – Category
Default member: category member on the context bar.
Default member: time period on the context bar.
● G – Group
Default member: the selected group
● Currency Rate Entities
Default member: Global. If Global is not defined, then the first member of Entity in the RATE InfoProvider
displays.
You should be able to select multiple time periods.
After defining all the members for these dimension types, click OK and execute a currency translation by
Related Information
Currency Translation Rule [page 85]
5.1.2 Run a Consolidation
You run consolidations in the Consolidation Central module of SAP Business Planning and Consolidation.
Prerequisites
An administrator has assigned relevant authorization objects to you to manage a consolidation and execute
business rules in Consolidation Monitor. For detailed information about how to assign the authorization
objects, refer to the topic “Authorization for Performing Consolidation Tasks” in the Security Guide available on
the SAP Help Portal.
You can run a consolidation at a group level if you have Write access to the group.
Activities
Execute Carry Forward
If you execute carry forward on an entity, then a carry forward dialogue box appears with the following
● C – Category
Default member: category member on the context bar
Default member: time period on the context bar
● E – Entity
● R – Currency
Default member: group currency on the context bar
You should be able to select multiple currencies. In this case, carry forward the selected entity with the selected
currency and local currency.
If you execute carry forward on a group, then a carry forward dialogue box appears with the following
● C – Category
● G – Group
You can change to other groups. In this case, carry forward entities belong to the new group with the group
currency and local currency.
After defining all the members for these dimension types, click OK and execute currency translation by
Execute Account-Based Calculation
If you execute account-based calculation on an entity, then an Account-Based Calculation dialogue box
appears with the following dimension types and corresponding default members:
● C – Category
● E – Entity
● R – Currency
You should be able to select multiple entities and currencies. In this case, carry forward the selected entity with
the selected currency and local currency.
If you execute account-based calculation on a group, then an Account-Based Calculation dialogue box appears
with the following dimension types and corresponding default members:
● C – Category
● G – Group
You can change to other groups. In this case, account calculation is performed on entities belonging to the
selected group and the selected group currency.
Execute Intercompany Booking
If you execute intercompany booking on an entity, then an Intercompany Booking dialogue box appears with
the following dimension types and corresponding default members:
● C – Category
● E – Entity
● R – Currency
You should be able to select multiple entity members and currencies. In this case, intercompany booking is
performed on the selected dimension and selected currency.
If you execute intercompany booking on a group, then an Intercompany Booking dialogue box appears with the
following dimension types and corresponding default members:
● C – Category
● G – Group
You can change to other groups. In this case, intercompany booking is performed on entities belonging to the
selected group and the selected group currency.
Execute Elimination and Adjustment
If you execute elimination and adjustment on an entity, then an Elimination and Adjustment dialogue box
● C – Category
● G – Group
Default member: the direct group of the selected entity
You should be able to select multiple time period members.
If you execute elimination and adjustment on a group, then an Elimination and Adjustment dialogue box
● C – Category
● G – Group
You should be able to select multiple time periods and multiple group members.
Change Work Status and Run Controls
Click on the intersection cell of the task type and the entity or group for which you want to change the work
status or run controls, and choose the Execute button. You can then change the work status to the desired work
status or run a control for an entity or for a group along with all entity members under that group.
For rules about changing work statuses and executing controls, refer to Work Status Setup [page 135] and
Create a Control [page 103].
Related Information
Account-based Calculation Rule [page 85]

Intercompany Booking Rule [page 90]
Carry-Forward Rule [page 91]
Eliminations and Adjustments Rule for Legal Consolidation [page 94]
5.1.3 Working with Periodic Consolidations and Currency

Translations
When you modify data during an accounting period that occurs prior to the period for which a consolidation is
requested, it may be necessary to reconsolidate future periods. In this case, you must verify that periodic
currency translation and consolidation rules exist and confirm whether or not data from prior periods was
modified.
This verification must be done manually, by reconsolidating every period consecutively in full consolidation
mode.
Related Information
Run a Consolidation [page 18]
5.2 Controls Monitor
The Controls Monitor enables you to execute and monitor controls.
Use
Controls are run on a selected entity or group of entities. If you select a Group, you can run the controls for all
the aggregated entities belonging to this Group. Controls are executed in the order in which they appear in the
control set.
The Controls Monitor displays the Group/Entity structure based on the hierarchy created in the Ownership
Manager (only Consolidation type models). For information on configuring an ownership-based hierarchy, see
Ownership Manager [page 39].
The Controls Monitor is split into the following areas:
● At the top, the scope context area displays the dimensions selected as the Controls context.
To modify the dimension members displayed in the scope context area, click the linked members to display
the Member Selector dialog box.
● In the middle, a list of control sets organized by entity, displaying the control status and the number of
blocking or warning controls
In a Consolidation model, only the entities belonging to the Group selected in the scope context area are
displayed.
● At the bottom, a list displaying details on failed controls for the entity previously selected in the control set
list.
Each time you select a different entity in the control set list, the list of failed controls is refreshed.
Prerequisites
An administrator has assigned relevant authorization objects to you to view and execute controls in Control
Monitor. For detailed information about how to assign the authorization objects, refer to the topic
“Authorization for Performing Consolidation Tasks” in the Security Guide.
Controls are enabled for the model in Planning and Consolidation Administration. If you choose Derive from
Work Status, you also need to make sure work status settings have been configured.
Features
Run controls
Run controls for the selected entity or group. Control results are displayed in the Controls Monitor page. You
can run controls from the main Controls Monitor page, or from the controls results page for a selected entity.
Display details on failed controls
When you select an entity or the group on which you have run controls, a summary of failed controls is
displayed in the Details on Failed Controls list in the Controls Monitor page.
Sort columns
You can sort the columns alphabetically in the list in the Controls Monitor page by clicking on the column
header. A triangle appears, indicating the direction of the sort. Clicking the column header a second time
changes the direction of the alphabetical sort.
Show descriptions
By default, only the entity code is displayed in the Controls list. You can display the entity descriptions by
selecting the Show Description option.
Display controls results for one or more entities
You can display for an entity or for the group the control status of each control in the control set using the
Controls Results option in the Controls Monitor page. In the Controls Results page, you can do the following:
● Expand a control with one or more breakdown dimensions.

The status and data for each breakdown dimension member is displayed.
● Filter the list of controls displayed using the Show dropdown list.
Available filters include All, Passed, To be executed, Failed, and Dismissed.
● Dismiss or reset blocking controls
If you have the appropriate access right, from the Controls Results page, you can dismiss a blocking control
when the control status is Failed, thereby changing its status to Dismissed. This gives you the ability to
update the work status - allowing data to be validated in the workflow - even when a blocking control
produces an error when executed.
 Example
For instance, the definition of a blocking control specifies that the same amount for depreciation of
buildings be entered in a specific Balance Sheet account/flow and in a specific P& L account. If the
amount is not entered in the corresponding account in the balance sheet, because of your
organization's accounting procedures, the blocking control returns a status of Failed after execution.
You can then dismiss the blocking control so that the data can be validated in the workflow.
You can reset the status of the blocking control to Failed if it is determined that the original control status
should be kept. For more information on control types, see Create a Control [page 103]; for more information
on control status, see Control Set Status [page 25].
Refresh the controls page
You can refresh the list of controls by clicking Refresh. For example, if data entry was just performed, you can
refresh the page to take into account the updated status.
You can perform a refresh of the main Controls Monitor page, as well as of the controls results page for a
selected entity or group of entities.
When you enable control for a model, you can decide whether the context of the control monitor should be
derived from the work status or set manually.
You can also set the context of the control monitor on the parent node level.
Activities
● To run controls for the selected entity or entities, see Execute a Control Set [page 24].
● To display detailed control results:
1. In Consolidation Controls Monitor , select on which execution level you want to display control
results. Options are loaded data, translated data, and consolidated data.
2. Select the entity or group for which you want to display detailed information and click Open Controls
Results in the toolbar.
○ If you select on the group level, the page displays results for all entities under this group.
○ If you select on the entity level, the page displays the result for this entity under all groups.
3. In the Controls Results page, if a control has one or more breakdown dimensions, expand the control by
clicking its arrow to display the data and status of each of the breakdown dimension members for that
control.
● To dismiss or reset blocking controls:
1. In Consolidation Controls , select the entity for which you want to display control results.
2. Click Open Controls Results in the toolbar.
3. In the Controls Results page, select the Blocking type control whose status is Failed, and click Dismiss
Block in the toolbar.
The status of the blocking type control is now Dismissed.
4. To reset the control status to Failed, select the control and click Reset Block in the toolbar.
Related Information
Controls [page 100]

Create a Control Set [page 108]
5.2.1 Execute a Control Set
Perform these steps to execute controls and monitor their progress.
Prerequisites
An administrator has assigned relevant authorization objects to you to execute controls in Control Monitor. For
detailed information about how to assign the authorization objects, refer to the topic “Authorization for
Performing Consolidation Tasks” in the Security Guide for SAP Business Planning and Consolidation, version
for SAP BW/4HANA available on the SAP Help Portal.
A category/time pair has been assigned in Planning and Consolidation Administration to the control set you
want to execute. See Working with Control Sets [page 108].
Procedure
1. In Consolidation Controls Monitor , select the entity or group of entities required and click Run
Controls.
The results are displayed in the Controls Monitor page.
 Note
For loaded data, when the property Bypass LC in ctrls in the Entity dimension is left blank for a
given member, the Local Currency member (LC) of the Reporting Currency dimension is used to run
controls.
To bypass this, you can set the property Bypass LC in ctrls to Y, which means the currency
specified for the entity (for example, EUR) is used to run controls.
Controls are executed according to the control level associated to the selected entity.
 Example
If the entity on which controls are executed is Basic (Control Level 1), then only Level 1 controls are
executed within the relevant control set. If the entity on which controls are executed is Standard (Control
Level 2), then Level 1 and 2 controls are executed. If no control level is associated to the selected entity, all
controls are executed for the selected entity.
A specific Data Manager package can trigger the execution of a control set.
Related Information

Control Set Status [page 25]
5.2.2 Control Set Status
A control set has only one output - the control set status.
Possible control set status values are the following:
● Not applicable
No control set has been defined for the selected Category and Time dimension members.
● To be executed
Applies in the following cases:
○ A control set has been defined for the selected Category and Time dimension members and has not
yet been executed for the corresponding entity or group of entities.
○ When data is updated through data entry and journal entries at the entity level, the control set status
corresponding to the Category, Time, Entity dimension members (and any other work status driving
dimension) is reset to To Be Executed.
○ If you add additional dimensions to a work status, the control set status is reset to To Be Executed for
the corresponding dimension members.
○ If you modify the control set
○ If you change the structure of the entity dimension
 Note
When a control set status is reset to To Be Executed, calculated control data is not reset.
Every time calculations are executed, controls that were dismissed remain dismissed if they fail,
provided that the Reset dismissals option in Planning and Consolidation Administration is not
enabled.
If the controls are Passed after execution, or if there is no data, the control status is updated by the
new calculation.
● Passed: all controls (blocking and warning) have succeeded

● Passed with dismissals: at least one blocking control was dismissed
● Passed with warnings: at least one warning control has failed
● Failed: at least one blocking control has failed
When a control set is executed, its status is a summary of the status of each of the controls available in the set
(according to the level assigned to the control and the entity for which controls are executed).
A control set status is always attached to one of the following dimensions for controls performed in the loaded
data (local currency), and for translated data or consolidated data on base entities:
● Category
● Time
● Entity
● Local Currency or Entity Currency, depending on the value of the property CTRL_CURRENCY_NOT_LC
(Bypass LC in ctrls) in the Entity dimension
Control status results on node entities or groups
The control status of a parent member or group depends on the control status of the child entities.
If the control status:
● of all child entities is Passed, the parent status is "Passed".

● of one child entity is in error, then the parent status is "Failed".
● at child level contains no errors but some warnings, then the parent status is "Passed with warnings".
● at child level contains a dismissed blocking control, then the parent status is "Passed with dismissals".
● of at least one child entity is "To be executed", then the parent status is either "To be executed" if no error is
found in any entity, or "Failed" if an error is found.
Control status results by entity control level for blocking and warning type controls
If a control fails when executed, it generates an error if it is a blocking type control and its level is inferior or
equal to the control level defined for the entity. Otherwise, the control generates a warning.
 Example
Entity Control Entity Control Entity Control Entity Control

Control Type Control Name Control Level Level 1 Level 2 Level 3 Level 4
Blocking Control A Level 1 Error Error Error Error
Control B Level 2 Error Error Error
Control C Level 3 Error Error
Control D Level 4 Error
Warning Control E Level 1 Warning Warning Warning Warning
Control F Level 2 Warning Warning Warning
Control G Level 3 Warning Warning
Control H Level 4 Warning
As shown in the table abpe, Entity 1 is assigned level 1. Entity 2 is assigned Level 2. Entity 3 is assigned level
3. Entity 4 is assigned Level 4. Therefore, in this case:
● Entity 1 will be checked against control A and E.

● Entity 2 will be checked against control A, B, E and F.
● Entity 3 will be check against control A, B, C, E, F and G.
● Entity 4 will be check against all the controls listed in the table.
First assume that after executing each entity by the related Time and Category, the control status turns out
as below:
● Entity 1 failed after executing Control A.

● Entity 2 failed after executing Control B.
● Entity 4 failed after executing Control H.
● The others passed.
Then add controls A to H to control set S and assign this control set S to a time and category. The result will
be:
● Group Level: Failed

● Entity 1: Failed
● Entity 2: Failed
● Entity 3: Pass
● Entity 4: Pass with Warnings
Analysis: The control set failed at the Group level because Entity 1, Entity 2, and Entity 4 all failed. The
control set failed at Entity 1 because Control A is a blocking type and it shows an error. The control set failed
at Entity 2 because Control B is a blocking type and it shows an error. The control set passed with a warning
at Entity 4 because Control H is a warning type.
Related Information

Execute a Control Set [page 24]
5.3 Journals
You use journals to record and make adjustments to data in the database.
This is typically done as part of the month-end or quarter-end process. For example, administrators load
general ledger information into a model using Data Manager. Before the close, line managers can review the
data and make adjustments as necessary using a journal entry form.
Prerequisites
● At least one journal template has been created for the model.
● An administrator has assigned relevant authorization objects to you to manage journals. For detailed
information about how to assign the authorization objects, refer to the topic “Authorization for Performing
Consolidation Tasks” in the Security Guide available on the SAP Help Portal.
Features
The following table describes the available journal tasks and explains how to perform each one. You perform
these tasks in Consolidation Central Journals .
Task Navigation What You Should Know
Create a journal entry Click New in the toolbar of the Journals For more information, see Journal En
page. tries [page 31].
Modify a journal entry Select a journal entry from the list in the You can modify saved and unposted
Journals page and click Open in the journal entries. For more information,
toolbar. In the Journal Entries tab, make see Journal Postings [page 34].
your changes to one or more journal en
try rows, then click Save.
Copy one or more journal entries Select one or more journal entries in You can copy selected entries to an
the Journals page. To select non-contig other member of one of the header di
uous journal entries, hold down the mensions.
CTRL key as you make your selections.
Select Copy To from the toolbar, specify
whether to keep the same Time, Cate
gory, and Datasource dimension mem
bers and confirm.
Preview line item detail of a journal en Select a journal entry from the list on You can review detail lines of a journal
try the Journals page and select the entry for the entries to which you have
Preview option in the toolbar. The de View rights. For more information, see
tails on the journal entries appear below Journal Queries [page 36].
the list of journal entries.
Open one or more journal entries Select a journal entry from the list on You open journal entries to view or edit
the Journals page and click Open in the them. For more information, see Jour
toolbar. You view the details of the jour nal Entries [page 31].
nal entries in the Journal Entries tab.
You can open additional journal entries
and toggle between them using the
tabs that appear with each open journal
entry.
Post one or more journal entries Select one or more journal entries from When you post an entry, the system ap
the list on the Journals page and click plies the values in the journal entry to
Post in the toolbar. All the selected en the database, so that model data is ap
tries are posted. To select non-contigu pended. You can configure a journal en
ous journals, hold down the CTRL key try to be posted with multiple header di
as you make your selections. mensions or multiple values. For more
information, see Journal Postings [page
34].
Unpost one or more journal entries Select one or more journal entries from The system reverses the original entry
the list on the Journals page and click to the model. For more information, see
Unpost in the toolbar. All the selected Journal Postings [page 34].
journal entries are unposted. To select
non-contiguous journal entries, hold
down the CTRL key as you make your
selections.
Ungroup journal entries Select one of the journal entries in a For more information, see Journal
journal group and click Ungroup in the Groups [page 35].
toolbar. All the journal entries in the
group are ungrouped.
Search for journal entries In the Filter by menu located in the tool If a large number of journal entries are
bar of the Journals page, choose written to a model, use the Advanced
Advanced Query. In the Advanced Query Query to define queries so you can
dialog box, define your query and click search for specific entries. The
OK. Advanced Query searches through both
header and detail dimensions. If you
have multiple journal entries, they are
grouped under the first entry. For more
information, see Journal Queries [page
36].
Lock and unlock journal entries Select a journal entry from the list in the When you lock a journal entry, you can
Journals page and click Lock in the tool not make changes to the line item de
bar. To unlock the journal entry, select it tails.
and click Unlock in the toolbar.
Reopen journal entries Select one or more journal entries from To reopen one or more single journal
the list on the Journals page and click entries to new single journal entries in a
Reopen in the toolbar. subsequent time period, see Reopen
Journal Entries [page 37].
Require balanced journal entries Select the Enforce Balanced Journals A balanced journal entry is one in which
option in the journal model parameters. the debits equal the credits in the jour
nal entry. If this option is set, you can
not post the journal entry until it is bal
anced. For more information, see Jour
nal Model Parameters [page 143].
Print a journal report Select one or more journal entries from You can generate reports based on jour
the list on the Journals page and click nal entries. As long as you can view the
Report in the toolbar. To select non-con journal report, you can print the journal.
tiguous journals, hold down the CTRL For more information, see Print Journal
key as you make your selections. In the Reports [page 38].
Journal Report tab that opens, click
Print.
Delete one or more entries Select one or more journal entries from When you delete an entry that has been
the list on the Journals page and click unposted, its status changes to
Delete in the toolbar. To select non-con Deleted. When you delete saved entries,
tiguous journals, hold down the CTRL they are deleted from the system. An
key as you make your selections. entry that has been posted cannot be
deleted until it is unposted. For more in
formation, see Journal Entries [page
31].
Define journal reopen rules In Planning and Consolidation Adminis Design a template of translation infor
tration, select Features Journal mation for the dimensions you want to
reopen. For more information, see Jour
Templates . Open a journal template
nal Reopen Rules [page 142].
and click the Reopen Rules tab.
5.3.1 Journal Entries
You create and maintain journal entries using the journal entry template built by your administrator.
Features
The following features are related to journal entries:
Postings
You can post journal entries after they have been saved. For more information, see Journal Postings [page 34].
Reports
Once you save and post journal entries, you can track and report on all adjustments to data. For more
information, see Print Journal Reports [page 38].
Journal IDs
The first time you save one or more entries, the system generates a journal ID, which you can use to identify the
entry. If you create journal entries as a group, the system also assigns a group ID.
Standard Journal Entries
You can enter standard journal entries, which have one member defined for each header dimension and one
credit or debit value.
Activities
To create a journal entry, select Consolidation Journals , then click New in the toolbar. For more
information, see Journals [page 28].
5.3.2 Journal Entry Form
You use the journal entry form to create, modify, and post journal entries.
Features
Use the journal entry form as described in the following table to enter journal entries:
Form fields Description
Model information Read-only fields that display the environment name and the
model for which you are entering the journal.
Header dimensions The fixed dimensions for all journals in the current model
that are displayed in the scope context area of the journal
entry form. You select members for each dimension by click
ing the entry cell to display the Member Selector dialog box.
Additional Properties Text fields or lists containing clarifying information, such as

date or type, that you save along with the journal entry form.
The system does not require additional header items, but
your business process may require them. If they are present
in your journal entry form, you must complete them before
you can post a journal entry.
Multiple Headers Choose this option if the same amounts need to be posted
to more than one member in one of the dimensions in the
data region. When you select the Multiple Headers option,
the associated Dimensions member lookup then becomes
available.
Multiple Values Choose this option if different amounts need to be posted to

more than one member in one of the dimensions in the data
region. When you select the Multiple Values option, the asso
ciated Dimensions member lookup then becomes available.
Journal Entries tab Display in columns so that each row under the dimension
name is unique. Each unique combination of members rep
resents one detail line. You can enter the members associ
ated with the data values you want to change, and the debit
or credit amount. When you create multiple entries with mul
tiple values from a single header item, a set of debit and
credit columns displays for each additional member speci
fied.
Form fields Description
Multi Posting tab The journal entry is posted to the database under each di
mension member defined for Multiple Headers and Multiple
Values. This tab is grayed out until one of the aforemen
tioned options is selected.
Status information The following information displays for auditing purposes:
● Status: The current status of the journal entry. Statuses

include Saved, Posted, Unposted, and New.
● Original ID: If a journal entry is reopened, the old journal
ID is the ID of the original entry.
● ID: Lists the journal ID (determined by model).
● Group ID: Taken from the first Journal ID in the Group.
Journal options These options allow you to perform advanced functions on

the journal entry:
● Balanced: This option allows you (or an administrator)

to require that journals are balanced upon posting.
● Reopen in Next Period: This option allows you to reopen
the journal entry to another account in a subsequent
time period.
● Auto Reverse: This option allows you to reverse the
credit or debit value in the journal entry in the next time
period.
 Note
This option sets up a new journal; it does not create
postings.
Related Information
Journal Entries [page 31]

Journal Postings [page 34]
5.3.3 Journal Postings
You post journal entries to enter the details of a transaction into the database.
Prerequisites
An administrator has assigned relevant authorization objects to you to post journals. For detailed information
about how to assign the authorization objects, refer to the topic “Authorization for Performing Consolidation
Tasks” in the Security Guide available on the SAP Help Portal.
One or more journal entries have been saved.
Features
When you post a journal entry, the system takes the following actions:
● Validates the journal entry for completeness and accuracy. For example, if you require balanced journal
entries, debits must equal credits.
● Locks the journal entry so it cannot be edited.
● Applies the values in the journal entry to the database, so application data is appended to the numbers in
the database. Unlike in input schedules, the system appends data; it does not replace it.
● Updates the entry to record the user who posted the entry. This information is useful when you create
journal reports for the entries.
Reposting journal entries
You can repost journal entries that you accidentally delete. Only journal entries that have previously been
posted can be reposted.
Unposting journal entries
You can unpost one or more journal entries to make changes to them.
Multi-Posting journal entries
You can configure a journal entry to be posted to the DataStore Object (advanced) under multiple dimension
members that you define in the journal entry page. You can choose one or both of the following:
● Multiple headers: the same amounts need to be posted to more than one member in one of the dimensions
in the data region. For example, the journal entry needs to be posted to both the actual and forecast
categories.
● Multiple values: different amounts need to be posted to more than one member in one of the dimensions in
the data region.
Activities
● To post one or more standard journal entries, in the Journals page, select a journal entry and click Post in
the toolbar. All of the selected journal entries are posted.
● To find a specific entry to post, from the Journals page, select Advanced Query from the Filter by dropdown
menu, and build a query to find the entries that you want to post. Select all entries that you want to post,
and then click Post in the toolbar. To select non-contiguous journal entries, hold down the CTRL key as you
make your selections.
● To unpost a journal entry, in the Journals page, select a journal entry and click Unpost in the toolbar. When
you unpost a journal entry, the following events occur:
○ The system keeps the same journal ID.
○ The status of the journal entry changes to Unposted.
● To configure a journal entry for multi-posting mode
1. In the Journals page open the journal entry. Select one or both of the following options, and select the
dimension member from the corresponding member lookup:
○ Multiple Headers
○ Multiple Values
2. Click the Multi Posting tab to add additional headers or values:
 Note
The Multi Posting tab is greyed out until you select one of the options listed above.
○ To add additional headers, in the Multiple Headers list click Add, then select the dimension
members you require from the Member Selector dialog box.
○ To add additional values, in the Multiple Values list click Add, then select the dimension members
you require from the Member Selector dialog box.
Related Information
Journal Entries [page 31]
5.3.4 Journal Groups
When you enable multiple headers in a journal entry, you create a journal group.
You can add two or more journal entries to a journal group. See Journal Entry Form [page 32].
You group and ungroup journal entries in Consolidation Journals .
Features
Journal groups have the following features:
● Group ID
All journal entries in the same group have the same journal group ID, which is taken from the first journal ID
in the group. (Each journal entry still maintains a unique journal entry ID.)
● Group Status
All journal entries in a group have the same status. When you perform an action that updates the status of
a journal entry in a group, for example, posting the journal entry, all journal entries in the group are also
posted and their status updated.
Activities
● To create a journal group

1. In the Journals page, click New in the toolbar to create a journal entry.
2. In the journal entry form, select Multiple Headers.
The Multi Posting tab becomes available, and you can add the required additional headers.
● To ungroup journal entries
○ In the Journals page, select a journal entry in the journal group and click Ungroup in the toolbar.
All journal entries in the group are now ungrouped.
You can no longer perform multi-posting on these journal entries; the Multi Posting tab is grayed out in
the journal entry form.
Related Information
Journal Postings [page 34]
5.3.5 Journal Queries
If a large number of journal entries are written to a model, you can define queries to search for specific entries.
Both header and detail dimensions are searched.
Features
Once you display a query, you can perform the following tasks on journal entries:
● Open the saved or posted entries

● Open all, posted, unposted, deleted entries
● Review the line item detail on posted or saved entries
● Post the saved entries or unpost the posted entries
● Delete the unposted entries
Activities
Define a journal query:
1. From the Journals page, select Filter by Advanced Query .

2. Specify as many query parameters as necessary. You can add additional query parameters by adding new
rows.
3. Once you have made your selections, click OK. The query results are displayed.
 Note
The query settings are saved until you deselect Advanced Query in the Filter by menu.
Related Information
Journals [page 28]
5.3.6 Reopen Journal Entries
You can reopen one or more journal entries from a previous year, then post them to another set of accounts for
the following year.
Prerequisites
The administrator has customized the reopen rules table. The table defines the source and destination
accounts for the reopening of journals. You define criteria to reopen from one dimension to another dimension.
See Journal Reopen Rules [page 142].
The system is set to allow for reopening of journals using the Allow Journals to be Reopened journal parameter.
See Journal Model Parameters [page 143].
The selected source journal entries are posted to the database.
The Reopen in Next Period option is selected in the journal entry.
Features
You can reopen one or more journal entries to new journal entries.
Activities
To reopen a journal entry:
1. In the Journals page, click Reopen in the toolbar.

2. In the Reopen dialog box, in the Select journals to be reopened section, specify a Category and Time
member. The journal entries you want to reopen will be selected from these two members and other
source dimensions members when defining the journal template.
3. In the Select destination section, specify a Category and Time member in which you want to reopen the
journal entries.
In the next period, all the journals in the selected member range will be reopened to the target member range.
5.3.7 Print Journal Reports
You can generate and print reports based on journal entries. These reports, which are web-based, represent an
audit trail of all journal entries.
Features
The printed journal entry report contains all postings for the selected journal entries.
You can filter the journal report by creating a journal query based on multiple parameters, including but not
limited to dimension member such as account, journal status, posted date, or group ID. You can then select the
journal entry from the filtered list. For more information, see Journal Queries [page 36].
Reports are displayed in separate tabs.
Activities
To print a journal report of one or more journal entries
1. Select Consolidation Journals .

2. Select one or more journal entries in the Journals page and click Report in the toolbar.
 Note
To select non-contiguous journals, hold down the CTRL key as you make your selections.
The journal report, containing all the postings for the selected journal entry or entries, opens in a new tab.
3. Click Print in the toolbar.
5.4 Ownership Manager
The Ownership Manager in the Consolidation Central module enables you to create and manage ownership-
based hierarchies used for performing statutory consolidations.
An ownership-based hierarchy combines Groups and Entity members, where entities can be differently
connected to or disconnected from groups according to Category and Time. Groups are nodes whereas entities
are base members.
You define ownership-based hierarchies in the system to set up and report on entity hierarchies that cannot be
managed by a fixed hierarchy.
While management reporting entity structures are fixed, and children roll up 100% to their associated parent,
ownership-based hierarchies support the legal structure of statutory consolidations that cannot be managed
by a fixed hierarchy.
Features
The static hierarchies exist above the ownership-based portion of a hierarchy, which is attached below a base-
level member in the static hierarchy. The Groups dimension is used to identify consolidation sequences and for
reporting.
● The ownership relationships required for legal reporting may exceed a one-to-one relationship in their
reporting structure or they may change frequently.
● There are two scenarios where you should define ownership-based entity hierarchies:
○ If a child member is owned by more than one parent
○ If the child is partially owned by a parent (not 100%)
● In the Ownership Manager you define an ownership-based hierarchy entity structure. The Ownership
Manager allows you to create period-specific hierarchies of corporate entities to use in statutory
consolidation, or in cases where hierarchy changes for an application need to be tracked by Category and
Time.
● When you set up a Statutory model, the system tracks hierarchies for statutory reporting. Statutory
models have an upper-level static hierarchy associated with a Group dimension.
● Ownership-based hierarchies are only available in consolidation type models.
Activities
To display the Ownership Manager, select Consolidation Ownership Manager .
Related Information
Create Ownership-based Hierarchies [page 40]
5.4.1 Create Ownership-based Hierarchies
You create ownership-based hierarchies using the Ownership Manager, which is an ownership-based hierarchy
editor provided in Consolidation Central.
Procedure
To create ownership-based hierarchies in SAP Business Planning and Consolidation, select Consolidation
Ownership Manager Edit .
● The top of the window shows the Category, Time, and Groups setting for the active current view. Use the
member lookup in these fields to change the Category and Time members for which you want to create an
ownership-based hierarchy. Use the member lookup in the Groups field to specify the member that you
want to use as the parent in the hierarchy. If this Group dimension member is defined as part of a fixed
hierarchy for a statutory consolidation, this fixed hierarchy is imported intact into the Ownership Manager.
In the tree structure to the left, expand the parent member to view any existing children.
You can also maintain children for each group level by choosing a group and clicking Add to add entities to
or remove entities from the group. Currently you cannot choose an external entity members to add to the
group.
● To display all members that have detail but are not used in a hierarchy, select the Show empty option in the
toolbar. This function helps assure that you do not forget to specify the method and percentage for newly
inserted members.
● After you create the desired hierarchy, you can enter detail for each child member, as described in the
following section, and run ownership calculations.
Enter Child Member Detail
When working with consolidation models, you can provide consolidation information, such as percent
ownership, percent control, percent consolidation, and the consolidation method to the child members. You
enter this detail in the right-hand part of the Ownership Manager window.
From the Ownership Manager Edit window, select the desired child member from the hierarchy on the
left. In the right-hand part of the Ownership Manager window, double-click in the Current column
corresponding to the parameter whose value you want to update. Select the Update ownership upwards option
if you want the updates made to an entity member to apply to all groups (parents) above.
Remove a Child Member
Select a child member in the tree hierarchy and click Remove. If a deleted member had method, ownership or
consolidation detail specified, this detail is deleted along with the member.
Copy Ownership Data
To copy ownership data to another period, display the hierarchy in the Ownership Manager Editor, highlight the
group dimension and select Copy to from the toolbar. In the Copy Ownership to window, select the Category
and Time combination to which you want to copy the hierarchy. If ownership data already exists in the
destination period, the copied ownership data is merged into the existing data set.
Cut and Paste a Child Member
Select a child member in the tree hierarchy and click Unpin in the toolbar. Position the cursor at the point in the
tree hierarchy where you want to paste the child member and click Pin in the toolbar.
Related Information
Example of an Ownership-Based Hierarchy with Divested Entities [page 41]
5.4.1.1 Example of an Ownership-Based Hierarchy with

Divested Entities
In this example, an ownership-based hierarchy is divested of two entity members in 2015. The entity members
remain part of the ownership-based hierarchy in the period 2015, but are excluded in the period 2016.
Activities
1. You create an ownership-based hierarchy with the Parent Group member GROUP_WORLDWIDE, and
assign the entity members to parent entities as follows:
Parent entity members Child entity members
AMERICA USA
CANADA
EUROPE UK
FRANCE
ASIA CHINA
JAPAN
2. You assign the following Consolidation Method, Percent Control, and the Percent Ownership to the entity
members:
Entity member Consolidation Method Percent Control Percent Ownership
USA Full 100% 100%
CANADA Full 100% 100%
FRANCE Holding 100% 100%
UK Equity 20% 20%
CHINA Proportionate 50% 50%
JAPAN Full 100% 60%
3. For the period 2015.June, you assign the Consolidation Method, Percent Control, and Percent Ownership at
the level of the Parent Group GROUP_WORLDWIDE (select the highest level parent in the left-hand
hierarchy) as follows:
USA Full 100% 100%
UK Full 100% 100%
CHINA Full 100% 100%
JAPAN Full 100% 100%
Methods are defined for each group, at the level of the first immediate parent for each entity.
The percentage values you assign to the first parent entity group are not inherited by the parent group by
default. To do so, you must select the option Update Ownership Upwards in the toolbar while positioned on
the parent entity group whose values you want the parent group to inherit.
4. The UK and Japan entity members are divested following the period 2015.June. The UK and Japan entity
members still appear in the ownership-based hierarchy for the period 2015.Dec. as follows:
USA Full 100% 100%
UK Divested 0% 0%
JAPAN Divested 0% 0%
5. For the period 2016.Dec., the divested entity members no longer appear in the ownership-based hierarchy.
The members and percentage values are as follows:
USA Full 100% 100%
Related Information
Create Ownership-based Hierarchies [page 40]
6 System Reports
You can prepare reports containing system information and a history of business user activities.
● General - The following general reports are available:

○ Business process flows. For information, see Reporting on Business Process Flows [page 45].
○ Data changes. For information, see Reporting on Data Changes [page 45].
○ Work status. For information, see Reporting on Work Status [page 47].
Activities
To create a new report, go to System Reports, and from the list of reports, choose the type of report that you
want to create. Set the appropriate reporting options and display the report.
Once you have displayed the report, you can do the following:
● Edit the report selection criteria

Click Edit Criteria to change the selection criteria.
● Refresh the report
Click Refresh to regenerate the report if you think that the data, upon which the report is based, has
changed.
● Print the report
Click Print. The system grays out this option if a printer is not available.
● Export the contents of the report to a file
Click Export to File and specify the file name and location.
Comments in reports
Comments are shown in the Comments column when you display a report. The cells in the column show the
number of comments, and hovering your mouse over the entry in the cell shows a tooltip with metadata about
the most recent comment; cells with no comments are simply blank. Click the link to see the comments
ordered by date/time. Comments are not shown in the print form of reports because the comment length is
unlimited and printing has a fixed character limit. When exporting reports, the most recent comment is
exported.
More Information
Data Auditing [page 148]
44 PUBLIC System Reports
6.1 Reporting on Business Process Flows
You can generate reports on Business Process Flows (BPFs). Reports can be viewed online and printed.
Features
The following types of BPF reports are available:
● Instance
● Activity
Activities
To view a business process flow audit report, select go to System Reports, and from the list of reports, choose
the type of report that you want to create. Set the appropriate reporting options, and display the report.
6.2 Reporting on Data Changes
Business Planning and Consolidation records audit information on who changed transactional data in the
InfoProvider.
Features
The report shows who changed the data, what time they made the change, how they made the change (for
example, through SAP EPM solutions, add-in for Microsoft Office), and the details of the record that was
changed.
You can choose from the criteria listed below to fine tune your report. In the report, the columns correspond to
these parameters.
Option Description
InfoProvider Select an InfoProvider that has data change audit enabled.
Dimension Members Select the dimension and dimension members the audit in
formation is stored against.
The special dimension Audit Mode can have the value PLAN.
System Reports PUBLIC 45
Option Description
Date and Time You can choose start and end dates for the report or display
the full history of the selected data audit information
(Anytime).
Additional Criteria Select from the following options:
● Data Modified by Task

○ All
○ The EPM add-in for Microsoft Office
○ Data Manager Import
○ Data Manager Clear
○ Logic Script Execution
○ Web Report Input
○ Journals Input
○ Business Rule Execution
○ Ownership
○ FIM Import
● User
● IP Address
● Group Rows by
○ Activity
○ AddInfo1
○ AddInfo2
○ Machine Name
○ IP Address
○ Dimensions relevant to the model
○ User
● Show Rows by
○ ID (Member ID)
○ Description (Member description)
● Machine Name
● Current, which includes audit records of data changes
that have not yet been archived
● Archived, which includes audit records of data changes
that have already been archived
● Current and archived, which is the combination of both
options
● User
Activities
To view a data changes report, go to System Reports, and from the list of reports, choose Data Changes. Set the
appropriate reporting options and display the report.
More Information
6.3 Reporting on Work Status
The report on work status allows you to display the work status codes for a set of given criteria.
Work status is a feature that allows you to lock regions of data from being overwritten. You define “work
states”, for example, Locked, Submitted, or Approved, so users can control input to specific data regions.
You can filter the report to the specific region of the model for which you want the work state.
Features
The work status report shows Data State, which is the current work state for the data. It tells you the current
stage of the data in the overall approval process.
It also shows the dimensions for which you define work status as being applicable. There can be 1 to 14
dimensions; the report adjusts dynamically based on the active application.
You specify the report parameters as specified in the following table:
Option Description
Model Select a model, for example, PLANNING or RATE.
Dimension Members Select dimensions and dimension members that the work
status is stored against.
The dimensions displayed depend on the selected model.
Date and Time You can choose start and end dates for the report.
Additional Criteria User ID - Enter the User ID for which you need the work sta
tus report.
Activities
To view a work status report, go to System Reports, and from the list of reports, choose Work Status. Set the
appropriate reporting options and display the report.
System Reports PUBLIC 47
Related Information
Work Status Setup [page 135]
7 Administration
In the Administration screen, administrators perform setup and maintenance tasks.
Setup and maintenance of Business Planning and Consolidation consist of the following tasks:
● Environment management
● Dimension management
● Model management
● Legal consolidation
● Security management, which is explained in the Security Guide available on the SAP Help Portal.
● Management of controls
● Set up of business process flows
● Set up of work statuses
● Set up of auditing
Related Information
Environment Management [page 49]

Model Management [page 58]
Consolidation [page 64]
Rules [page 83]
Controls [page 100]
Business Process Flow Management [page 114]
Work Status Setup [page 135]
Journal Administration [page 140]
Auditing [page 148]
Dimension Management [page 51]
7.1 Environment Management
An environment consists of one or more models.
An environment is a virtual concept of a container that holds different planning scenarios in the form of models.
Company-wide planning processes can be built on top of an environment.
Administration PUBLIC 49
Features
Adding New Environments
Administrators create new environments from scratch in the Manage All Environments screen.
 Note
In BPC 11.0, embedded environment automatically generates 2-bits string in its prefix consisting of
numbers and letters (a-z). This will impact consolidation embedded functions such as creating business
rules. To solve this issue, follow the instructions in the note 2634332 .
For more information, see New Environments [page 50].
Using E-Mail Notifications
Administrators can use an e-mail notification service to send e-mails to users or teams defined in the system.
The appropriate SMTP parameters must be set up correctly. For detailed information, refer to the SMTP
Configuration Guide available on the SAP Help Portal.
Deleting Environments
You can delete environments after choosing Manage All Environments and selecting an environment.
 Caution
When you delete an environment, you will delete all objects under this environment:
● Models
● BPF templates and instances
● Work status settings and data
● Worksheets
● Analysis Office add-in reports
However, all BW modeling and settings done in the BW back-end transactions will still be available.
7.1.1 New Environments
You create new environments from scratch in the Manage All Environments dialog.
Activities
To access the Manage All Environments screen, follow these steps:
1. On the upper right corner of the screen, click the button.

2. Click the name of the current environment.
3. In the dialog that appears, choose Manage All Environments.
50 PUBLIC Administration
To add a new environment, choose the Create button. When you create the environment, you assign a name
and description to it. The type of the environment is preselected to Embedded. You cannot change it.
7.2 Dimension Management
A dimension is a collection of related data members that represent one aspect of a business, for example,
accounts, products, or entities.
You can manage dimensions in the following ways:
Task More Information
Displaying Dimension You can modify an existing dimension. When you modify a dimension, you can change the
Structures name, description, dimension type, reference dimension, and dimension properties as well as
enable member formulas for the dimension.
See Dimension Structure [page 52].
Maintaining Dimension You can maintain a dimension member, add a new member, delete an existing member, or
Members change property values for an existing member.
See Dimension Member Management [page 52].
Processing Dimensions When you create a dimension or make changes to an existing dimension, you need to process
the dimension.
See Dimension Processing [page 53].
Maintaining Hierarchies You can add a new hierarchy, maintain an existing hierarchy structure, or delete an existing
hierarchy.
See Hierarchy Management [page 54].
Maintaining Dimension Se You can manage dimension member security at the dimension level using Business Ware
curity house and a Business Planning and Consolidation data access profile.
See Dimension Security [page 56].
Creating Local Dimensions You can create local dimensions based on existing central dimensions, as well as remove un
necessary properties and add new properties during the creation process. Local dimensions
can also be deleted when they are no longer useful.
See Creating Local Dimensions [page 56] and Deleting Local Dimensions [page 57].
Activities
To manage dimensions, go to the Administration screen and under Modeling choose Dimensions. Once you
select a dimension, you can perform one of the available tasks.
Security
For information about the authorizations needed to maintain master data for dimensions, see the Security
Guide, which is available on the SAP Help Portal.
Related Information
Dimension Structure [page 52]

Dimension Member Management [page 52]
Dimension Processing [page 53]
Hierarchy Management [page 54]
Dimension Security [page 56]
7.2.1 Dimension Structure
You can view the structure of a dimension used in an InfoProvider that has been assigned to a model within an
environment. You can see the dimension description and the dimension properties that have been assigned.
Activities
You can display the structure of a dimension on the Administration screen by choosing Dimensions, selecting a
dimension, then choosing View Structure.
7.2.2 Dimension Member Management
You manage dimension members by adding and modifying members within a particular dimension.
You add members to dimensions based on your business needs. For example, if your company opens a new
office, the financial information of that office must be part of the Entity and Category dimensions.
Features
A dimension contains a set of predefined properties based on its type. You can add new properties by using the
BW modeling tools, if desired.
Managing Dimension Members
You can add, delete, and modify members in dimensions within an environment in the Administration section.
Under the Modeling section, choose Dimensions , select a dimension, and then choose Edit Members.
Time-dependent Property and Text
You can maintain the time-dependent property and text when time dependency is activated in the BW backend,
as follows:
● A time-dependent property and text are identified with a clock icon in their column header.
● When there is at least one time-dependent property or text, a key date field appears in the menu of the
maintenance screen. The current calendar date is used as the default date when member maintenance
initially loads. You can choose a different key date to toggle a different property value or text across time.
● By default, a changed value for a time-dependent property and text updates to the current time range (in
which the key date lies) when saving.
● By selecting the checkbox in the column From <key date>, a changed value for a time-dependent property
and text is applied to a new time range starting from the selected key date
Compounding Dimensions
You can maintain the member of a compounding dimension after it has been activated in the BW backend.
When you add a new member for a compounding dimension, you can select an existing member for superior
dimensions from the value's help.
Maintaining the Member of a Property Dimension
You can maintain the member of a dimension property when the property itself has master data. To maintain a
member for the dimension, view the dimension structure and click directly in the property ID.
 Caution
You cannot rename dimension member IDs.
Maintaining Members and Properties of Local Dimensions
● You can add a new member that does not exist in a global dimension and maintain its properties.
● You can overwrite property values for members inherited from a global dimension.
● You cannot delete members inherited from a global dimension.
● Time-dependent property and text compounding are not supported.
7.2.3 Dimension Processing

Whenever you add a new dimension member, modify an existing dimension member, or delete a dimension
member, you must process the dimension.
Activities
You can process dimensions in the Administration screen. In the Modeling section, choose Dimensions ,
select one or more dimensions, then choose Process.
You can also process dimensions when you maintain a dimension member by choosing Save and Process.
7.2.4 Hierarchy Management
You manage dimension hierarchies by adding new hierarchies, deleting existing hierarchies, and maintaining
the hierarchy structure for a particular dimension.
You manage dimension hierarchies based on your business needs. For example, if your company opens a new
office, the hierarchy of your Entity dimension should be updated to include this new office.
Features
A dimension can be defined to have a hierarchy or not. To enable a hierarchy for your dimension, use BW
modeling tools. A hierarchy you maintain in the Business Planning and Consolidation HTML5 web client can
also be verified and maintained in BW modeling tools.
Adding a New Hierarchy
You can add a new hierarchy to a dimension within an environment in the Administration screen. In the
Modeling section, select Dimensions, choose a dimension, select Edit Hierarchy, then select Add.
Maintaining a Hierarchy Structure
By selecting a hierarchy name in the hierarchy list, you can maintain the hierarchy structure.
You can add new nodes to a hierarchy by selecting a parent node and selecting Add, then choosing dimension
members from either the current dimension or external dimensions.
You can add text nodes or internal nodes, and you can sort and filter by member ID or property by selecting
each column header of the grid.
 Note
The External Dimension option is by default not displayed in this page if you did not choose an external
dimension for the current hierarchy. To define external dimensions, enter Business Warehouse (BW)
transaction RSA1, choose InfoObjects in Modeling, and enter the Hierarchy page of the current dimension.
Then you can add external dimensions in the External Characteristics of Hierarchy view.
Time and Version Dependent Hierarchies
Time and version dependent hierarchies are supported in the Business Planning and Consolidation Web client.
To define a time and version dependent hierarchy, use Business Warehouse (BW) transaction RSA1 and go to
the Hierarchy tab of the related InfoObject to make the corresponding settings. After that, you can define
hierarchies of different versions based on a different date range, as well as hierarchies in a different time range
based on different versions in the hierarchy view of the dimension. The detailed settings are as follows:
● Entire Hierarchy is Time Dependent

All existing Time ranges display at the top of the right pane. You can select different time ranges to toggle.
To create a new time range, select Create hierarchy date range from the time range drop-down. The
hierarchy structure of the currently displayed time range will be used as the default hierarchy for the new
time range.
● Time-dependent Hierarchy Structure
The time range of each hierarchy node displays for the node ID/Description when you move your mouse
over the node. All newly added nodes have the default time range 1000.01.01-1999.12.31. To edit the
time range, choose the pen icon.
● Version-dependent Hierarchy
All existing versions display at the top of the right pane. You can select different versions to toggle.
To create a new version, select Create hierarchy version from the version drop-down.
Using Local Hierarchies
You can use local hierarchies by either creating them from scratch or by making a local copy of a hierarchy that
has had its master data loaded into the system. To make a local copy after selecting a dimension and viewing
its global hierarchies, choose a hierarchy and select Copy. Since local hierarchy does not support time or
version dependent hierarchies, you need to enter a key date for time-dependent hierarchies or specify a time
range if the entire hierarchy is time-dependent, which is the date on which or the date range during which you
want to take a snapshot of the hierarchy to add locally. If the global hierarchy from which you copy a local
hierarchy is version-dependent as well, you also need to select a version.. Then you can assign a new ID and
description if desired and make other changes in the local hierarchy by adding, deleting, or moving items in it, if
necessary. Note that you can have only internal nodes and text nodes in local hierarchies. External nodes are
automatically converted to text nodes when the hierarchy is copied from global to local. After that, you can
save and process your changes.
Reverse Sign for Nodes
To enable the reverse sign for nodes, use Business Warehouse (BW) transaction RSD1. Reversed
displays for each node ID/Description when you move your mouse over the node. To change the sign, choose
the pen icon.
Processing Required
You must process all changes made to a hierarchy before the hierarchy can be used in reporting and planning.
7.2.5 Dimension Security
Security for dimension members is at the dimension level. Once you make a dimension in the Business
Warehouse backend as authorization-relevant, the dimension is secured in all models where it is used.
Features
You can use BW analysis authorization and a Business Planning and Consolidation data access profile to define
access to a dimension member and transaction data.
For more information, see the Security Guide, which is available on the SAP Help Portal.
7.2.6 Creating Local Dimensions
By leveraging Business Warehouse workspace concepts and extending Business Planning and Consolidation
local providers, you can generate local dimensions, which are named local InfoObjects in BW. The central
InfoObject mentioned here is the corresponding global InfoObject in Business Warehouse.
Prerequisites
A central BW InfoObject, known as the central dimension, can be used as a reference to create a local
InfoObject - a dimension - when all of the following prerequisites have been met:
● The InfoObject is not authorization relevant.

● The InfoObject has master data.
● • The InfoObject should be assigned to an InfoArea and exposed as an InfoProvider in BW. You can check
this via the InfoArea section in the global InfoObject’s Master Data/Texts page. Go to Transaction RSA1,
then choose Modeling InfoObjects . Select the target central InfoObject and navigate to the Master
Data/Texts tab.
● The referenced BW workspace must have the setting Creation of Master Data Allowed turned on. To
activate this setting, enter Transaction RSWSPW, search for the referenced BW workspace and go to the
Settings tab of the workspace.
 Note
The Creation of Master Data Allowed option is by default not checked when a new workspace is
created. To change this behavior, go to transaction RSBPCADMIN and set the value of parameter
WSP_SIDX to “X”.
● The central InfoObject is assigned to the central providers list in the current workspace (environment). To
make sure of this, go to Transaction RSWSP, input the current environment ID as the Workspace ID and click
Display. Then, click the Central Providers tab and check if the target central InfoObject is listed there. If not,
click the Build InfoProvider Selection button, select the target central InfoObject, drag it to the central
providers list on the right, and activate the modification.
Context
A local dimension inherits all the metadata and master data from its central InfoObject. All changes to master
data made in central InfoObjects are automatically reflected in the local dimension if they are not overwritten
by subsequent changes to local dimension.
After generating a local dimension from the original central InfoObject, you can rename the member ID or
change the attribute value. You can also add to the local dimension new attribute values, such as new members
that do not exist in the central InfoObject. The new attribute value is visible only in the local dimension and
overwrites the property value inherited from the global BW InfoObject.
 Note
A central InfoObject can have only one local inherited version of the InfoObject within one Business
Planning and Consolidation environment.
Procedure
1. Go to Administration and choose Dimensions under Modeling.

2. In the dimension list, select one central dimension, whose visibility needs to be Central, from which no
local dimension has been created.
3. Click Create Local, enter a description, and click OK. Then, enter the dimension structure view of the local
dimension you are creating.
4. Add new attributes and remove existing attributes.
5. Click Save to finish creating the local dimension.
Related Information
Deleting Local Dimensions [page 57]
7.2.6.1 Deleting Local Dimensions
You can delete local dimensions that are no longer useful.
Context
Note that you cannot delete a local dimension that is being used inside a local provider.
Procedure
1. Go to the dimension list view, then select the local dimension you want to delete.
2. Click Delete on the toolbar.
7.3 Model Management
A model is a representation of the relationships, calculations, and data of an organization or business segment.
Models can be categorized as ‘planning models’ or ‘consolidation models’. Planning models are used for
generic planning-related activities. Consolidation models are designed for performing consolidation tasks.
Consolidation type models must have specific components defined to fullfil legal consolidation requirements.
For detailed information, see Planning and Consolidation Models [page 60] and Set up a Consolidation Model
[page 65].
Features
You can use the following features when managing models:
Creating New Models
To create a model, go to Administration and under the Modeling section, choose Models. On the screen that
appears, choose New.
When you create a new model, you set references to InfoProviders that exist in SAP Business Warehouse (BW).
You can choose an arbitrary number of InfoProviders to include in the model. When creating a new model you
can use the following types of InfoProviders:
● DataStore Objects (advanced)

For the definition of DataStore Object (advanced) and steps about how to create DataStore Objects
(advanced), see DataStore Object (advanced) and Creating DataStore Objects (advanced).
● BAdI Providers with write interface.
For more information, see BAdI Provider.
● Local providers
For more information, see Working with Local Providers [page 61].
 Recommendation
We recommend that you familiarize yourself with the documentation of SAP BW as all InfoProviders that
you can use for creating models in Business Planning and Consolidation are delivered by BW.
 Note
You cannot create new InfoProviders through the web interface of Business Planning and Consolidation. If
you want to create InfoProviders that you could later use in your models, you must create them in the BW
modeling tools. For more information, see the documentation ofWorking with BW Modeling Tools in Eclipse.
Adding or Removing InfoProviders
To add a new InfoProvider to a model, or to remove an InfoProvider that is already included in the model, follow
the steps below:
1. Go to Administration and under the Modeling section, choose Models.

2. Choose the model that you want to change.
3. Choose the Add/Remove button. A list of all available InfoProviders appears.
4. Use the checkbox for each InfoProvider to include or exclude it from the model.
Reviewing the Structure of Models
You can review the structure of each individual InfoProvider that is included in a model. To do this, follow the
steps below:
1. Go to Administration and under the Modeling section, choose Models.

2. Choose the model whose structure you want to review.
3. Choose an InfoProvider that is included in the model.
The screen that appears, has three tabs:
● Structure - displays the structure of the InfoObject

● Aggregation Levels - displays a list of the aggregation levels that are defined for the InfoProvider. Each
aggregation level is a selection of characteristics and key figures.
 Note
The Business Planning and Consolidation web user interface displays only simple aggregation levels.
These aggregation levels are set on DataStore Objects (advanced). The complex aggregation levels
(aggregation levels that are created on CompositeProviders) are not displayed.
● Related MultiProviders - shows the MultiProviders that exist for the selected InfoProvider.
Adding Business Rules to Models
You can add business rules to a model in the Business Rules area of the Administration screen. You activate the
rule types you need for the model and add the new business rules of each type to the model. For more
information, see Business Rules Management [page 83].
Setting up Work Status Settings for Models
Managing work status involves specifying who can make changes to your data and who can change the work
state on a data set. You create work states to reflect the status of data as it moves through your business
processes. See Work Status Setup [page 135].
Deleting Models
Administrators can delete models when necessary.
7.3.1 Planning and Consolidation Models
The following table describes the different types of models and lists the InfoProviders available for each.
Type of Model Description InfoProviders
Consolidation Consolidation models are used to carry ● CONSOLIDATION InfoProvider

out both management and legal consol
(mandatory)
idation. You can define business rules
This is the main InfoProvider con
for consolidation models.
taining all financial data. All consol
idation postings such as elimina
tions and minority interest calcula
tions are posted in this InfoPro
vider.
● OWNERSHIP InfoProvider (man
datory)
This manages the organizational
structure and ownership percen
tages by defining ownership details
such as the consolidation scope,
method, and percentage of shares
owned by the holding company or
groups.
● RATE InfoProvider (optional)
This stores all currency exchange
rates for the different rate types.
Currency conversion applies to
consolidation models to which a
corresponding RATE InfoProvider
has been referenced.
● SOURCE InfoProvider (optional)
This can be used as source data if
you have a non-planning InfoPro
vider that contains the source data
for consolidation. If you refer to
this InfoProvider, you must make
sure it contains the same dimen
sions (InfoObjects) as defined in
the Consolidation InfoProvider.
For detailed information about the re

quired InfoObjects and attributes of
these InfoProviders, refer to Create In
foObjects and InfoProviders [page 66]
and Maintain InfoObject Attributes
[page 69]
Planning Planning models are used for reporting No specific InfoProviders are required
for a planning model.
and planning.
7.3.2 Working with Local Providers
Local providers work in a similar way to central InfoProviders. You can use local providers for different
purposes, for example, as a basic information holder for an ad-hoc planning application.
A local provider is visible only in the current environment.
Creating New Local Providers
1. Go to the Administration page, and in the Modeling section, choose InfoProviders.

2. On the screen that appears, choose Local Providers and then choose New to start the local provider
creation wizard.
3. Enter the ID and Description of the new local provider. If you want to set a prefix for the local providers
generated in the environment, go to transaction RSBPCADMIN and add the parameter WSP_PFX, In the
value of this parameter, you can specify the prefix. There’re some other customization settings you can
define in transaction code RSBPCADMIN:
○ Parameter WSP_MAX_SP: set maximum memory
○ Parameter WSP_MAX_PR: set maximum number of local providers
○ Parameter WSP_SIDX: if the value is “X”, then generation of master data (SID) is allowed
4. In the Data File field upload a comma-separated value (CSV) file and enter the following format information
about the file:
○ The number of the header row
○ The number of the first data row
○ The character that is used as separator
○ The character that is used as a field delimiter
○ Select the character that is used as decimal mark.
○ Select the format of the date.
 Note
The CSV file must contain transaction data (for planning) and must have columns that represent
dimensions and key figures.
Choose Next.
5. In Map InfoObjects you can map your dimensions to SAP BW InfoObjects, or you can manually enter the
data type of a column. Select at least one key figure. In this step you can also enable data auditing for the
new provider.
 Note
When you map a dimension to an existing SAP BW InfoObject, its master data and hierarchy can be
used directly by the local provider. The dimensions that are not mapped to SAP BW InfoObjects receive
their master data from the uploaded CSV file.
When you map a column to a BW InfoObject, you have three options:

○ Map to a global BW InfoObject
○ Map to a global BW InfoObject and select the checkbox Generate Local InfoObject to create a local
InfoObject
○ Map to an existing local InfoObject, which are InfoObjects created in the current environment
For information about how to create a local dimension directly from a dimension list, refer to Creating
Local Dimensions [page 56].
A local InfoObject (dimension) has the same metadata as the global BW InfoObject from which it was
created. The local InfoObject inherits master data from the global BW InfoObject; master data changes in
the global BW InfoObject are reflected in the related local InfoObject. Also, new members are visible only in
the local InfoObjects and overwrite the property values of global members (members from the global BW
InfoObject).
Choose Next.
6. In the Create Model step you can create a new model that uses the local provider. If you do not need to
create a model at this time, you can skip this step.
 Note
Models that contain a local provider cannot be exported.
7. Review your changes and choose Done.
Updating Local Providers
1. Go to the Administration page, and in the Modelling section, choose InfoProviders.

2. On the screen that appears, choose Local Providers, then select the required provider and choose Update.
3. In the Data File field upload a comma-separated value (CSV) file and enter the following format information
about the file:
○ The number of the header row
○ The number of the first data row
○ The character that is used as separator
○ The character that is used as a field delimite.
○ Select the character that is used as decimal mark.
○ Select the format of the date.
 Note
The CSV file must contain transaction data (for planning) and must have columns that represent
dimensions and key figures.
Choose Next.
4. In Map InfoObjects you can map your dimensions to SAP BW InfoObjects, or you can manually enter the
data type of a column. Select at least one key figure. In this step you can also enable data auditing for the
new provider.
 Note
When you map a dimension to an existing SAP BW InfoObject, its master data and hierarchy can be
used directly by the local provider. The dimensions that are not mapped to SAP BW InfoObjects,
receive their master data from the uploaded CSV file.
Choose Next.
5. Review your changes and choose Done.
Displaying Details for Local Providers
1. Go to the Administration page, and in the Modelling section, choose InfoProviders.

2. On the screen that appears, choose Local Providers, then select the required provider.
The following information is displayed:
○ The local provider's name and description
○ The aggregation level that was generated automatically
○ The query that was generated automatically
○ Data auditing settings
○ The dimensions of the provider
Data Auditing
When creating or updating a local provider you can choose the data auditing settings as follows:
● When you choose Enable Data Audit, the system automatically creates the necessary auditing dimension.
● When you choose Activate Data Audit, the system begins to log information when data is changed or new
data is entered.
Work Status
If a local provider has dimensions that are mapped to SAP BW InfoObjects, you can use work status for the
models that are built on that local provider.
Planning and Reporting
Besides the default aggregation level that is generated automatically, you can also create new aggregation
levels with transaction RSPLAN.
You can also create new queries on aggregation levels with BW modeling tools. Queries can be consumed
through the Business Planning and Consolidation Web client or the Analysis Office add-in.
You can find the default query as follows:
1. Go to Library and choose New Worksheet.

2. Choose Search and from the Description dropdown list select Default Query.
3. To find the query, enter the initial string of the default aggregation level.
 Note
The default aggregation level is created on all dimensions of the local provider. The default query is based
on the default aggregation level and does not have any filters or variables.
7.4 Consolidation
Finance departments of a corporation use legal consolidation to consolidate numbers from subsidiaries and
produce consolidated financial statements of this group of legal entities at the end of a financial period.
This section focuses on the consolidation model set up and relevant settings required for the various tasks that
are required to successfully perform legal consolidation using SAP Business Planning and Consolidation.
This section also discusses the configuration of business rules, including how to set up currency translations,
intercompany eliminations, copy opening tasks, and other business rules in Planning and Consolidation
Administration. Business rules provide the mathematical foundation for SAP Business Planning and
Consolidation models, allowing users to manage both management and legal consolidation reporting.
Features
You perform the following activities in Business Planning and Consolidation during the financial consolidation
process:
● Initialize opening balances at the start of a new reporting cycle.

● Enter amounts for each entity.
● Match intercompany transactions. For example, AR/AP reconciliation.
● Convert local currency data to the desired group reporting currencies.
● Generate all the consolidation entries for the desired groups of entities, such as:
○ Ultimate ownership calculation
○ Elimination entries for intercompany revenue, investments, and profit in inventory
○ Adjusting entries
○ Reclassifications
○ Minority calculations and other calculations
● Make the final validation.
● Generate a consolidation report.
Activities
To enable users to generate consolidated financial statements, you should configure the legal model, and set
up the legal and statutory consolidation business rules, in order to perform the activities required in the
generation of consolidated statements of a group of legal entities.
To set up your consolidation environment, you do the following:
● Create the legal consolidation environment and set the necessary parameters. See Create an Embedded
Environment [page 65].
● Create required InfoObjects and InfoProviders and maintain required InfoObject attributes in BW modeling
tools. See Create InfoObjects and InfoProviders [page 66] and Maintain InfoObject Attributes [page 69].
● Create the consolidation model. See Create or Modify a Consolidation Model [page 80].
● Enable business rules. See Business Rules Management [page 83].
● Make sure the EXCHANGE RATE InfoProvider and OWNERSHIP InfoProvider are maintained in Business
Warehouse. See Create or Modify a Consolidation Model [page 80].
● Define tasks order in task sequences. See Set Task Sequence [page 80].
● Set the work status, which is optional.
● Set the journal template and validation criteria. See Journal Administration [page 140].
7.4.1 Create an Embedded Environment
If you have an existing environment, for example for planning or reporting, you can use this environment to host
your legal consolidation. Using the environment for planning or reporting as a basis to build consolidations
allows you to share the relevant dimensions, such as account, with your consolidation environment.
Related Information
Set up a Consolidation Model [page 65]

Set Task Sequence [page 80]
Preparations for Executing Consolidation Tasks [page 82]
Load Data [page 82]
7.4.2 Set up a Consolidation Model
Since SAP Business Planning and Consolidation directly consume Business Warehouse data, you must prepare
InfoObjects (dimensions) and related attributes (properties) in BW to be used by the consolidation engine of
SAP Business Planning and Consolidation.
BW back-end preparation includes the following tasks:
1. Create the required InfoObjects. See Create InfoObjects and InfoProviders [page 66].
2. Maintain the InfoObjects with required attributes. See Maintain InfoObject Attributes [page 69].
3. Create required InfoProviders, such as DataStore Objects (advanced) and CompositeProviders and input
relevant InfoObjects. See Create InfoObjects and InfoProviders [page 66].
4. Create aggregation levels based on the InfoProviders. See Aggregation Level.
After that you can create a Consolidation model and define it in the SAP Business Planning and Consolidation
web client, including adding InfoProviders with aggregation levels predefined in BW to the Consolidation model,
mapping InfoObjects to corresponding Business Planning and Consolidation dimension types and mapping
attributes of the InfoObjects to related Business Planning and Consolidation dimension properties. For detailed
settings, refer to Create or Modify a Consolidation Model [page 80].
Upon successfully creating the Consolidation model, you can select one or more of the following consolidation
business rules that need to be implemented:
● Currency Conversion
Conversion of local currency data to the desired reporting currencies
● Account-based Calculations
To calculate and store amounts that are required for purposes of account-based calculations
● Carry Forward
Initialization of beginning balances when a new fiscal cycle starts
● Intercompany Booking
Matching intercompany transactions
● Eliminations and Adjustments
Generation of all consolidation entries for the desired groups of entities. For example, eliminations,
adjustments, reclassifications, and minority calculations.
Consolidation business rules allow the automated processing of data to render a consolidated set of financial
statements. This is commonly thought of as eliminations of investments in subsidiaries, adjustments of
minority interest, reclassifications, and any other postings depending on the nature of the consolidation
methodologies required.
7.4.2.1 Create InfoObjects and InfoProviders
Follow these guidelines to create InfoObjects and InfoProviders that can be used by the Consolidation engine of
Business Planning and Consolidation.
In SAP Business Planning and Consolidation, a consolidation model requires the following types of
InfoProviders to be mapped from Business Warehouse:
● CONSOLIDATION InfoProvider (Mandatory)

This is the main InfoProvider containing all financial data. All consolidation postings such as eliminations,
and minority interest calculations are posted in this InfoProvider.
● OWNERSHIP InfoProvider (Mandatory)
This manages the organization structure and ownership percentages by defining ownership details such as
the consolidation scope, method, and percentage of shares owned by the holding company or groups.
● RATE InfoProvider (Optional)
This stores all currency exchange rates for the different rate types, such as average and spot rate. Currency
conversion applies to consolidation models to which a corresponding RATE InfoProvider has been
referenced, where the appropriate exchange rates are searched for each relevant currency.
● SOURCE InfoProvider (Optional)
This can be used as source data if a user has a non-planning InfoProvider that contains the source data for
consolidation. If you refer to this InfoProvider, then you must make sure it contains the same dimensions
(InfoObjects) as defined in the Consolidation InfoProvider.
 Note
For the two mandatory CONSOLIDATION and OWNERSHIP InfoProviders, you must make sure they contain
inputtable InfoProviders, such as DataStore Object (Advanced) or CompositeProviders that contain
DataStore Objects (Advanced).
You also need to create the InfoObjects required by the Consolidation engine of Business Planning and
Consolidation that match various Business Planning and Consolidation dimension types and input them into
different types of InfoProviders. You can choose the names of these InfoObjects, but we suggest that you name
them according to the dimensions you are going to match in the Business Planning and Consolidation web
client. These dimension include:
Business Planning and Consolidation dimensions
Dimension Description
Account (CONSOLIDATION) Members of this dimension are, for example, Revenue or Sal
aries.
Account (RATE) Members of this dimension are used to detail the different
types of rate, for example, Average or End-of-period.
Account (OWNERSHIP) Members of this dimension are, for example, METHOD (con
solidation method), POWN (ownership percentage), and
PCON (control percentage).
Category Contains the types of data you are going to track, such as
Actual, Budget, and Forecast. You can also set up categories
to store versions, such as BudgetV1 and BudgetV2.
Audit Used in the business rules of a reporting consolidation

model to segregate input data.
Subtable (FLOW) Breaks down account activity or flow into sub-units.
Entity (CONSOLIDATION) Contains the business units that are used to drive the busi
ness process. Depending on your model design, the Entity
type can be, for example, an operating unit, a cost center, or
a geographic entity.
Entity (RATE) Used to store multiple tables of rates, if desired; otherwise,

the R_Entity dimension may be limited to one dummy mem
ber, typically named GLOBAL.
Intco Contains the intercompany codes for the entities.
Time Contains the periods for which you store data.
Currency (CONSOLIDATION) The currency type dimension is required if the customer re
ports on local currency and translated values.
Dimension Description
Currency (RATE) This dimension is used to store each applicable local cur
rency.
Group Represents the relationship of entities and consolidation

scopes for a given consolidation result. It also defines the pa
rent members used in an ownership-based hierarchy.
Time and Category dimensions must be shared by all the InfoProviders involved in consolidation. Other
dimensions, such as Account (CONSOLIDATION), Account (RATE) and Account (Ownership), share the same
Business Planning and Consolidation dimension types but are specific to each InfoProvider, so they have to be
maintained with different members. However, in most cases, we recommend that you use the same
dimensions across InfoProviders as it is easier to maintain, as follows:
● The ENTITY dimension of the CONSOLIDATION InfoProvider can be the same as that used in the
OWNERSHIP InfoProvider or it must contain the appropriate matching members if different.
● The GROUP dimension used must be the same in the OWNERSHIP InfoProvider and the CONSOLIDATION
InfoProvider.
● The CURRENCY dimension of the CONSOLIDATION InfoProvider can be the same as that used in the RATE
InfoProvider, or it can be different if it is maintained with appropriate matching members.
 Note
The TIME dimension must use the 0FISCPER InfoObject in Business Warehouse inside all InfoProviders
referenced by the Consolidation model.
The relationships between these Business Planning and Consolidation dimensions and different types of
InfoProviders are shown in the following table:
Relationships of InfoProviders
Business Planning
and Consolidation Di
mension Dimension Type CONSOLIDATION OWNERSHIP RATE
Account (Consolida A √
tion)
Account (Ownership) A √
Account (Rate) A √
Audit D √
Flow S √
Category C √ √ √
Entity (Consolidation) E √ √
Entity (Rate) E √
Business Planning
and Consolidation Di
mension Dimension Type CONSOLIDATION OWNERSHIP RATE
Intercompany I √ √
Time T √ √ √
Group G √ √
Currency (CONSOLI R √
DATION)
InputCurrency R √
The Source InfoProvider shares the Business Planning and Consolidation dimension type with the
CONSOLIDATION InfoProvider. As shown in the table, the RATE InfoProvider containing exchange rates must
specifically have Account (Rate), Category, Entity (Rate), Time, and InputCurrency dimensions. The
OWNERSHIP InfoProvider storing the ownership details must specifically have Account (Ownership), Category,
Entity (Consolidation), Intercompany, Time, and Group dimensions.
Activities
1. Go to the BW Modeling Tools.

2. Refer to the required Business Planning and Consolidation dimensions and create corresponding
InfoObjects for each. For more information about creating InfoObjects, refer to Creating Characteristics.
3. Maintain the required attributes of the InfoObjects. See Maintain InfoObject Attributes [page 69].
4. Create the following four InfoProvider in the types of: CONSOLIDATION, OWNERSHIP, RATE, and SOURCE.
5. Input corresponding InfoObjects to each InfoProvider.
6. Create aggregation levels based on the InfoProviders.
 Note
When adding the InfoProviders to the Consolidation model you want to create, you must select an
aggregation level based on the InfoProvider to make sure only the desired dimensions required for legal
consolidation are selected.
After these InfoProviders and InfoObjects are correctly maintained, you can further add and map them when
creating or modifying a consolidation model in SAP Business Planning and Consolidation. For detailed settings,
refer to Create or Modify a Consolidation Model [page 80].
7.4.2.2 Maintain InfoObject Attributes
Several dimension properties are required by the consolidation engine of SAP Business Planning and
Consolidation.
When you map the required InfoProviders into a consolidation model, all the underlying dimensions will
automatically be referred into the dimension library. To ensure the correct operation of consolidation and
related processes, such as currency translation, simulation, and eliminations and adjustments, several
dimension properties are required by the consolidation engine of SAP Business Planning and Consolidation,
and you need to ensure that these properties are maintained in Business Warehouse so that they could be
further mapped while creating the consolidation model in SAP Business Planning and Consolidation. You
should also ensure that these properties are maintained with the appropriate values of the consolidation
process for your business requirements.
Account Dimensions
The Account dimension defines the chart of accounts for the model and how these accounts are calculated and
aggregated. Any dimension that is assigned the type A is considered an Account dimension. Each InfoProvider
can have only one account-type dimension.
The following table details the account dimension properties:
Account Dimension Properties
Property Name Length Description of Property Values
ACCTYPE 3 This property can have the following

values:
● INC for income

● EXP for expense
● AST for asset
● LEQ for liabilities and equity
DIMLIST 20 Used to group the accounts for use in

business rules. For example, using the
DIMLIST property value can help re
duce the size of the FXTRANS table.
Several DIMLIST properties can be used
for one dimension.
RATETYPE 10 This property determines the business

rules to be applied when translating any
given account from local currency to re
porting or group currency.
● When left empty, no currency

translation rules are matched and
therefore, no translation will be
performed.
● When the value is defined as the
name of a currency translation
rule, that translation rule will be ap
plied in the translation.
ELIMACC 20 Used in the elimination process and

represents the difference account to
which the accounts to be eliminated are
posted.
 Note
In an OWNERSHIP InfoProvider, all required O_Account dimension members, including POWN, PCON,
PCTRL, METHOD, and PGROUP, need to be maintained by an administrator.
Category Dimensions
The properties required in this dimension as described in the table below are for three business rules: currency
translation, eliminations and adjustments, and copy opening balances.
For simulation purposes, or to analyze the variances from one set of data to another, you should mix-and-
match different rates and values of different data categories from different periods. For example, a user might
want to compare ACTUAL with BUDGET values when both are translated at the ACTUAL rates, or this year's
ACTUALS with last year's ACTUALS, both being translated using last year's rates.
This can be done by either creating an additional simulation CATEGORY, such as Actual_at_Budget_rate or
similar, or adding an extra dimension to the MAIN InfoProvider, where all the simulated cases can be stored.
There is no need to copy the input values to all models for all the desired simulations. A few definitions stored in
some specialized properties of the CATEGORY or the FX simulation dimension inform the translation procedure
where to read the input values and where to write the translated results.
To minimize the impact of the different simulations on the size of the database, it is also possible to tell the
system to store only the difference between the default results and the simulated scenarios.
When using the simulation categories in the MAIN InfoProvider, simulated translations are stored in additional
members of the Category dimension. These categories have non-blank values for one or more of the properties
in the table below.
Any dimension that is assigned the type C is considered to be a Category dimension.
Category Dimension Properties
FX_SOURCE_CATEGORY 20 The category for the source (LC) data. If

blank, it is the current category.
RATE_CATEGORY 20 The category from which the rates are

read.
RATE_YEAR 4 The year from which the rates are read.
The value can be absolute, such as

2008 or 2009, or a relative value, such
as -1, -2, +1, +2. If blank, it is the same
as the source.
RATE_PERIOD 10 The period from which the rates are

read.
The value can be absolute, ssuch as

DEC or FEB, or a relative value, such as
-1, -2, +1, +2. If blank, it is the same as
the source.
FX_DIFFERENCE_ONLY 1 If Y, only the difference between the de

fault values and the simulated values is
stored.
The business rules for copying opening balances can be controlled by assigning special properties to the
category dimensions. If used, these properties affect the execution and are defined in the following table:
Special Properties for Category Dimensions
CATEGORY_FOR_OPEN 20 ● Blank
The category for the opening bal
ances is the same.
● Not blank
The ID of the category from which
to read the opening balances.
OPENING_YEAR 4 ● Blank
Read the opening balances from
the year before the current year.
● Not blank
Contains the year from which to
read the opening balances. It can
be an absolute or a relative
amount.
OPENING_PERIOD 10 ● Blank
Read the opening balances from
the last period of the year.
● Not blank
Contains the period from which to
read the opening balances. It can
be an absolute or a relative
amount.
Audit Dimension
You should consider the following rules:
● Mandatory for the elimination business rules.

The DATASCR dimension is required for elimination and consolidation business rules. For example,
automatic elimination works only when you have a base level value of data source type A.
● Mandatory for the consolidation business rules.
It is required as the results destination. For example, you can define, by source data source, a specific
destination data source where the resulting postings should be posted.
Any dimension that is assigned the type D is considered to be an Audit dimension.
The following table details the data source dimension properties:
Data Source Dimension Properties
IS_CONVERTED 1 ● Y
The data source is converted.
● N
The data source is not converted.
● G
Converts the data source from the
reporting currency to the group
currency. That is, the members are
copied from the reporting currency
of the GROUP that is being trans
lated into the currency member
corresponding to the specified
group.
IS_CONSOL 1 ● Blank
łÙŸ²ˆÃG—q¶�ƒ~^5™—¾ÑA yÓéøŒ¢S0æâƒ€J.�{`¡Ým/]ãÃÇL†…Vc=6Á„ ²sZE
solidated amounts .
● Y
Standard setting to consolidate
data.
DATASRC_TYPE 1 ● I - input
● M - manual journal entry
● A - automatic adjustment
● L - level
This is used in consolidation by
level to move prior level elimina
tions into a data source with prop
erty DATASRC_LEVEL of Y in the
GROUP dimension.
COPYOPENING 1 ● Y (or blank)

The member is copied.
● N
The member is not copied.
OPENING_DATASRC 20 ● Blank
The data source is the same as the
source member.
● Non-blank
Contains the ID of the desired des
tination data source for the copy.
Entity Dimension
The Entity dimension defines the organizational structure of the business units for your model and how the
units aggregate. Any dimension that is assigned the type E is an Entity dimension. Each model can have only
one entity-type dimension.
The following table details the entity dimension properties:
Entity Dimension Properties
CURRENCY 20 Local currency used by the entity. This

currency must be defined in the Input
Currency dimension.
INTCO 32 Used for maintaining the trading part

ner of an entity. Must be maintained to
gether with the INTCO attribute of the
Entity dimension.
FX_TYPE 20 Assigns a set of translation rules to an

entity. Different entities can use differ-
ent sets of rules. Optional.
CONTROL_LEVEL 1 Used on Controls to indicate the control

level:
● 4 (or blank) – Comprehensive (the

most strict option)
● 3 – advanced
● 2 – Standard
● 1 – basic
Optional
CTRL_CURRENCY_NOT_LC 1 Used in Controls. If marked as Y, the

controls validation will be performed on
a user-specified reporting currency
other than the local currency for this
entity. This setting affects the loaded
data level only.
ELIM 1 If mark as Y, it will be considered as an

Elimination entity, which will be used to
hold elimination results in US elimina
tion or legal consolidation. Optional.
OWNER 60 Used for work status. Optional.
Intercompany Dimension
The Intercompany dimension (I) defines the intercompany codes for entities in consolidation and ownership
InfoProviders.
Intercompany Dimension Properties
ENTITY 32 Can be validated against the Entity di

mension. Blank fields are allowed.
Must be maintained together with the

INTCO attribute of the Entity dimen
sion.
Currency
The currency type dimension is required to report on local currency and translated values. The required
property for currency dimension is the following:
Currency Dimension Type
Description of Property Val

Dimension Type Property Name Length ues
R CURRENCY_TYPE 1 ● CURRENCY_TYPE
○ L - local currency
○ R - reporting cur
rency REPORTING
(length 1)
○ T - transaction cur
rency
● Reporting: Y or blank
Group
The required properties for a separate group dimension are the following:
Group Dimension Properties

G GROUP_CURRENCY 20 Can be any valid reporting

currency. Used for currency
translation.
This property can only be

used on CURRENCY mem
bers with the property CUR
RENCY_TYPE of G and, in
this case, it must contain a
valid ID from the CURRENCY
dimension with the property
CURRENCY_TYPE of R.
G PARENT_GROUP 20 If you want to do the consoli

dation by level, you must in
dicate by this property the
higher level group of each
group. The presence of the
property enables the Groups
hierarchy. Though the prop
erty is populated with group
hierarchy information, it does
not generate a true hierarchy
made up of members in the
Group dimension.
The property itself has no de

fault value. The value you en
ter must be a valid ID from
the Groups dimension. If this
property is blank, the owner
ship-based hierarchy from
the group dimension of the
OWNERSHIP InfoProvider is
used. The Groups hierarchy
defined by this property is
also displayed and used in
Ownership Manager.
G ENTITY 20 Blank or a valid Entity ID.
Since Group is only a gather

ing of entities that does not
store any amounts, it needs a
corresponding entity to store
the aggregated consolidated
amounts. For example:
Group member ID G_E1 has
the Entity property value E1.
It corresponds to Entity di
mension member E1.
If this property is filled with a

valid ID, and the property
STEntityORE_ENTITY is set
to Y, the results of the cur
rency translation for the cur
rent group are also copied
into this entity.
 Note
The ENTITY attribute
should use the same In
foObject as the ENTITY
dimension in the model.
Also, the value entered in
the ENTITY attribute
should be a valid entity
ID.
G STORE_GROUP_CURR 1 Used for currency transla

tion.
● Y
By default the results of
the translation into a
Group currency are writ
ten in both the Group
member and in the Cur
rency member of the
currency dimension.
● N (or blank)
If only the Group mem
ber is to be stored, set
this property to N.
G STORE_ENTITY 1 ● Y
If you want to store in
the ID entered in the En
tity property.
● Blank
If you do not want to
store in the ID entered in
the Entity property.
G STAGE_ONLY 1 This property controls the

way the converted values are
saved when performing a
multi-level conversion of
groups.
This property can only take

the values Y, E, or N (blank).
G CURRENCY_TYPE 1 Specifies whether the Group

member is a consolidation
scope (CUR
RENCY_TYPE=G) or the de
fault member for that dimen
sion (CUR
RENCY_TYPE=N)：
● G - Group member
● N - Non-group member
G FIRST_CONS_DATE 10 ● Blank
Management model
● YYYYMM
Indicates the month and
year of the consolida
tion.
Flow Dimension
The flow type dimension is optional, but its use is highly recommended. This dimension allows you to track
changes within account activities, such as opening balance, additions, subtraction, and currency translation
adjustments. If you do not require this level of detail, leave the business rule tables blank for the sub-table field.
Flow is similar to the movement type in SAP ERP.
If Flow is included in a model, you can use it in the following ways:
● The currency translation procedure can detail the changes in the balance sheet generated by fluctuations
in the exchange rates
● The consolidation procedure can detail the eliminations applied to the movements of the balance sheet
accounts.
Any dimension that is assigned the type S is considered a Flow dimension.
If you choose to use a flow type dimension, the following properties are required:
Flow Dimension Properties
FLOW_TYPE 12 ● OPENING - opening

● VARSCP - variation in scope (ge
neric)
● VARSCPMETH - variation in scope
method
● VARSCPPERC - variation in scope
percentage
● VARSCPNEW - variation in scope;
new company
● VARSCPLEAV - variation in scope;
sold company
● CLOSING - closing
● NONE - no flow
● Blank - all other flows
DIMLIST 20 Used to group the flows for several

business rules
Flow dimensions should contain dimension members that require the following FLOW_TYPE property values:
● OPENING
● CLOSING
● VARSCP
Optional - All dimensions could be mapped with the ENABLEJRN property and the DIMLIST property. For
detailed information about the property ENABLEJRN, refer to Limits to Dimension Members for Journal Entries
[page 144].
Activities
● To make sure every dimension (InfoObject) possesses the required dimension attributes for a
consolidation scenario, you need to maintain the dimension structure beforehand in BW modeling tools.
For detailed information, refer to Creating Characteristics.
● To make sure the dimension master data is correct, you can maintain the master data either in BW
modeling tools, or you can maintain the dimension master data directly in the SAP Business Planning and
Consolidation web client. Refer to Dimension Management [page 51] for details on how to maintain
dimension master data.
After dimension (InfoObject) attributes and its master data are correctly maintained, you can further map
those attributes when creating or modifying a consolidation model in SAP Business Planning and
Consolidation. For detailed settings, refer to Create or Modify a Consolidation Model [page 80].
7.4.2.3 Create or Modify a Consolidation Model
A model is either a planning model or a consolidation model. After completing relevant Business Warehouse
back-end settings, you can create and define a consolidation model in the Business Planning and Consolidation
web client.
Within the same environment, multiple consolidation models may exist, each one pointing to its own
consolidation, rate, and ownership InfoProviders. Multiple consolidation models can share the same
consolidation or rate or ownership InfoProviders, if appropriate.
To create a consolidation model, you must map BW InfoProviders to a CONSOLIDATION InfoProvider and an
OWNERSHIP InfoProvider. You have the option to map BW InfoProviders to an EXCHANGE RATE InfoProvider
and a SOURCE InfoProvider. Then, you need to map InfoProvider dimensions to dimension types required by
the SAP Business Planning and Consolidation consolidation engine, as well as map InfoObject attributes to
dimension properties required by the consolidation engine.
1. In the navigation panel, go to Administration Modeling Models .

2. Select the consolidation model you want to maintain or create a new consolidation type model.
3. Select the corresponding InfoProviders for the CONSOLIDATION InfoProvider and the OWNERSHIP
InfoProvider and, if needed, select corresponding InfoProviders for the EXCHANGE RATE InfoProvider or
SOURCE InfoProvider.
4. Click Go to Mapping/Review Mapping to navigate to the dimension mapping view for one of the
InfoProviders (CONSOLIDATION, OWNERSHIP, EXCHANGE RATE, or SOURCE) you want to change.
5. Choose an aggregation level for the InfoProvider.
6. Map the InfoObjects to related dimension types.
7. Click Go to Mapping/Review Mapping for each dimension to navigate to the dimension property (attribute)
mapping view.
You will be able to see all the pre-delivered dimension attributes that may be useful in a consolidation
scenario. The attributes with a red asterisk are mandatory. You can use the dropdown box on the right side
to map an existing dimension (InfoObject) attribute to the dimension properties required by consolidation
engine.
8. Navigate to Create New Model Advanced Settings , then select superior compounding members for
each dimension member. For Account and Time type dimension members, fixed superior compounding
dimension members must be specified. For others, this value is optional. Once a fixed superior
compounding member is selected, you cannot select other superior compounding members in
consolidation calculations.
9. After finish all the settings, click Save and Validate to finish creating the Consolidation model.
7.4.3 Set Task Sequence
When you define a task sequence, you determine which consolidation tasks you would like to trigger from
Consolidation Monitor, as well as set the sequence of tasks to be displayed in Consolidation Monitor.
For each business rule type below is a corresponding consolidation task type:
● Currency translation
● Account-based calculation
● Intercompany booking
● Carry forward
● Elimination and adjustment
● US elimination
If you have enabled work status and controls for models, two additional rule types are available:
● Work status
● Controls
To add a task to a model, you need to define general settings and specific settings for the task. In General
Settings, you specify the periods to which the task applies. By selecting Every Period with 000 Period or Every
Period without 000 Period, you define the frequency as every period. 000 means a financial period 000 that
starts before all other existing periods is included. By entering one or more values manually in the Periods field,
you specify on which periods the task is executed. You can also specify the category dimension members in
General Settings. Later, when users execute tasks in Consolidation Monitor, only the tasks whose periods and
category members match the context time and category dimension members display.
In Task Specific Settings, you use Other Dimension Filter to restrict members for dimensions other than the
ones in General Settings. To do this, follow this format:
● Prefix for hierarchy version: !

● Prefix for InfoObject name: #
● Prefix for dimension members: !
● Compounding dimension member: <Superior dimension member>/<dimension member>
● Dimension member separator: ,
● InfoObject (Dimension) separator: ;
 Example
The superior dimension of C1000 and C2000 is China. If you want to choose C1000 and C2000 of the
entity dimension ZPAKENT from the V1 version of hierarchy H1 and you select P1 from the user-defined
dimension PRODUCT, you enter the formula below in the Other Dimension Filter field:
ZPAKENT=H1!V1#ZPAKENT!China/C1000,H1!V1#ZPAKENT!China/C2000; PRODUCT=P1
Through the task-specific settings you can customize tasks of the same task type and use different task names
to identify these tasks. For example, you can define two account-based calculation tasks and give them
different task names. Then you can go to Consolidation Monitor and select either of the account-based
calculations to trigger the corresponding task.
Activities
To add or modify business rule tasks, follow these steps:
1. Go to Administration Rules Task Sequences .

2. Click the hyperlinks of the consolidation model for which you want to define task sequences.
3. Click Add to add a new task. You are required to enter a task name. If you enter a task name and
description, the description displays as the name of the task in Consolidation Monitor.
4. Define General Settings and Task Specific Settings.
5. After adding the tasks, you can delete a task or change its sequence in the task list.
6. Click Show All Settings to further set the task sequence:
○ To enable dependencies among tasks based on their sequence in the task list, select Enable Task
Dependency. After that when you re-execute a task in Consolidation Monitor, the status of all the tasks
following that task is reset to To be Executed as well.
○ To allow users to further change the selection range on which you execute business rules, controls, and
work statuses when clicking the Execute button in Consolidation Monitor, select Allow to Change
Settings in Consolidation Monitor.
○ To enable the real-time consolidation Periodic check, select Enable Data Submit Check. This allows you
to drill down to related S/4 HANA reports to show the data submitted by entity or group. For detailed
information, refer to SAP note 2375986 .
7.4.4 Preparations for Executing Consolidation Tasks
SAP Business Planning and Consolidation leverages Business Warehouse planning functions to execute
consolidation tasks.
Before implementing a scenario for consolidation, you first need to install all necessary InfoObjects including /
CPMB/RULE and /CPMB/RENT and required planning functions including /CPMB/LAUNCH_LOGIC and /
CPMB/WRITE_BACK. For detailed steps, refer to the section “Install InfoObjects and Planning Function Types
Necessary for Consolidation (Embedded only)” in the Installation Guide available on the SAP Help Portal.
After you enable these InfoObjects and planning function types, you can trigger consolidation tasks either
through the planning function in the Business Warehouse backend or in Consolidation Monitor in the Business
Planning and Consolidation web client.
Consolidation tasks, such as currency translation as well as matching and elimination of inter-unit balances,
are predefined functions in Business Planning and Consolidation to calculate and post amounts required to
support common accounting activities.
For each predefined function, there are one or more business rule tables that provide the flexibility for you to
customize the functions to meet your specific business needs without having to understand scripting or
programming. For more information about the business rules delivered with SAP Business Planning and
Consolidation, see Business Rules Management [page 83].
7.4.5 Load Data
Perform these steps to load your data.
1. Load the exchange rate to the RATE InfoProvider.

The RATE model stores the exchange rates for currency translation. You should make sure the exchange
rate data is already correctly maintained inside the RATE InfoProvider that is referenced by your
consolidation model.
2. Input ownership data and calculate ultimate ownership.
SAP Business Planning and Consolidation provides Ownership Manager in Consolidation Center so you can
update the Ownership InfoProvider directly.
3. Load the financial data.
After loading the financial data, use an SAP Business Planning and Consolidation report to validate that the
numbers reconcile with the numbers in the source system.
7.5 Rules
Perform data calculations using business rules.
Business rules are parameter-driven functions within models for calculating and posting monetary amounts in
support of common accounting activities.
More Information
Business Rules Management [page 83]

Controls [page 100]
7.5.1 Business Rules Management
Business rules are parameter-driven functions within SAP Business Planning and Consolidation models for
calculating and posting monetary amounts in support of common accounting activities, such as intercompany
booking, currency translation, and eliminations and adjustments.
To manage business rules in SAP Business Planning and Consolidation, select Planning and Consolidation
Administration Rules Business Rules .
Features
Adding Business Rules to Models
When you create or modify a model, you can add business rules to it. You can add the following types of
business rules:
● Account-based calculation
● Currency translation
● Intercompany booking
● Carry-forward processing to initialize beginning balances when a new fiscal cycle starts
● US Eliminations
● Eliminations and adjustments when generating consolidation entries for a group of entities, such as
eliminations, adjustments, reclassifications, and minority calculations
After adding a business rule type to a model, you must customize it to meet your needs by specifying
parameter values. For example, in Eliminations and Adjustments, you can indicate which balances to read
before calculating an amount, or under which account and audit member to post the calculated amount. In
addition to customizing default business rules, delivered with the IFRS starter kit for instance, you can define
new rules for various types of business processes and add them to a model.
Editing Business Rules
You can edit the list of available rules for a selected type of business rule within a model. You can then edit a
specific rule in the list. You can use standard Microsoft Excel functionality to perform the following actions:
● Select multiple detail record rows

● Copy, paste, and delete detail records by row
● Copy and paste within a cell by right-clicking and selecting a context menu option or using CTRL + C and
CTRL + V
● Copy rows
You can look up members within the cells of a rule by clicking the Lookup icon that appears when you place the
cursor within that cell.
Validating Business Rules
You can verify the detail records of a business rule after modifying it by clicking Validate in the <Rule Name>
page. A message appears displaying a successful status or any errors encountered.
 Note
Currently you can choose text nodes and external nodes as source members of the dimension types
account (A), category (C), audit (D), and flow (S), but not as destination members unless the source and
destination dimensions share exactly the same hierarchy.
Activities
In SAP Business Planning and Consolidation, all business rules need to be run through Consolidation Monitor.
To do this, you need to first define a task sequence after setting up all the business rules and then trigger these
tasks from Consolidation Monitor.
Related Information
Set Task Sequence [page 80]
7.5.1.1 Account-based Calculation Rule
Account-based calculations read and aggregate the values posted to specific combinations of accounts, flow
types, and audit members in order to post the aggregated amount under an alternate destination account, flow
and audit member combination. You may apply this rule for cash flow reporting.
Features
The following dimensions can be specified in order to define source and target members in the calculation:
● Category (C-type dimension)

● Account (A-type dimension)
● Flow (S-type dimension)
● Audit (D-type dimension)
The account-based calculations business rule can invert the sign when posting calculated amounts when
appropriate, which alternates debit and credit amounts.
This rule can also use reference data in other periods and years to determine amounts to post.
This rule also supports year-to-date calculations in period-based models.
You can utilize account-based calculations in legal consolidation models.
7.5.1.2 Currency Translation Rule
You use this to convert local currency values into one or more reporting or group currencies in accordance with
major Generally Accepted Accounting Principles.
Currency translation rules are executed from the Consolidation Monitor in the Consolidation Central area.
Prerequisites
Currency translation applies to consolidation models to which a corresponding EXCHANGE RATE InfoProvider
has been referenced.
When performing currency translation, different exchange rates such as average and period end rates, as well
as formulas, are applied. A currency translation rule contains the necessary rates and logic for a unique
account rate type. The account rate type must exist in the Account dimension in order to be triggered.
However, you can create and name the currency translation rule first, and then assign the RATE_TYPE in the
account dimension to the accounts to which it relates. When currency translation runs, it translates each
account in accordance with the rules defined for the account rate type which has been assigned to that
particular account.
The following list provides a summary of the environment requirements to support currency translation:
● The consolidation model must be assigned an EXCHANGE RATE InfoProvider where exchange rates are
stored.
● The CONSOLIDATION InfoProvider itself must include a currency type dimension and a Group dimension.
● The Currency (R type) dimension must map to the properties:
○ REPORTING, whose values are Y or blank
○ CURRENCY_TYPE, whose values are R for Reporting Currencies, T for transaction currency, or L for
local currency.
● For Consolidation models, the Group (G) dimension must include the following properties:
○ GROUP_CURRENCY, whose values are valid currencies in the previously mentioned Currency dimension
○ CURRENCY_TYPE, whose values are G for group currency or N for Non-Group related data, meaning
local data
● The Entity (E type) dimension must include the property CURRENCY, whose values are valid
Input_Currencies. Input currencies are valid Reporting currencies defined in the currency dimension of
the EXCHANGE RATE InfoProvider.
● The Account (A type) dimension must include the property RATETYPE, values of the RATETYPE property
should be names of corresponding currency translation rules.
● The Time (T type) dimension must use 0FISCPER.
● The Audit dimension must include the following properties for currency translation:
○ DATASRC_TYP, whose values include the following:
○ I – Input
○ M – Manual Adjustment
○ A – Eliminations and Adjustments
○ L – Audit level (use only for Elimination and Adjustment)
○ IS_CONVERTED, whose values include the following:
○ N – these members are ignored in the conversion
○ Y (or blank) – these members are converted from LC into the desired currency unless the
members are flagged as requiring manual adjustment; these members have their currency
conversions entered manually
○ G – these members are copied from the reporting currency of the group that is being translated
into the currency member corresponding to the given group
You also need to include the following properties if they are mentioned in other business rules:
○ COPEOPENING, whose values include the following:
○ N (or blank) – These members are ignored in the copy opening.
○ Y – These members will perform copy opening if it is also specified in the business rule.
○ IS_CONSL, whose values include the following:
○ N (or blank) – These members are ignored in the Elimination and Adjustment.
○ Y – These members will perform Elimination and Adjustment if it is also specified in the business
rule.
○ OPENING_DATASRC, the property enables you to post data on a specific data source when running the
Carry- Forward rules.
● The Flow (S type) dimension is not mandatory for currency translation, but if you include it, the dimension
must include the property FLOW_TYPE.
● The InputCurrency dimension within the applicable EXCHANGE RATE InfoProvider must include the
property MD, whose values are M for multiply rates or D for divide rates.
The default translation reads all values in local currency where currency = LC, applies the correct exchange rate
according to the applicable EXCHANGE RATE InfoProvider, and writes the results in the appropriate reporting
currency (USD, EURO, and so on).
Rate selection
For the selection of the correct rate, the following rules apply:
● The source currency is derived from the property CURRENCY of the entity being translated.
● The rate to be applied during translation, such as Endflow, Histrate, and so on, is derived from the
property RATETYPE of the account being translated.
● The valid rates are those corresponding to an account of the rate model for which the value of the GROUP
property is FX rate.
● The system does not convert any accounts with a rate type that is not a part of the currency translation
business rules.
 Note
The default currency translation supplied with the product for multi-currency models performs a cross-rate
translation; it multiplies the amount in local currency by the ratio between the rate of the destination
currency and the rate of the source currency. This allows the model to use only one table of rates for
translating any source currency into any destination currency.
 Note
Other types of translations can be defined by using the currency translation business rules tables and the
relevant properties in the Currency and InputCurrency dimensions to support the ability to use different
tables of rates by reporting (destination) currency and the ability to distinguish between Multiply currencies
and Divide currencies.
Preconditions for Running Currency Translation
Currency translation can run in the following two modes:
● Reporting currency mode

Reporting currency mode converts transaction data recorded in a local currency to the specified reporting
currency. To run currency translation in Reporting mode, make sure the entity member is selected in the
entity hierarchy tree on the left side of the Consolidation Monitor.
● Group mode
Group mode converts subsidiaries' data to a group's currency. This is mainly used before consolidation. To
run currency translation in Reporting mode, make sure the Group member is selected in the entity
hierarchy tree on the left side of the consolidation monitor.
● Some dimensions, such as Account, Entity, and Currency, must contain appropriate properties as noted in
the following table:
Model Dimension Property Description
Main Account RATETYPE The value of the RATETYPE

property must be the name
of a currency translation
rule, such as AVG, END, and
ENDFLOW.
Main Entity CURRENCY The CURRENCY property de

notes the local currency for
the current entity. For exam
ple, for entity US, the cur
rency is USD; for FRANCE,
the currency is EUR. The
value of this property must
be a valid member of the In
putCurrency dimension.
Main Currency CURRENCY_TYPE The CURRENCY_TYPE prop

erty specifies the currency
type, and it should take the
following values:
○ L (local currency)
○ R (reporting currency)
○ G (group, for compati
bility on migrated mod
els only)
Main Group CURRENCY_TYPE The CURRENCY_TYPE prop

erty specifies if the member
is a group/sub-group or is
used to enter local data:
○ G (Group)
○ N (Non-Group, used for
data input)
The following properties in the Audit and Flow dimensions are mandatory:
Dimension Property Description
Audit DATASRC_TYPE The DATASRC_TYPE property signifies

the audit member type. The following
four values are available:
● I (input)
● M (manual adjustment)
● L ( audit level, for consolidation
only)
● A (eliminations and adjustments)
Audit IS_CONVERTED When the IS_CONVERTED property is

set to N or blank, members are ignored
in the conversion. When set to Y, mem
bers are converted from the local cur
rency to the desired currency.
Flow FLOW_TYPE The FLOW_TYPE property can take

many values, but the most important is
the value CLOSING. The rule of cur
rency translation with
FORCE_CLOSING = Y makes use of
it.
The following properties are needed in the Group dimension:
● The ENTITY property can be blank or a valid Entity ID. It is used to define the link between the group and
the entity and to indicate the entity where the aggregation should be stored. (Refer to the STORE_ENTITY
property below.)
● The GROUP_CURRENCY property can be used only on Group members with the property CURRENCY_TYPE=
G. It must contain a valid ID from the Currency dimension with the property CURRENCY_TYPE = R.
● The STAGE_ONLY property controls the way the converted values must be saved in case of a multilevel
conversion of groups. This property can have the three values Y, E, or N (blank).
● The STORE_ENTITY property can have the values Y or blank. It indicates whether the system copies the
results of the currency translation for the current group into the entity specified in ENTITY property.
● The STORE_GROUP_CURR property can have the values Y or blank. It indicates whether the system stores
the currency translation result in the group currency. Otherwise, the system stores the result only in Group,
not in currency.
● The PARENT_GROUP property defines the group hierarchy. The value of this property should be a valid
Group ID in the dimension.
7.5.1.3 Intercompany Booking Rule
The Intercompany booking function supports the overall Intercompany reconciliation process.
Prerequisites
The following are required to perform Intercompany eliminations within an application:
● Five additional data sources must be defined for Data Source Dimension in IC_ORIGIN attribute. These
data source members will be used for IC Data Calculation, which is the pre-step for intercompany
bookings:
○ I – Source data source to be used in IC Data
○ D1 – My Debit Accounts
○ D2 – Their Debit Accounts
○ C1 – Their Credit
○ C2 – My Credit
● The appropriate business rule table must be set up.
● The Account dimension must define a dedicated hierarchy to include all accounts for Intercompany
booking.
This configuration not only allows intercompany details to be entered for any account, but it also supports an
automatic elimination-by-level for all desired accounts.
 Note
Although not mandatory, Intercompany reconciliation is normally performed in a separate Intercompany

matching application apart from the actual Consolidation application.
Features
The consolidation engine supports a mechanism to perform the matching of the inter-company declarations
among the entities of a group. This mechanism is split into two independent procedures as follows:
● ICDATA: this procedure can be used to copy the declarations of all entities versus a given entity by inter-
company account. Essentially it concentrates into each single entity the declarations of all other entities
versus each entity. This mechanism allows the owners of an entity to run a report matching all its
declaration against what the rest of the world has declared against him, without the need to assign to each
owner read permits into other entities.
● Intercompany Booking: this procedure can be used to automatically generate the bookings that will make
the intercompany declarations match.
By defining “Seller”, “Buyer”, or “Greater” in the business rule booking type, the system can automatically book
the difference by assuming the correct value is Seller, Buyer, or either one with the greater booking value.
By configuring the “Maximum Booking” amount, you can set up the maximum threshold for automatic
booking. Any differences bigger than this maximum value will be kept for manual adjustment later.
Intercompany bookings are executed from the Consolidation Monitor in the Consolidation Central area.
7.5.1.4 Carry-Forward Rule
Carry-forward populates the opening balances for the current year with the closing balances of the last period
of the prior year.
Features
Carry-forward rules are executed from the Consolidation Monitor in the Consolidation Central area.
Carry-forward rules enable you to generate the Opening Balance of any category based on the following
properties:
● Flow_Type in the Flow dimension: the value of this property should be OPENING on the relevant Opening
flow and CLOSING in the relevant Closing flow.
● Category_for_ope, Opening_year, Opening_period in the Category dimension
Carry-Forward rules can be used to initialize a new reporting period with the closing balances of the last
period from the previous year into the opening balances of the current period. It can also copy closing
balances from a designated year ( Opening_year property) and period ( Opening_period property) to
the current period. The designated year and period can be an absolute or relative number. You can also
specify a Category in which to store the closing data using the Category_for_ope property. For example,
you may need to create opening data in a Budget category using data from a Forecast category.
● DataSrc_Type, Opening_Datasrc, Copyopening in the Audit dimension
Currently this procedure is limited to copying the opening balances as found in the Audit dimension
members flagged as I and M in the DATASRC_TYPE property. The procedure copies only the input balances
and their related manual adjustments. The balances generated automatically by the consolidation
procedure ( Audit members flagged as A) are taken into account during the consolidation process by the
consolidation procedure itself.
The Copyopening property enables you to identify the members on which the carry-forward rule should
be executed.
The Opening_Datasrc property enables you to post data on a specific datasource when running the
Carry-Forward rules.
● Within a carry-forward rule, the field Account specifies the Destination account. The property
Same_period enables you to copy the same period balances to the current period. The YTD property
enables you to sum up the balances of YTD to the current period.
7.5.1.5 US Eliminations Rule
US eliminations functionality addresses the posting of intercompany US eliminations in scenarios where a full
legal consolidation is not required.
Prerequisites
The following are required to perform intercompany eliminations within the Consolidation InfoProvider of a
model:
● The InfoProvider must include a dimension of type I (Intercompany).

● The I type dimension must include the property ENTITY, whose values are entity IDs.
● The account (A type) dimension must include the property ELIMACC, whose values are account IDs.
● The entity (E type) dimension must include the property ELIM, whose values are Y or blank.
● The appropriate business rule table must be set up.
When reporting the financial results of a group of entities, you may want to see the results for the group net all
intercompany activity within the group. Therefore, the system identifies intercompany activities, and balances
and posts entries so these activities and balances are fully eliminated when looking at the overall results for the
group.
US eliminations functionality addresses the posting of intercompany eliminations in scenarios where a full legal
consolidation is not required. When utilizing a consolidation model that is shared by the US Eliminations rule
and the Eliminations and Adjustments rule - which is generally called matrix consolidation - a different set of
Entity and Interco dimensions needs to be maintained for the US Eliminations rule. Therefore, two new
types of dimensions are available for US Eliminations: Entity for matrix (P type) and Intercompany for matrix (Q
type).
Except in the case of matrix consolidation, US eliminations normally use consolidation models different from
the models used by legal consolidation.
Intercompany elimination entries should be reflected only in groups in which both the entity and the partner
entity are part of the group. To address this, US eliminations uses a concept known as posting at first common
parent.
The US eliminations business rules define the audit members to eliminate. For each of these audit members
you then define the corresponding destination audit member under which the system should post the
elimination postings.
The values entered in the following properties determine default elimination logic:
Dimension Property Length in Characters Content
Account ELIMACC 20 A valid account against which

the actual intercompany ac
count to be eliminated
should be offset
Dimension Property Length in Characters Content
Entity ELIM 1 Y or blank
Intercompany ENTITY 20 The entity ID corresponding

to this intercompany mem
ber
Currency REPORTING 1 Y or blank
The default elimination logic does the following:
● Scans all base level non-elimination entities, specifically entities having the property ELIM <> Y.
● When the model has a currency dimension, the default elimination logic restricts its action to all reporting
currencies only, which are currencies having the property REPORTING=Y. Data in local currency cannot be
eliminated because it is in different currencies.
● Eliminates all values of the accounts to be eliminated, specifically accounts having the property
ELIMACC<>blank, into the desired plug account, which is the account specified by the ELIMACC property
itself.
● The elimination is posted to the elimination entity immediately below the first common parent. The
common parent is derived as follows:
○ For a particular record the system identifies the two entities for which a common parent must be
found. The first entity is the current entity member and the second entity is the entity corresponding to
the current intercompany member. This entity is obtained by reading the content of the property
ENTITY of the current intercompany member.
○ The system searches in a selected entity hierarchy for the first member that has both entities as
descendants. This is the common parent.
○ Then the system searches the immediate descendants of the common parent for a valid elimination
entity, which is an entity having the property ELIM=Y. This is the entity where the results of the
elimination are stored.
The default elimination logic does its searches in the first organizational structure of the entity dimension.
This can be modified so that the system performs the elimination in all hierarchies that exist in the entity
dimension. If no common parent is found, no elimination occurs. If no elimination entity is found below the
first common parent, the next common parent is searched.
Related Information
Consolidation Monitor [page 15]
7.5.1.6 Eliminations and Adjustments Rule for Legal
Consolidation
You use this type of business rule when performing a legal consolidation process to generate adjustments and
postings that integrate results from subsidiary reporting entities into consolidated financial statements in
accordance with Generally Accepted Accounting Principles.
Eliminations and adjustments are executed from the Consolidation Monitor in the Consolidation Central area.
Prerequisites
Before executing eliminations and adjustments, do the following:
● Enter any ownership changes into the OWNERSHIP InfoProvider, such as the acquisition of a new
company, the sale or transfer of shares, and divestitures.
● Update consolidation methods and accounting methods as necessary.
● Update percent ownership and percent control within the group.
 Note
Ownership calculations can be run to calculate the overall ownership within each group. Consolidation
parameters assigned to each entity within each group then need to be validated within the ownership cube.
You must have the following items in your consolidation model before performing the eliminations and
adjustments:
● OWNERSHIP InfoProvider
Stores the overall ownership and percentage control of each entity by group on a category and time
dependent basis as well as the corresponding method of consolidation to apply
● Group dimension
Provides the ability to store consolidated results by the group to which they relate
● Currency dimension
Provides the ability to store consolidated results in the currencies specified for each group
● Methods and Method-based Multipliers and Consolidation
Define the formulas to use in calculating the amounts to post
● Eliminations and Adjustments rules
Define the balances upon which eliminations and adjustments are made and the items such as accounts
and flow to which calculated amounts are posted
Features
The most important of the necessary adjustments for legal consolidation relate to the elimination of
intercompany activity between the various reporting units, and reclassifications and supporting the model of
the applicable rules for the accounting of long-term investments. Eliminations and adjustments rules support
the calculation and generation of these postings.
Eliminations and adjustments rules are applicable only to a legal consolidation model to which you attach a
corresponding ownership InfoProvider.
When eliminations and adjustments rules are executed for a given group, the system performs the following:
● Reads from the ownership InfoProvider which entities make up the group, the applicable consolidation
method, and the ownership and consolidation percentages.
● Determines for each elimination and adjustment defined in the business rules the base amount upon which
the elimination and adjustment is to be calculated based on the source data.
● Identifies for each elimination and adjustment the corresponding method-based multiplier from the
business rules.
● Based on the identified method-based multiplier and the method of consolidation assigned to a given
entity, determines the formulas to apply in calculating the amounts to post. Ownership and consolidation
percentages can be applied in the calculations.
● Posts the calculated amounts based upon the posting rules defined in the Eliminations and Adjustments
business rules tables.
The following information describes the fields of the General tab in the Business Rules interface of Eliminations
and Adjustments:
● Source Audit ID: Restricts the type of transaction data to which the rule applies. This can be a member of
the audit dimension, or a DIMLIST in the audit dimension. This field can also be blank to represent all audit
members with an audit type of I or M. (You can use Adjustment Level to apply further restriction.)
● Destination Audit ID: Indicates the kind of data the rule generates. This should be one base member with
an audit type of A.
● Group Type Filter: Restricts the rule to specific group or scope members.
● Entity Property Filter: Similar to Group Type Filter, this restricts the rule to specific entity members.
● Adjustment Type: Defines the rule type. Possible values are the following entries:
○ Blank: generic rule type
○ N: for new entities in the group/scope; similar to a generic rule
○ P: for proportional entities
○ E: for equity entities
○ L: for entities that leave the group/scope in the beginning of the year
○ I: for integration consolidation, which deals with the inconsistencies that occur when some
consolidation rules are defined using periodic mode while the ownership hierarchy changes during the
fiscal year. For more information, see Integration Rule for Consolidation [page 99].
● Adjustment Level: Indicates the execution sequence of all elimination rules. The system executes an
elimination rule with an adjustment level of 0 first, then level 1, then 2, and so on. The result of an
elimination rule with a lower adjustment level can be the input of an elimination rule with a higher
adjustment level. The source audit ID for an elimination rule with an adjustment level larger than 0 has
further restrictions.
● Other Dimension Filter: A string in this field indicates filters or special restrictions on other dimensions. For
example, if you have a user-defined dimension called Product and you want to run an elimination for only
one of its members called Pro1, you would enter Product = Pro1.
● Force Destination Member: When filled, indicates the value to which the system should force the
elimination result. For example, if you enter Product = ALL, then for the generated elimination result, the
system populates the dimension Product to ALL, no matter what the original value was.
● Ownership Filter: Filters the ownership value. For example, to apply a rule to only those entities whose
ownership percentage in a group or scope is larger than 70%, you enter POWN > 0.7.
7.5.1.6.1 Method-based Multipliers and Consolidation
Methods
You can set up global business rules at the environment level. Once the headers, methods, and rules are
defined, they can be used in all related business rule tables within an environment.
Features
You populate the following two global definitions:
● Methods
● Method-based multipliers
Global Definitions
You can add a new Global Definition in Planning and Consolidation Administration by:
● Selecting the type of Global Definition (Method or Method-based Multiplier)

● Entering the required fields
● Saving or validating the Method or Method-based Multiplier
Once defined, the rule can be used in any consolidation model in the environment.
The Consolidation Method list describes the accounting methods available for consolidating each entity.
Field Name Description
Method code ● The unique method code. The value must be an integer between 1
and 98
● 99 - a reserved value and means any method, consequently it can
not be assigned to any entity
Method name The name of this method.
 Example
Leaving, Equity, Proportional, Global, Holding.
Method type The Entity method type.
Available types: New, Holding, Global, Proportionate, Equity, Leaving

(During the Year), Disposed at last year-end
Method-based multipliers
Method-based Multipliers control how the amounts or the destination accounts should be calculated.
You define a name (ID), a description, and a type as noted in the following table. The consolidation method
defined in the Type field limits the use of the rule to the specified type of consolidation method.
The calculation of consolidated data is controlled by the multiplier being used, the consolidation method
assigned to the current entity, and its Intercompany partner, if applicable.
The following fields can be defined:
ID The identifier of the rule.
 Example
RULE01
Description A description of the rule.
 Example
Equity, 100% Minority part, Dividends, Stock Holder Equities, Inter
company elimination
Type The consolidation method using the method-based multiplier can be

restricted to:
● Proportional
● Equity
● Leaving
● Disposed
● New
● or blank
Entity Method A valid entity method, as defined in the Consolidation Methods list, or a
list of entity methods separated by commas to which the multiplier ap
plies.
IntCo Method A valid entity method, as defined in the Consolidation Methods list, a
list of entity methods separated by commas, or 99 for all methods. For
the Intercompany dimension, this is the entity value to which the multi
plier applies.
ALL Formula An expression that represents the percentage (or formula) to apply to
the Destination All account property from the Eliminations and Adjust
ments business rule.
The value can be an arithmetic expression combining any defined per

centage in the account dimension of the ownership model. All percen
tages where the property IS_INPUT is equal to Y can be used. Note the
following guidelines:
● The members must be enclosed in square brackets.
 Example
[POWN], [PCTRL], [POWN]
● Add the prefix P to the percentage to use the Prior value.
 Example
[PPOWN], [PPVOTE]
● Add the prefix I_ to the percentage to add the Intercompany

value.
 Example
[I_POWN]
● The syntax of the prior value can be combined with the syntax of
the INTCO value.
 Example
[I_PPOWN]
 Note
The calculation of POWN by both direct share method and group
share method is supported.
We also support the calculation of PCTRL (calculation of ultimate

control %) in the business rule tables.
There are two options for obtaining results: system calculations

and manual updates. There is also an option to change from sys
tem to manual while calculating. This gives you the means to man
age security by protecting system calculations that cannot be over
written by manual updates.
To support this, we also provide the O_ACCT dimension in Environ

mentShell by adding a set of members that store only system cal
culations. The members are POWN_SYS, PCTRL_SYS, and

METHOD_SYS.
Group formula An expression that represents the percentage (or formula) to apply to
the Destination Group account from the Eliminations and Adjustments
business rule. The value can be an arithmetic expression combining
any defined percentage as defined by the Account dimension of the
Ownership model. All percentages where the property IS_INPUT is
equal to Y can be used. The percentage must be enclosed in square
brackets. See the All formula field above for further details.
Minority formula An expression that represents the percentage (or formula) to apply to
the Destination Minority account from the Eliminations and Adjust
ments business rule. An arithmetic expression combining any defined
percentage as defined by the Account dimension of the Ownership
model. All percentages where the property IS_INPUT is equal to Y can
be used. The percentage must be enclosed in square brackets. See the
All formula field above for further details.
Remark Text for this rule.
7.5.1.6.2 Integration Rule for Consolidation
Integration consolidation deals with the inconsistencies that occur when some consolidation rules are defined
using periodic mode while the ownership hierarchy changes during the fiscal year.
Context
When you save or validate the I type rule in in the business rules user interface of Eliminations and Adjustment,
the validation checks the following fields:
● Destination Audit Member must be blank.

● Entity Property Filter must be blank.
● Other Dimensions Filter must be blank.
● Force Destination Members must be blank.
● In the rule details, Force interco member and Swap entity interco cannot be selected.
● In the rule details, Source Flow and Destination Flow cannot both be empty.
In the rule details, method-based multipliers must be used. Also, the integration rule must be 99 as the
intercompany method. However, rule validation does not check this.
How the integration rules work
When the integration mode is enabled for a model, the currency translation does not generate results on the
group level.
You can find a new type of consolidation rule with rule type I. The definition of the consolidation rule with type I
is similar to the generic consolidation rule. The main difference is that for the integration rule, you do not have
to define the destination audit ID because the integration rule keeps the audit ID unchanged.
When using the integration rule, you can customize how the translated results in the reporting currency are
posted to the consolidated results to a specific group. When integration mode is enabled, you do not have to
define consolidation rules with types E, P, D, and L because these types of rules can be replaced by integration
rules. After integration mode is enabled, the previously defined rules with types E, P, D, and L are hidden from
the user interface and are used in the consolidation calculation. You cannot create new rules with types E, P, D,
and L after integration mode has been enabled.
To enable the integration rule in consolidation, perform these steps:
Procedure
1. On the Home page, go to Administration Dimensions and Models Models .

2. Choose the model for which you want to enable integration mode. Only a Consolidation-type model can
enable integration mode.
3. Edit this model, expand Advanced Settings, then select Enable Integration Mode.
4. Save the change.
7.5.2 Controls
Controls enable you to test the validity of data gathered in a reporting process.
Use
Controls can be applied to any type of data. For example, a control can be used to check whether assets equal
liabilities for data entered in data entry schedules or for adjustments entered in journals.
Controls are run on the data available in the model in loaded data (local currency), translated data, or
consolidated data, on base entities. If a dimension is deleted from the model, all control results relevant to that
dimension are also deleted.
Controls are grouped into control sets.
The main steps to follow when setting up your controls are as follows:
Control steps
Location Step Additional Information
Business Planning and Consolida 1. Associate a level to each entity in the entity di
tion Administration mension
2. Enable controls for a selected model
3. Create controls Define control level, tolerance

threshold, expression, and so on.
4. Create control set and add controls
5. Assign control set to Category/Time combina

tion
Consolidation Central 6. Run controls Only controls in the control set

with a level less than or equal to
the level of the Entity are run.
7. Monitor controls
 Note
An entity for which no control level is defined is automatically assigned a control set status of Level 4,
meaning all controls are run when a control set is executed.
You manage controls in Planning and Consolidation Administration Rules Controls .
You execute controls in Consolidation Central Controls Monitor . You can also execute tasks in a business
process flow, provided that the relevant tasks are set up in the business process flow definition.
Prerequisites
To view the Controls page in Planning and Consolidation Administration, you must have the View Controls
Manager right. You can follow the steps in the topic “Authorization for Performing Consolidation Tasks” in the
Security Guide of this release to assign relevant authorization objects to target users.
Features
A control has two output values:
● The calculated amount for the control

Controls are calculated at the Entity level in loaded data (local currency), translated data, or consolidated
data.
● The control status
When a control set is executed, the status is a roll-up of the status of all the controls available in this set. If
any problems are detected when the controls are run, warnings or errors are generated. A warning does
not prevent the data from being validated in the workflow. A blocking error prevents the data from being
validated, meaning the work status cannot be modified for the corresponding category, time and entity
members. .
Enable controls
Controls can be enabled or disabled at the model level in Planning and Consolidation Administration. Controls
can be enabled only in a consolidation type model.
Before enabling controls, make sure two properties of the Entity dimension, namely Control Level and
CTRL_CURRENCY_NOT_LC (Bypass LC in Ctrls) are mapped to corresponding InfoObjects in Business
Warehouse. For detailed information, refer to the topic “Map Dimension Properties” in the Business Warehouse
application help.
 Note
To enable controls, work status dimensions must be set with at least three main dimensions: Category,
Time, and Entity. For more information, see Create a Control [page 103].
When enabling controls for a model, you can choose whether the context of the control monitor is derived from
the work status or set manually. You can also set the context of the control monitor on the parent node by
selecting the checkbox Parent Node Enabled while choosing dimensions. After that you will be able to run
controls against all leaf nodes under the parent node.
Edit Assignments
A control set must be assigned to a Category/Time dimension pair to be executed. For more information, see
Assign a Control Set [page 112].
You can have dynamic control on work status by using the Derive from Work Status option. This allow users to
change a work state in Consolidation Monitor even though a failed result exists. All selected work statuses
cannot be changed when there is a failed result; the control result must be checked and reviewed. However, any
unchecked work status can be changed even though a failed result exists.
Activities
● To enable controls
1. In the Controls page, select the model whose control sets you want to enable.
2. Select Enable controls.
3. Define under which context you want to run controls by choosing Derive from Work Status or Select
Dimension.
○ If you choose Derive from Work Status, the context bar of Control Monitor will be made up of the
driving dimension and other dimensions of the corresponding work status.
By default settings, if you failed to run a control, you cannot change any work statuses until the
control passes the check. To offer more flexibility, you can still change one or more work states in
Consolidation Monitor even though a failed result exists by unchecking the corresponding work
states.
○ If you choose Select Dimension, the context bar of Control Monitor will be made up of the selected
dimensions.
If you select the checkbox Parent Node Enable for a dimension, you will be able to run controls
against the parent node and all its leaf node members in Control Monitor. If you do not select the
checkbox Parent Node Enable for a dimension, you will not be able to select parent node members
of the dimension to run Control Monitor.
4. Click Save to save the settings.
● To display the Controls page in Planning and Consolidation Administration, select Rules Controls .
● To display a control definition:
1. In the Controls page, select the model containing the control(s) you want to view.
2. In the Controls for <Model name> page, click an individual control to display its properties.
● To edit assignments for a control set, see Assign a Control Set [page 112].
7.5.2.1 Create a Control
This topic contains information about creating a control.
Prerequisites
An administrator has given you the Edit Controls Manager right.
Procedure
You create controls in the Controls page of Business Planning and Consolidation Administration.
To create controls in SAP Business Planning and Consolidation, do the following:
1. Select Planning and Consolidation Administration Rules Controls .

2. Select the model for which you want to create a control.
3. Click Open to display the list of existing controls for that model, then click New.
When dimensions are added or removed from the system, control definitions containing a deleted dimension
are updated accordingly and are marked as being invalid for change tracking reasons. Impacted control
definitions must be verified. If a dimension is removed from a model, all control results are deleted.
If a driving dimension is added to the Work Status definition, control results are deleted as well as existing
locks. This new dimension is also removed from the control expression, since driving dimensions cannot be
used in control expressions. If a dimension is removed from the Work Status, all control data is cleared and
control expressions must be verified accordingly.
The control properties that you can define include:
● ID
● Description
● Rule Type
● (Control) Type
● Execution Level
● Equation Type
● Control Level
● Breakdown Dimensions
● Absolute Value
● Calculate on YTD
● Tolerance Threshold
● Expressions
ID
A control must be identified with a unique code.
Description
A control description should clearly and concisely describe which verification is being performed and for which
reason, and what the accounting, financial, or economic logic is. For example, "Assets = Liabilities".
Rule Type
● Standard: Choosing this option will use the standard configuration validation rule.
● Customized: Choosing this option means this rule will use the validation logic implemented in
BADI_UJCTRL_RUN_CONTROL.
(Control) Type
You assign one of the following two control types:
● Blocking: Prevents the user from going to the next work status level until the blocking status is cleared.
● Warning: Warns the user of noncritical data quality issues. Does not prevent the user from going to the next
work status level.
Execution Level
Select one or more types of data to which this control pertains:
● Loaded data
● Translated data
● Consolidated data
See the section Activate the Execution Level Field below for information on how to enable the use of this field in
your system.
For detailed information about the data validation range of each execution level, refer to SAP note 2263755 .
Equation Type
You choose the operand for the expression: =, >, <, >=, <=, <>. The operand determines how the two amounts
in the expression will be compared.
Control Level
This field is linked to the Control Level property in the entity dimension. A control level is defined for each
control, organizing the controls by rank so the relevant data can be verified.
Four control levels are available:
● Basic: Level 1
● Standard: Level 2
● Advanced: Level 3
● Comprehensive: Level 4
Controls are executed according to the control level associated with the selected entity. If an entity has no
control level defined, it is automatically assigned Level 4, meaning all controls are run when a control set is
executed.
Breakdown Dimensions
Choose up to two dimensions for which the control should be executed on all members. Breakdown
dimensions allow you to define controls to be run on any type of data, for example, input, manual adjustments,
automatic adjustments.
 Example
CTRL1 is defined as TOTAL_ASSET = TOTAL_LIABILITIES, breakdown dimension: DATASOURCE with

member TOTAL_INPUT specified in the control expression. TOTAL_INPUT is the aggregation of INPUT,
INPUT_ADJ1 and INPUT_ADJ2.
When the control is executed, it compares TOTAL_ASSET versus TOTAL_LIABILITIES for both members
INPUT, INPUT_ADJ1 and INPUT_ADJ2. As a result, if two members generate an error, the following
information is generated:
● One row appears displaying the aggregated information for the control, without data in any of the
columns except for the status, which displays as Failed.
● Two rows appear for the given control to display the detailed calculations with data for both lines.
 Note
Any dimension can be used as a breakdown dimension, except for dimensions used as driving dimensions
in the Work Status setting, currency dimensions, and group dimensions.
Absolute Value
Selecting Absolute Value indicates that the system should treat the value for the control as an absolute (non-
negative) value regardless of whether it is positive or negative.
 Example
Result A is 100 and result B is -125. If you set the rule to check whether result A is larger than (>) result B
and you do not select Absolute Value, then it passes. If you select Absolute Value for this rule however, the
system compares 100 and 125, and the result fails.
Calculate on YTD
As data stored is supposed to be periodic data, this option indicates the type of data on which the control runs.
When the option is checked, the control runs on year-to-date data when YTD aggregation is performed during
the execution of the control. When unchecked, controls are run on periodic data.
Tolerance Threshold
The tolerance threshold is an amount that is compared to the difference between the two amounts (the
"control result"). If the control result is less than or equal to the amount defined in the tolerance threshold, then
the difference is considered to be insignificant and the control status is considered to be OK.
 Example
Expression of control for Comparison difference/ Control result Example

amounts x and y tolerance
x=y < Tolerance Valid Tolerance entered: 1
Amount x: 1,000,000
Amount y: 1,000,000.5
Difference: 0.5
The difference is less than

the tolerance. The two
amounts are therefore con
sidered equal.
The control, run to check if

the two amounts are equal,
is therefore valid.
> Tolerance Error or warning
x<y < Tolerance Error or warning Tolerance entered: 1
Amount x: 1,000,000
Amount y: 1,000,000.5
Difference: 0.5

sidered equal.
The control, run to check if x

is less than y, is therefore in
error.
> Tolerance and x < y Valid
> Tolerance and x > y Error or warning
x>y < Tolerance Error or warning
> Tolerance and x > y Valid
> Tolerance and x < y Error or warning
x≤y < Tolerance Valid Tolerance entered: 1
Amount x: 1,000,000
Amount y: 1,000,000.5
Difference: 0.5

sidered equal.
The control, run to check if x

is less than or equal to y, is
therefore valid.
> Tolerance and x < y Valid
> Tolerance and x > y Error or warning
x≥y < Tolerance Valid
> Tolerance and x > y Valid
> Tolerance and x < y Error or warning
Expressions
The expression is the formula used for identifying the two amounts to be compared. In the Expressions tab, the
upper panel contains the formula for identifying the first amount to be compared. All the dimensions must be
specified.
When breakdown dimensions are specified, an icon appears in the column header identifying that dimension as
a breakdown dimension.
The lower panel contains the formula for identifying the second amount to be compared, which can be from
another Category, Time, or Group.
In the Category field you can enter any member from the Category dimension. In the Year Offset field, you can
enter an integer preceded by "+" or "-". In the Period field you can enter an integer which is associated to the
MONTHNUM property of the Time dimension. For relative periods, "+" or "-" signs can be used; for example, for
the previous month you enter "-1".
If the lower panel is left blank, the first member of the expression that was defined in the upper panel is
compared to zero.
Activate the Execution Level Field
Follow these steps to make the Execution Level field visible in the Web client:
1. Go to transaction SPRO.
2. Navigate to Planning and Consolidation Configuration Parameters Set Global Parameters .
3. In the Global Parameter window, add the ENABLE_CTRL_ON_DIFF_LEVELS parameter and set its value to
X.
4. Clear the cache of the system.
7.5.2.2 Working with Control Sets
A control set is a grouping of controls. In order to create, modify, copy, or delete a control set, you must have
the Edit Controls Manager right.
Control sets are associated to a particular model. You can define more than one control set for a model. The
controls in a control set are organized in the order in which they are executed. A control set must be assigned
to a Category and Time dimension pair in order to be executed.
Control Set Properties
The control set properties include:
● ID
A control set must be identified with a unique code. This field is mandatory.
● Description
A control set should clearly describe the type of verifications to be performed.
Related Information

Display or Modify a Control Set [page 109]
Copy a Control Set [page 110]
Delete a Control Set [page 111]
Assign a Control Set [page 112]
Additional Actions Involving Control Sets [page 113]
7.5.2.2.1 Create a Control Set
Prerequisites
To edit controls in Planning and Consolidation Administration, you must have the Edit Controls Manager
right. You can follow the steps in “Authorization for Performing Consolidation Tasks” in the Security Guide
available on the SAP Help Portal to assign relevant authorization objects to target users.
Context
A control can be assigned to more than one control set.
Procedure

2. In the Controls page, select the model where you want to add the control set and click Edit Sets in the
toolbar. Alternately, click the number in the Sets column corresponding to the model where you want to
add the control set.
3. In the Control Sets: <Model name> page, click New in the toolbar.
4. Specify a name and a description for the control set.
5. To add controls to the control set, click Add/Remove in the toolbar.
6. In the Add/Remove Controls dialog box, use the arrows to move controls from the Available Controls list
into the Selected Controls list, then click OK.
7. Save the control set.
Related Information
Working with Control Sets [page 108]

7.5.2.2.2 Display or Modify a Control Set
Prerequisites
You must have the Edit Controls Manager right.
Context
A control can be assigned to more than one control set.
Procedure

2. In the Controls page, click the number in the Sets column corresponding to the model for which you want
to display all the control sets. Alternately, select the row containing the model and click Edit Sets in the
toolbar. You can also directly click the Go To: control sets hyperlink in the Controls list page.
3. In the Control Sets: <Model name> page, select the control set that you want to display or modify.
4. To add or remove controls from the control set, click Add/Remove.
5. In the Add/Remove Controls dialog box, use the arrows to move controls between the Available Controls list
and the Selected Controls list, then click OK.
6. Save the control set.
Related Information

7.5.2.2.3 Copy a Control Set
Copying an existing control set allows you to quickly create a new control set, which you then modify as
needed. You can also quickly initialize a control set containing multiple controls, without having to add the
controls one by one.
Prerequisites
Procedure

2. In the Controls page, select the model containing the control set you want to copy and click Edit Sets in the
toolbar.
3. In the Control Sets: <Model name> page, select the control set and click Copy in the toolbar.
4. In the Copy Control Set dialog box, enter a name and description and click OK.
The copied control set contains the same controls as the original control set. You can then modify the
control set as needed.
Related Information

7.5.2.2.4 Delete a Control Set
Prerequisites
Context
Deleting a control set does not delete the associated controls.
Procedure

2. In the Controls page, select the model containing all of the control sets you want to delete and click Edit
Sets in the toolbar.
3. In the Control Sets: <Model name> page, select all control sets you want to delete and click Delete in the
toolbar.
Related Information

7.5.2.2.5 Assign a Control Set
To execute a control set, you must specify when you want your control set to be run and on what type of data,
by assigning at least one Category/Time dimension pair to your control set.
Context
Creating a category/time pair consists of choosing at least one category and one period per control set.
Procedure
1. To assign category/time pairs to control sets, in Business Planning and Consolidation Administration
select Rules Controls .
2. In the Controls page, select the row of the model containing the control sets for which you want to define
assignments. Alternately, click the number in the Assignments column corresponding to the required
model.
Related Information

7.5.2.2.6 Additional Actions Involving Control Sets
You can display category/time pair assignments for control sets, display additional periods or categories, and
sort and move columns.
Display category/time pair assignments for control sets
There are two ways to display the category/time pair assignments for control sets:
● Show Categories by Time

You select the option Categories by Time to display the active control sets assigned to each category and
period intersection.
In the Assignments grid, the categories are listed in rows and the periods are listed in columns. Assigned
control sets appear in the grid in cells at the intersection of a category and a period.
To modify an assignment, click Edit and double-click in a cell to display the list of available control sets. You
can then assign a control set to the selected category/time pair.
● Show Control Sets by Time
You select the option Control Sets by Time to display the category/time pairs organized by each available
control set.
In the Assignments grid, the active control sets are listed in rows and the periods are listed in columns.
Expand a control set by clicking its arrow to display the selected categories; in doing so you display the
category/time pairs for the expanded control set in the form of a checkbox in each grid cell. If the checkbox
is selected, the control set is run for that category and period.
 Note
The Control Sets by Time view is for consultation only. You cannot modify the category/time pairs in
this view.
To display additional control sets, click Control Sets and select additional control sets in the Member
Selector dialog box.
Display additional periods or categories
You can display additional periods or categories in the Assignments grid. Click Category or Time in the toolbar
and make your selections in the Member Selector dialog box. The additional dimension members are displayed
in the grid.
 Note
You can define and implement your own validation logic by leveraging the BAdI UJCTRL_RUN_CONTROL. For
detailed information, refer to SAP note 2264009 .
Related Information
7.6 Business Process Flow Management
This function enables you to create and manage business process flow (BPF) templates - also called process
templates - and manage the processes created from these templates.
A process template is the specification of a single enterprise-wide business process, containing tasks that can
span across the various modules of Business Planning and Consolidation. It defines the business processes
that are presented to users as a prepackaged set of application tasks. For an additional level of control over the
workflow, you can integrate work status rules.
Once you have completed a process template, you can create a process based on the template, in the
Administration screen. A process represents an iteration of the enterprise-wide business process, which allows
the user to see only the tasks relevant for that user, given his or her role and data access privileges.
Prerequisite
You must have the BPF authorization object RSBPC_BBPF assigned to you in order to manage business process
flows. For detailed information about how to assign the authorization object, refer to the topic “Authorization
Objects” in the Security Guide available on the SAP Help Portal.
Features
The following functions are available to authorized users:
Function More Information
Create new process templates You can create a new process template on which to base
processes, copy existing process templates, and modify ex
isting templates. For more information, see Creating New
Process Templates [page 116].
Function More Information
Validate process templates When you create a new process template, the system auto
matically validates the template for completeness before
saving the template. The result of this validation is shown in
the Status column. A template can be Valid or Invalid. If it is
invalid, you can revalidate it by selecting the template , and
clicking Validate.
Unlock process templates If the system automatically locks a template because you
unexpectedly logged off while editing, you can unlock it by
selecting the template and clicking Unlock.
Note that you cannot unlock templates that are locked by

other users. To find out who has locked a template, select
the template and click Versions.
Deploy a template If a template is not locked and has a status of Valid, you can
deploy it so that it can be used for creating processes. Select
the template, and click Deploy.
Copy a template and create new version If you want to create a new template based on an existing
template, select the template you want to copy and choose
Copy.
Once a template is deployed for creating processes, it can no

longer be modified. To make changes to a deployed tem
plate, you can select the template and choose New Version.
View all templates and versions If you select a template and choose Versions, the Template
Versions window opens. The list contains all versions of the
selected template. To view an obsoleted version of a tem
plate, select a template in this window and click View.
Integrate external workflows with BPFs You can integrate external workflows with BPC BPF proc
esses to accommodate complicated planning processes. For
more information, see External Process Integration [page
133].
7.6.1 Creating New Process Templates
With the correct authorization, you can use this process to create a new process template. You can define up to
100 process templates for each environment.
Process
1. Go to Administration and under the Business Process Flows section, choose Process Templates.
2. Choose New to start the creation of a new process flow.
3. On the Process Settings tab, provide details such as name and description of the business process flow.
See Process Settings [page 117].
4. On the Activities tab add activities to represent the flow of the business process. See Activities [page 118].
You can create a new activity as well as duplicate an existing activity and then modify it. You can also
change the order of activities.
5. You can add actions to define the specific tasks users perform within the activities. See Defining Actions
[page 127].
6. When you save a new process template, the system automatically validates the template to ensure it is
properly defined and completed before saving the template. The result of this validation is shown in the
Status column. A template can be Valid or Invalid.
Template validation is a prerequisite for creating a process.
 Note
Validation occurs every time that you click Save. So, if you make an interim save to avoid losing your
work, you will probably receive some validation errors or warnings. You can view these by choosing See
Details next to the warning message. You must solve all validation errors before deploying a template.
7. Deploy the saved template.

You can only create process instances based on a template that has been deployed. Once you deploy a
template, you cannot make any more changes to it. However, you can create a new version of that template
and edit it.
Result
Based on the process template you created, you can generate processes in the Administration screen and
perform actions on the process instances. See Creating Process Instances [page 130].
7.6.1.1 Process Settings
Before creating a process template, you provide basic information that identifies the process template. If you
want to further modify a process template, you can use the same features as the setup process described in
this topic.
The following table describes the information you need to complete the setup process in the Process Settings
tab:
Item Description
Name The name of the process template.
Description A description for the process template.
Identity Dimensions One or more dimensions common to all processes created

from this template.
The identity dimension is used to distinguish a BPF instance.

The members of any identity dimensions must be specified
every time a new BPF instance is created.
Process Monitors These are the users that have rights to monitor and change
processes created from the process template.
Check only the current step when reopening When this checkbox is selected, you can reopen the current
activity if you are the performer or reviewer of the activity.
Otherwise, you must be the performer or reviewer of both
the current activity and the next open activity to reopen the
current activity. For detailed information, refer to Criteria for
Reopening Activities [page 124].
Navigation attribute is now supported in the embedded configuration of Business Planning and Consolidation,
which allows you to select certain navigation attributes as identifying dimensions or driving dimensions in a
process template. After you define an attribute as a navigation attribute in an InfoObject, the navigation
attribute displays in the corresponding InfoProvider. Then enable the checkbox in the On/Off column of the
navigation attribute and you can then use it in the Business Planning and Consolidation web client. For detailed
information about the usage of navigation attribute, refers to .
Activities
To create a process template from scratch, go to Administration and under the Business Process Flows section,
choose Process Templates. Choose New to start the creation of a new template.
You can also use Copy or New Version to create a process template based on an existing template.
To define activities within the business process flow, choose the Activities tab. For more information, see
Activities [page 118].
7.6.1.2 Activities
You can create activities that form part of a process.
For guidelines on defining activities, see Criteria for Defining Activities [page 120].
The following table summarizes the information that you need to supply for each activity:
Item Description
General
Name Provide a title for the activity.
Description Provide a description of what is to be done in the activity.

This is the instruction that is displayed to a user performing
a process based on this process template.
Opening Criteria Select the appropriate radio button to open by All activity
contexts or Matched activity contexts.
For more information, see Criteria for Opening Activities

[page 122].
Allow Reopen To allow authorized users to reopen an activity, select the

checkbox.
For more information, see Criteria for Reopening Activities

[page 124].
Driving Dimension
Driving Dimension Select the driving dimension.
This is the dimension that is common to all activity contexts

that users might use for completing the tasks in the activity.
For more information, see Defining Activity Context Criteria

[page 121].
Members In the Members drop down list, clicking Select

MembersCriteria Editor. You can directly select members
from one hierarchy or click to filter members by dimen

sion property and add them to the Selected Members list as
a batch.
For more information, see Defining Activity Context Criteria

[page 121].
Map Driver to Create a mapping between the driving dimension and an in
ternal dimension. For more information, see Internal and Ex
ternal Driving Dimensions [page 126].
Activity Performer
Item Description
Performer Select the property that defines the performer for each
member.
To define an action that a performer must perform when re

viewing the activity.
A Performer is the person, to whom the activity is provided

to at run time, that is the person, who has to perform the
work items in the activity and mark it as complete. This can
be one or more users, or a team. Performers are determined
by a property of the dimension used as driving dimension of
the activity. You can select the “Owner” property or any
other property for this. Owner property has a specific mean
ing in Business Planning and Consolidation; it is the dimen
sion property that determines who can change the work sta
tus of each member to anything other than unlocked. So you
could choose to have an activity that is performed by the
same owner as work status.
 Note
A property of a dimension is an attribute of a character
istic in BW. You can maintain BW characteristics using
BW modeling tools. For more information, see .
For more information, see Defining Actions [page 127].
You can define a deadline for the activity’s performer in proc

ess templates. The deadline is calculated in days by default
starting from the end of the last activity. You can also define
whether to wait or to close the activity when the activity
deadline occurs. The deadline you set in BPF templates can
be adjusted in BPF instances later. For more information, see
Setting Deadlines for Activities [page 125].
Activity Workspace By choosing Create you can create hyperlinks.
Activity Reviewer
Require Reviewer If required, select this checkbox and select a property that
defines the reviewer for each member.
Reviewer You select the reviewer in the same way as selecting a per
former, but you can select a different property to determine
the reviewer users.
For more information, see Defining Actions [page 127].
Item Description
Deadline You can define a deadline for the activity’s reviewer in BPF
templates. The deadline is calculated in days by default
starting from the end of the last activity. You can also define
whether to wait or to close the activity deadline fell occurs.
The deadline you set in BPF templates can be adjusted in
BPF instances later. For more information, see Setting Dead
lines for Activities [page 125].
Activities
To create a new activity, click New; to edit an existing activity, select the activity. To copy an existing activity,
select the activity, and chose Duplicate. You are offered the opportunity to duplicate the activity definition and
contents, or just the activity definition.
You can preview instances of this activity by clicking Preview Activity Instances.
Once you have defined an activity, you can create a working area where users can add, view, and manipulate
data. Choose Create a performer workspace. This opens a workspace, that is driven by the process and whose
driving dimensions are those defined for the activity. In this workspace, you can add any Business Planning and
Consolidation function for data entry, creating reports, and so on. For more information, see Defining Actions
[page 127].
You can define a workspace for each activity. You can choose whether the reviewer uses the same workspace or
has a separate workspace for reviewing this activity. You can also set a deadline for the performer and the
reviewer of the activity in a process template and make further adjustments to the activities when creating
relevant process instances. For more information, see Setting Deadlines for Activities [page 125].
7.6.1.2.1 Criteria for Defining Activities
Activities have defined criteria to control the activity context, opening of activities, review criteria, and
reopening of activities if required.
Each process must contain at least one activity.
The following are guidelines for defining activities:
● All activities can have more than one action associated with them. The primary action is the launch action;
the additional actions appear in the action pane when the primary action is launched.
● Activities may require approval by a reviewer before the system considers the activity complete.
● Performers and reviewers must perform activities in the order defined in Activities.
● Each activity is assigned a driving dimension, which determines the generation (iteration) of the activity by
process context. The driving dimension assigned to the activity is also associated with the performer and
reviewer property for each activity context. The performer and reviewers can be modified when you create
a process instance later.
● The process owner can finalize the process only when all activities are completed.
● Up to one thousand activities per process template or process can be defined.
● Up to one million activity contexts per process can be defined. The activity contexts can be calculated as a
product of the number of activities and number of process contexts.
Related Information
Activities [page 118]
7.6.1.2.2 Defining Activity Context Criteria
To complete the creation of an activity in a process template, you must define the activity context criteria for
that activity.
Procedure
You define activity context criteria in the Driving Dimension of the Activities tab by performing the following
steps:
1. Select the driving dimension. Each activity has only one driving dimension, and this determines which
members can be selected for that activity.
2. In the Member's drop down list, choose Select Members and set member criteria for the activity context
using the Criteria Editor. There is a limit of six member definitions per step:
○ Select specific valid member IDs from the list. This list is generated depending on the driving
dimension you have selected. You can make multiple dimension member selections.
○ If you select a parent ID, which is a node that has subnodes, in the dialog box that appears, you can
generate dimension members based on the dependent (Children), or base (Base Members) nodes
of the parent ID. If you do not select Children, Base Members, or All Members, the selection
defaults to Single Member, which includes only the selected node.
 Note
Dependent members are all entries one level below the parent node.
Base members are all entries at the lowest level below the parent node.
In some cases you will have to manually enter the members that you want to use in the activity.
In the member Criteria Editor page, you can also click the button to filter members by selecting
properties of the driver dimension and add them to the Selected Members list in a batch.
The logical relationship of selections is:
○ All selected members are on one hierarchy: OR
○ Filtered by the same property: OR
○ Filtered by different properties: AND
○ Selected from different hierarchies and filtered by different properties: AND
 Note
“OR” refers to a union set of selection, while “AND” refers to an intersection selection.
Order of activities:
1. If there is a hierarchy selection, follow the preorder traversal of the hierarchy, which means selecting
members from the tree and subtrees of the hierarchy from root to children and from left to right.
2. If there is only a property selection, follow alphabetical order. The operators supported in property
selections are equal, not equal, between, and like.
For example, the driver dimension of one step is D, which has hierarchy H1 and H2, and properties P1 and
P2. The selections are the following:
1. Base members of member M1 in H1
2. Children of member M2 in H2
3. P1 = 'Variance 1'
4. P1 between 'Variance 2' and 'Variance 3'
5. P2 = 'Variance 4'
The members displayed in Selected Members will satisfy the logical relationship (1 OR 2) AND ((3 OR 4)
AND 5).
7.6.1.2.3 Criteria for Opening Activities
Use
By selecting the opening criterion when you define activities in the Process Template Designer interface, you
can define a new criterion for the opening sequence of activities.
Features
When choosing an opening criterion for an activity, consider the following guidelines:
● There is no opening criterion for the first activity of a process. The first activity is always open, regardless of
how the opening criterion for the activity is defined in the process template.
● When you complete all activities in a context, the next activity automatically opens regardless of the
opening criteria.
When you are defining an activity, you can choose the opening criteria to be All or Matched. The following
sections describe how these criteria affect activities.
All Activity Contexts
Choosing All Activity Contexts as the opening criterion for an activity introduces the following constraints:
● All activity contexts must be completed before the next activity opens.
● Use with matching driving dimensions, or different driving dimensions.
● Use this option when you have matching driving dimensions, but different activity contexts between
activities.
 Example
You must complete all tasks for all activity contexts in activity 1 before activity 2 opens:
Activity Driving Dimension Activity Context Status
1 Entity Italy Complete
1 Entity France Open
2 Entity Italy Pending
2 Entity France Pending
Matched Activity Contexts
Choosing Matched Activity Contexts as the opening criterion for an activity introduces the following
constraints:
● When you complete an activity context, the next activity opens for that same activity context.
● Use with matching driving dimensions only.
● Do not use when you have matching driving dimensions, but different activity contexts between activities.
 Example
The matched activity context opens in activity 2 when you complete the tasks for the corresponding
activity context in the first activity. All tasks for the other activity contexts are pending:
Activity Driving Dimension Activity Context Status
1 Entity Italy Complete
1 Entity France Open
2 Entity Italy Open
2 Entity France Pending
7.6.1.2.4 Criteria for Reopening Activities
You can reopen a completed activity to perform actions in that activity once again. You enable the reopen
function when you are defining activities in the Process Template Designer interface.
When choosing a reopening criterion for an activity, consider the following guidelines:
● The Allow Reopen checkbox must have been selected in the activity that you want to reopen when
designing the process template.
● You reopen activities one by one starting from the most recently completed activity, which means that
except for the last open activity, the reopen function is available only for the activity prior to the one that is
now active; you cannot reopen an activity that is not consecutive.
● By default, you must be a performer or reviewer in both the current activity and the next open activity to be
able to reopen the current activity. To change the default setting, you can following the steps described in
Check Only Current Step when Reopening below.
● If you are the process owner you can reopen an activity, regardless of owner or reviewer assignment, from
the process monitor.
● You cannot specify which activity context to reopen; it is an activity operation.
● You cannot reopen an activity once it has been finalized.
Check Only Current Step when Reopening
By default, if you act only as a performer or a reviewer instead of the process owner of a process, you must be a
performer or reviewer in both the current activity and the next active activity to be able to reopen the current
activity. To enable a performer or a reviewer to directly reopen the current activity, perform the following step:
● Select the option Check only the current step when reopening in the Process Settings page when creating or
modifying a process template.
The following sections describe how All and Matched criteria affect activities.
All Activity Context
Choosing All Activity Contexts as the reopening criterion for an activity introduces the following constraints:
● You must be a participant in at least one activity context of thecurrent activity.

(The process owner can ignore this).
● You must be a participant in at least one activity context of the next openactivity.
● The opening criterion of the next open activity is All.
● The open activity must be fully active, which means that all the activity contexts of the current activity
must be Open, Reopened, Rejected, or Submitted.
 Example
When you reopen activity 1, all activity contexts for activity 2 change to status Delayed:
Driving Dimen
Activity sion Activity Context Performer Reviewer Status
1 Entity US A B Reopen
1 Entity Canada C D Reopen
Driving Dimen
2 Entity US A B Delayed
2 Entity Canada C D Delayed
Matched Activity Context
Choosing Matched Activity Contexts as the reopening criterion for an activity introduces the following
constraints:
● You must be a participant of the matched activity context in the current activity to reopen that activity
context.
● You must be a participant of the matched activity context in the next open activity to reopen that activity
context in the current activity.
● The opening criterion of the next open activity is Matched.
● The open activity must be an active activity , which means at least one of the activity contexts of the
current activity must be Open, Reopened, Rejected, or Submitted.
 Example
When you reopen activity 1, activity context Canada reopens. Canada changes to status Pending in activity
2.
Activity context US does not reopen as it is already complete in activity 2 - the activity context must be
active in the next open activity to reopen it in the current activity:
Driving Dimen
1 Entity US A B Complete
1 Entity Canada C D Reopen
2 Entity US A B Complete
2 Entity Canada C D Delayed
7.6.1.2.5 Setting Deadlines for Activities

Timelines, including activity deadlines, are important within a planning process.
Deadlines can be set for activity performers and activity reviewers in Process Templates and Process Instances.
After specifying a deadline for an activity, process owners can easily monitor its status in the process monitor.
Defining Deadlines in Process Templates
In a BPF template, a deadline is the number of days after which an activity will expire. For example, if you enter
2 days for the deadline, the activity will be due two days after its start date.
You can also define actions upon the expiration of the activity. When choosing to wait, the activity keeps its
original status and does not close automatically. When choosing to close the activity, the activity automatically
closes. If you further define a different deadline or choose not to enable a deadline for the activity when
creating a process instance based on the current template, the deadline you defined in the process template is
replaced by the newly defined deadline in the process instance.
Defining Deadlines in Process Instances
You can adjust deadlines you defined in process templates or define new deadlines when setting timelines
during the creation of a process instance. Different deadlines can be set in accordance with different start
dates:
● If you want to start the process instance immediately or on a certain date, you can check the Enable with
Deadline option and choose the date of the deadline for the performer and reviewer of each activity.
● If you want to start the process manually later, you can check the Enable with Deadline option and enter
after how many days each activity will be due.
After you successfully create the process instance, the deadlines you set display in My Activities for the
performer and reviewer and in Process Monitor for the process owner.
 Note
You can still make changes to your planning activities and modify deadlines in Process Monitor after the
process starts to run. For more information, refer to Process Monitor [page 14].
Email notification of an upcoming due date for each activity can also be automatically sent. To set the email
notification, use transaction SA38 and execute program RSBPC0_DAEMON_UI to start a job. Use transaction
SM37 to view the job status of job name BPC_DAEMON_JOB.
7.6.1.2.6 Internal and External Driving Dimensions
Business Planning and Consolidation reuses the InfoObjects that are delivered with SAP Business Warehouse.
Some of these InfoObjects may not have the performer and reviewer properties defined, therefore they
cannot be used directly for driving dimensions. We recommend that you use the following workaround:
1. Create a new InfoObject that has the same structure as the InfoObject delivered by SAP.
2. Maintain the performer and reviewer properties in the newly created InfoObject.
3. When choosing the driving dimension, choose the External Dimensions radio button to display the
dimensions of your manually created InfoObject.
4. Choose the required driving dimension.
5. The Map Driver to dropdown list displays the InfoObjects delivered by SAP. Select the dimension to which
you want to map the driving dimension of the activity.
After you perform these steps, you can select the required performers and reviewers for the activity.
7.6.1.3 Defining Activity Workspaces
You can assign action groups to an activity in the activity's workspace.
After you finish editing an activity workspace, you can assign review actions to activities, which require the
approval of a reviewer.
Prerequisites
You have defined an activity when creating or editing a process template.
Procedure
Add an Action Group
1. When creating a process template, choose the Create button in the Workspaces field of the Activities tab.
2. Click the Add button and choose Add Action Group.
You can add hyperlinks only to perform actions of existing elements. Therefore, you must make sure these
elements exist before you start defining actions.
Business Planning and Consolidation supports the following types of actions:
○ Consolidation – Define a hyperlink to perform various kinds of actions in Consolidation including
opening a journal list, creating a new journal, opening Consolidation Monitor, opening Ownership
Manager, opening Controls Summary, and opening Controls Details.
○ Analysis Office Plug-in:
○ Define a hyperlink to a Business Warehouse query. If the query has variables set in it, you can
assign values to these variables.
○ Define a hyperlink to an Analysis Office workbook. If the workbook contains a query that has
variables set in it, you can assign values to these variables. If the workbook contains queries with
the same variables, you can assign values to these variables for each query. You can also assign
values to all of the variables once by selecting Merge Variables.
○ Work Status - Set a target work state for a context and define a target work state for a specific activity
status. When there is a change of a certain activity status, the system can automatically change the
work state to the defined target state. For more information about work status integration,
seeIntegrating with Work Status [page 129].
○ External Resources - You can open a URL or an external web-based application.
For more information about external web-based applications, see Configuring Links to External Web
Applications [page 128].
3. Choose Stop Editing. You can then click the hyperlink to test the action of the activity.
4. Repeat these steps for all of the actions to be associated with each activity in the process template.
5. After all the actions have been defined, go back to the process template and save it.
You can specify that the reviewer uses the same workspace or that a reviewer has a specific workspace, which
you can define in the same way.
Result
You have defined actions for your activity.
7.6.1.3.1 Configuring Links to External Web Applications
You can use this procedure to configure a link to an external web-based application from a BPF instance (for
example, a Web Dynpro report).
Prerequisites for BPF Navigation
You must first configure the web-based application that you want to use as a role in the User Interface Add-On.
1. Enter Tcode LPD_CUST.

2. Click Create New Launchpad, then input the role name, instance, and description. Use uppercase letters for
the role name and instance.
3. Double-click the newly created launchpad and create a new folder.
4. Create a new application in the new folder. When you create a new application inside a launch pad, the URL,
transaction, and Web Dynpro ABAP should be supported in Business Planning and Consolidation.
5. Input the link text, application type, and application parameter.
6. Input a system alias, such as SAP_LOCALSYSTEM.
7. Create a unique application alias.
8. Input parameter: target parameter = web dynpro parameter name; source parameter = BPF defined
parameter name.
Registering a Role in SAP GUI
1. In SAP GUI run transaction SE38.

2. Execute program RSBPCB_MAINTAIN_SEM_OBJ to display the list of registered roles.
3. To register a new role, choose Register.
4. In the Role field, enter the name of the required role. With the F4 key you can display a list of all available
roles.
5. Choose Register to complete the registration of the selected role.
Maintaining Links
1. In SAP GUI run transaction SE38.

2. Execute program RSBPCB_MAINTAIN_SEM_OBJ_LK
3. Select the required role and choose Edit.
4. Choose Add and enter the new link for the role.
You can view the links that are already defined for the role by choosing Display Existing Links.
5. Choose Maintain Parameters to create new parameters or to change the existing ones.
6. If you want to remove a link and all its parameters, select that link and choose Delete.
Configuring External Resources in a BPF Instance
When configuring workspaces for the performer and the reviewer in BPF, you can add hyperlinks to the web-
applications that you configured with the procedures above.
1. When configuring a workspace, from the Target Action list, select External Resources.
2. From the second-level dropdown list that appears, select Open External Web-based Application.
3. From the Target Object list that appears, select the required role.
4. Enter values for the parameters of the target object.
The activity performer will be able to click the hyperlink to open the target action in the web-based application
with the corresponding parameters to perform any assigned tasks.
7.6.1.3.2 Integrating with Work Status
When defining a target action for Set work status, you can set this action to be executed automatically
when there is a change of activity state.
Context
You can specify one of the following desired target work states for all possible Business Planning and
Consolidation activity states:
● On Submit
● On Approve
● On Reject
● On Complete
● On Reopen
Procedure
1. Select the checkbox Automatically executed on a change of activity state.

2. To specify one of the target work states for the possible activity states, select the checkbox Include All
Descendants.
7.6.2 Creating Process Instances
A process instance is a process that has been created based on a process template.
Use
An authorized user can create a process instance in the Administration screen. You can create up to 24 process
instances for each process template.
Generating a process creates all required activities and activity contexts. Once generated, the process instance
is no longer associated with the template. Any changes to the template definition do not impact previously
generated processes.
Prerequisites
A process template has been created, validated, and deployed.
Procedure
In the Process Instances screen, choose New. This opens the New Process Instance wizard that has the
following steps:
1. Select the process template.

2. Choose the process owner.
3. Select the context.
4. You can change the performer or reviewer for each activity.
Select an activity and click Change Performer or Change Reviewer as appropriate and choose a different
user or team.
5. You can set a timeline by scheduling a start date for the process instance and enabling corresponding
deadlines for each activity. For more detailed information, refer to Setting Deadlines for Activities [page
125].
 Note
Any settings you made in the process instance overwrite those made in the process template.
Therefore, if you choose not to enable deadlines for the activities during the creation of the process
instance, the deadlines you previously set in the process templates will not take effect.
6. Review the process, select Start the process instance and click Finish.
The title of the created process is derived from the process template name and the context of the process.
Result
You have created a process. Click Refresh in the Process Instances screen to add the new process to the list; it is
displayed with a status of Active.
You must manage the process and activate it before a user can see it in the interface. You can perform the
following functions for a process in the Process Instances window:
Function Description
Start/Resume Start is normally used to manually begin an activity. Resume

is to restart a suspended process. After that the status
changes to Running.
Suspend Suspend deactivates an active process or a process waiting

for finalization. The status changes to Suspended. The proc
ess can be reactivated using Resume.
An inactive process does not appear available for users and

can be seen only in the Administration window. Note that the
deadline is not postponed even when a process is sus
pended.
Change Assignments The Change Assignments wizard allows you to change the
process owner and an activity performer or reviewer.
Reset Resets a process back to activity 1. The system resets the

status within the process so users must perform the steps
again. The system does not, however, reset changes made to
your metadata or transaction data.
Refresh To refresh the display after changes have occurred.
7.6.3 Setup of E-mail Notifications
Administrators can turn on and turn off e-mail notifications and customize an e-mail template for business
process flow activities.
The e-mail addresses to which each business process flow e-mail notification automatically sends are the e-
mail addresses of the process instance owner, activity performer, or activity reviewer maintained in Business
Warehouse via transaction SU01. You must make sure that proper SMTP settings are configured via
transaction SCOT to allow the system to automatically send out the emails. For detailed information, refer to
the SMTP Configuration Guide available here on the Help Portal.
The email notifications automatically sent to users contain a link to bring them either to the activity or process
monitor directly, or to external URL-based applications including transactions, Fiori, and ABAP Web Dynpro
applications.
Activate Email Notifications
To turn on and turn off e-mail notifications, administrators can perform the following steps:
1. Run transaction SE38.

2. Execute the RSBPCB_MAINTAIN_EMAIL_TMPL program.
3. Do one of the following tasks on the email template page:
○ To activate e-mail notifications, change the value of the Is Active column to Yes.
○ To turn off e-mail notifications, change the value of the Is Active column to No.
Create a New Email Template
Besides the default e-mail templates, administrators can also customize an e-mail template by performing the
following steps:
1. On the e-mail template page, click the Change button and choose New Entries (F5).
2. Choose Customizing Email Template in E-mail Template Type.
3. Choose an e-mail template ID for the customized email template. Later, if both this customized email
template and the default email template sharing the same ID are activated, the customized email template
takes priority.
4. Type an e-mail template title in which two variables can be included:
○ %PROCESS_NAME%: Process instance name
○ %STEP_REGION_NAME%: Activity name
5. Select a Smart Form body or directly enter an e-mail body.
Smart Forms are predefined via transaction SMARTFORMS. For detailed information, refer to the section
below called “Manage Smart Form Body”.
An e-mail body is simply made up of a single line text. If both Smart Form and e-mail body are defined, the
Smart Form body will be used.
6. Use the same URL Callback RSBPCB_SF_XSF_URL_CALL_BACK or UJB_SF_XSF_URL_CALL_BACK as in
the default template to call the proper URL.
7. Choose a corresponding BPF Operation.
8. Activate and save the template. The responsible person will receive e-mail notifications based on the
customized template.
Manage Smart Form Body
Administrators can change the Smart Form body by using the Smart Form Editor.
1. Open the Smart Form Editor using transaction SMARTFORMS.

2. Create a new e-mail template by copying an existing template. Choose an existing e-mail template from the
Form list, and then copy it by clicking on the Copy icon in the toolbar.
3. Enter a name for the new Smart Form Body. We recommended that you begin the name of the customized
e-mail template with Z or Y.
You can create this new template only as a local object, or you may transport it by choosing a package.
4. Click the Display or Change button in the toolbar to enter SAP Form Builder, in which the newly created
Smart Form Body opens in edit mode.
5. Open the e-mail template body by expanding Pages and Windows until you see the leaf node NOTIF_BODY.
Double-click this and you can edit the notification text body.
6. In the notification, you can use the following variables:
Variable Description
&I_PROCESS_NAME& Process instance name
&I_INST_CTX_STR& Process instance context
&I_RGN_NAME& Activity name
&I_RGN_CTX_STR& Activity context
&GV_URL& URL to either Activities list or Process Monitor in user-

friendly name
&URL& Full URL to either Activities list or Process Monitor
 Note
You can maintain parameter EMAIL_NOTIFICATION_URL_PREFIX to replace the http link with the relevant
server name. For detailed information, refer to SAP Note 1717100 .
Related Information
Business Process Flows [page 11]
7.6.4 External Process Integration
Integrate external workflows with Business Planning and Consolidation business process flows.
Complicated planning processes may exist where data flows among different organizations and departments
and requires multiple levels of approvals, counter-signatures, and so on. To help accommodate this, you can
integrate business process flows with workflows that are outside of Business Planning and Consolidation.
Overall Process
1. The process owner and the business user define the planning process. Then, the process owner defines
the BPF template as a main planning process within BPC and defines the activities that need approval.
2. The process owner maintains the approval workflow in an external workflow system, for example, the office
automation system (OA). Meanwhile, all workflow processes are registered in the BPC BPF automatically
(if there is an API to load the workflow process from the OA system) or manually. The user maintains all
necessary parameters such as server and URL in the BPC BPF.
3. For each activity that needs an external approval workflow, the process owner assigns the corresponding
approval workflow process. The process can be different for different driving dimensions and contexts.
4. The user assigns the external workflow to a deployed BPF template. If a new template version is created,
the mapping of the old version is not inherited automatically. When the user selects the template, no
mapping is shown. The user can check the process mapping of the previous template version and can copy
the mappings to the new template version.
 Note
Creating two mapping entries with the same context, activity, and driving dimension member is not
permitted. You can create an entry for all driving dimension members, however. If another entry exists
for specific driving dimension members with the same context and activity, the system uses this
specific entry at runtime.
7.6.4.1 Integrating External Workflows with Business

Process Flows
Steps for integrating workflows that are outside of Business Planning and Consolidation with the system's
business process flow functionality.
Procedure
1. The planning instance owner initiates the planning process.

2. The performer finds the activity in BPC My Activity. Optionally, an OA notification activity may be created,
which can be found in the OA. The performer can open a link in the OA notification to launch the BPC
activity and complete the required task.
3. The performer submits an activity, which initiates the workflow instance and passes the following
information to the workflow: instance information, such as name and owner; activity information, such as
context, driving dimension, and comments; links for any attachments; reviewer workspace URL; and key
figures.
4. The approver sees all information in the workflow necessary to support his completing the approval action.
The approver can open the activity reviewer workspace by selecting the link provided, but cannot approve
or reject the activity from the reviewer workspace.
5. In the external workflow, the approver approves or rejects the activity, and add comments if needed. The
following then apply:
a. If the current approver is the last approver in the workflow process, the BPF activity is approved or
rejected automatically.
b. If the current approver is not the last approver in workflow process, the BPF activity status remains
unchanged.
c. Workflow status can be updated to BPF instance comments.
6. Performers can see the workflow status and comments in My Activities.
7. Process instance owners can see the latest status and comments of all instances for which they are
responsible in the Process Monitor.
8. Process instance owners can sort, filter, and search for instances in the Process Monitor to quickly locate
specific instances.
A performer can reopen an activity in a BPF. When the reopened activity is submitted, a new external
workflow is initiated.
7.7 Work Status Setup
This function allows you to lock a region or slice of data in a model. The work status setting overrides the
member access privileges of a user to write to a given region.
Use
The region of data to be locked is defined by several dimensions per model that are composed of one Owner
dimension and a number of Other dimensions. You can predefine an attribute of the owner InfoObject as the
owner property on the Business Warehouse backend to maintain work status owners. An InfoObject can be
used as an owner dimension only when some criteria are met. Refer to the section Owner Dimension and
Hierarchy below for detailed information.
When you set up work status, you define the following:
● Work states - Physical statuses of data that can be customized according to your business needs, such as
unlocked, submitted, and approved.
● Level of security - The users or teams who can change data in the system, which is All, None (locked for
all), Manager, or Owner. See Controlling Who Can Change Data below.
The users or teams who can change the work status, which is Owner, Manager, or Owner and Manager. See
Controlling Who Can Set Work Status below.
● Push - Equivalent to the check box On All Descendants when setting work statuses, the option allows you to
set one work state to all descendants of a member. This does not includet the selected parent member.
After you set up work statuses, other users can use them to apply a state to a current view and lock its data for
review, approval, and so on. For example, your month-end close business process requires that a specific set of
data is locked down so that accurate month-end reports can be created. After a data submission, the owner
sets the work status to Submitted, which has a security level of None. This locks the data intersection from
subsequent submissions.
Features
Owner Dimension and Hierarchy
● The owner dimension must be shared by all InfoProviders in the model.

● The owner dimension must have an attribute that can be used for setting the owner. The attribute should
be of the type CHAR and its length should be at least 12.
● One or more hierarchies should be maintained for the owner dimension on the Business Warehouse
backend.
Derive Owner
You can either specify an attribute of the owner dimension as Owner (the value should be a user ID) or as Team
(the value should be a team's ID); you can also specify both.
The user(s) derived from the owner attribute, or the team member(s) derived from the team attributes, or from
both attributes, are considered owners of the current member ID of the owner dimension.
Controlling Who Can Change Data
You define who can change the data in the system:
● All - All users with the appropriate member access rights can change data
● None - No one can change the data
● Manager - Only managers (members in the parent nodes of owners) can change data
● Owner - Only owners can change data
Controlling Who Can Set Work Status
You define who can set the work status to a particular state for a region of data:
● Owner and Manager - The owner of the specific member ID and the owner of the parent to the specific
member ID
● Owner - The owner of the specific member ID
● Manager - The owner of the parent to the specific member ID
Owner/Manager Determination
● A manager is the owner of a parent-level member.

● Parent member owners act as an owner for that specific parent member ID
● Parent member owners act as a manager for their direct children - the parent owner can change any
specific direct child work status; can be both parent and base members
● When using On All Descendants - the owner of a parent node member can update all children of all levels
below
● Base members owners act as owner only
● Members (top of a hierarchy) that have no parent but only children act as their own manager in addition to
owner
Controlled By Rule
● An owner is defined by only one dimension hierarchy, the OWNER dimension

● A work status can be set on a specific single member ID, where the manager does not use On All
Descendants
● A work status can be set on a series of member IDs, where the manager uses On All Descendants
Setting the Work Status
● If the user is acting as an owner, they can select a work status controlled by Owner or Owner and Manager.
● If the user is acting as an owner and the selected member has no parent, the user also acts as a manager
(top of the hierarchy) and they can select a work status controlled by Owner, Manager or Owner and
Manager.
● If the user is the parent owner in the role of Manager, then they can use the On All Descendants option (to
push the work status to children). This option is not valid for a base member, the Owner role.
Consecutive Work Status Rules
● You can set work status in a forward direction (progressive) or in a backward direction (regressive)
● For a user acting as an Owner, the order matters
○ The user can only select the next (forward) work status that is controlled by either Owner or Owner
and Manager
○ The user can select the previous (backward) work status that is controlled by either Owner or Owner
and Manager
○ The user cannot select a work status that skips a work status controlled by Manager, either forward or
backward
● For a user acting as a Manager, the order does not matter.
○ The user can only select a work status that is controlled by either Manager or Owner and Manager,
either forward or backward
○ The user can select a work status that skips a work status controlled by Owner, either forward or
backward
● If you expand all records on the non-OWNER dimensions only, and find the current work status on each
record, the model checks each and every expanded record for the rules. If one record fails, the whole
request is ignored
Bottom-Up Rule
● A parent work status cannot be higher than its children. Order matters.
○ The order of work statuses is determined top to bottom in the work status code screen. The first code
is 0, the next code is 1, and so on.
○ A child can have a work status that is greater than or equal to its parent.
● For a user acting as owner:
○ If a child is set to Submit, it parent cannot be set to Approve.
○ If one or more children have a work status that is lower than the work status being set for a parent
(forward), then an error appears.
○ If the parent's work status has a higher work status, an error appears if you attempt to regress a child's
work status (backward).
● The rules above also apply when the user is acting as a Manager, where On All Descendants is selected or
the Manager sets a specific child work status.
● For all expanded records (non-OWNER dimensions), the immediate parent is checked to verify that it has a
work status that is less than or equal to its children. If one child fails this rule, all fail.
External Hierarchy Nodes
● You can set work status for a node member which is an external dimension (SAP BW characteristic)
member. The owner is derived by the same property that is defined in the owner dimension. If the owner
cannot be derived, the work status cannot be set.
● You can set work status for a member whose parent node is an external dimension member. The manager
of the current owner is derived as follows:
1. The owner of the parent node (external dimension) is derived from the same property as defined in the
owner dimension and it becomes the manager of the current member.
2. If an owner of the parent node cannot be derived (the parent node does not have the same property, or
the property does not have a valid value), the system checks one level up the hierarchy, until an owner
is found.
3. If the system cannot derive an owner of the parent node, the owner of the current member also
becomes a manager.
 Note
Work status cannot be set on a text node. Text nodes are skipped when searching for an owner.
Defining Work Statuses
Work statuses are defined for a specific model.
There is no limit to the number of work states you can create, but there is a practical limit.
There is a default work state that must be first. It has an internal code of 0 and is controlled by the Manager
and Owner (Controlled by is set to Owner and Manager). You cannot change the Controlled by value. You can
change the text description.
You can change the order of work states. When you do that, the system deletes all locks for the model to which
the work status belongs. Deleting states also deletes all locks. Adding states to the bottom of the list or
changing a state definition does not impact existing locks, but may impact business users. We recommend that
this be done only during the testing phase of a system implementation.
Work Status Rules
Note that in this section the term member denotes the members of the owner dimension.
The following rules describe work status behavior:
● The default method for managing work status is bottom-up. That is, the status of a parent cannot be higher
than the status of its children.
● The maximum status a parent can be set to is the lowest status of its immediate children.
● If the status of a parent is set to Locked, you cannot unlock the children.
● The minimum status a child can be set to is the status of its immediate parent. For example, if the parent
status is Submitted, the child status must be at least Submitted.
● The owner of an entity can set the work status to any status designated as an Owner status, where Owner
status means that the status is controlled by the owner or the owner and the manager.
● The manager of an entity can set the work status to any status designated as a Manager status where
Manager status means that the status is controlled by the manager or the owner and the manager.
● A manager is the owner of a parent-level member. The owner of a parent level member is the manager of all
its descendants.
● When setting a lock on the parent members of multiple dimensions, locks are set for all members under all
parents, specifically, the Cartesian product is stored as locked. For example, the following table shows the
locks that are set when including all children for entity:p1, category:actual and time 2016.Q1.
Entity Category Time Work Status
Child1 Actual 2016.Jan Upload
Child2 Actual 2016.Jan Upload
Child1 Actual 2016.Feb Upload
Child2 Actual 2016.Feb Upload
Child1 Actual 2016.Mar Upload
Child2 Actual 2016.Mar Upload
● If you reorder work status codes in the Admin client, all locks are deleted. This also applies deleting a work
status.
● A parent value for a non-OWNER dimension is not stored. When the user selects a parent for a non-OWNER
dimension, it is expanded to all base members, and only stores the base members.
● A parent value for the OWNER dimension is stored. For example, the following table shows what is stored
for entity:p1, category:actual and time 2016.Q1.
Entity Category Time Work Status
P1 Actual 2016.Jan Upload
P1 Actual 2016.Feb Upload
P1 Actual 2016.Mar Upload
● When applying rules, if the model encounters any error, it rejects the entire user request. In this case, no
records are updated.
Number of Locking Dimensions
Work status supports between 1 and 14 locking dimensions, including the owner dimension. The default
number is 5.
To change the number of locking dimensions, run transaction RSBPC_ADMIN, and change the value of the
BPC_WS_DIM_COUNT property.
Setting the Work Status by InfoProvider
If an administrative user select the Set Work State by InfoProvider option, other users can then choose to
change the work status by individual InfoProvider when they do reporting or planning jobs. In this case, when
the work status of that InfoProvider is changed, the other InfoProviders will not be affected.
Sending E-mail Notifications to Owners and Managers
The system can send an e-mail notification to corresponding owners and managers to notify them when a work
status changes.
The e-mail address to which the notification is sent is defined in Business Warehouse. To add or modify the
default e-mail address for an owner or manager, an administrator can run transaction SU01, choose the name
of the user, and then enter an e-mail address in the Address tab. You also need to make sure proper SMTP
settings are configured via transaction SCOT for the e-mails to be automatically sent out. For detailed
information, refer to the SMTP Configuration Guide.
Then you can compose an e-mail notification template and trigger the e-mail notification for work status
changes in the Planning and Consolidation web client by choosing Notifications and checking Activate E-mail
Notifications in the Work Status Settings page. You can either directly use the default message template or
customize a new message.
Activities
You create work statuses to reflect statuses of different data entry levels with the progress of your business,
such as unlocked, submitted, and approved. No predefined work statuses exist within Business Planning and
Consolidation.
Go to the Administration screen and under the Work Status section, choose Work Status Configuration. After
that select the model, whose work status you want to configure.
You can modify the order in which work statuses display in the system by using the up and down arrows.
You can delete a work status that is not currently in use by selecting the work status and choosing Delete.
Select the Set Work State by InfoProvider checkbox, so that only a given provider is affected by the work status
change.
7.8 Journal Administration
Administrators set up and manage the Journals component of SAP Business Planning and Consolidation.
Prerequisites
Before users can adjust data in the database using the Journals feature, an administrator must perform the
following tasks:
● Define a journal template. See Journal Template Creation [page 140].

● Set journal model parameters. See Journal Model Parameters [page 143].
Users must be granted corresponding authorization objects on the Business Warehouse side to perform these
tasks. For detailed information, refer to the topic “Authorization Objects for Performing Consolidation Tasks
(Embedded only)” in the Security Guide available on the SAP Help Portal.
7.8.1 Journal Template Creation
A journal template is an input form into which you enter journal entries. You can set up one or more journal
templates for each model.
Features
A journal template consists of the following:
● Headers
○ Header dimensions, which are fixed, constant dimensions for all journals in a model.
The header dimensions set in a journal template become page keys for journal entries based on that
template. The template header must always include one dimension. Model dimensions that are not
part of the header become detail dimensions for which users add line items when creating a journal
entry.
○ Additional header items containing clarifying information that are saved with the journal entry. These
items are free text entry fields (limited to 60 characters) or lists of entries from which users make a
selection. Alternatively, an additional header can be defined as a Date.
Adding additional header items is not required when creating a template, and if they exist in a
template, users are not required to complete them. The maximum length of an additional header item
is 20 characters.
○ Detail dimensions, which are the remaining dimensions that are required to change the model data via
the journal entry. The Account and Flow dimensions are always included in the detail section of a
template.
Detail dimensions are in columns, so each row under the dimension name becomes a detail line. You fill
in members for each of the dimensions and the debit or credit amount for that detail line. The
maximum number of detail lines is determined when you create the journal entry.
Two additional options are available for detail header dimensions:
○ Balanced by Entity: If you select this option, for each entity in the journal entry, credits must be
equal to debits.
○ Balanced by Currency: If you select this option, for each currency in the journal entry, credits must
be equal to debits. There can be multiple reporting currencies in a journal entry.
 Note
If you have already created a journal template, creating a new template that changes the structure of
the journal entries deletes the old template and all journal entries associated with that template. This
removes your audit trail, even though changes made to the model data (InfoProvider data) through
posted journal entries are maintained. If you recreate the journal template, all transaction data is
deleted. However, if you add or remove one or more dimensions from a model, the corresponding
journal template is automatically updated and the journal entries are maintained. If you recreate the
journal template, but do not change the structure of the template keeping all header and detail
dimensions the same, you have the option to keep the existing journal entries.
● Reopen Rules
Define translation information for the dimensions used in the reopen tasks. For more information, see
Journal Reopen Rules [page 142].
Activities
To create a journal template for a model, perform these steps:
1. Go to Administration and under the Features section, choose Journals.

2. Select the row containing the model for which you want to create the journal template, then click New in
the toolbar.
3. Select header dimensions and modify the order of the header and detail dimensions if desired.
4. Add additional header items if necessary.
To create extra header text fields in a template and to change the header text fields to selection boxes,
define sub-items for one of the additional header items.
5. Define reopen rules.
6. Save and close.
Related Information
Journal Model Parameters [page 143]
7.8.1.1 Journal Reopen Rules
Before you can reopen journal transactions, you must define translation information for the dimensions used in
the reopen tasks.
The translation table defines the Source and Destination accounts. You typically do this for specific accounts,
but you can create translations for other detail dimensions.
Features
When you open the translation table for the first time, the system opens a default table based on the journal
template of the environment. The default value is *, which is interpreted as any dimension member. You can
modify the table as needed.
The table is divided into two column groups: Source and Destination. The individual columns in each of these
column groups are described below:
Column Heading Description
Account Type Displays the four required account types: AST, EXP, INC, and
LEQ. The first time the system creates the translation table
for a model, it uses these required account types. You can
add additional account types by adding new rows, but these
account types must remain in the table.
<Filtering Property> Select the filtering property from the Filtering Property drop
down list above the table.
<Source dimension members> One or more columns that were selected during the tem
plate creation.
Column Heading Description
Sign Enter plus ( +) to keep the value in the same credit or debit
position. Enter minus ( -) to switch the value from the debit
to credit, or credit to debit position.
<Target dimension members> One or more columns that were selected during the tem
plate creation.
Activities
To define journal reopen rules:
2. Select the row containing the model whose journal template you want to open, then click Open in the
toolbar.
3. Select the Reopen Rules tab. Insert a new row for each additional account type (AST, LEQ, INC, EXP) by
choosing the Add button. Remove rows by choosing the Remove button.
4. For each account or dimension you want to convert, enter the source and destination member IDs under
the associated dimension.
7.8.1.2 Journal Model Parameters
You use model parameters to define conditions for journals.
Features
The following journal parameters are available:
● Enforce Balanced Journals

Select this parameter to specify that journals must be balanced when they are posted.
When selecting this parameter this affects all the journals that are generated from the given template. If
you only want some of the journals to be balanced, you must set this separately for each journal entry.
● Allow Journals to be Reopened
Select this parameter to allow users to reopen journals. If selected, the Reopen button appears in the
toolbar in the Journals page of Consolidation Central.
Activities
To set up journal model parameters for a model, perform these steps:

2. Select the model whose journal parameters you want to modify and click Journal Parameters in the toolbar.
3. Make your selections in the Journal Parameters dialog box. By default, parameters are not selected.
4. Click OK.
7.8.2 Delete All Journal Entries from Model
You can delete all journal entries from a model database before moving from a development environment to a
production environment.
You delete journal entries from a model in Business Planning and Consolidation Administration.
 Caution
Although changes that were posted to the database by journals remain, deleting the journal entries
removes the journals themselves and their audit trail from the model.
Prerequisites
You have AdminJournal rights.
Activities
To delete all journal entries from a model, do the following:
1. Go to Administration and under the Features section, choose Journals. Then select the row of the model
whose journals you want to delete.
2. Click Delete Journals.
All journals for the model are deleted.
7.8.3 Limits to Dimension Members for Journal Entries
You can limit the dimension members available to users when they double-click member cells in a journal
template during journal entry.
Features
You can limit journal dimension member lists by adding the property EnableJRN to the dimension for which
you want to limit journal access. Then, in its dimension sheet, type a Y in the EnableJRN column of base-level
members for which you want to allow users to post journal entries. Repeat this for each dimension you want to
limit, then process the dimensions.
Example
You might want only some account members used for journal entries, regardless of whether the users have
access to other members.
7.8.4 BAdI for Generating Calculated Amounts When Saving
a Journal
When saving a journal, you can add or calculate extra amounts by implementing the Business Add-In (BAdI)
UJJ_CALCULATED_AMOUNT.
Features
Enhancement Spot
The BAdI is defined in the following enhancement spot: UJJ_CALCULATED_AMOUNT.
When implementing a new BAdI, a filter must be set with the following parameters:
● Appset_id: Model ID
● Application_id: Environment
Sample BadI Implementation
A sample implementation is located in the following implementation spot:

CALCULATED_AMOUNT_SAMPLE_IMPL.
In the sample, when P & L entries are made, the resulting net profit (loss) impact is generated on the Balance
Sheet retained earnings account. This impacts the closing balance flow, every time a balance sheet account is
booked.
Interface to Implement
You implement the following interface: IF_UJJ_CALCULATED_AMOUNT.
Method CALCULATE_AMOUNTS:
Import Parameter Description
IT_JOURNALS Type A table containing the list of journals to be saved.

UJJ_T_BADI_CA_JOURNAL
Export Parameter Description
ET_CALCULATED_AMOUNTS Type A table of calculated amounts containing the amounts to be added

UJJ_T_BADI_CA_JOURNAL_AMOUNTS to the journal list. The output journal ID must match the input jour
nal list.
 Caution
When returning a table of calculated amounts, these amounts must contain only the values for the detail
dimensions. If you set a value for a header dimension, the BAdI returns an error.
Exception Description
CX_UJJ_EXCEPTION A journal exception that may be thrown.
Data Types
UJJ_T_BADI_CA_JOURNAL
Table for UJJ_S_BADI_CA_JOURNAL.
UJJ_S_BADI_CA_JOURNAL
The following fields are defined in the structure:
Field Type Description
APPSET_ID UJ_APPSET_ID Environment ID
APPL_ID UJ_APPL_ID Model ID
JRN_TMPL_ID UJJ_JRNTMPL_ID Journal Template ID
JRN_ID UJJ_JRN_ID Journal ID
DESCRIPTION UJ_DESC Description
USERC UJ_USER_ID The user who saves the journal
DATEMODIFIED TIMESTAMP The modification date
USERP UJ_USER_ID The ID of the user who has posted the journal
DATEPOSTED TIMESTAMP The posted date
STATUS UJ_DESC The status of the journal
IDJ_AUTO_REV UJ_ID The auto reversed ID
IDJ_OLD UJJ_JRN_ID The original ID of the journal
IDJ_GROUP UJJ_JRN_ID The ID of the group to which the journal belongs
AUTO_REVERSED UJ_FLG CHAR True if the journal is automatically reversed
MUST_BE_BALANCED UJ_FLG True if the journal must be balanced to be

saved
MAY_BE_REOPEN UJ_FLG CHAR True if the journal may be reopened
EDITABLE UJ_DIM_MEMBER Multiple header dimension of a journal group
VARIABLET UJ_DIM_MEMBER Multiple value dimension ID
AMOUNTS UJJ_T_BADI_CA_AMOUNT Table of amounts
EXTRA_FIELDS UJJ_T_KEYMEM Table of additional headers
IS_BALANCED UJ_FLG CHAR True if the journal is balanced
UJJ_T_BADI_CA_AMOUNT
Table for UJJ_S_BADI_CA_AMOUNT.
UJJ_S_BADI_CA_AMOUNT
REMARK UJ_STRING Remark
AMOUNT UJ_KEYFIGURE The value of the amounts
DEBITCREDIT UJJ_DEBITCREDIT Set the value to:
● C: if the amount is a credit

● D: if the amount is a debit
MEMBERS UJJ_T_KEYMEM This table contains the list of dimensions that

defines the journal amount. Both detail and
header dimensions are included in this table.
UJJ_T_KEYMEM
Table of UJJ_S_KEYMEM.
UJJ_S_KEYMEM
TABKEY TABKEY The dimension ID
MEMBER UJ_VALUE The member value
IS_HDR_FLD UJ_FLG CHAR Set the value to True if the dimension is a

header dimension; otherwise it is a detail dimen
sion.
UJJ_T_BADI_CA_JOURNAL_AMOUNTS
Table for UJJ_S_BADI_CA_JOURNAL_AMOUNTS.
UJJ_S_BADI_CA_JOURNAL_AMOUNTS
JOURNAL_ID UJJ_JRN_ID The journal ID
AMOUNTS UJJ_T_BADI_CA_AMOUNT The table of amounts
7.9 Auditing
Use this function to configure data auditing.
You can perform data auditing to track changes to transactional data at the InfoProvider level.
More Information
7.9.1 Data Auditing
This function tracks changes to transactional data at the InfoProvider level, such as when and by whom records
were changed within an InfoProvider.
Activities
To display data auditing, go to Administration and under the Audit section, choose Data Changes. Select an
InfoProvider, and change its status to On.
Once a data change is recorded, you can run a report that shows that change based on specified criteria (see
Reporting on Data Changes [page 45]).
You can create a BW Query with audit characteristics.
7.10 Supported BAdIs
SAP Business Add-Ins (BAdIs) are used to adapt SAP software to specific requirements. They can be inserted
into the system to accommodate user requirements that are not included in the standard delivery.
Business Process Flows
● BADI_RSBPCB_SETUSER - Provides the performer and reviewer of a BPF activity. This BAdI applies to both
Business Process Flows and Work Status.
Work Status
● BADI_RSBPCB_SETUSER - You can implement customized logic that provides the owner and manager for
work status. This BAdI applies to both Business Process Flows and Work Status.
7.11 Security
User Administration and Authentication
● User Management [page 150]

This lists the tools to use for user management and the types of users required.
● Integration into Single Sign-On [page 151]
This describes how the application supports Single Sign-On mechanisms.
● Setting Up Users [page 152]
This explains how to add new users in an environment, modify them, and delete them.
● Setting Up Teams [page 153]
This explains how to set up and maintain teams of users.
Authorizations
The SAP BW/4 HANA authorization concept is based on assigning authorizations to users based on roles. For
role maintenance, use the profile generator (transaction PFCG).
To define the models and data within those models to which users have access, you can use data access
profiles in both the standard and embedded configurations of Planning and Consolidation. For detailed steps in
a standard configuration, refer to ; For details in a embedded configuration, refer to Data Access Profile Setup
[page 154].
To define what types of activities or tasks a user is authorized to perform in different functions, you can
leverage the SAP NetWeaver authorization concept:
● In the Business Planning and Consolidation embedded configuration, you assign authorization objects to
users based on roles.
● In the Business Planning and Consolidation standard configuration, you assign task profiles to users or a
team of users in the web client.
For more information about how to maintain roles, see the SAP NetWeaver role administration information on
the SAP Help Portal at http://help.sap.com.
7.11.1 User Management
User management for the application uses the mechanisms provided with the Application Server ABAP, for
example, tools, user types, and password policies.
This table shows the tools to use for user management and user administration in the application.
User Management Tools
Tool Detailed Description Prerequisites
User and role maintenance with SAP For more information about user and -
NetWeaver AS ABAP (Transactions role administration of AS ABAP, see the
SU01, PFCG) SAP Help Portal at http://help.sap.com
.
User Types
Business Planning and Consolidation
The user types required for the application include the following:
● Individual users
○ Dialog users are used for administration-related tasks.
● Technical users — not required
Standard Users
Business Planning and Consolidation
The application does not require the creation of additional dedicated users for any special purposes. Its use is
possible via user accounts created for regular users by assigning the necessary application-related
authorizations to them.
User Data Synchronization
The application does not deliver additional user data synchronization related features in addition to those
available in the SAP NetWeaver platform. It also does not impose any special needs or restrictions, which would
limit the usage of related NetWeaver tools.
 Recommendation
We recommend that the application is used in an environment where the same users exist throughout all
the connected systems in the landscape.
7.11.2 Integration into Single Sign-On
The application is capable of operating in any single sign-on environment supported by SAP BW/4 HANA out of
the box, meaning there are no limitations imposed by the application on the possible single sign-on
configurations within an SAP landscape. Refer to the Authentication and Single Sign-On section in the Security
Guide for SAP BW/4 HANA.
The supported mechanisms are as follows:
● Secure Network Communications (SNC)

● SAP Logon Tickets
● Client Certificates
● SAML 2.0
 Note
SAML support is only available on SAP NetWeaver ABAP or Java 7.02 or higher.
● SPNego with Kerberos
For more information about the supported mechanisms, search using corresponding keywords on the SAP
Help Portal at http://help.sap.com .
SSO Ticket Validity and Web Session Expiration
When a user connects to the Planning and Consolidation web client, SAP NetWeaver not only creates a web
session but also generates an SSO (single sign-on) ticket (in the MYSAPSSO2 cookie). This ticket has a default
validity of 8 hours.
After session timeout, the web session correctly expires but the SSO ticket remains valid. If the user sends a
new request after the session has expired, the system authenticates the user through SSO and creates a new
session. From the user perspective, it appears that the session has not expired.
In order to have correct session expiration, the administrator must limit the validity period of the SSO ticket
(for example, to two minutes, which is the validity period of reentrance tickets). You set this using the kernel
parameter login/ticket_expiration_time in the SAP NetWeaver default.pfl configuration file, for
example, login/ticket_expiration_time=0:02.
For more information about how to set this parameter, see the SAP NetWeaver help at http://help.sap.com/
saphelp_nw74/helpdata/en/22/41c43ac23cef2fe10000000a114084/content.htm .
7.11.3 Setting Up Users
You can add new users in an environment and assign them to teams, task profiles (standard only), and data
access profiles.
If you are not using the default task or data access profiles and have not set them up yet, we recommend that
you define them before adding users. You might also want to create teams, so that you can assign the newly
added users to the appropriate teams.
Alternatively, when you define the teams and profiles, you can assign users to them at that time.
 Note
Sarbanes-Oxley compliance is a hardcoded behavior in Business Planning and Consolidation, as the

system does not save users' passwords on client machines.
Adding Users
Before you can add a new user, you must have created that user in the ABAP back-end. For more information,
see the SAP NetWeaver Security Guide.
To add users to Business Planning and Consolidation in a standard configuration, go to Administration and
under the Security section, choose Users. In the Users view, select Add. In the Add User assistant, select the
one or more users to add in the environment and assign one or more teams to the users.
To add users to Business Planning and Consolidation in an embedded configuration, enter transaction code
SU01 on the Business Warehouse back-end, type the name of the new user, and choose Create. Then go the
Business Planning and Consolidation web client to define teams or data access profile.
Modifying Users
To modify a user definition, go to Administration and under the Security section, choose Users. In the Users
view, highlight the user and select Edit. You can then add or remove teams, task profiles (in a standard
configuration of the application) and data access profiles for the user.
Removing Users (Standard only)
To remove an existing user, go to Administration and under the Security section, choose Users. In the Users
view, highlight the user and select Delete, then click OK.
Related Information
User Management [page 150]

Integration into Single Sign-On [page 151]
Setting Up Teams [page 153]
7.11.4 Setting Up Teams
You can set up and maintain teams of users. When you assign security to a team, the security works collectively
on the team members. This allows you to set up task and data access security for several users at the same
time.
Teams are not required to successfully set up security.
Adding Teams
To add teams, go to Administration and under the Security section, choose Teams. In the Teams view, select
New. In the Add Team assistant, enter an ID and a description for the team and assign one or more users to it.
Modifying Teams
To modify teams, go to Administration and under the Security section, choose Teams. In the Teams view,
highlight the team and select Edit. You can then add or remove users, task profiles and data access profiles for
the team.
Removing Teams
To remove teams, go to Administration and under the Security section, choose Teams. In the Teams view,
highlight the team and select Delete, then click OK.
Assigning Team Leaders
Assigning one or more team leaders is useful when you want to give them special access rights to the team's
folder. You can assign team leaders while you are defining or modifying a team. You can choose one or more
team members to be a team leader.
Related Information
User Management [page 150]

Integration into Single Sign-On [page 151]
Setting Up Users [page 152]
7.11.5 Role Assignment Based on Authorization Objects
In the Business Planning and Consolidation embedded configuration, you assign authorization objects to users
based on roles by leveraging the profile generator (transaction PFCG) tool of BW/4HANA.
Related Information
Authorization Objects for SAP Business Explorer

Authorization Objects for Administration (Embedded only)
Authorization Objects for Maintaining Data Access Profiles (Embedded only)
Authorization Objects for Modeling (Embedded only)
Authorization Objects for Reporting and Planning (Embedded only)
Authorization Objects for Performing Consolidation Tasks (Embedded only)
7.11.6 Data Access Profile Setup
Configuring a Dimension as Authorization Relevant
To configure a dimension as relevant for authorization, follow the steps below:
1. Run transaction RSD1.

2. Enter the dimension's technical name and choose Maintain.
3. In the maintenance screen that appears, choose the Business Explorer tab and then select Authorization
Relevant.
Authorization Levels
● SAP BW Analysis Authorization

Defined centrally in the BW backend system. The data access is controlled independently from other data
access tools.
This type of authorization is defined in transaction RSECADMIN and is assigned to a user.
● Environment Authorization
Extend the BW analysis authorization to an environment in Planning and Consolidation.
● Data Access Profile
The owner of Planning and Consolidation environment can define a data access profile and assign it to
Planning and Consolidation users.
Creating an SAP BW Analysis Authorization
1. Run transaction RSECADMIN and create a standard analysis authorization.

2. Assign the authorization to a PFCG role and generate a SAP NetWeaver profile with transaction PFCG.
3. Run transaction SU01 and assign the PFCG role or the NetWeaver profile to a user.
For more information, see the SAP BW/4 HANA analysis authorization documentation available on the SAP
Help Portal.
Creating an Environment Authorization
1. Create a standard SAP BW analysis authorization.

2. To assign the analysis authorization to a Planning and Consolidation environment, run transaction
RSECENVI.
3. Enter the environment name.
4. On the next screen, choose the required BW analysis authorizations.
Creating a Data Access Profile
1. In the Business Planning and Consolidation web client, go to the Administration page and under the
Security section, choose Data Access Profile.
2. On the screen that appears, choose New.
3. Enter the ID and description of the new data access profile.
4. Select the required model from the list.
5. For each authorization-relevant dimension, select the required members and set their access rights.
Important: Be sure to read the note below.
6. Go to the Users or Teams tab to assign the new data access profile to users that are assigned to the current
environment or teams that have corresponding users assigned to it.
 Note
You can group several members by hierarchy and access rights. To do that, select the required members
and choose Group.
You can split a member to separate lines for easier access rights maintenance. To do that, select the
required member and choose Split.
In step 5 above, if the members you select come from a hierarchy, you can further define the selection
range according to the relationship and level of the selected member in the hierarchy. However, if you
choose All Members or Aggregation, or you select members from a flat view, you will not be able to further
define such a selection range. For instructions on how to use Relationship and Level to define a certain
selection range, review this example in which you select member China from a hierarchy level that has
been defined as shown below:
Level 0 Level 1 Level 2 Level 3
Asia China Shanghai A1
A2
Beijing B1
B2
EUR FR PARIS E1
E2
After selecting China in this example, you then choose one of the five relationships and define levels of how
deep in the hierarchy you want the access right to take effect:
● If you choose Only Selected Nodes, the access right affects only China, which is the exact member you
select.
● If you choose Subtree Below Nodes, the access right affects China and all of its descendants.
● If you choose Subtree Below Nodes to Level (Static to Hierarchy) and set the level value to 2, this defines
to which level the selection range expands, starting from the root level, also known as level 0. In this
case, the affected members start from China and end at the level 2 members Shanghai and Beijing.
● If you select Subtree Below Nodes to Level (Relative to Node) and set the level value as 2, this defines to
which level the selection range expands, starting from the selected member. In this case, the affected
members are China and all members from the next two levels, which are Shanghai and Beijing in level 2
and A1, A2, B1, B2 in level 3.
● If you choose Complete Hierarchy, the access right affects all the members in the current hierarchy.
 Example
In the following example there are two dimensions - Customer and Country. The possible values for the
Customer dimension are 1, 2, 3 and 4, and the possible values for the Country dimension are DE and FR.
The access rights for these dimensions are defined as follows:
When the analysis authorizations and the environment authorizations are combined, customers 1, 2 and 4
all gain authorizations for country FR. The authorizations for country DE are not changed:
After the data access profile is added to the combined result of the previous step, only customer 2 has
authorizations for country FR because that is the only customer that appears in both the combined result
and the data access profile.
The data access profile does not define any permissions for country DE. There is no intersection between
the combined result of the previous levels and the data access profile. Because of that the permissions for
country DE are entirely excluded from the final combination of authorizations.
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.
Important Disclaimers and Legal Information PUBLIC 159
www.sap.com/contactsap
© 2018 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

BPC Embebido PDF

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

BPC Embebido PDF

Transféré par

Droits d'auteur :

Formats disponibles

PUBLIC

SAP Business Planning and Consolidation, version for SAP BW/4HANA

Application Help - SAP Business Planning and

THE BEST RUN

3 Business Process Flows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

5 Run Consolidation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

HTML5-based web client

SAP Analytics Cloud

Starting the Web Client

To start the Planning and Consolidation Web Client, do the following:

Open a browser and connect to the URL http://<PC_server:port>/sap/epm/bpc/web/, where

To log on directly to a specific environment, enter http://<PC_server:port>/sap/epm/bpc/web/

You can change the following settings:

Language The language in which you want the UI texts to appear

Date Format The format in which the date appears

Number Format The format in which the numbers appear

You can also upload a photo to customize your profile.

● To change the settings, choose Save.

1. Enter transaction code se38.

1. Enter transaction code se38 and execute program RSBPC_CUSTOM_LOGO

Home Page and Navigation [page 9]

2.5 Home Page and Navigation

The main navigation panel is composed of the following categories:

Changing the Environment

Context Sensitive Help

● Open-To perform: The new activity is waiting for completion or to be submitted.

● Reopened: The completed activity has been reopened.

Performing or Reviewing Activities

Work Status Integration

The following Consolidation features are available:

Consolidation Monitor [page 15]

5.1 Consolidation Monitor

In the Consolidation Monitor you can do the following:

● Execute consolidation tasks

1. In Consolidation Consolidation Monitor , select corresponding dimension members for dimensions in

Run a Consolidation [page 18]

5.1.1 Run a Currency Translation

You should be able to select multiple time periods.

Currency Translation Rule [page 85]

5.1.2 Run a Consolidation

Execute Carry Forward

Execute Account-Based Calculation

Execute Intercompany Booking

Execute Elimination and Adjustment

You should be able to select multiple time period members.

Change Work Status and Run Controls

Account-based Calculation Rule [page 85]

5.1.3 Working with Periodic Consolidations and Currency

Run a Consolidation [page 18]

5.2 Controls Monitor

The Controls Monitor enables you to execute and monitor controls.

The Controls Monitor is split into the following areas:

Display details on failed controls

Display controls results for one or more entities

● Expand a control with one or more breakdown dimensions.

Refresh the controls page

Controls [page 100]

5.2.1 Execute a Control Set

Perform these steps to execute controls and monitor their progress.

Controls Monitor [page 22]

5.2.2 Control Set Status

Possible control set status values are the following:

● Passed: all controls (blocking and warning) have succeeded