BPC101NW - S4HANA - en - Optimizado PDF

PUBLIC
SAP Business Planning and Consolidation for SAP NetWeaver 10.1

Document Version: 1.0 – 2018-09-05
Application Help for SAP Business Planning and

Consolidation for SAP S/4HANA
© 2018 SAP SE or an SAP affiliate company. All rights reserved.
THE BEST RUN

Content
1 SAP Business Planning and Consolidation for SAP S/4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.1 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Grid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.2 Home Page and Navigation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.3 Business Process Flows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
My Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.4 Process Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.5 Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.6 Documents (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.7 Run Consolidation (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Consolidation Monitor (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Controls Monitor (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Journals (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Ownership Manager (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
1.8 Run Consolidation (Embedded only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Consolidation Monitor (Embedded only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Controls Monitor (Embedded only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Journals (Embedded only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Ownership Manager (Embedded only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
1.9 System Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Reporting on Business Process Flows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Reporting on Data Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Reporting on Work Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Reporting on Comments (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Reporting on Administration Activity (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Reporting on Security Information (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
1.10 Creating Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Components of Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Charts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
Member Selector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92
Disaggregation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Work Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Comments (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Comments (Embedded only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Context (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Application Help for SAP Business Planning and Consolidation for SAP S/4HANA
2 PUBLIC Content
Page Axis (Embedded only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Planning Sessions and Locking Cells in Input Forms (Embedded only). . . . . . . . . . . . . . . . . . . . 101
1.11 Dashboards (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Create a Dashboard and Add Tiles (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Delete a Report or Input Form Tile in a Dashboard (Standard only). . . . . . . . . . . . . . . . . . . . . . 103
Modify or Delete a Dashboard (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
1.12 Creating and Modifying Workspaces (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
1.13 Uploading and Modifying Crystal Dashboard Templates (Standard only). . . . . . . . . . . . . . . . . . . . .105
1.14 Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Environment Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Dimension Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Model Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Consolidation (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Consolidation (Embedded only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189
Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Business Process Flow Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Work Status Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .344
Journal Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Context Defaults (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Drill-Through Setup (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
Document Types and Subtypes (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Auditing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Time-Dependent Hierarchies (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .369
Parallel Execution (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Supported BAdIs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Content PUBLIC 3
1 SAP Business Planning and Consolidation
for SAP S/4HANA
Product Information
Release SP00
4 PUBLIC SAP Business Planning and Consolidation for SAP S/4HANA
Feature Enhancements and Documentation Changes ● In the section titled Integration below, added informa
tion about data integration enhancements with SAP An
alytics Cloud.
● In Components of Reports [page 89], added informa
tion about excluding members from selected member
list.
● Modified all information about transaction code RSA1
(RSD1), as all configurations in RSA1, including manag
ing InfoObjects and InfoCubes, have been transferred to
BW modeling tools.
● In Process Settings [page 323], added information
about supporting the navigation attribute in the embed
ded configuration.
● In Creating Process Instances [page 339], removed the
standard only classification for archiving process in
stances as this is now supported in both standard and
embedded configurations.
● In Create or Modify a Consolidation Model (Embedded
only) [page 206], added information about choosing
fixed superior compounding dimensions.
● In Business Rules Management (Embedded only) [page
289], added information that you can choose text no
des and external node members only for source mem
bers of account, category, audit and flow type dimen
sions.
● In Create or Modify a Consolidation Model (Embedded
only) [page 206], added information about choosing
fixed superior compounding dimensions.
● In Consolidation Monitor (Embedded only) [page 48],
added information about supporting US Elmination type
business rules, changing work statuses, and executing
controls in consolidation monitor.
● In Set Task Sequence (Embedded only) [page 206],
added information about a new way of setting up tasks
and their sequences to be executed later in Consolida
tion Monitor.
● Added the new section US Eliminations Rule (Embed
ded only) [page 298] about enabling US Eliminations
and matrix consolidation in the embedded configura
tion.
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.
This release of SAP Business Planning and Consolidation uses SAPUI5 user interface technology, which is
based on standard HTML5. The user interface provides all the benefits of HTML5 and it supports languages
such as Hebrew and Arabic that are written and read from right to left.
SAP Business Planning and Consolidation for SAP S/4HANA PUBLIC 5
Two product variations called embedded and standard are supported based on the way your installation is
configured. Prior to support package 3 of release 10.1, these configurations were called unified and classic
respectively.
● Business Planning and Consolidation in the embedded configuration is integrated with SAP Business
Warehouse Planning Applications Kit. By using the BW Planning Applications Kit you can perform SAP
HANA-optimized planning. You can use the embedded configuration of SAP Business Planning and
Consolidation only with SAP HANA-based systems. For details about BW Planning Application Kit and BW
planning processor, refer to the Planning Processor topic within the SAP NetWeaver Analytic Manager
application help available at http://help.sap.com.
● In a standard configuration, you can use all the functionalities that are available in release 10.0 of SAP
Business Planning and Consolidation, version for SAP NetWeaver.
For details about the changes in the embedded and standard configurations, refer to “What’s New (Release
Notes)” available on the SAP Help Portal.
 Note
When information in this application help applies to only one of the configuration types, the title of the topic
contains an indicator of either Embedded only or Standard only. Topics that contain no indicator in their
titles apply to both embedded and standard configurations of Business Planning and Consolidation. Also,
information within a single topic that differs between the configuration types will be clearly explained within
the relevant content.
About this Release
Business Planning and Consolidation for SAP S/4HANA, is specifically designed for Real-Time Consolidation
while retaining all previous BPC functionality.
Real-Time Consolidation (RTC) is a consolidation solution that is based on the deep integration between SAP
S/4HANA and the embedded configuration of SAP Business Planning and Consolidation. It has privileged
direct access to universal journal entries, while leveraging the consolidation capabilities from the embedded
configuration of SAP BPC. For detailed information about Real-Time Consolidation, see the Real-Time
Consolidation (version 1709) in SAP S/4HANA help available on the SAP Help Portal.
Integration
HTML5-based web client
The HTML5-based web client offers an integrated view for both business users and administrative users.
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.
Web Client
When you first open the Web Client, you are presented with the home page. The home page is always available,
and it contains all components that you are authorized to access, including:
● Library [page 14] - Provides information about how to access the objects that are saved in the Library
view. You use the Library view to store and organize Planning and Consolidation objects (reports and input
forms).
● My Activities [page 12] - Provides information about using Business Process Flows (processes). For
information about setting up process templates, see the Administration section of the help.
● Administration [page 107] - enables administrators to perform setup and maintenance tasks for Planning
and Consolidation environments and models.
● System Reports [page 76] - Provides information about reporting on system information and activity.
● Run Consolidation (Standard only) [page 17] - Provides information about generating and managing
consolidated data to give you an accurate view of the financial situation of your organization in a standard
configuration.
● Run Consolidation (Embedded only) [page 47] - Provides information about generating and managing
consolidated data to give you an accurate view of the financial situation of your organization in an
embedded configuration.
● Documents (Standard only) [page 15] - Provides information about using the Documents view to post,
share, and retrieve files, and to manage the display of content. The Documents view contains documents
that users have uploaded manually
For more information about the home page, see Home Page and Navigation [page 10].
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/

#cm=<environment ID>;connType=<environment type>, where <environment type> has one of the
following values:
● classic - for Business Planning and Consolidation environments in a standard configuration

● 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.
1.1 Getting Started
Use
The following features are available within SAP Business Planning and Consolidation:
● You can change the user preferences to customize the display of your UI (see Preferences [page 8]).
● You can change the way data displays in table format (see Grid [page 9]).
1.1.1 Preferences
Use
You can change the user preferences to customize the display of your UI. You can make changes to the
language, date format and others.
Features
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.
Activities
To view and edit user preferences, in the upper left 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.
1.1.2 Grid
Definition
A table that displays data and allows you to alter the display of that data.
Use
You can display data in table format and change the display as follows:
● You can reorder the columns in a table using drag and drop.
● Where available, you can filter the data displayed in a table. To do that click the column header and then
click the button.
By entering a specific value, you can narrow the data displayed to only include that value.
● Display or hide certain columns using the (Column Selector), 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 selecting the column header.
The data is sorted in ascending or descending order.
1.2 Home Page and Navigation
Use
When you log in to the Web client of Business Planning and Consolidation, the first screen that you see is the
home page. From this page you can choose the functionality that you want to access.
In the home page you can choose the following pages:
● Library - Provides information about how to access the objects that are saved in the Library view. You use
the Library view to store and organize planning and consolidation objects (reports and input forms). If you
are using Planning and Consolidation in the standard configuration, you can also work with workspaces.
For more information, see Creating Reports [page 87] and Creating and Modifying Workspaces (Standard
only) [page 104].
● My Activities - Provides information about using business process flows (processes). For information about
setting up process templates, see Business Process Flow Management [page 320].
● Administration - Enables administrators to perform setup and maintenance tasks for Business Planning
and Consolidation. See Administration [page 107].
● System Reports - Provides information about reporting on system information and activity. See System
Reports [page 76].
● 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 (Standard only) [page
17].
● Standard only: Documents - Provides information about using the Documents view to post, share, and
retrieve files, and to manage the display of content. The Documents view contains documents that users
have uploaded manually. See Documents (Standard only) [page 15].
Navigation
When you open several pages, you can use the following ways to navigate between them:
● Use the arrows that appear at the left and right side of the page.
● Choose the button to select one of the opened pages.
● Choose the button to return to the home page.
Change the Environment
Click the active environment from the lower right corner of the screen and select the desired one from a list.
Set Preferences
Click on your name that is displayed in the upper left corner of the screen and choose Preferences to set
individual preferences. For more information, see Preferences [page 8].
1.3 Business Process Flows
Use
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 13].
● 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. 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.
For information on how system administrators configure e-mail notifications, see Setup of E-mail Notifications
[page 340].
1.3.1 My Activities
Use
This function displays the activities requiring action by you as the currently logged-on user. The action might
include performing activities assigned to you or reviewing any 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 that you can use to execute 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. It is not possible to 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. In the upper portion of the panel, you
can choose to display finalized or active processes, or display processes by ID, description, or both.
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 select the activities 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 332].If you are a process instance owner, you can
reopen activities of the processes you own without any limitations. To reopen an activity, hover your mouse
over the corresponding process and choose Reopen to select any activities that you want to reopen.
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. For details about how to define the integration of work status with business process
flows, refer to Integrating with Work Status [page 338].
1.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.
1.5 Library
Use
This function enables you to create and display Business Planning and Consolidation objects, such as
workspaces, reports and input forms. In Business Planning and Consolidation in a standard configuration, you
can also display dashboards that were created in SAP Crystal Dashboards, books created in the EPM add-in,
and dashboards made up of reports and input forms.
Features
Folders
The objects in the Library view are sorted by folders. You can select the following folders to see the objects
saved to it:
● Favorites - You can add objects to this folder to group to together the objects that you use frequently.
● Public - This folder contains content that can be accessed and modified by all users depending on the
permissions in place. It is possible to restrict access to this folder.
In Business Planning and Consolidation in an embedded configuration, users with the task profile Edit
Content of Public Folder can add and manage the content.
In Business Planning and Consolidation in a standard configuration, users with the task profile Update
Company Folders can add and manage the content.
● Private - You can create your personal folder and save content in it, which you do not want to share with
other users. The content of this folder cannot be accessed by other users.
● Teams - Each team has its own folder under Teams. The folder name is the team name. Users in the team
can access the corresponding team folder. Only team lead has edit access of the team folder.
You can create new folders under the Teams, Public, and Private folders.
Activities
To access the Library view, in the home page choose Library.
To filter by object type, select the object type from the Show menu. To show all objects, select All.
To add a new object, choose one of the object types that appear in the New bar.
For information about analyzing data using the EPM add-in, which is an add-in to Microsoft Office Excel,
Microsoft Office Word, and Microsoft Office PowerPoint, see the EPM Add-in for Microsoft Office User Guide
available on the SAP Help Portal ( http://help.sap.com/epm ).
Related Information
Uploading and Modifying Crystal Dashboard Templates (Standard only) [page 105]
Creating Reports [page 87]
Context (Standard only) [page 98]
Dashboards (Standard only) [page 101]
1.6 Documents (Standard only)
Use
The Documents view is a central repository for storing or sharing files and websites. You can use the features of
the Documents view to post, share, and retrieve files or the contents of a website and to manage the display of
content.
Features
Posting Files to the Documents View
You can post files or specify a URL to add to the Documents view by clicking Add Item. You then describe the
file or website, set access, and determine whether you want to send a notification e-mail about the posting.
A file can be any file saved to a hard drive or network folder. By default, the system allows you to upload files of
the following types, or file extensions: .XLS,
XLT, .DOC, .DOT, .PPT, .POT, .XML, .MHT, .MHTML, .XLSX, .XLSM, .XLSB, .ZIP, .PDF, .PPTX, .PPTM, .POTX, .POT
M, .DOCX, .DOCM, .DOTX, .DOTM, .CDM, .TDM, .PNG, .GIF, .JPG, .CSS, .MRC.
 Note
Administrators can change the environment parameter DEFAULT_EXTENSIONS to add other file types. For
example, files with the extension .TXT are not supported by default. Administrators must add it to the
parameter. For more details, see the SAP Business Planning and Consolidation 10.0 IMG Guide.
Administrators should evaluate carefully before enabling file types such as .HTM and .HTML for any user.
We recommend that you avoid using these extensions.
Viewing and Managing Content
Posted files and websites display in a list, and are filtered by a user's context, a user's view rights to
information, and any manual filters set. You can do the following with the files and websites in the Documents
view:
● You can view one item by double-clicking the title of the item. If the item is a website, it opens in a new
browser window. If the item is a document, the Save/Open dialog box appears.
● Documents that are associated with data are characterized as having a model context. For example, a
Microsoft Word document might be associated with a particular report. If you want to view a report and
anything that is associated with that report, select a particular context. The relevant reports and
documents are displayed.
● You can sort the list by column or row. Click the appropriate heading.
● You can categorize, sort, and filter documents in the Documents list by the following elements:
○ Document type and subtype
○ Model context
○ Access rights
○ Date
● You can filter the items in the Documents list to see a subset of the files by clicking Filter.
● You can assign a document type and subtype to aid sorting and filtering. Administrators define document
types. Subtypes are defined by users when the document is posted.
● You can permanently delete items that you posted to the Documents view by selecting one or more items
and clicking Delete.
Activities
To post or view documents in the Documents view, in the home page choose Documents.
1.7 Run Consolidation (Standard only)
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 (Standard only) [page 17]

Controls Monitor (Standard only) [page 23]
Journals (Standard only) [page 29]
Ownership Manager (Standard only) [page 40]
1.7.1 Consolidation Monitor (Standard only)
The Consolidation Monitor is a global dashboard for monitoring the consolidation progress for 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 incremental consolidations, since it communicates
to the consolidation engine on which entities to execute a currency translation or consolidation. For more
information about setting up your consolidation environment with dimension properties, model settings, and
journal definitions, see Consolidation (Standard only) [page 166].
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 (Standard only) [page 40].
The scope context area displays the selected dimension members: Time, Category and Group.
You can perform a full consolidation, which processes all entities in the ownership-based hierarchy, or you can
perform an incremental consolidation, which processes only updated entities. Incremental consolidations
reduce the impact on system performance and decrease response time.
Incremental consolidations and currency translations
You perform incremental currency translation or consolidation, or both, in the following cases:
● When an update to an entity is more recent than the last currency translation performed for the group or
sub-groups to which the entity belongs, then an incremental currency translation must be performed for
the entity.
● When an update to an entity is more recent than the last consolidation performed for the group or sub-
groups to which the entity belongs, then an incremental consolidation must be performed for the entity.
● When currency translation is performed for an entity, then an incremental consolidation must also be
performed, regardless of when the last consolidation was run.
 Example
A currency translation and a consolidation are performed on the Groups G_WORLD and G_ASIA, at 9:00
a.m. and 9:01 a.m., respectively:
Category Time Groups Currency translation Consolidation
Actual 2009.DEC G_WORLD 2010/09/01 09:00 2010/09/01 09:01

a.m. a.m.
Actual 2009.DEC G_ASIA 2010/09/01 09:00 2010/09/01 09:01

a.m. a.m.
At 9:05 a.m., the data for the entity Shanghai is updated:
Category Time Entity Data Updated
Actual 2009.DEC Shanghai 2010/09/01 09:05 a.m.
Since the data update occurs after the last currency translation and consolidation on the Groups to which
the entity Shanghai belongs, an incremental currency translation and consolidation must now be
performed on the entity Shanghai.
Technical entity storing aggregated data
If the Groups dimension (G or R type) contains group members (currency_type= G) having a corresponding
consolidation entity ( STORE_GROUP_CURR=Y and ENTITY=<Entity Dimension Member>) then, not only
the base entity with new data is reconsolidated, but at the end of each step (currency translation and
consolidation processes), the consolidation entity also re-aggregates all of the data of the entity members.
In the example above, when a currency translation and consolidation are performed for the entity Shanghai,
the corresponding consolidation entities ( E_WORLD and E_ASIA) re-aggregate data from all owned entities for
the corresponding groups (if G_ASIA has three entities: Shanghai, Seoul and Tokyo, all three entities are re-
aggregated to E_ASIA. The same principle applies to G_WORLD).
Prerequisites
An administrator has given you the View Consolidation Monitor and Run Consolidation Tasks access rights.
Features
In the Consolidation Monitor you can do the following:
● Display the control set status

Display the results of control execution. The control set status enables users to verify the accuracy of
reported data. For more information, see Control Set Status (Standard only) [page 26].
● Display the work status
Show the level of completeness of submitted data.
To display the work status in the Consolidation Monitor, the driving dimensions must be at a minimum
Category, Period and Entity. If additional dimensions are added, then a member must be selected for each
additional dimension to enable work statuses to be displayed. Every time a work status is changed, the
appropriate control set status must be checked.
● Display the currency translation status
Display the outcome of the currency translation processing. The status can be "Done" or "To be executed"
if data was modified since the last consolidation was executed.
● Run currency translations
Available currencies are those specified in the Group dimension or group members. Currency translation is
available at the 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. When you select a Group or Sub-
Group, the currency translation is run on the currencies defined for the selected group. For more
information, see Run a Currency Translation (Standard only) [page 20].
● Display the consolidation status
Display the outcome of the consolidation processing. The status can be "Done" or "To be executed" if data
was modified since the last consolidation was executed.
● Run consolidations
Generate consolidated data using data entered in packages manually or uploaded using Data Manager, and
journal entries (Journals). For more information, see Run a Consolidation (Standard only) [page 21].
● Display the running processes
Running processes are displayed with percent completion. You can only display processes for Groups to
which you have Read access.
● Reset the consolidation status
You can reset the status of a consolidation to "To be executed", in which case you would then need to run a
full consolidation. For example, you may want to reset the consolidation status to "To be executed" in the
following cases:
○ Changes in the Rate and Ownership cubes do not trigger incremental processes (consolidation and
currency translation)
○ Incremental processes for simulation categories do not verify updates to source categories
○ Masterdata changes do not trigger incremental processes
Activities
● Set the work status for an entity

1. In Consolidation Consolidation Monitor , select an entity and click Work Status in the toolbar.
2. In the Change Work Status dialog box, verify the selections in the Change Status For groupbox.
3. Choose a new status in the New Work Status groupbox and click OK.
● Run a currency translation.
● Run a consolidation and display running processes.
1.7.1.1 Run a Currency Translation (Standard only)
You can convert amounts from their source currency to a target currency. You can perform currency translation
at any group/entity level.
You perform currency translations in the Consolidation Central module of SAP Business Planning and
Consolidation.
Prerequisites
An administrator has given you the Run Consolidation Tasks access right.
You can perform currency translation on an entity if you have Write access to this entity.
To run a currency translation, you must define the following items:
● Category
Choose the type of reported data to which the amount to be translated is linked.
● Time
Select the data entry period in which the amount to be translated was entered.
● Group/Entity
Select the scope for which you want to run the translation. The translation is executed on the currencies
defined in the Group dimension.
● Reporting Currency
If you selected a base entity, this dimension is displayed, enabling you to select the currency in which you
want to run the translation.
● Rate Entity
If you selected a base entity, this dimension is displayed, enabling you to select the Rate Entity in which the
exchange rates to be used are stored.
● Execution Mode
You can perform a full translation, or you can update a previous translation by performing an incremental
translation.
Additionally, before running a currency translation in Consolidation Monitor, you can select an available post
logic script. The system will automatically execute the selected logic script after the translation is done.
Activities
To run a currency translation
1. In Consolidation Consolidation Monitor , in the scope context area, select the Category, Time and
Group dimension members for which you want to run the currency translation.
2. Select the row for the Group or Entity you require and click Translate Currency.
3. In the Translate dialog box, verify the selected dimension members and choose whether to run a full or
incremental translation.
4. Click OK.
Related Information
Currency Translation Rule (Standard only) [page 271]
1.7.1.2 Run a Consolidation (Standard only)
You run consolidations in the Consolidation Central module of SAP Business Planning and Consolidation.
Prerequisites
An administrator has given you the Run Consolidation Tasks access right.
You can run a consolidation at group level if you have Write access to the group.
To run a consolidation, you must define the following items:
● Category
Choose the type of reported data that you want to consolidate.
● Time
Select the data entry period in which the amounts were entered.
● Group
Select the scope for which you want to run the consolidation.
● Execution Mode
Choose whether to perform a full consolidation or to update a previous consolidation by performing an
incremental consolidation.
Activities
To run a consolidation, do the following:
1. In Consolidation Consolidation Monitor , in the scope context area, select the Category, Time and
Group dimension members for which you want to run the consolidation.
2. Select the row for the Group or Entity you require and click Consolidate.
3. In the Run Consolidation dialog box, verify the selected dimension members and choose whether to run a
full or incremental consolidation.
4. Click OK.
To monitor the progress of your consolidation, click Display Running Processes in the toolbar. The status of the
consolidation is displayed in the Consolidation Monitor page.
To reset the status of the consolidation to To Be Executed, select the group or entity for which a consolidation
has been run and click Reset in the toolbar. For an example on when to reset the consolidation status, see
Consolidation Monitor (Standard only) [page 17].
1.7.1.3 Working with Periodic Consolidations and Currency

Translations (Standard only)
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. Alternately, you can manually reset the entity's data to "To be executed" in the Consolidation Monitor,
for every consecutive period. In this case you would use incremental consolidation.
Related Information
Run a Consolidation (Standard only) [page 21]
1.7.2 Controls Monitor (Standard only)
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 (Standard only) [page 40].
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. In a Finance model, if a node entity is selected in the scope context area, only the child entities
of the node entity 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 given you the View Controls access right.
The Work status settings and the controls have been configured, and controls are enabled for the model, in
Planning and Consolidation Administration.
A value has been specified for the MONTHNUM property in the Time dimension.
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, Dismissed.
● Open a linked document to analyze the result in case of an error, and, for example, to perform manual
adjustments in data entry schedules.
● 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 309]; for more information
on control status, see Control Set Status (Standard only) [page 26].
Refresh the controls page
You can refresh the list of controls by clicking Refresh. For example, if a 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 (Standard only) [page 25].
● 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.
● 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 306]
1.7.2.1 Execute a Control Set (Standard only)
Perform these steps to execute controls and monitor their progress.
Prerequisites
An administrator has given you the Execute Controls access right.
You have read access to the data region for which controls are to be executed.
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 314].
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 (Standard only) [page 26]
1.7.2.2 Control Set Status (Standard only)
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, data load, journal entries, script logic 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 toTo Be Executed, calculated control data is not reset.
Every time calculations are executed, controls which 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 loaded data
(local currency), translated data, or consolidated data:
● 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 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 (Standard only) [page 25]

1.7.3 Journals (Standard only)
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.
● You have the appropriate rights to perform given tasks.
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 (Standard only) [page 32].
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 (Standard only)
your changes to one or more journal en [page 35].
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 (Standard only) [page
the list of journal entries. 37].
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 (Standard only) [page 32].
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
(Standard only) [page 35].
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 (Standard only) [page
journal entries are unposted. To select 35].
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 (Standard only) [page 36].
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 Querysearches 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
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 (Standard only) [page
38].
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 356].
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. For more information, see
Report in the toolbar. To select non-con Print Journal Reports (Standard only)
tiguous journals, hold down the CTRL [page 39].
key as you make your selections. In the
Journal Report tab that opens, click  Note
Print. To use this task, users must have
one or more task profiles related to
Journals, including
CreateJournal, PostJournals,
ReviewJournals and
UnpostJournals.
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 Reopen Journal Entries
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 Re
Templates . Open a journal template
open Journal Entries (Standard only)
and click the Reopen Rules tab.
[page 38].
1.7.3.1 Journal Entries (Standard only)
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 (Standard
only) [page 35].
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 (Standard only) [page 39].
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 (Standard only) [page 29].
1.7.3.2 Journal Entry Form (Standard only)
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.
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 (Standard only) [page 32]

Journal Postings (Standard only) [page 35]
1.7.3.3 Journal Postings (Standard only)
You post journal entries to enter the details of a transaction into the database.
Prerequisites
An administrator has given you Post rights.
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 cube 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 above options.
○ 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 (Standard only) [page 32]
1.7.3.4 Journal Groups (Standard only)
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 (Standard only) [page 33].
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 (Standard only) [page 35]
1.7.3.5 Journal Queries (Standard only)
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 (Standard only) [page 29]
1.7.3.6 Reopen Journal Entries (Standard only)
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 355].
The system is set to allow for reopening of journals using the Allow Journals to be Reopened journal parameter.
See Journal Model Parameters [page 356].
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, select a journal and 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 from which to select the journal entries you want to reopen.
3. In the Select destination section, specify a Category and Time member in which you want to reopen the
journal entries.
1.7.3.7 Print Journal Reports (Standard only)
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 (Standard only) [page 37].
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.
1.7.4 Ownership Manager (Standard only)
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 periodspecific 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
● Display the Ownership Manager

Select Consolidation Ownership Manager .
Related Information
Create Ownership-based Hierarchies (Standard only) [page 41]
Ownership-based Hierarchy Requirements (Standard only) [page 44]
1.7.4.1 Create Ownership-based Hierarchies (Standard

only)
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 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 maintain children for each group level by choosing a group and clicking the Add button to add
entities to or remove entities from the group.
● You can 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.
1.7.4.1.1 Example of an Ownership-Based Hierarchy with

Divested Entities (Standard only)
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 %
 Note
Methods are defined for each Group, at the level of the first immediate parent for each entity.
 Note
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 (Standard only) [page 41]
1.7.4.2 Ownership-based Hierarchy Requirements

(Standard only)
This topic describes the hierarchy requirements for Statutory, Main, and Ownership models.
Use
To set up a general model for use with ownership-based hierarchies, you need a main model that stores the
entity information and contains links to a supporting Ownership-type model where the data is stored. For
information about creating an Ownership model, see Consolidation (Standard only) [page 166].
Features
Requirements for the Statutory Model
In consolidation type models, you can combine an ownership-based hierarchy with a static, upper-level portion
of the hierarchy representing Groups. You can use this portion of the hierarchy to generate statutory reporting
or to identify a series of groups for consolidation.
The Groups hierarchy is controlled by the dimension property called PARENT_GROUP. This property has no
default value; the presence of the property enables the Groups hierarchy. The property is populated with
hierarchy information (similar to the PARENTHn field), but does not generate a true OLAP hierarchy of
members in the Group dimension. This is because in statutory models Groups cannot be rolled up, since
consolidation consists of both a complex aggregation as well as eliminations. A complex aggregation means
that aggregation is also performed according to a Consolidation Method and a specific percent consolidation.
There is a split between the base-level members (the members of the Entity dimension) and the parent-level
members (the members of the Group dimension). In some cases, parents in the Group dimension are actually
base-level members to which entities are attached.
These members are used by the Business Rules engine which writes the contribution of each Entity to each
Group (using the Entity/Group intersection). The consolidation of each upper-level Group begins with the base-
level entities.
Groups may have a corresponding Entity (as defined in the Entity property), since this member is used to store
the aggregated amount of consolidated amounts. They are also used when creating reports.
Requirements for the Main Model
Required dimension-types: Account (A), Category (C), Time (T), Entity (E), Group (G) and Reporting Currency
(R).
 Note
You can also include the Intercompany (I) dimension in the ownership model in order to use the ownership
calculation feature.
Requirements for the Ownership Model
The main model must link to a supporting Ownership-type model. It must contain the following dimension
types, as no other dimension types are supported:
Dimension Type Description
Account (A) The Account-type dimension must contain an account (the

default name is PGROUP) that has a nonzero value for the
valid intersections of the Entity and Group dimensions. You
must enter the name of this member in the
Org_AccountOwn model parameter in the ownership
model. This refers to SAP Business Planning and Consolida
tion, version for the Microsoft platform.
It may also contain other accounts that can be used to store

additional information relating to an Entity/Group intersec
tion for a given Category and Time. The set of accounts to
display in the Ownership Manager is controlled by an
ORG_ACCOUNTOWN model parameter.
 Note
All required members, including POWN, POWNG, PCON,
Method, and PGROUP, are listed in the O_Account di
mension delivered with EnvironmentShell.
 Caution
Renaming the Account dimension member in the owner
ship model could cause errors when executing the own
ership calculations.
Category (C) Must be the same Category dimension used in the main
model.
Time (T) Must be the same Time dimension used in the main model.
Entity (E) Must be the same Entity dimension used in the main model.
Dimension Type Description
Groups (G) Referred to as Groups, defines the parent members used in

the ownership-based hierarchy. This dimension must have a
property named Entity. The property values define the link
between the Group dimension member and its correspond
ing Entity dimension member. These members are the pa
rents that are used in the ownership-based hierarchy. For ex
ample: Group member ID G_E1 has the Entity property value
E1. It corresponds to Entity dimension member E1. The
property named STORE_ENTITY ( Y for Yes; N or empty for
No) works in conjunction with the ENTITY property. It be
haves as the triggering flag for aggregating the consolidated
amounts to the ENTITY defined in the ENTITY property.
The CURRENCY_TYPE property specifies whether the Group

member is a consolidation scope (CURRENCY_TYPE=G) or
the default member for that dimension
( CURRENCY_TYPE=N).
Intercompany (I) Must be the same Intercompany dimension used in the main
model.
1.8 Run Consolidation (Embedded only)
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 (Embedded only) [page 48]

Controls Monitor (Embedded only) [page 55]
Journals (Embedded only) [page 61]
Ownership Manager (Embedded only) [page 72]
1.8.1 Consolidation Monitor (Embedded only)
The Consolidation Monitor is a global dashboard for monitoring the consolidation progress for 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 on which entities to execute business rules. For more information about setting up your
consolidation environment with dimension properties, model settings, and journal definitions, see
Consolidation (Embedded only) [page 189].
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 (Embedded only) [page 72].
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 to manage Consolidation Monitor and
execute business rules. To perform control type tasks, you also need to be assigned 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.
Before running relevant business rule tasks, corresponding dimensions and attributes must be maintained by
your administrator. For detailed information, see Business Rules Management (Embedded only) [page 289].
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 (Embedded only) [page 289] and Set Task Sequence (Embedded only) [page 206].
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
○ Execute control
For more information, see Run a Consolidation (Embedded only) [page 51].
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 or Failed 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. Running
processes are displayed with percent completion. 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 that follow that task also need to be re-executed.
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.
 Note
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 (Embedded only) [page 51]
1.8.1.1 Run a Currency Translation (Embedded only)
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 (Embedded only) [page 48].
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 (Embedded only) [page 291]
1.8.1.2 Run a Consolidation (Embedded only)
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.
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 Execute. 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 344] and
Create a Control [page 309].
Related Information
Account-based Calculation Rule (Embedded only) [page 291]

Intercompany Booking Rule (Embedded only) [page 296]
Carry-Forward Rule (Embedded only) [page 297]
Eliminations and Adjustments Rule for Legal Consolidation (Embedded only) [page 300]
1.8.1.3 Working with Periodic Consolidations and Currency

Translations (Embedded only)
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 (Embedded only) [page 51]
1.8.2 Controls Monitor (Embedded only)
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 (Embedded only) [page 72].
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 309]; for more information
on control status, see Control Set Status (Embedded only) [page 58].
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 (Embedded only) [page 57].
● 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 306]

Create a Control Set [page 315]
1.8.2.1 Execute a Control Set (Embedded only)
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.
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 314].
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 (Embedded only) [page 58]
1.8.2.2 Control Set Status (Embedded only)
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

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 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 (Embedded only) [page 57]
1.8.3 Journals (Embedded only)
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.
Features
The following table describes the available journal tasks and explains how to perform each one. You perform
these tasks in Consolidation Central Journals .
Create a journal entry Click New in the toolbar of the Journals For more information, see Journal En
page. tries (Embedded only) [page 64].
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 (Embedded only)
your changes to one or more journal en [page 67].
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 (Embedded only)
the list of journal entries. [page 69].
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 (Embedded only) [page
nal entries in the Journal Entries tab. 64].
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 (Em
bedded only) [page 67].
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 (Embedded only)
journal entries are unposted. To select [page 67].
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 (Embedded only) [page 68].
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 (Em
bedded only) [page 69].
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 (Embedded only) [page
70].
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 356].
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 (Embedded only) [page 71].
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 (Embed
ded only) [page 64].
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 355].
and click the Reopen Rules tab.
1.8.3.1 Journal Entries (Embedded only)
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
(Embedded only) [page 67].
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 (Embedded only) [page 71].
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 (Embedded only) [page 61].
1.8.3.2 Journal Entry Form (Embedded only)
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:
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.
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 (Embedded only) [page 64]

Journal Postings (Embedded only) [page 67]
1.8.3.3 Journal Postings (Embedded only)
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.
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 cube 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 above options.
○ 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 (Embedded only) [page 64]
1.8.3.4 Journal Groups (Embedded only)
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 (Embedded only) [page 65].
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 (Embedded only) [page 67]
1.8.3.5 Journal Queries (Embedded only)
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 (Embedded only) [page 61]
1.8.3.6 Reopen Journal Entries (Embedded only)
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 355].
The system is set to allow for reopening of journals using the Allow Journals to be Reopened journal parameter.
See Journal Model Parameters [page 356].
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.
1.8.3.7 Print Journal Reports (Embedded only)
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 (Embedded only) [page 69].
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.
1.8.4 Ownership Manager (Embedded only)
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 periodspecific 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 (Embedded only) [page 73]
1.8.4.1 Create Ownership-based Hierarchies (Embedded

only)
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 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 maintain children for each group level by choosing a group and clicking the Add button to add
entities to or remove entities from the group. Currently you cannot choose 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.
1.8.4.1.1 Example of an Ownership-Based Hierarchy with

Divested Entities (Embedded only)
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:
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 (Embedded only) [page 73]
1.9 System Reports
Use
This function allows you to prepare reports that contain system information and a history of administration and
business user activities.
Features
System reports enable you to report on any of the following topics:
● General - The following general reports are available:

○ Business process flows. For information, see Reporting on Business Process Flows [page 77].
○ Data changes. For information, see Reporting on Data Changes [page 78].
○ Work status. For information, see Reporting on Work Status [page 80].
○ Comments (standard only). For information, see Reporting on Comments [page 81].
○ Administration activity (standard only). For information, see Reporting on Administration Activity
[page 82].
● Security (standard only) - The following security reports are available:
○ Users
○ Teams
○ Task Profiles
○ Data Access Profiles
For information, see Reporting on Security Information [page 86].
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.
More Information
Data Auditing [page 367]
Activity Auditing [page 368] (standard only)
1.9.1 Reporting on Business Process Flows
Use
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
● Operation (standard only)
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.
1.9.2 Reporting on Data Changes
Use
Business Planning and Consolidation in a standard configuration records audit information on who changed
transactional data in the model. Since a data audit can be captured only for a model, this report is applicable
only at the model-level.
Business Planning and Consolidation in an embedded configuration 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 the EPM add-in for Microsoft Office), and the details of the record that was changed.
You can choose from the following criteria to fine tune your report:
Option Description
Model (standard only) Select a model, for example, PLANNING or RATE.
InfoProvider (embedded only) Select an InfoProvider that has data change audit enabled.
Dimension Members Select the dimension and dimension members the audit in
formation is stored against.
Embedded only: The special dimension Audit Mode can have

the value PLAN.
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).
Option Description
Additional Criteria For Business Planning and Consolidation in a standard

configuration, 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
For Business Planning and Consolidation in an embedded

configuration there is one additional criterion - 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.
In the report, the columns correspond to the parameters in the above table. In Business Planning and
Consolidation in a standard configuration there is an additional Value column. The Value field shows you what
the value was changed to, as a result of the change. That is, it shows you the new value (not the original nor the
delta value posted to the database).
More Information
1.9.3 Reporting on Work Status
Use
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. In
Business Planning and Consolidation in a standard configuration, you can also control input methods (for
example, to prevent the Data Manager being used to update data).
In Business Planning and Consolidation in a standard configuration, you can filter the report to the specific
region of the cube for which you want the work state.
In Business Planning and Consolidation in an embedded configuration, 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.
Option Description
Date and Time You can choose start and end dates for the report. In Busi
ness Planning and Consolidation in a standard configuration,
you can also display the full history of the selected work sta
tus information (Anytime).
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
Related Information
Work Status [page 94]

Work Status Setup [page 344]
1.9.4 Reporting on Comments (Standard only)
Use
The comments report allows you to see the comments made for the current model from your context.
Features
You can choose how many and which comments are displayed by applying filters. The following table shows the
filtering options that are available:
Option Description
Model Select a model, for example, PLANNING or RATE.
Dimension Members Enter the individual dimensions the comment is stored

against.
Option Description
History You can choose to display the entire commenting string

(that is, all comments that match your filter criteria) or only
the most recent comments (that is, only one record is re
turned).
Date & Time You can choose start and end dates for the report or display
the full history of the selected comments ( Anytime).
Priority Choose from:
● Priority
○ All
○ Critical
○ High
○ Medium
○ Low
○ No Priority
With the exception of All, these filter elements select a
particular priority and all higher priorities. For example,
High selects High and Critical comments.
● User - Enter a User ID if you want to report on the com
ments made by a particular user.
Activities
To view a comments report, go to System Reports, and from the list of reports, choose Comment. Set the
In the Comments report, the columns correspond to the parameters in the above table.
More Information
Comments [page 95]
1.9.5 Reporting on Administration Activity (Standard only)
Use
The administration activity audit records information on tasks performed in the system, for example, who is
creating, changing, deleting models, dimensions, and security.
This report applies to the environment or model level.
Features
You can set the following report options:
Option Description
Date and Time You can choose start and end dates for the report or display the full history of the se
lected activities ( Anytime).
Option Description
Task Selection The following options are available:
● Task Name
You can enter the following tasks:
○ COPY ENVIRONMENT
○ DELETE ENVIRONMENT
○ CREATE MODEL
○ COPY MODEL
○ MODIFY MODEL
○ DELETE MODEL
○ CREATE DIMENSION
○ COPY DIMENSION
○ MODIFY DIMENSION
○ DELETE DIMENSION
○ PROCESS DIMENSION
 Note
The functional tasks are case-sensitive. When you enter the functional tasks,
the system tries to anticipate your entry as you type in partial text.
● Task Area
○ Environment - Report on activity at the environment level
○ Model - Report on activity at the model level
● Task Group
○ All - Report on activity for both user types (Admin and User)
○ Admin - Reports the activity selected in the Task Type field (described below).
Admin activity shows both the previous and new values.
○ User - Reports work status changes
○ Process - Reports business process flow activity
○ Business Rule - Reports business rule activity
● Task Type
○ All - All activity types
○ Add - Only add activity
○ Change - Only activity that involves changes within the system
○ Delete - Only delete activity
● Current, which includes audit records of activity that has not yet been archived
● Archived, which includes audit records of activity that has already been archived
● Current and archived, which is the combination of both options
●
Option Description
Task Parameters These fields are optional and are used for additional information. You typically use them
in reporting, but not for filtering.
● Modified Object
● Parameter Value
● Field Value
● Pre-Task Value
● Post-Task Value
● User
Modified Object and Parameter Value are at the audit header record. Field Value, Post-
Task Value, and Pre-Task Value are at the detail record.
Report Contents
The report header shows the date and time of the report, and the number of records returned. It also shows the
options that you selected for Task Selection and Task Parameters, as described above.
In the report, the columns correspond to report criteria above, with additional items:
● Task Name - Name of the task

● Date and Time - Date and time of the task
● Model - The name of the model in which the task occurred
● User - Name of the user who performed the task
● Modified Object - The name of the modified object.
● Machine ID - The IP address of the machine on which the task was performed
● Machine Name - The name of the machine on which the task was performed
● Parameter Value - Additional information
● Task Group - Task group for which the task was performed
● Task Type - Type of task performed
● Field Value - Details of the task performed, for Create Member if a dimension member was created.
● Pre-Task Value - Value in the field before the task was performed. For new dimension members, this is
blank. For deleted dimension members, this shows the ID of the deleted member. For modified dimension
members, this shows the value of the modified property or hierarchy before the change, or blank if there
was no value before processing.
● Post-Task Value - Value in the field after the task was performed. For new dimension members, this shows
the ID of the created member. For deleted dimension members, this is blank. For modified dimension
members, this shows the value of the modified property or hierarchy before the change, or blank if the
value was removed.
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.
Report Filters
You can filter a report by entering a filter value in a column heading. You can combine filters by entering filter
values for multiple columns.
Sorting a Column in a Report
You can sort the columns in a report in ascending or descending order by clicking a column heading.
Activities
To view an administration activity report, go to System Reports, and from the list of reports, choose
Administration Activity. Set the appropriate reporting options and display the report.
In the report, the columns correspond to the parameters in the above table.
More Information
Activity Auditing [page 368]
1.9.6 Reporting on Security Information (Standard only)
Use
The purpose of the security audit reports is to show a summary of the users, teams, and profiles that exist for a
particular environment. It does not show any security-related activity; for that purpose, you can use activity
auditing and the administration audit report, with the appropriate filters.
Prerequisites
To view security reports of other users, you must have the Run Security Reports task privilege assigned to
you. However, all users can access their own security report.
Features
The following security reports are available:
● Users
This report allows you to see in a grid, the users assigned to the environment, and the teams and profiles to
which they are assigned.
You can also drill down to view the detailed report for each user.
● Teams
See a summary of the teams created for the environment, or drill into the details and see the users and
profiles assigned to that team.
● Task Profiles
This report shows you all the task profiles in the system, and for each profile, the individual tasks that have
been assigned. The detailed report also shows user and team assignments.
● Data Access Profiles
This report shows, by model, all the members assigned to the profile and whether they are for Read, Write,
or Deny access. The detailed report also shows user and team assignments.
 Note
In each report, you can toggle between the list and the detail report using the Show List/Show Detail link.
Activities
To view a security report, go to System Reports, and from the list of reports, choose the type of security report
you want to view.
More Information
See the SAP Business Planning and Consolidation Security Guide available on the SAP Help Portal.
1.10 Creating Reports
You can use this function to create reports and input forms.
In Business Planning and Consolidation in an embedded configuration reports and input forms are based on
BW queries that are created with the BEx Query Designer. You can also use default queries that are available for
all InfoProviders. These queries have special names, starting with "!". There are also special default queries
that exist on aggregation levels. These queries start with "!!I" and can be used as the basis for input forms.
Procedure
To create a new report or input form, go to Library and choose New: Report or New: Input Form
Business Planning and Consolidation in a standard configuration
1. In the Define Data Grid dialog, choose the dimensions that you want to include by dragging them to the
required area - Rows or Columns.
2. To select the members that you want to include in the report, click the name of the required dimension.
The member selector appears.
3. Select the checkbox for each member that you want to include in the report or click to include all
children, descendants, and base members of a parent member into the selection. Then choose OK.
4. Choose Save to save the report.
Business Planning and Consolidation in an embedded configuration
1. Enter the name of the report.

2. Select the model you want to work on.
3. Select the query on which you want to build the report. You can search the query, select a query from the
History list, or browse from the list of available queries.
For input forms, the query must be designed to be input-ready. This means that at least one key figure
must be set to input-ready state. Otherwise the query cannot be used as a basis for an input form.
4. Under the Set Variables step, enter values of the variables that will be used in the report. These variables
are defined in the BW query that is used as a basis for the report. Later you can give these variables
different values and thus you can change the output of the report.
5. Under the Define Data Grid step, choose the dimensions that you want to include by dragging them to the
required area - Page Axis, Row Axis or Column Axis. The Page Axis is optional, but there must be
dimensions in either Row Axis or Column Axis or both.
6. To select the members that you want to include in the report, click the name of the required dimension.
The member selector appears.
7. Select the checkbox for each member that you want to include in the report and choose OK.
8. Under the Review and Create step check your entries and choose OK.
The report is created and the data in it is refreshed automatically.
9. Choose Save to save the report.
Additional Functions
You can export a web report or an input form to a comma-separated values (CSV) file. After that you can open
the file with MS Excel, do data analysis, format the report, print it with Excel, or copy the changed data back
from Excel to a web input form.
In a report, you can suppress empty rows and the rows whose values are zero so that the report is more usable
and easier to read. To do this, choose Display from the menu bar. In the submenu that appears, select one of
the following options:
● Keep All - When this option is selected, all rows are shown.
● Suppress Empty Rows - When this option is selected, the empty rows are not shown. The rows that have
values in them are shown, even if they are zero values.
● Suppress Empty and Zero Rows - When this option is selected, all empty and zero rows are hidden.
More Information
Home Page and Navigation [page 10]
Components of Reports [page 89]
Charts [page 91]
Work Status [page 94] (Standard only)
Comments [page 95] (Standard only)
Context [page 98] (Standard only)
1.10.1 Components of Reports
Use
When creating a report, there are several components you can add to it. Some are required, such as
dimensions and members, and some are optional, such as charts.
Features
The following table lists the components that you can add to a report and how you can manipulate these
components:
Component Actions
Dimensions Choose to edit the report. The available dimensions appear.
Drag the dimension to the Row Axis area or the Column Axis area. In Business Planning and Consolida
tion in an embedded configuration, you can also drag them to the Page Axis area.
You can nest dimensions by placing additional dimensions on the column or row.
You can remove dimensions from a column or row by clicking the x next to that dimension.
Component Actions
Members You can select the members you want to use.
Select a dimension in the Column Axis, Row Axis or Page Axis (embedded only) area and click Select
Members to select the members to use for that dimension. The member selector is displayed. Here you
define the set of members to display for the selected dimension.
Standard Only
You can select members by choosing the following options:
● Single Member - You can select a single member of the current context or a fixed member.
● Fixed List - You can select a fixed list of members.
● Select Children - You can select the children of the current context or a fixed member.
● Select Children and me - You can select both the children and the parent member.
● Select Descendants - You can select all descendants of the current context or a fixed member. In the
window that appears, select the levels to include using the Number of Levels Down and Do not
include intermediate levels options.
● Select Descendants and me - You can select both the descendants and the parent member. In the
window that appears, select the levels to include using the Number of Levels Down and Do not
include intermediate levels options.
● Select Base Members - You can select the base members of the current context or a fixed member.
● Select Base Members and me - You can select both the base members and the parent member.
You can exclude members from the selected member list in the following ways:
● Exclude a single member - If you exclude a base member, you exclude that single member from the
selected member list.
● Exclude descendants and me - If you exclude a parent member, you exclude that parent member
and all descendants of it.
If you do not specify any members, the current context is always used.
Embedded Only
If you do not specify any members, all members defined in the query for the dimension will be used.
Charts You can create a chart from a report or input form.
See Charts [page 91].
Work Status You can set the work status on data that you enter and save.
(standard only)
See Work Status [page 94].
Comments You can add comments to any selected cell. You can also enter a comment for a specific context, in
(standard only) which case the comment also appears in all other reports containing the same context.
You can view and report on comments including the commenting thread that shows the history of a
comment.
See Comments (Standard only) [page 95].
Activities
You can cut, copy, or paste data both from and to Excel. You can also export a complete report to Excel.
You can format reports to determine their appearance. The formatting options include the following:
● Setting the scaling factor

● Setting the number of decimals to display after the separator
● Placement of the totals
You can export a complete report to Excel.
You can save data. For more information, see Additional Functions for Input Forms [page 101].
1.10.2 Charts
Use
You can create a chart from a report or input form. You can also add a chart to a report or input form so it
displays on the same page. When you change the report in any way, the associated chart is updated.
Features
You can do the following with charts in reports:
● You can display the chart together with the report or only the chart alone.
You can select the following options for displaying charts and reports:
○ Show Report Only
○ Show Chart Only
○ Show Report and Chart
You can remove a chart from a report by choosing the display option Show Report Only.
● You can specify how the chart is displayed. In the Chart Options pane on the right side, you can select
options as follows:
○ You can set the type of chart (Vertical Bar, Horizontal Bar, Stacked Vertical Bar, Stacked Horizontal Bar,
Line, and Pie).
○ You can select the dimensions and members to display on the group and series axis.
○ You can choose to display the group and series axis labels.
● In addition, you can apply filter for the dimensions that are not in the group and series axis.
More Information
1.10.3 Member Selector
The member selector provides a dialog box in which you can select or exclude members that belong to the
same dimension hierarchy.
By selecting members in the member selector for a specific dimension, you can restrict the display of data, for
example, in a report table.
To access the member selector, click on the name of a dimension in the report or input form.
Function Navigation
Selecting one or more dimension members Select the checkbox next to the specific dimension mem
bers.
Selecting children or descendants of a dimension member

In the menu for a dimension member in the member se
(standard only)
lector, choose Select Children or Select Descendants.
Excluding members from selected members list (standard

In the menu for a dimension member in the member se
only)
lector, choose Exclude descendants and me, then the mem
ber and all its descendants are removed from the selected
members list.
Searching for members

Choose and enter the name or ID of the member. When
searching by ID, make sure you choose either ID or ID and
Description in the Display Column..
Displaying dimension members in a hierarchy or list format In a Standard configuration, in a dimension member list,
choose Display and select either Hierarchy or List.
In an Embedded configuration, in a dimension member list,

choose Go To and switch between Hierarchy and Member
List view.
Choosing a key date or version for time-dependent and ver For a dimension with a time-dependent or version-depend
sion-dependent hierarchy (embedded only) ent hierarchy, if no key date or version is predefined during
query design, you can specify a key date and version within
the member selector to display corresponding members.
Example
You have the Calendar Year dimension added in a report. You can filter the dimension members that are
displayed in the report table using the member selector. Selecting only 2009 and 2010 restricts the display of
data in the report to information relevant for these dimension members.
1.10.4 Disaggregation
In Business Planning and Consolidation in a standard configuration, you can use this functionality to
disaggregate target values to the base levels.
When you want to use top-down planning you can enter a target value in a parent node and the system will
perform disaggregation.
 Example
You enter a sales target for the EMEA region and then use the disaggregation function to disaggregate that
value to the base levels.
The following disaggregation rules are available:
● Self-reference distribution - data will be disaggregated according to the ratio of the existing base level
values.
● Base level equally distribution - data will be disaggregated to all base levels evenly.
● Reference-based - data will be disaggregated according to the ratio of the base level values in a selected
equivalent member range. For example, if you use the Time dimension, you must specify which time period
to refer to.
In Business Planning and Consolidation in an embedded configuration, you can use this functionality to
distribute a value to the granularity of the aggregation level.
To use disaggregation you must set it in the BEx queries that you use for your reports and input forms. For
more information, see the SAP BW documentation available at http://help.sap.com/nw74.
After enabling disaggregation in the BEx queries, you can still change the type of disaggregation in reporting by
following these steps:
1. Open an input form.

2. Select the cell on which you would like to perform disaggregation.
3. Click the planning button in the toolbar.
4. Click Disaggregation, then select the type of disaggregation you want to use, and click OK.
You are able to change the value in target cell and the value you entered will be properly disaggregated
based on the new setting. The new setting will be applied to the whole column.
1.10.5 Work Status
Use
You can change a work status setting on a data region to which you have access. Then all users will adapt to the
data entry permissions defined in the new work status. This is typically done after saving data to the database
from an input form.
Prerequisites
● Work status is enabled on the active model.

● You have the authority to change the work status for the data region.
● You can change a work status setting on a data region to which you have access.
● An administrator has defined at least one work state.
Features
If you have the appropriate authority, you can change the work status from one authorized status to another.
You can use the work status to control whether it is possible to enter or modify data in the data region.
When you change the work status setting of a region, the following events occur and rules apply:
● If that region has no work status record, the Change Work Status button will not display in the tool bar.
● If work status = 0 (no locks) is set to a higher work status, it is possible to return to work status = 0 if all the
other rules have been passed.
● If the region has a default work status, in a Business Planning and Consolidation embedded configuration
the current state will show the text description of the work state. In a standard configuration, the current
state will show the name of the work state.
● You can progress only from a lower state to the next higher state, or from a higher state to the next lower
state. You cannot skip any work state while changing work status.
Activities
To run a work status in a report or input form, follow these steps:
1. In a report or input form, select Change Work Status.

2. In the Change Work Status dialog box, select one or more members for the owner dimension and other
dimensions to define the exact data range for which you want to change work status.
3. Select On All Descendants to apply the work status change to all the descendants of the selected
members, if needed.
4. In the New Status field, select the desired setting from the drop-down list and choose OK.
More Information
Reporting on Work Status [page 80]
1.10.6 Comments (Standard only)
Use
Comments provide a vehicle for submitting, storing, and retrieving text commentary associated with report
data cells. This allows you to annotate data so other users can view supporting information associated with a
particular piece of data.
Features
You can use comments in the following ways:
● You can add comments to a report.

● You can view (manage) all comments in a data region.
● You can edit comments.
● You can retrieve comments added to a report. Within the report, comments are displayed as tooltips.
● You can see a history of the comments for a specific cell in a report.
● You can delete a comment.
Adding Comments
You can add comments to a specific cell in a report or input form.
You add a comment in run mode by selecting a cell, then choosing Comments and then Add comment. You
enter the comment in the Add Comment dialog box. The default length for a comment is 255 characters.
 Note
Administrators can change the comment length using the environment parameter COMMENT_MAX_LENGTH.
The default value is 255 and the maximum length is 1,332 characters.
When adding a comment, you can select More and then specify the following items:
Item Description
Priority Specifies the desired priority level or None. The report shows comments in order of their priority
level.
Item Description
Keywords Specifies keywords to organize and search for comments in the database. This field takes blanks and
empty strings.
Modify Context Allows you to select specific members for the context using the Member Selector. See Member Se
lector [page 92]. You cannot modify the context of a comment using the View History dialog box of a
report or an input form.
Viewing Comments
You can view individual comments in a report, as well as all of the comments associated with a report. You view
a comment in a selected cell in a report by placing the cursor on a cell to which a comment has been added.
The comment, originator and modification date are displayed.
You view all comments in a report by selecting Comments and then Manage comments. The Manage comments
workspace is displayed showing details of all comments. The following details are displayed:
Item Description
Comment Displays the entire comment. If you are the originator of the comment or if you have administrator
rights, you can modify the value directly in the cell. When you finish modifying the text, choose
Update Comment.
Keyword Displays the keyword associated with the comment. If you are the originator of the comment or if
you have administrator rights, you can modify the value directly in the field.
Date and Time Displays the date that the comment was saved to the database. If the comment is updated by the
originator or an administrator, the updated date appears in this cell. The value in this cell is display
only.
User Displays the comment originator's name. The value in this cell is display only.
Priority Displays the priority for the comment. If you are the originator of the comment or if you have ad
ministrator rights, you can modify the value directly in the cell by selecting another option from the
drop-down list.
Dimension Members Displays the details of the cell of the report to which the comment was added.
Filtering Comments
You can specify filter criteria for displaying the comments in the Manage comments workspace. To set filter
criteria, choose Edit Criteria and select the following options:
● Dimension Members - You can select the dimension members for which to display comments.
● Modification Date - You can choose start and end dates for the comments, or display the full history of the
selected comments ( Anytime).
● Additional Criteria - You can specify a Priority, User ID and Keyword for which to display comments.
Deleting Comments
You can delete a comment associated with a cell. You delete a comment by selecting the cell, then Comments,
and then Delete comment. You must click OK to confirm.
 Note
An administrator can delete or remove comments with conditions through the ClearComment package in
Data Manager. For more information, see SAP BusinessObjects EPM solutions, add-in for Microsoft Office
help.
Activities
To work with comments in a report, open the report and select Comments. Choose one of the options as
described above.
More Information
Reporting on Comments [page 81]
1.10.7 Comments (Embedded only)
Comments provide a vehicle for submitting, storing, and retrieving text commentary associated with report
data cells.
By leveraging the feature of short texts in a BW query, you can submit, store, and retrieve text commentary in.
For detailed information, refer to the BW manual on the SAP Help Portal available at http://help.sap.com/
nwbw. Go to SAP Business Warehouse 7.4, powered by SAP HANA, open the SAP BW Documentation in the
application help section, then navigate to Data Modeling When Using a SAP HANA Modelling with the BW
Modeling Tools in Eclipse Tasks Defining Queries More Information Editing Short Texts in Queries .
Generally speaking, you can follow the steps below to enable short comments:
1. Create a characteristic for comments.

2. Create a DataStore object and add the characteristic into a data field and set it as the key figure.
3. Add the DataStore object to a MultiProvider and transfer the characteristic to the MultiProvider’s key
figures.
4. Transfer the characteristic from the MultiProvider’s key figures to the key figures of the aggregation level
that will be used for reporting.
5. Adjust the definition of the query for reporting.
After proper adjustments have been made for modeling and querying, you can add, edit, and delete short
comments in the queries.
Comments are editable in input forms, but read-only in web reports. The maximum comment length of each
cell is 250 characters.
You can also define disaggregation rules inside a query for comments. Two disaggregation options are
available:
● No Disaggregation: No comments can be added on total result cells.

● Disaggregation Copy: Comments on total result cells overwrite the comments of all children cells.
1.10.8 Context (Standard only)
Use
You can use this function to filter the content displayed in a workspace or report. It allows you to focus on a
specific subset of the data.
Since a workspace can contain one or many views, the data selected on each level has a scope. The value
selected on a lower level object overrides the value of the same data type selected on a higher level.
When the workspace is saved, the context data associated with the workspace is also saved.
Integration
The context bar is displayed when you open a report or workspace.
Prerequisites
● The application is context-enabled; it can receive and respond to context data.

● The appropriate permissions have been assigned to be able to work with the dimensions and associated
dimension members.
Features
The following functions are available:
● Manage Context dropdown menu:

It displays details about the current model and provides the option to change the model.
Display Dimension Names: You can decide whether to show or hide dimension names to the left of member
names in the context bar. You can also use the default settings.
● Add Dimension: To focus the display in a workspace or report on a specific set of data, you add dimensions
and select members for those dimensions in the context bar.
You can change the dimension member selection. This changes the focus of the content you are viewing.
You can add all dimensions to the context bar.
● Inherit and Override: If you add a dimension at workspace level, all views inside the workspace display
content according to the specified dimension and dimension member.
When you add the same dimension at view level, but select a different dimension member, the dimension
member on the view (lower level) overrides the dimension member on the workspace (higher level). All
other views inside the workspace continue to take the workspace-level dimension member.
In a view, the inherited dimensions always appear first in the context bar. Any new dimensions you add at
view level appear after these.
● Locking: The locking of dimensions is automatic in process workspaces. If a dimension is locked, it cannot
be added to or removed from the context bar. It is visible, but grayed out and is displayed.
Activities
For more information about the activities that can be performed related to context, see Managing Context
[page 100].
Example
Example 1
1. You add context to a report with dimension: Calendar Month and member: April by choosing in the
context bar and selecting this dimension member.
This displays data in the report for the month of April.
2. If you change the dimension member, for example, by selecting March as the calendar month; this changes
the context of the report to display data for March.
Example 2
1. You add a dimension, Region at workspace level and select member, Europe. All views within that
workspace display data for Region: Europe.
2. If you add the Region dimension to a view inside the workspace and select member, Asia, the view displays
data for Region: Asia.
All other views in the workspace continue to display data for Region: Europe.
1.10.8.1 Managing Context (Standard only)
Procedure
To manage the context in a report or workspace, you can perform the following tasks:
Function Navigation More Information
Change the model (None)

In the dropdown menu, choose
Change Model....
Open the dimension member selector Dimensions already added to context

In the context bar, choose and se
bar are grayed out
lect a dimension from the list.
Select a different dimension member Select the dimension member hyper (None)
link.
Return to the default dimension mem Whenever a dimension is added to the

Choose .
ber context bar, a default dimension mem
ber is displayed.
Remove a dimension from the context (None)

Choose .
bar
Add all dimensions to the context bar In the Add Dimension dropdown list, (None)
choose Add All Dimensions.
Display dimension names next to di In the Manage Context dropdown To display only the dimension member
mension members in the context bar menu, choose Display Dimension descriptions, choose Hide All.
Names Display All . You can also select the default display
by choosing Use Default Settings.
1.10.9 Page Axis (Embedded only)
When designing a report or an input form, you can select dimensions for the page axis. Later you can select
specific members of these dimensions and display their aggregated values in the report/input form.
By default all members of the dimensions in the page axis are displayed. To select specific members, follow the
steps below:
1. Choose a dimension from the page axis that appears at the top of the report. The page axis member
selector appears.
2. Select the checkboxes of the members whose data you want to include in the report.
3. Choose OK.
1.10.10 Planning Sessions and Locking Cells in Input Forms
(Embedded only)
Planning Session
A planning session buffers the data before sending it to the database. You can make changes to the data in the
input form and all these changes are buffered in the planning session. When you finish the editing, you can
submit the data to the database.
Also, when you change the work status the change is stored in the planning session and it is sent to the
database together with the planning data when you submit it.
The following options are available:
● Send data to the planning session - to do this, choose Transfer Data.

● Submit data to the database - to do this, choose Submit Data.
● Clear the data from the planning session - to do this, choose the arrow button next to Transfer Data and
then choose Roll Back.
Locking Cells
This function allows you to lock cells in the input form so their values cannot be changed. You might want to
lock cells in order to protect them when modifying other cells - by changing operands in formulas and changing
other data values - to see the effect of your modifications on the data in the report.
If you want to make these cells editable again, you can unlock them.
The locks persist during various operations. For example, if you remove a dimension that has a locked cell the
lock remains, although the cell is not visible any more. If you decide to add the dimension again, the lock is still
in place.
To lock or unlock a cell, select it and either choose Lock Cells or Unlock Cells in the ribbon or right-click and
choose Lock Cells or Unlock Cells.
1.11 Dashboards (Standard only)
A dashboard is a grouping of, or a display of, reports and input forms that allows you to have a comprehensive
overview of critical information.
In a dashboard, you can include content from the Library or create new reports or input forms. Reports and
input forms that you create are part of the dashboard and are not available outside the dashboard until you
save them as separate entities to the Library.
Prerequisites
Users can always open and view any dashboard.
To create or edit a dashboard, users need to be assigned the Edit Dashboard task profile. Meanwhile, if they
have the Edit Content of Public Folder task profile assigned to them, they can delete dashboards in
the Library.
To perform more tasks in a dashboard such as creating and saving reports, other task profiles need to be
assigned to the users:
● Edit Report
Allows users to open, create, and edit web reports.
● Use Input Forms and Save Data
Allow users to create, edit, and modify input forms and control data submissions from web reports.
Features
In total, up to six reports or input forms can be added to the dashboard. The added content is defined as tiles of
the dashboard. You can move, resize, and maximize the tiles freely. By choosing the Edit button of each tile, you
can hide either the menu bar or the scope context bar of the tile. All the report and input form tiles added to the
dashboard share the same functions with common reports and input forms, such as comments, drill-through,
changing work status, and displaying by report or chart.
Every dashboard contains a global context bar at the top of the page, from which you can change the model
and dimension members. This global context bar defines the default value of the context bars of all the report
tiles or input form tiles sharing the same model in this dashboard. However, if you choose a different member
for a dimension in the context bar of a certain report tile or input form tile, this change overwrites the default
value inherited from the global context.
Related Information
Create a Dashboard and Add Tiles (Standard only) [page 102]

Delete a Report or Input Form Tile in a Dashboard (Standard only) [page 103]
Modify or Delete a Dashboard (Standard only) [page 104]
Library [page 14]
1.11.1 Create a Dashboard and Add Tiles (Standard only)
Prerequisites
To create or edit a dashboard, users need to be assigned the Edit Dashboard task profile.
To perform more tasks in a dashboard such as creating and saving reports, other task profiles also need to be
assigned to the users:
● Edit Report
Allows users to open, create, and edit web reports.
● Use Input Forms and Save Data
Allow users to create, edit, and modify input forms and control data submissions from web reports.
Procedure
1. In the Home page, go to Library.

2. From the New: toolbar, choose Dashboard.
3. In the newly created dashboard, click the More Options sign in the global context bar to specify the
dimensions to display.
4. If you want to add existing reports or input forms to a dashboard, click Add Content and choose from the
list of items available in the Library view. To directly create a new report or input form tile inside a
dashboard, click Add New Report or Add New Input Form. For more details, see Creating Reports [page 87].
5. After inputting data into the input form tiles, you can save them from the dashboard. By default, when
saving the data, all the other report and input form tiles in the dashboard are automatically checked and
refreshed. If you do not want to refresh any other report or input form tile, click the Refresh button of that
tile and uncheck the Auto Refresh option.
6. After creating the report or input form tile, you can click the Edit button of the tile and choose Save as to
save it to the Library. Otherwise, the report or input form will be available only in the dashboard.
7. To save the dashboard, click the dashboard name and choose Save or Save as in the dropdown list. You can
save the dashboard to any one of the folders in the Library. Give it a name and description, then click OK.
Related Information

Library [page 14]
1.11.2 Delete a Report or Input Form Tile in a Dashboard

(Standard only)
Context
Deleting a report or input form tile in a dashboard does not delete the corresponding report or input form you
have saved to the Library
Procedure
1. Click the Edit button of a tile.

2. Choose Delete.
Related Information

Library [page 14]
1.11.3 Modify or Delete a Dashboard (Standard only)
Prerequisites
To edit a dashboard, users need to be assigned the Edit Dashboard task profile.
If users have the Edit Content of Public Folder task profile assigned to them, they can delete
dashboards in the Library.
Procedure
1. Go to the Library page and click the name of the dashboard to make modifications.
2. Select a dashboard and choose the Delete button to delete it.
Related Information

Library [page 14]
1.12 Creating and Modifying Workspaces (Standard only)
Use
A workspace is a grouping of specific content. It behaves like a folder, which contains Business Planning and
Consolidation items, such as reports, input forms, Crystal Dashboards, and so on.
In a workspace, you can include content from the Library or create new reports or input forms. Content that
you include is available both in the workspace and in the Library. Reports or input forms that you create are
part of the workspace and are not available outside the workspace.
Procedure
Creating a Workspace
1. To create a new workspace, in the home page go to Library and from the New: toolbar choose Workspace.
2. To add a global context to the workspace, click the plus sign to specify the dimensions and members. See
Context [page 98].
3. To start adding content to the workspace, click Add Content.
You can choose from the list of items (for example, reports or Crystal Dashboards) available in the Library
view. Select an item, then click OK.
4. To add a new report, click Add New Report and then create the report. For more details, see Creating
Reports.
5. To save the workspace, click Save.
You can save the workspace to any one of the folders in the Library. Give it a name and description, then
click OK.
Open or Modify Existing Workspaces
1. Open the Library view.

2. Select a folder from the folder hierarchy.
3. To open the workspace, do one of the following:
○ Select the workspace and click Open.
○ Click the workspace name.
This opens the workspace as a new tab at the workspace navigation level.
Additional Actions
To perform tasks on an item within a workspace, click the context menu icon next to the item and select from
the following options:
● Set as default - To set this item to be displayed when the workspace is opened.
● Delete - To delete the item.
● Rename - To rename the item.
1.13 Uploading and Modifying Crystal Dashboard Templates

(Standard only)
Use
You can upload a template allowing you to visualize report data and analyze data with dimension mapping.
Prerequisites
There is a template available in SWF format for upload.
 Note
Use caution when uploading an SWF file and be aware of the potential risks to your BPC system from
uploading malicious code in such a file. SAP is not responsible for damage caused by the upload of SWF
files containing suspicious code.
Procedure
Uploading a Template
1. Go to the Template Administration panel and choose .
 Note
If you are using SAP Business Planning and Consolidation, you can upload templates in the Library by
choosing BI Dashboard in the New: toolbar.
2. In the Upload dialog box, browse for the relevant SWF file. If available, browse for the XLF file of the
template.
The preview of the template is shown in the dialog box that appears, along with the template details and
connections.
3. Provide a name for the template.
4. In the dropdown menu, select the appropriate template type.
The possible options in the Type dropdown menu include Template (for generic templates) and Chart (for
specifically created chart templates following a set of naming conventions).
5. Select a Variable Format option. This field is only relevant if the template has a FlashVars connection.
If the XLF file has been uploaded, the Variable Format field is grayed out; XML is automatically selected.
6. Edit the connection details.
○ The variables were specified when the template was created. You can map these variables, which
represent the dimensions of the template, to a particular grid's dimensions for analysis.
○ By default, the data type of all the variables is String. You can change this to Number if required.
○ Optional: Provide a description for each of the variables.
 Note
If the XLF file has been uploaded, any available Flash variables, which were specified when creating the
template, are automatically included in the list. If the XLF file is not uploaded, you can add the Flash
variables manually by choosing Add Variable.
7. Save your entries.

The template has been uploaded and is available to use for analysis.
Modifying a Template
1. In the Template Administration panel, hover the mouse pointer over the template that you want to modify.
Select a task in the menu.
 Note
If you are using SAP Business Planning and Consolidation, you can modify templates in the Library by
choosing BI Dashboard and selecting the relevant template.
2. Choose a display option: Open in New Tab, Add to New View, or Add to Active View.
3. Rename: Change the name of the template.
4. Edit Details: This allows you to edit the template properties, for example. name and connection details.
5. Download XLF: This option is only available if the template has an associated XLF file. This allows you to
download the XLF file to your local system, and edit it.
You can subsequently upload the updated SWF and XLF files.
6. Delete: You can delete the template from the repository.
Additional Options
● To refresh the list of templates, choose .
1.14 Administration
Use
In the Administration screen, administrators perform setup and maintenance tasks.
Features
Set up 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
● Management of data calculations for member formulas, logic scripts, business rules, and controls (all in
standard only)
● Management of controls
● Set up of business process flows
● Set up of work statuses
● Set up of journals (standard only)
● Set up of context defaults (standard only)
● Configuration of drill-through (standard only)
● Management of document types and subtypes (standard only)
● Set up of auditing
Related Information
Environment Management [page 108]

Dimension Management [page 114]
Model Management [page 150]
Consolidation (Standard only) [page 166]
Consolidation (Embedded only) [page 189]
Rules [page 209]
Controls [page 306]
Business Process Flow Management [page 320]
Journal Administration [page 353]
Context Defaults (Standard only) [page 363]
Drill-Through Setup (Standard only) [page 364]
Document Types and Subtypes (Standard only) [page 366]
Auditing [page 366]
1.14.1 Environment Management
Use
In Business Planning and Consolidation in a standard configuration, an environment consists of one or more
models. An environment stores all the data from each model. Each model contains the master data that
controls the data in the environment. Models can share one or more dimensions with other models within the
environment.
In Business Planning and Consolidation in an embedded configuration, an environment consists of one or

more models. An environment is a virtual concept of a container that holds different planning scenarios
(models). Company-wide planning processes can be built on top of it.
Features
Adding New Environments
In Business Planning and Consolidation in a standard configuration, administrators create new

environments by copying information from the EnvironmentShell sample environment that is delivered with
Business Planning and Consolidation.
In Business Planning and Consolidation in an embedded configuration, administrators create new

environments from scratch in the Manage All Environments screen.
For more information, see New Environments [page 110].
Setting the Environment Status (standard only)
The environment status determines when and how users can log on and interact with the data. See
Environment Status [page 114].
Setting the Template Version (standard only)
If you have made changes to any of the dynamic templates for reports or schedules, you can force an update of
template files by changing the template version. Therefore, clients that log on to the environment receive the
new templates. You can set template versions by choosing Manage All Environments, selecting an environment,
then choosing Set Template Version. Increment template versions by 1.
Viewing User Activity (standard only)
Business Planning and Consolidation logs user and administrator behavior. You can view activity logs by
choosing Manage All Environments, selecting a environment, then choosing User Activity.
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 more details, see the SAP Business Planning
and Consolidation 10.1 IMG Guide.
Deleting Environments
You can delete environments after choosing Manage All Environments and selecting an environment.
 Caution
In Business Planning and Consolidation in a standard configuration you can delete an environment when
it contains data. You cannot, however, delete a dimension member when there is data associated to that
member in a model.
 Caution
In Business Planning and Consolidation in an embedded configuration when you delete an environment,
you will delete all objects under this environment:
● Models
● BPF templates and instances
● Work status settings and data
● Web reports and input forms
● EPM add-in reports and input forms
However, all BW modeling and settings done in the BW back-end transactions will still be available.
Additional Information (standard only)
The following information is important when managing environments:
● An environment is equivalent to an InfoArea within NetWeaver with nearly all unique objects within this
InfoArea.
● No objects are shared across environments, except delivered properties such as scaling, formula, and so
on. An InfoArea is like a folder, where in the case of an environment, it is much more delineated.
● You can transport environment changes between development and production systems. For more
information, see the Administrator’s Guide available on the SAP Help Portal at http://help.sap.com/
bopacnw101.
More Information
EnvironmentShell Sample Environment [page 111] (standard only)
1.14.1.1 New Environments
Use
In Business Planning and Consolidation in a standard configuration you create new environments by
copying the EnvironmentShell sample environment or an existing environment.
In Business Planning and Consolidation in an embedded configuration you create new environments from
scratch in the Manage All Environments dialog.
Features (Standard only)
You can copy all the components from a source environment to the target, which includes, but is not limited to,
business process flows, drill-throughs, audit, security, work status, transaction data, documents, journals, and
Library view data. You have the option to not copy database records, documents, and Library view data. After
the copying is complete, you can begin to modify the default models, add new ones, and assign users to them.
When you create a new environment, Business Planning and Consolidation does the following:
● Copies the environment WebFolders/data within File Service and user workspaces
● Creates a copy of all NetWeaver BI objects
● Copies all transactional and master data from the source environment to the new environment
● Copies security and Business Planning and Consolidation metadata
If the system encounters an error when copying a environment, it rolls back to clear the objects created during
the failed copy.
Activities
To access the Manage All Environments screen, follow these steps:
1. Choose the name of the current environment in the lower right part of the screen.
2. In the dialog that appears, choose Manage All Environments.
In Business Planning and Consolidation in a standard configuration you add an environment by copying an
existing environment. When you create the copy, you assign a name and description to the new environment
and indicate which records you want copied from the source.
In Business Planning and Consolidation in an embedded configuration 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.
More Information
EnvironmentShell Sample Environment [page 111] (standard only)
1.14.1.2 EnvironmentShell Sample Environment (Standard

only)
Use
You can use the EnvironmentShell sample environment to create your own environments.
Because it is a shell, it needs to be populated with publications and reports to become a fully functional
environment. The EnvironmentShell sample environment does not contain any data except Time dimension
information, and has only a limited amount of master data in the form of dimension members. The dimension
master data is limited to default members in most dimensions so the environment works when an
administrative task is run.
When you install a new version of Business Planning and Consolidation, the EnvironmentShell sample
environment and its components are overwritten.
 Caution
You must not modify the EnvironmentShell environment.
Features
The EnvironmentShell environment contains the following components needed to build a functioning
environment:
● Four sample models - Planning, Rate, Consolidation, and Ownership - that contain most of the functionality
you need to start building your own environment.
○ The Planning model is a multi-currency financial model. It is designed, by default, to accommodate
currency translation.
○ The Rate model, which stores the currency rates, is assigned to the Planning model as a supporting
model. The combination of the two models allows for the calculation of currency conversions.
○ The Consolidation model contains consolidation information, such as percent ownership, percent
control, percent consolidation, and the consolidation method to child members.
○ The Ownership model is a supporting model for a consolidation reporting model. It stores information
such as the consolidation methods, ownership percentages, and group roll up information used for
legal consolidation.
If you need to build more complex environments, for example, for legal reporting, you can build an
environment using the components included within EnvironmentShell.
● A set of dynamic report and input schedule templates
● Data Manager packages
● Blank documents in the Documents view and reports in the Library view
● Required administration setup parameters
● All required dimensions with the properties needed to create a basic planning and consolidation
environment
Dimensions in the EnvironmentShell sample environment
Unified dimensions for Business Planning and Consolidation models
Dimensions Models
Dimension De
Type ID Dimension ID scription Planning Consolidation Rates Ownership
C CATEGORY Category X X X X
T TIME Time X X X X
E ENTITY Entity X X X
A ACCOUNT Account X X
D AUDITTRAIL Audit Trail X X
R RPTCURRENCY Reporting Cur X X

rency
I INTERCO Intercompany X X X
Partner
Dimensions specific to Consolidation
Di
men
sions Models
Type Dimension Descrip

ID Dimension ID tion Planning Consolidation Rates Ownership
G SCOPE Scope X X
S FLOW Flow X
Dimension specific to Planning
Di
men
sions Models

U PRODUCT Product X
Dimensions specific to the Rates model
Di
men
sions Models

A R_ACCOUNT Rate Account X
E R_ENTITY Rate Entity X
R INPUTCURRENCY Input Currency X
Dimension specific to the Ownership model
Di
men
sions Models
Type ID Description Planning Consolidation Rates Ownership
A O_ACCOUNT Ownership Account X
More Information
New Environments [page 110]
Dimension Types [page 118]
1.14.1.3 Environment Status (Standard only)
Use
An environment can have a status of either Online or Offline. A newly created environment has a status of
Offline until an administrator makes it available for use by giving it a status of Online. When an environment is
offline, users may be restricted from performing data retrieval and export tasks.
Features
When users attempt to log on to an environment that is offline, the system displays a warning and may open
the environment to work offline on parked or locked documents. Users can also query the model information,
but the data may not be completely up-to-date.
Activities
You can manually set the status of an environment by choosing Manage All Environments Change Status .
You can enter a message to display to users who try to perform a restricted task while the environment is
offline. We recommend including the current date and time and giving an estimated time of when the
environment will become available, if appropriate.
More Information
1.14.2 Dimension Management
A dimension is a collection of related data members, which represents one aspect of a business; for example,
accounts, products, or entities. When you manage dimensions, you perform various tasks such as maintaining
the members of the dimensions, create their structure, and process the dimensions.
To view more information on managing dimensions, choose the configuration type of your Business Planning
and Consolidation installation:
● Dimension Management (Embedded only) [page 142]

● Dimension Management (Standard only) [page 115]
1.14.2.1 Dimension Management (Standard only)
Use
A dimension is a collection of related data members, which represents one aspect of a business; for example,
accounts, products, or currency. You manage dimensions to add and perform other operations on dimensions
within your environments, such as defining members and assigning properties. The dimensions can be added
to one or more models in the environment.
Features
You can manage dimensions in the following ways:
Task More Information
Adding Dimensions You can add new dimensions to an environment to make them available for use in its models.
See New Dimensions [page 116].
Copying Dimensions You can copy existing dimensions to create new dimensions. When you copy a dimension, you
specify the source dimension, a new name, and a description.
See New Dimensions. [page 116]
Modifying Dimensions You can modify an existing dimension. When you modify a dimension, you can change the
name, description, dimension type, reference dimension, and dimension properties as well as
enable member formulas for the dimension.
See New Dimensions. [page 116]
Processing Dimensions When you create a dimension or make changes to an existing dimension, you need to process
the dimension.
See Dimension Processing [page 120].
Deleting Dimensions You can delete a dimension from an environment. However, you cannot delete a dimension
when it is already assigned to a model.
You delete a dimension from an environment by selecting a dimension and choosing Delete.
Activities
To manage dimensions, go to Administration and under the Dimensions and Models choose Dimensions. Once
you select a dimension, you can perform one of the available tasks.
More Information
Dimension Types [page 118]
Dimension Security [page 119]
Dimension Processing [page 120]
Dimension Member Management [page 121]
Assignment of Dimensions to Models [page 121]
Dimension Properties [page 124]
1.14.2.1.1 New Dimensions (Standard only)
Use
You add dimensions to an environment to make them available for use by its models. To add a dimension to an
environment, you can create a new dimension or make a copy an existing dimension.
Features
When adding a dimension using the New Dimension wizard, you supply the following information. This
information is also useful when copying or modifying a dimension.
Field More Information
ID Dimension IDs are not case sensitive and display in the case you typed. They must
be unique regardless of case.
You can use any ID you want for a dimension as long as you follow these guidelines:
● Do not use special characters such as accented characters or Cyrillic fonts in

IDs.
● Enter a maximum of 16 characters and without single quotation marks ('), dou
ble quotation marks ("), back slashes (\), or ampersands (&).
Dimension IDs cannot contain a dash (-), but can contain an underscore (_).
● Do not begin a dimension ID with a number as its first character.
● Do not use the following names: App, AppAccess, AvlObject,
CategoryAccess, CollabDoc, CollabIcons, CollabRecipient,
CollabSupport, CollabType, DBVERSION, Defaults, DesktopStyleDef,
Dimension, DrillDef, DTIParam, Function, Formula, Group,
InvestParam, MemberAccess, MessageLog, Packages, PageDef,
Permission, PublishedBooks, Rate, ReportParam, SectionDef, Status,
StatusCode, TaskAccess, User, UserGroup, UserPackages, UserPovDef,
WebContents, SOURCE, SIGNEDDATA
Description Create dimension descriptions with a maximum of 255 characters.
Type The dimension type allows you to organize data within models based on the type of
information included.
See Dimension Types [page 118].
Referential Integrity Referential Integrity validates the properties of the dimension with the dimension
member IDs of a different dimension.
When you process the dimension, the system checks the values of the Referential In
tegrity property (see Dimension Processing [page 120]). Validation does not com
plete if they do not pass validation.
See the following table for the dimension validation rules.
Dimension properties You can assign new properties to a dimension.
See Dimension Properties [page 124].
Dimension Validation Rules
Dimension Type ID - De Reference Type ID - De

scription scription Property ID Reference Property ID
A - ACCOUNT A - ACCOUNT RATETYPE ID
C - CATEGORY T - TIME YEAR YEAR
E - ENTITY R - CURRENCY CURRENCY ID
Dimension Type ID - De Reference Type ID - De
scription scription Property ID Reference Property ID
I - INTERCOMPANY E - ENTITY ENTITY ID
Activities
You can create a new dimension in the Administration screen by choosing Dimensions New Dimension
under the Dimensions and Models section, and then entering the required data.
1.14.2.1.2 Dimension Types (Standard only)
Use
You use dimension types to organize data within models based on the type of information involved. An
environment can have multiple dimensions of one type. Each model within the environment, however, can have
only one of each of the required types. For example, the environment might contain the entity dimensions
EntityB and EntityF, with the Budgeting model using EntityB and the Forecasting model using EntityF.
The following table describes the types of dimensions within Business Planning and Consolidation:
Type ID Type Description More Information
A Account Usually contains chart of accounts and other planning assumption measures. The di
mension is normally represented by a hierarchy of accounts.
C Category This represents the versions or scenarios based on which data would be tracked. It
contains the types of data you are going to track, such as Actual, Budget, and Fore
cast. You can set up categories to store versions, such as BudgetV1, BudgetV2, and so
on.
D Audit This represents the various data source that could be used to manage the main data
and adjustments if any. This can be used very effectively in calculations and in busi
ness rules of a reporting consolidation model to segregate input data
E Entity Represents the business units that are used to drive the business process. Depending
on your model design, the Entity type can be an operating unit, a cost center, a geo
graphic entity, and so on. This represents the organization unit, whether defined for
legal purpose or from a business angle. This could be cost center, profit center, legal
company or region. The dimension is normally represented by hierarchy of entities.
Type ID Type Description More Information
G Group Reports consolidated results in multiple group currencies within a single entity struc
ture. Group provides multiple currencies for a group member.
 Note
Assign both an R and a G identifier to a consolidation model but assign only the G
identifier to the ownership model referred from the consolidation model. You can
not assign both an R and a G identifier to the same ownership model.
I Intercompany Contains the intercompany codes for the entities. This represents the intercompany
codes for the purposes of legal consolidation intercompany matching and elimination.
R Currency Contains the currency rates for all currencies in which your company does business.
For validation purposes, all environments must contain a Currency dimension; how
ever, each model within an environment is not required to have a Currency dimension.
The Currency dimension in a Reporting model must contain the REPORTING property;
the Currency dimension in a Rate non-reporting model does not need to contain the
REPORTING property. For information about reporting and non-reporting models, see
Model Management [page 150].
S Subtables This is used to break down the account activity or flow. For example, some accounts,
such as Fixed Assets, have a Subtables dimension containing Opening, Additions, De
letions, Transfers and Ending Balances. The Subtables type dimension is important
for writing business rules that require currency translation amounts to be calculated
by account.
T Time Contains the time periods for which you store data. This represents the time periods
based on which data are stored. The time periods could be represented in various
forms such as weekly, monthly, quarterly or custom.
U Userdefined This represents any Userdefined dimension that may be required for the planning
process. Referred to in the system as U1, U2, U3, and so on.
More Information
1.14.2.1.3 Dimension Security (Standard only)
Use
Security of dimensions is at the model level. You secure a dimension within a model. Dimension security
controls access to dimensions and their members.
Features
You can utilize the following features to secure dimensions:
Secured and Unsecured Dimensions
You can have a mixture of secured and unsecured dimensions in a model. Securing dimensions allows you to
control which users or teams have read, write or deny access to dimensions and their members. You need to
define a dimension as secured if you want to control member access by specific dimensions. All users can
access unsecured dimension members.
Data access profiles are used to grant model access. At least one dimension in a model should be secured to
ensure control over model and data access. When defining member access for secured dimensions, be sure to
define access for all secured dimensions of the model. Failure to do so results in the inability to access that
model for any users or teams assigned to the member access profile. For more information about setting up
member access profiles, see Member Access Profile Setup in the Security Guide for SAP Business Planning and
Consolidation.
Security for Member-level Dimensions
In addition to defining dimensions as secure for individual models, you can assign write access to members
within the dimension using member access profiles. Since by default, users do not have access to any
members of a secured dimension, member access profiles must be set up for the users you want to give read-
only or write access.
1.14.2.1.4 Dimension Processing (Standard only)
Use
When you create a dimension or make changes to an existing dimension, you must process the dimension.
Features
● When you process a new dimension, its properties are saved in the database.
● When you process an existing dimension, any changes you made to it are saved in the database.
● You can schedule the processing of dimensions with a Data Manager package.
For information on scheduling the processing of dimension members, see the SAP BusinessObjects EPM
solutions, add-in for Microsoft Office help.
Activities
You can process dimensions in the Administration screen. In the Dimensions and Models section, choose
Dimensions , select one or more dimensions, then choose Process.
1.14.2.1.5 Dimension Member Management (Standard only)
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, Category, and Currency dimensions.
A dimension contains a set of predefined properties based on its type. You can add new properties by choosing
Edit Structure, if desired.
You can assign dimension formulas that calculate and store information based on member values.
Adding members to dimensions
You can add members to dimensions within an environment in the Administration screen. Under the
Dimensions and Models section, choose Dimensions , select a dimension, and then choose Edit Members.
The maximum length for a member name is 32 characters. However, this limit only applies to newly created
dimensions. For dimensions that were migrated from Business Planning and Consolidation version 7.5, the
previous limit of 20 characters remains for member names.
 Note
If you make changes to any rules in the dimension, such as adding a new formula, you must validate and
save those rules, and process the dimension.
You can also add members to dimensions in bulk using packages and process chains within Data Manager.
For more information, see the SAP BusinessObjects EPM solutions, add-in for Microsoft Office help.
 Caution
You cannot rename dimension member IDs.
1.14.2.1.6 Assignment of Dimensions to Models (Standard

only)
Use
You assign dimensions to models to make the data in those dimensions available in your model. Each model
must have at least one dimension of the required types: Account (A), Category (C), Entity (E), and Time (T).
Additional dimensions may be required depending on the type of model.
 Note
Use caution when adding dimensions from a model that already contains data. Assign dimensions only to
new models that do not contain data. If you do add a dimension to a model with data, the system finds the
first base member alphabetically, and loads it into the Fact tables, therefore writing all of the data from the
model to that member.
Activities
To assign a dimension to a model, you modify the model as follows:
● Select the model and choose Edit.

● Choose Add / Remove.
● Select one or more available dimensions, then choose Add, then OK.
To remove a dimension from a model, you modify the model as follows:
● Select the model and choose Edit.

● Choose Add / Remove.
● Select one or more selected dimensions, then choose Remove, then OK.
More Information
1.14.2.1.7 Custom Measure Formulas (Standard only)
Use
You use the UJA_MAINTAIN_MEASURE_FORMULA program to create and maintain custom measure formulas.
Restrictions on Maintaining Measures
● Measures delivered with Business Planning and Consolidation cannot be deleted.

● The measures PERIODIC on a Periodic cube and YTD on a YTD cube that are delivered with Business
Planning and Consolidation cannot be changed. Other delivered measures can be changed at your own
risk.
 Note
Changes made to measures delivered with Business Planning and Consolidation are overwritten when
you make any changes to that model from the Administration screen. We recommend that you create
custom measures instead of changing the delivered measures.
● Formula names cannot be duplicated.

● Formula names must be entered in uppercase letters.
● Parent nodes of a hierarchy cannot be used in measure formulas.
Hints for Maintaining the Formulas
● Use the same formula name as you defined in the Formula Name field when you give the measure name in
[MEASURES].[<measure name>].
● If your formula has to refer to another measure, enter the other formula statement and new formula
together in the formula statement section. For example, refer to the formula statement of Periodic and QTD
measure on model with a YTD storage type.
● If you want to use a property of dimension within Measure Formula, you must include the SAP Business
Warehouse Technical name. You can find this name using transaction MDXTEST, for example. In this
transaction, choose InfoProvider as the catalog and then choose your model (cube). The system displays
the list of dimensions. Expand the dimension and then its properties to view the property list.
[%TIME%].CURRENTMEMBER.PROPERTIES("2/CPMB/GJPDBWP ") is a syntax for using the TIMEID
property of the TIME dimension.
Creating a Custom Measure Formula
1. Go to Transaction SE38 in the ABAP layer and enter UJA_MAINTAIN_MEASURE_FORMULA as the program
name.
2. Click the Debugging button.
3. In the Maintain Measure Formula screen, enter the model set ID, model ID, and user ID. You must have write
access to the core model to save a formula.
4. Click the Enter button on the System Function Bar.
5. In the Maintain Measure Formula screen, do any of the following:
○ To create a measure:
1. Click the new item button.
2. Enter a measure formula name, description, and formula.
○ To display a measure formula, double-click it.
○ To display an existing measure, place the cursor on the measure you want to display and click the
Display button.
○ To change an existing measure, place the cursor on the measure you want to change and click the
Change button.
○ To delete a measure, place the cursor on the measure you want to delete and click the Delete button.
Sample - YTD on YTD Model
MEMBER [MEASURES].[YTD] AS 'IIF(([%P_ACCT%].CURRENTMEMBER.PROPERTIES("2/CPMB/

ACCTYPE")="INC" OR [%P_ACCT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="LEQ"),-
([MEASURES].[/CPMB/SDATA], CLOSINGPERIOD([%TIME%].[LEVEL02])), ([MEASURES].[/CPMB/
SDATA], CLOSINGPERIOD([%TIME%].[LEVEL02])))' SOLVE_ORDER=3
Sample - PERIODIC on YTD Model

SDATA], CLOSINGPERIOD([%TIME%].[LEVEL02])))' SOLVE_ORDER=3## AS 'IIF(([%P_ACCT
%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="INC" OR [%P_ACCT
%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="EXP") AND NOT ([%TIME
%].CURRENTMEMBER.PROPERTIES("2/CPMB/PERIOD")="TOTAL" OR [%TIME
%].CURRENTMEMBER.PROPERTIES("2/CPMB/PERIOD")="Q1" OR [%TIME
%].CURRENTMEMBER.PROPERTIES("2/CPMB/PERIOD")="JAN" ), [MEASURES].[YTD]-([MEASURES].
[YTD],[%TIME%].LAG(1)), [MEASURES].[YTD])' SOLVE_ORDER=3
Sample - QTD on YTD Model

SDATA], CLOSINGPERIOD([%TIME%].[LEVEL02])))' SOLVE_ORDER=3
AS 'IIF(([%P_ACCT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="INC" OR [%P_ACCT
%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="EXP") AND NOT ([%TIME
%].CURRENTMEMBER.PROPERTIES("2/CPMB/PERIOD")="TOTAL" OR [%TIME
%].CURRENTMEMBER.PROPERTIES("2/CPMB/PERIOD")="Q1" OR [%TIME
%].CURRENTMEMBER.PROPERTIES("2/CPMB/PERIOD")="JAN" ), [MEASURES].[YTD]-([MEASURES].
[YTD],[%TIME%].LAG(1)), [MEASURES].[YTD])' SOLVE_ORDER=3
MEMBER [MEASURES].[QTD] AS 'IIF(([%P_ACCT%].CURRENTMEMBER.PROPERTIES("2/CPMB/

ACCTYPE")="INC" OR [%P_ACCT%].CURRENTMEMBER.PROPERTIES("2/CPMB/
ACCTYPE")="EXP"),IIF([%TIME%].CURRENTMEMBER.PROPERTIES("2/CPMB/TILEVEL")="QUARTER",
[MEASURES].[PERIODIC],IIF([%TIME%].CURRENTMEMBER.PROPERTIES("2/CPMB/
TILEVEL")="MONTH" OR [%TIME%].CURRENTMEMBER.PROPERTIES("2/CPMB/TILEVEL")="WEEK" OR
[%TIME%].CURRENTMEMBER.PROPERTIES("2/CPMB/TILEVEL")="DAY",SUM(PERIODSTODATE([%TIME
%].CURRENTMEMBER.PARENT.LEVEL, [%TIME%].CURRENTMEMBER),[MEASURES].
[PERIODIC]),NULL)),[MEASURES].[YTD])' SOLVE_ORDER = 3
1.14.2.1.8 Dimension Properties (Standard only)
Use
By assigning properties to dimensions, you can implement powerful features in your reporting, member
lookup, formulas, and Data Manager selections. You can filter on properties in many places in the system. For
example, if you want to be able to easily select entities by geographic region, you simply add a REGION
property, and enter a region value for each entity. Then you can filter and sort by region, apply account logic by
region, or define a report format based on region.
The system requires various properties depending on the dimension. You can also assign additional properties
for your business needs.
Many of the properties are generic, such as ID and DESCRIPTION, while others can be unique to a dimension,
such as SCALING. The properties define the behavior of members within the dimension.
Features
You can use the following features when working with dimensions:
Adding properties to dimensions You can add properties to a dimension by selecting a dimension
within the dimension library and clicking Add in the toolbar above
the property list.
When you add a property to a dimension, you must specify the fol
lowing:
● ID - An ID for the property. The ID is not case sensitive but is

displayed in the case it is typed. The ID must be unique (re
gardless of case) within a dimension. The maximum length of
an ID is 20 characters. The permitted characters are: A-Z,a-z,
0-9,_,-,. An ID cannot contain the following invalid characters:
single quotation mark ('), double quotation mark ("), backslash
(\), ampersand (&), dash (-) The ID cannot start with a number
as a first character. The ID cannot be the same ID as that of a
system-generated property. The ID cannot contain the string
of characters “PARENTH”. The ID cannot be the same ID as
one of the special properties described below.
● Name - A name for the property. The maximum length for a
property name is 40 characters.
● Number of Characters - The maximum length for values of the
property. This must be an integer greater than zero.
Adding properties to dimensions in Consolida When you add a property to a dimension in a consolidation, owner
tion,Ownership, and Rates models ship, or rates model, you have the option to add the set of prede
fined properties for the following dimension types:
● Account
● Category
● Audit
● Entity
● Time
● Currency
When you add properties to any of these dimension types, you can
select to add a new property or add the set of required properties
for consolidation type models. For the Account dimension, you can
also add the set of required properties for ownership type models.
When you add the set of predefined properties required for consoli
dation, ownership, or rates models, if there is already a property
with the same ID as one of the required properties, the system han
dles this as follows:
● The corresponding property is not added to the dimension.

● If the number of characters of the existing property is greater
than expected, the system does not change it.
● If the number of characters is smaller, it is updated with the
default value specified for this property in the set of predefined
properties
A message is displayed at the end of the process to inform you if

the system did not add some of the properties because they al
ready exist, and if the system changed the number of characters.
Modifying dimension properties You can modify a property which is not a system-generated prop
erty. You edit and change a property directly in the property list. You
cannot change a property ID after you have saved it. However, you
can change a property name and the number of characters, but you
cannot reduce the length previously specified.
Adding property values After you add a property to a dimension, you can assign property
values to members in the dimension. You can add property values
to properties by selecting the desired dimension from the dimen
sion library, selecting Edit Members, then adding the desired values
directly in the member grid under the appropriate property. After
you are done, you must save the changes and process the dimen
sion.
Removing dimension properties You can remove properties from a dimension by selecting a dimen
sion within the dimension library and clicking Remove in the toolbar
above the property list. This removes the property from the list. You
cannot delete a system-generated property.
Limiting the number of dimension members available When a user is filling a journal template, all base-level members
to users that this user has access to are available. You can use the “Enable
journal” function to limit the number of dimension members that
are available to the users during journal entry. You can limit journal
dimension member lists by adding the property EnableJRN to each
dimension for which you want to limit the journal access. After that,
in its dimension sheet, enter Y in the EnableJRN column of the
base-level members for which you want to allow users to post jour
nal entries. Do this for each dimension you want to limit, then proc
ess the dimensions.
System-generated Properties
The following properties are generated for all dimension types, but are not displayed in the list of properties for
a dimension.
Property Description
DESCRIPTION Display name of the dimension. This appears in the language specified in the Preferences set
tings.
CALC Indicates whether the member is calculated by means of a formula or is at a parent level. The
property values can be viewed in the Member Selector in the EPM add-in.
HIR Stores the hierarchy IDs associated with the member, for example H1;H2.
Special Properties
The following are reserved IDs that you cannot enter as a property ID when adding a new userdefined
dimension property:
Property Description
SOLVE_ORDER The SOLVE_ORDER property defines the order in which the system solves calculated members
when they intersect with other calculated members. SOLVE_ORDER determines the order in
which the system evaluates and calculates dimensions, members, calculated members, cus
tom rollups, and calculated cells. The system evaluates the member with the highest solve or
der first, and calculates it last. Zero is the highest priority.
Guidelines for implementing SOLVE_ORDER:
● Specify up to 3 measures and 5 members within a SOLVE_ORDER property.

● Specify dimensions by dimension name, making sure that capitalization is correct.
 Example
[ACCOUNT].[Account1] / [ACCOUNT].[Account2]
[PRODUCT].[Product1] + [PRODUCT].[Product2]
The only exception to this rule is that you do not need to specify an Account dimension by
name.
FORMULA The optional property FORMULA allows you to define calculations to perform for dimensions.
This powerful feature of the system gives you the ability to customize data management to
meet your business requirements.
Select the Enable Member Formulas option for the dimension to which you want to apply mem
ber formulas. For information about implementing formulas, see Member Formulas [page
209].
More Information
Dimension Processing [page 120]
1.14.2.1.8.1 Owner Property (Standard only)
Use
The owner designating dimension property is created in any dimension used as a driving dimension for a
business process flow. You add the property to the dimension with any name. We recommend using a naming
convention that denotes the relationship to business process flow owners. A dimension can have one or more
owner designating properties as long as each is unique.
For example, if your business process dictates that an entity is the differing factor when it comes to entering
data, the Entity-type dimension is the dimension that drives the owner of the activity context. If your business
process dictates that a department name is the differing factor, the Department dimension would have a
unique owner designating property that drives the owner of the activity context. The “Owner” property used for
work status is a reserved property. The business process flow owner properties must be named with a unique
name.
Prerequisites
The dimension you select to drive must have at least an owner type dimension property. When more than one
exists, you choose the appropriate property to use in the business process flow.
Features
The owner designating property takes user and team names in brackets as values. You can enter multiple
names and teams separated by commas. You must also include the domain or server name in the path.
Activities
You do the following to set up an Owner property:
● Set up the owner property by accessing the Dimension Library, choosing Maintain Dimension Property, and
adding an owner.
● Assign the owner property to a dimension by accessing Maintain Dimension Members. Define the owner
property on a dimension such as Entity, then define the property values. You can enter multiple names and
teams separated by commas. You must also include the domain or server name in the path.
1.14.2.1.8.2 Reviewer Property (Standard only)
Use
The Reviewer property is a special property used to identify the person or team that must review an activity
performed by another user in a business process flow. This person or team member can approve or reject the
action taken by the user. A reviewer can also reopen the previous step of a business process flow.
The Reviewer property must be defined prior to creating a BPF template, as the administrator is required to
enter it during the setup of a business process flow template.
Features
When defining the property, the following rules apply:
● The reviewer designating property can be set up on any dimension and can be any name, such as
BPF1_Reviewer. A dimension can have one or more uniquely named properties.
● You typically select a reviewer designating property when setting a drive dimension and owner property.
When defining the property values, the following rules apply:
● The value can be a user ID or a team, or a combination of both.

● If defining multiple property values, you must separate each entry by a comma.
● A team name must be enclosed in brackets, as in [TEAM].
● The reviewer property is case sensitive.
● The limit is 255 characters.
● A reviewer can reopen the previous step of a business process flow. The step must be defined to allow
reopen.
Activities
To define a reviewer property, open the dimension that you want to designate as the driver dimension of the
business process flow, then add a Reviewer property and its property values. For more information, see
Dimension Properties [page 124].
When creating a business process flow, choose Enable Reviewers, then set a Reviewer property when defining
the step region criteria for a new step.
More Information
Creating Processes [page 339]
1.14.2.1.8.3 Account Dimension Properties (Standard only)
Use
The account dimension defines the chart of accounts for your model and how those accounts are calculated
and aggregated. Any dimension that is assigned the type A is considered an account dimension. Each model
can have only one account-type dimension.
Features
An account dimension has the following system-generated properties:
Property Name Description
ACCTYPE Account type. Can be INC for Income, EXP for Expense, AST for Asset, LEQ for Liabilities and
Equity.
The account type cannot be blank.
RATETYPE Used by the currency conversion business rules. Value is optional.
SCALING Scaling options are Y or N. Used by EvDRE, EPMScaleData, and Library view. Value is optional,
but if a value is not defined, scaling is unavailable for the associated member ID.
The following property is required only if the account dimension is used in a consolidation model.
TYPELIM Specifies that Automatic Adjustments details are created

based on a generic value, rather than mentioning the mem
ber itself. Allows you to apply the same processing to several
accounts having the same property value.
The following property is required only if the account dimension is used in an ownership model.
IS_INPUT Flag for ownership accounts to be used in Method-based

multipliers.
More Information
1.14.2.1.8.4 Category Dimension Properties (Standard only)
Use
The category dimension defines the groupings in which you store information in your model. Typical categories
are Budget, Actual, and Forecast. Any dimension that is assigned the type C is a category dimension. Each
model can have only one category-type dimension.
Features
A category dimension has the following required properties:
YEAR Used to assign a YEAR to the category, to be used with the EPMRetrieveData and
EPMMemberOffset functions in reporting. For more information, see the SAP
BusinessObjects EPM solutions, add-in for Microsoft Office help.
The following properties are required only if the category dimension is used in a consolidation model.
CATEGORY_FOR_OPE Category of source data to use when performing carry forward (CopyOpening).
FX_DIFFERENCE_ONLY Specifies whether the translation result is calculated normally (blank or N) or if only
the translation difference with the source category is computed ( Y).
FX_SOURCE_CATEGORY Category of source data to be used when running currency translation on a simula
tion category.
OPENING_PERIOD Period number of source data to use when performing carry forward (CopyOpening).
This can be absolute (for example, 12 for December) or relative (for example, -1 for
prior period).
OPENING_YEAR Year offset of source data to use when running carry forward (CopyOpening). This is
relative (for example, -1 for prior period).
OWN_CATEGORY Category of source ownership data to be used when running consolidation on a simu
lation category
OWN_YEAR Period number of source ownership data to be used when running consolidation on a
simulation category. This can be absolute (for example, 12 for December) or relative
(for example, -1 for prior period).
OWN_PERIOD Year offset of source ownership data to be used when running consolidation on a sim
ulation category. This is relative (for example, -1 for prior year).
RATE_CATEGORY Category of source exchange rate data to use when running currency translation on a
simulation category
RATE_PERIOD Period number of source exchange rate data to use when running currency transla
tion on a simulation category. This can be absolute (for example, 12 for December) or
relative (for example, -1 for prior period).
RATE_YEAR Year offset of source exchange rate data to be used when running currency transla
tion on a simulation category. This is relative (for example, -1 for prior year).
STARTMNTH Starting month.
More Information
1.14.2.1.8.5 Currency Dimension Properties (Standard only)
Use
The Currency dimension is required if your company reports on local currency and translated values. These
dimensions store the reporting and input currencies for your organization. Any dimension that is assigned the
type R is a currency-type dimension.
Features
The following table describes the required properties of a currency dimension. If you are utilizing the legal
consolidation functionality of Business Planning and Consolidation, the currency-type dimension requires
additional properties.
ENTITY A 32-character field that can either be left blank or contain a valid member name of the entity
dimension associated to the current model. The ENTITY property is validated against the entity
dimension, and blank fields are allowed.
REPORTING Specify your reporting currencies. If Y, this member is used for reporting purposes.
The following property is required only if the currency dimension is used in a consolidation model.
CURRENCY_TYPE Identifies the local currency member (L) versus reporting

currency members (R) or transaction currency member (T).
The following property is required only if the currency dimension is used in a rate model.
MD Defines whether the currency exchange rate for that cur

rency is used to multiply or divide with the local amount.
More Information
1.14.2.1.8.6 Entity Dimension Properties (Standard only)
Use
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.
Features
An entity dimension has the following required properties:
CURRENCY The currency used by the entity.
CTRL_CURRENCY_NOT_LC Specifies the Reporting Currency dimension member against which a data con
trol is performed. A control is an individual check for data accuracy and consis
tency. Controls are enabled or disabled at the model level.
The following are valid values:
● Y - The generic LC (local currency) member is used.

● N - The entity currency property is used, for example, EUR. This can be used
when loading pre-translated data from a source system where currency
translation has already been performed.
If no value is set, the default value is Y.
For more information, see Controls [page 306].
CONTROL_LEVEL Specifies the controls that are relevant to an entity when a control set (a group of
controls) is executed.
The following are valid values:
● Level 1 - Basic controls

● Level 2 - Standard controls
● Level 3 - Advanced controls
● Level 4 - Comprehensive controls
If 4 is selected, all controls having a level from 1 to 4 are executed. If blank or 0,

no control is applicable.
For more information, see Controls [page 306].
The following properties are required only if the entity dimension is used in a consolidation model.
ELIM Defines whether the entity is used to store the intercompany elimination for a
given node in the hierarchy. Valid values are Y or N.
FX_TYPE Defines the subset of Currency Conversion rules to apply to the entity, where
FX_TYPE matches the Entity FX Type property of the rules.
INTCO Defines the corresponding intercompany member for an entity.
More Information
Dimension Properties (Standard only) [page 124]
1.14.2.1.8.7 Group Dimension Properties (Standard only)
Use
The group-type dimension represents the relationship of entities for a given consolidation result. This group is
consolidated in a single currency, so there is no need to have another dimension. You can continue to use the
currency-type dimension for this purpose or you can split it into a group-type dimension (type G) and use a
pure currency-type dimension (type R) to allow reporting in multiple group currencies.
 Note
A group dimension must be assigned to an ownership and a consolidation model. You should assign both a
currency and a group dimension to a consolidation model but you should assign only the group dimension
to the ownership model referred from the consolidation model. You cannot assign both a currency and a
group dimension to the same ownership model.
CONSO_TYPE Specifies which set of rules to apply to a group. Refers to group type filter in Adjustments
and Eliminations.
CURRENCY_TYPE Used for the currency conversion.
● N - Non-group
● G - Group
DATASRC_LEVEL Stores the consolidation differences resulting from different % or methods along the group
hierarchy
ENTITY Blank or a valid entity ID. This is used to define the link between the Group and the Entity or
to indicate the Entity where the aggregation should be stored.
If this property is filled with a valid entity ID, and the property STORE_ENTITY is set to Y,
the results of the currency conversion for the current Group are also copied into this Entity.
(Length = 20)
GROUP_CURRENCY This can be any valid reporting currency, and is used for currency conversion.
This property can only be used on Currency members with the property CURRENCY_TYPE
of G and, in this case, it must contain a valid ID from the Currency dimension with the prop
erty CURRENCY_TYPE value of R. (Length = 20)
PARENT_GROUP Must be a valid ID from the Groups dimension. If you want to do the consolidation by level,
you must indicate here the higher level from the group. If you want to use this property to
define the hierarchy, enter the same code as the ID for your top group. If this property is
blank, the dynamic hierarchy from the ownership application is used. (Length = 20)
STAGE_ONLY -
STORE_ENTITY Specifies whether to store the ID entered in the Entity property.
Y - If you want to store the ID entered in the Entity property.
Blank - If you do not want to store the ID entered in the Entity property.
STORE_GROUP_CURR Used for currency conversion.
Y - By default the results of the conversion into a Group currency are written in both the
Group member and in the Currency member of the currency dimension.
N (or blank) - If only the Group member is to be stored, set this property to N. (Length = 1)
More Information
1.14.2.1.8.8 Intercompany Dimension Properties (Standard
only)
Use
The Intercompany dimension defines the base members associated with the level at which Intercompany
balances are tracked for Intercompany eliminations.
Features
An Intercompany dimension has the following required properties:
ENTITY A 32-character field that can be left blank or contain a valid

member name of the entity dimension associated to the cur
rent model. The ENTITY property is validated against the en
tity dimension, and blank fields are allowed.
SCALING Scaling options are Y or N. Used by EvDRE and Library view.

The property is optional, but if a value is not defined, scaling
is unavailable for the associated member ID.
More Information
1.14.2.1.8.9 Time Dimension Properties (Standard only)
Use
The time dimension defines the units of time for your model and how those units aggregate. Any dimension
that is assigned the type T is a time dimension. Each model can have only one time dimension.
Features
A time dimension has the following required properties:
BASE_PERIOD A system-generated property, used by the query engine for calculations and by the Consoli
dation process.
LEVEL Time can be a year, quarter, month, week, or day. The LEVEL property is important in defin
ing your time periods. You must have the correct level for each member. You must follow the
chronological format throughout the time dimension. The correct format is the following:
● YEAR
● QUARTER
● MONTH
● WEEK
● DAY
PERIOD The PERIOD property allows you to filter, sort, and report based on the period.
YEAR The YEAR property allows you to filter, sort, and report based on the year. You should place
the YEAR properties in chronological order in the file, in order for the EPMMemberOffset
function to give offsets correctly.
The following property is required only if the time dimension is used in a consolidation model:
MONTHNUM Provides a sorting order to leaf members of the time dimen

sion within a year. For each base member, the number
should be unique.
TIMEID Numeric ID to used for identifying the time member, for ex
ample, 20120100 for 2012.JAN.
For detailed information about maintaining these properties, refer to the note 2114433 .
More Information
1.14.2.1.8.10 User-Defined Dimension Properties (Standard
only)
Use
A userdefined dimension is any dimension that is not one of the standard system dimensions.
Features
A userdefined dimension has the following required properties:
SCALING Scaling options are Y or N. Used by EvDRE, EPMScaleData, and Library view. The property
is optional, but if a value is not defined, scaling is unavailable for the associated member ID.
More Information
1.14.2.1.8.11 Audit Dimension Properties (Standard only)
Use
The audit dimension is userdefined and tracks the source of input data.
Features
An audit dimension has the following required properties:
SCALING Scaling options are Y or N. Used by EvDRE, EPMScaleData,

and Library view. This property is optional, but if a value is
not defined, scaling is unavailable for the associated mem
ber ID.
The following properties are required only if the audit dimension is used in a consolidation model.
DATASRC_TYPE Specifies whether a data source is used for Input ( I), Manual
Adjustments ( M) or Automatic Adjustments Eliminations
( A).
IS_CONSOL Specifies whether data is consolidated or not. Typically this

is set to yes ( Y), but set it no ( N) for data sources used in
groupspecific adjustments (for example, post consolidation
adjustments entered against a specific group).
IS_CONVERTED Specifies whether data is translated or not. Typically this is

set to yes ( Y), but set it to no ( N) for data sources used in
currencyspecific adjustments (for example, adjustments in
EUR, USD, and so on).
DATASRC_STAGE Defines to which Audit member consolidation adjustments

from lower groups are inherited in higher groups (Parent
groups).
DIMLIST Property used to create a grouping of data sources which

can later be used as filters in Automatic Adjustments and
Eliminations business rules.
COPYOPENING Flag used to filter data sources when running carry forward
(CopyOpening).
OPENING_DATASRC Specifies a different destination data source, to which the

corresponding amounts are carried forward. For example,
this can be used where certain entries are posted to a data
source that specifically identifies these adjustments as audit
adjustments in the current year, but in future years it might
be required to simply include in another standard data
source (that is, Input).
More Information
1.14.2.1.8.12 Subtable Dimension Properties (Standard only)
Use
Subtable dimensions break down account activity or flow. For example, some accounts, like Fixed Assets, have
a subtable dimension containing Opening, Additions, Deletions, Transfers, and Ending Balances. The subtable
type dimension is important for writing business rules that require currency translation amounts to be
calculated by account. Since the subtable information can be used for multiple accounts, it requires its own
dimension.
Features
A subtable dimension has the following required properties:
FLOW_TYPE Defines the type of flow of the dimension, as follows:
● OPENING - Opening
● TRANSLOPE - Change difference on opening
● ALLOCINC - Allocation
● MERGER - Merger
● INCOME - Net income from the period
● CHANGE - Variation
● TRANSFER - Transfer
● TRANSFLOW - Translation change on flow
● VARSCP - Variation in scope (generic)
● 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
SCALING Scaling options are Y or N. Used by EvDRE, EPMScaleData,

and Library view. The value is optional, but if a value is not
defined, scaling is unavailable for the associated member ID.
More Information
1.14.2.2 Dimension Management (Embedded only)
Use
A dimension is a collection of related data members that represent one aspect of a business, for example,
accounts, products, or entities.
Features
You can manage dimensions in the following ways:
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 (Embedded only) [page 144].
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 (Embedded only) [page 144].
Processing Dimensions When you create a dimension or make changes to an existing dimension, you need to process
the dimension.
See Dimension Processing (Embedded only) [page 145].
Maintaining Hierarchies You can add a new hierarchy, maintain an existing hierarchy structure, or delete an existing
hierarchy.
See Hierarchy Management (Embedded only) [page 145].
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 (Embedded only) [page 148].
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 (Embedded only) [page 148] and Deleting Local Dimensions
(Embedded only) [page 150].
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 at http://help.sap.com/bopacnw101.
Related Information
Dimension Structure (Embedded only) [page 144]

Dimension Member Management (Embedded only) [page 144]
Dimension Processing (Embedded only) [page 145]
Hierarchy Management (Embedded only) [page 145]
Dimension Security (Embedded only) [page 148]
1.14.2.2.1 Dimension Structure (Embedded only)
Use
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.
1.14.2.2.2 Dimension Member Management (Embedded only)
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.
A dimension contains a set of predefined properties based on its type. You can add new properties by using BW
modeling tools.
Managing Dimension Members
You can add, delete, and modify members in dimensions within an environment in the Administration screen.
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.
1.14.2.2.3 Dimension Processing (Embedded only)
Use
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.
1.14.2.2.4 Hierarchy Management (Embedded only)
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.
1.14.2.2.5 Dimension Security (Embedded only)
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 at http://help.sap.com/
bopacnw101.
1.14.2.2.6 Creating Local Dimensions (Embedded only)
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 Access Type of the InfoObject's master data is either default value or SAP HANA View.
● 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 (Embedded only) [page 150]
1.14.2.2.6.1 Deleting Local Dimensions (Embedded only)
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.
1.14.3 Model Management
Use
A model is a representation of the relationships, calculations, and data of an organization or business segment.
In a standard configuration of Business Planning and Consolidation, models can be categorized as 'reporting'
models and 'drivers and rates' models. Reporting models are used for user input and analysis. Drivers and rates
models store reference data such as currency rates and ownership data. For information about each, see
Reporting Models (Standard only) [page 154] and Drivers and Rates Models (Standard only) [page 155].
In an embedded configuration of Business Planning and consolidation, 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 legal consolidation tasks. Consolidation type models must
have specific components defined to fufill legal consolidation requirements. For detailed information, see Set
up a Consolidation Model (Embedded only) [page 190].
Features
You can use the following features when managing models:
Creating New Models in a Standard Configuration of Business Planning and Consolidation
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 model in the Planning and Consolidation Administration screen, you provide a name and
description, select the type of model and its options and settings, indicate whether you want to start from a
blank model or an existing model, and select the dimensions to include in the model.
The setting Non Interco Member in Ownership is used to indicate a non-intercompany member within the
ownership model.
The setting Parent/child property used for hierarchy of Groups is used with dynamic hierarchy statutory
applications when defining fixed hierarchies. The value must match the value in the ParentProperty property
value of entities in the statutory application's supporting ownership application.
During the model creation process, items such as model publications, private publications, Documents view,
reports, team tasks, and Data Manager packages may be copied from a source model. You can use the Use as
Source of Data for External Applications checkbox to make data within the model available for evaluation
through Process Control.
Once a model has been created, you can view features of Business Planning and Consolidation that are being
used for the model, including whether work status, data auditing, and journal template are on or off. You can
also enable comments and use the model as a source of data for external applications.
Copying Models (standard only)
You can copy an existing model as a quick way of creating a new model. The system copies the dimensions,
data, and templates from the source model to the new model. You can modify the model later. When you copy a
model in the Planning and Consolidation Administration screen, you select a source model, then provide a
name and a description of the new model.
Adding Business Rules to Models (standard only)
You can add business rules to a model in the Business Rules domain of the Administration screen. You activate
the rule types you need for the model, if not already activated, and then add the new business rules of each
type to the model. For more information, see Business Rules Management (Standard only) [page 269].
Setting up Legal Consolidation Models (standard only)
In order for a legal consolidation model to function properly, it must contain the four required ENTITY,
CATEGORY, TIME, and ACCOUNT dimensions (but can be named as desired). The remaining dimensions have
the following rules:
● The CURRENCY/ GROUP dimension is required for the consolidation and/or currency business rules
● The INTCO dimension used for matching intercompany activity
● The DATASRC dimension is required for elimination and/or consolidation business rules
● The SUBTABLE (flow) dimension is optional, and based on your requirements
Setting up Drill-through (standard only)
You can set up drill-throughs to view the source data that make up the content of a selected cell in an Excel
report. For more information, see Drill-Through Setup (Standard only) [page 364].
Optimizing Models (standard only)
When you create new environments and models, only a small amount of data exists. Since the amount of data
you maintain grows over time, we recommend you periodically run the optimize function to improve
performance. See the “Business Planning and Consolidation Administrator’s Guide” available on the SAP Help
Portal for instructions.
YTD Storage Models (standard only)
Since most general ledger and other source systems store balances on a periodic basis, default data storage
for models is based on periodic time intervals. With this method, all calculations are on periodic balances. The
balances are then accumulated for year-to-date reporting. In some business cases, calculations should occur
on a year-to-date basis, like in a model with foreign currency translation. If a year-to-date basis is required, you
can set your reporting models when you create them to store data on a year-to-date basis, so they accept data
entry in the YTD format. When data is entered into YTD, its periodic values, used for reporting purposes, are
derived by calculating the difference between the current period and the last period, as in the following
example.
 Example
This example depicts INC or EXP accounts. There is no change in behavior for AST or LEQ accounts.
January February March
Periodic 100 200 0
YTD 100 300 300
Both periodic and year-to-date storage methods support daily, weekly, monthly, quarterly and year-to-date
reporting requirements.
You create a YTD storage model by specifying YTD - Year To Date for the data entry mode when defining
the type of model you are creating.
Creating New Models in an Embedded Configuration of Business Planning and Consolidation
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 in an embedded configuration of Business Planning and Consolidation, 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:
● Real-time InfoCubes
● Input enabled DataStore Objects
● Virtual Providers with write interface
● Local providers
For more information about local providers, see Working with Local Providers (Embedded only) [page 159].
 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 ABAP
back-end of BW. For more information, see the documentation of SAP Business Warehouse, available at
http://help.sap.com/netweaver .
Adding or Removing InfoProviders (embedded only)
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 (embedded only)
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 real-time enabled InfoCubes. The complex aggregation levels
(aggregation levels that are created on MultiProviders) are not displayed.
● Related MultiProviders - shows the MultiProviders that exist for the selected InfoProvider.
Adding Business Rules to Models (embedded only)
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 (Embedded only) [page 289].
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 344].
Deleting Models
Administrators can delete models when necessary.
 Caution
In a standard configuration of Business Planning and Consolidation, you can delete a model when it
contains data. You cannot, however, delete a dimension member when there is data associated with that
member in the model.
Related Information
Dimension Types (Standard only) [page 118]
1.14.3.1 Reporting Models (Standard only)
Use
Reporting models hold financial data.
Features
The following table describes the different types of reporting models and lists the required dimensions for
each:
Type of Reporting Model Description Required Dimensions
Financial Financial models perform management Account (A)

and legal consolidation functions. They
Category (C)
support data translations from local
currencies to one or more reporting Entity (E)
currencies, intercompany elimination
Time (T)
calculations, and other calculations.
Currency (R)
When you create a financial model, you
must choose an associated rate model
(see Drivers and Rates Models [page
155]).
You can also choose to set up the fol

lowing business rules:
● Currency conversion
● Account transformation
● Intercompany bookings
● US eliminations
● Carry-forward rules
● Validations
Type of Reporting Model Description Required Dimensions
Consolidation Consolidation models perform more Account (A)

complicated legal consolidation func
Category (C)
tions than Financial models. Consolida
tion can incorporate complex organiza Entity (E)
tional structures involving full owner
Time (T)
ship, partial ownership, minority owner
ship and consolidation methods. Audit (D)
Consolidation models must reference Group (G)

an ownership model and a rate model Intercompany (I)
(see Drivers and Rates Models [page
155]). Subtables (S)
You can also choose to set up the fol Currency (R)
lowing business rules:
● Account transformation
● US eliminations
● Carry-forward rules
● Validations
● Automatic adjustments
Standard Standard reporting models have no Account (A)

special requirements other than the
Category (C)
four required dimensions. Generic mod
els have no default business intelli Entity (E)
gence. Therefore, to apply logic, create
Time (T)
it using logic scripts.
1.14.3.2 Drivers and Rates Models (Standard only)
Use
Use this function to become familiar with the types of non-reporting models available in Business Planning and
Consolidation.
Features
Drivers and rates models support reporting models by holding data such as currency exchange rates and
ownership percentages. You can report on drivers and rates model data. You cannot define business rules to
these model types. The following table describes the different types of drivers and rates models and lists the
required dimensions for each:
Type of Drivers and Rates Model Description Required Dimensions
Rate A rate model is a supporting model for Account (A)

financial and consolidation reporting
Category (C)
models. It is used to store exchange
rates that support currency conversion Entity (E)
in financial models.
Time (T)
The time dimension must be identical
Currency (R)
to the dimension used by the models
using the rate model to store their for
eign currency exchange rates and must
have the same category member IDs.
This model must include a currency di

mension detailing the exchange rates
by each input currency. The currency
dimension in a rate model does not
need to have the REPORTING property.
Ownership The ownership model is a supporting Account (A)

model for a consolidation reporting
Category (C)
model. It stores information such as the
consolidation methods, ownership per Entity (E)
centages, and group roll up information
Time (T)
used for legal consolidation.
Intercompany (I)
Group (G)
Generic A generic model has no special require Account (A)

ments other than the four required di
Category (C)
mensions. Generic models have no de
fault business intelligence. Therefore, to Entity (E)
apply logic, create it using script logic.
Time (T)
1.14.3.3 Large Key Figure Usage (Standard only)
By default Business Planning and Consolidation supports numbers with up to 13 digits before a decimal point
and 7 digits after a decimal point. You can use larger numbers by enabling functionality that allows large key
figures, which are numbers with up to 24 digits before the decimal point and 7 digits after it. To use large key
figures you must first activate the functionality in the SAP Reference IMG, and then enable it in the model.
Related Information
Activate Large Key Figure Support in the SAP Reference IMG (Standard only) [page 157]
Modify Existing Models for Large Key Figure Usage (Standard only) [page 158]
Create New Models that Use Large Key Figures (Standard only) [page 158]
1.14.3.3.1 Activate Large Key Figure Support in the SAP

Reference IMG (Standard only)
Perform this task to activate the use of large key figures within the system. You must also modify existing
models in order to use this functionality and follow specific steps when creating new models.
Prerequisites
To use this feature, you must have the following software installed:
● Planning and Consolidation 10.0 for the NetWeaver platform SP10 or later
● EPM solutions, add-in for Microsoft Office 10.0 SP14 or later
Procedure
1. Run transaction SPRO.

2. Choose SAP Reference IMG.
3. Choose Planning and Consolidation Configuration Parameters Set Global Parameters .

4. Enter a new flag with name ENABLE_LARGE_KEY_FIGURE and set its value to X.
5. Save your changes.
1.14.3.3.2 Modify Existing Models for Large Key Figure Usage
(Standard only)
To use large key figures in the system, you must modify existing models:
Procedure
1. In the Administration client, choose Models.

2. Select the model that you want to modify and choose Edit.
3. In the modification screen choose Change Type. The update wizard starts.
4. In the Key Figure Length option, select Large.
5. Finish the wizard and save your changes.
1.14.3.3.3 Create New Models that Use Large Key Figures

(Standard only)
To use large key figures in the system, follow these steps when creating new models:
Procedure
1. In the Administration client, choose Models.

2. Start the model creation wizard.
3. In the Key Figure Length option, select Large.
4. Finish the wizard to create the new model.
1.14.3.4 Stabilizing Cube Names (Standard only)
Use this function to keep the technical name of a cube unchanged after model modification, optimization, or
transport.
To keep the technical name of a cube unchanged after model modification, optimization, or transport, you can
use the parameter ENABLE_FIXED_CUBENAME with X as its value.
Modifying a model
When the parameter ENABLE_FIXED_CUBENAME is NOT set to X in the source and target system, the current
system behavior remains unchanged.
When the parameter ENABLE_FIXED_CUBENAME is set to X, then:
● If the model has no transaction data, the technical name remains unchanged after modifying the model
structure.
● If the model has transaction data, an error message appears to indicate that modifying the model in cube
name stabilization mode is not possible. You must to back up and clear the transaction data in the cube
and modify it again.
Optimizing a model
When the parameter ENABLE_FIXED_CUBENAME is set to X, then:
● A full optimization is automatically switched to light optimize mode and the technical name of the model
does not change after the optimization.
● If you run a light optimize, there is no change to the current system behavior.
Transporting a model
When the parameter ENABLE_FIXED_CUBENAME is set to X in both the source and target system, the resulting
behavior depends on several factors as shown in this table:
Effects of ENABLE_FIXED_CUBENAME when transporting a model

Cube technical name Cube technical name Cube technical name Cube technical name
Source system A A A A
Target system A (with transaction A (without transaction B (with transaction B (without transaction
data) data) data) data)
Behavior and result The import is rejected. The target model is In the target system: In the target system:
An error appears in the overwritten by the
1. Create a cube 1. Create a cube
log to indicate the fail source model.
named A. named A.
ure and to guide you
2. Copy the transac 2. Delete the cube
on how to proceed.
tion data from B named B.
to A.
3. Delete the cube
named B.
When the parameter ENABLE_FIXED_CUBENAME has different values in the source and in the target system,
the model import is not performed and an error message appears in the transport log.
1.14.3.5 Working with Local Providers (Embedded only)
Local providers work in a similar way to the 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 only visible 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 (Embedded only) [page 148].
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
The 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 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.
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 the BEx Query Designer. Queries can be consumed
through the Business Planning and Consolidation Web client or the EPM add-in.
You can find the default query as follows:
1. Go to Library and choose New Input Form/Report.

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.
1.14.3.6 Working with Local Queries
A query is a Business Warehouse (BW) concept that refers to a multi-dimensional query used to analyze data.
A query is built on top of InfoProviders. By selecting and combining individual query components called
dimensions and measures or reusable query elements called restricted and calculated measures in a query,
you define how you want to evaluate the data from the selected InfoProvider. Input-enabled queries can also be
used for manual planning.
However, queries alone may not meet your needs, as they support only global BW InfoProviders. Therefore,
Business Planning and Consolidation contains functionality for generating local queries. A local query not only
supports global BW InfoProviders whose exposed data can be used as InfoProviders for the query, but also
supports the upload of local providers. In this way, you can merge your own local data with data from other
sources such as a global, centralized IT department.
 Note
Company B is a subsidiary of Company A in Germany. Company A wants to review the final plan data from
different countries. Assume that Company B’s financial personnel keep a private version of their finance
plan locally and hand in a slightly adjusted ‘official version’ to Company A. Also, to compare and adjust data
more conveniently, they would like to see these different versions in one query. This can be done by
leveraging local queries. Local queries allow the locally planned data and global data to be managed in the
same place at the same time, thus enabling local department to design planning and analysis reports with
much more flexibility while not having to learn the underlying BW modeling concept.
Similar to workspace queries in BW, a local query in Business Planning and Consolidation is visible only inside
the current environment or workspace, and not exposed to the entire BW system. Therefore, only users with
access to your environment can view and edit local queries. You can go to the Business Planning and
Consolidation web client and choose the Local Query feature to create and design local queries. On the query
design page, the following components of a local query are displayed:
● Global Filter
The selections in the filter apply to the query in its entirety, restricting dimension members of the query.
When defining the filter, you can click the button and select dimension members from one or more
dimensions. All the InfoProvider data is aggregated according to the filter selections of the query.
● Dimensions
In the query definition, you assign the dimensions in the InfoProvider to the rows, columns, and free
characteristics in the query. With this selection, you specify the data areas of the InfoProvider through
which you want to navigate. The alignment of row and column content determines the initial view for the
query.
● Query Properties
Properties display information about the InfoProvider and show when and by whom the local query was
last changed.
● Measures
You can create a new measure or a planning-enabled measure. When creating a new measure, existing
transaction data can be further modified by manually entering or by uploading an xlsx, xlsm, or csv file or a
local provider.
Later you can drag and drop the newly created measures and planning-enabled measures as well as
existing measures in the query either to a row or a column. Then you define which numerical data is
displayed by restriction or formula:
○ Restrictions: restrict the measure value based on a combination of dimensions if necessary.
○ Formulas: calculations based on the measures or other structure members contained in the
InfoProvider. When editing a formula, you can get all the operands and operators available for the
formula under the Formula Editor box.
Related Information
Create a Local Query based on an Existing Central Query [page 164]

Create a Local Query based on a Model [page 165]
1.14.3.6.1 Create a Local Query based on an Existing Central

Query
Prerequisites
To create and design local queries, make sure that the following Internet connection services are activated in
the Business Warehouse back-end system using transaction SICF:
● /sap/bc/ui5_ui5/sap/rsl_wqd
● /sap/bw/modelling
Ensure you have a role with the authorization object S_RS_WSPAC with the activity value 68 assigned to you.
For example, the role SAP_BW_WORKSPACE_DESIGNER contains this S_RS_WSPAC authorization object.
Therefore, any user assigned this role would be able to design local queries.
Allow the creation of local queries in the Planning and Consolidation web client. Go to the model on which you
want to create a local query and set the option Allow Local Query to On. Then select Local Query Basis for the
relevant InfoProviders you want to use for designing local queries.
Procedure
1. Navigate to Modeling Local Queries .

2. On the Local Queries page, click New.
3. Choose Create Local Query with Query, select a model based on which central queries are already created,
then choose your desired central query.
The new query design page displays the existing layout of the central query.
4. Right-click on Measures in the left-side panel to add new measures or new planning-enabled measures.
Planning-enabled measures allows data input.
5. Drag and drop the newly created measure from the Measures list to the row or column where the central
query’s measures lie. You can also directly add new measures by right-clicking Measures in the rows or
columns and choosing Add Member.
6. Double-click the measure or right-click the measure to restrict the measure’s value and apply calculation
formulas if necessary.
7. Drag and drop other dimensions to the columns, rows, or free zones.
8. Save the query and carry out further tasks such as planning by directly choosing the report or input form
or by using SAP BusinessObjects Analysis, edition for Microsoft Office.
1.14.3.6.2 Create a Local Query based on a Model
Prerequisites
To create and design local queries, make sure that the following Internet connection services are activated in
the Business Warehouse back-end system using transaction SICF:
● /sap/bc/ui5_ui5/sap/rsl_wqd
● /sap/bw/modelling
Ensure you have a role with the authorization object S_RS_WSPAC with the activity value 68 assigned to you.
For example, the role SAP_BW_WORKSPACE_DESIGNER contains this S_RS_WSPAC authorization object.
Therefore, any user assigned this role would be able to design local queries.
Allow the creation of local queries in the Planning and Consolidation web client. Go to the model on which you
want to create a local query and set the option Allow Local Query to On. Then select Local Query Basis for the
relevant InfoProviders you want to use for designing local queries.
Procedure
1. Navigate to Modeling Local Queries .

2. On the Local Queries page, click New.
3. Choose Create Query with Model and select a model. Make sure that relevant InfoProviders are contained
in this model.
4. Click OK to display the query design page.
5. Right-click on Measures in the left-side panel to add new measures or new planning-enabled measures.
Planning-enabled measures allows data input.
6. Drag and drop existing measures and newly created measures from the measure list either to a row or a
column.
7. Double-click or right-click the measure and choose Edit to restrict the measure’s value and apply
calculation formulas if necessary.
If you create the local query based on a CompositeProvider, you can also restrict the measure to a certain
InfoProvider to define where the key figure will be written back.
8. Save the query and carry out further tasks such as planning by directly choosing the report or input form
or by using SAP BusinessObjects Analysis, edition for Microsoft Office.
1.14.4 Consolidation (Standard only)
This section focuses on the dimension properties and relevant settings required for the various tasks that are
required to successfully perform legal consolidation using SAP Business Planning and Consolidation.
The following tasks are described:
● How to set up currency translations, intercompany eliminations, copy opening tasks, and other business
rules using the business rules tables and script logic in Planning and Consolidation Administration
● How to set up the Data Manager package required to run the legal consolidation tasks in SAP Business
EPM solutions, add-in for Microsoft Office
Business rules provide the mathematical foundation for SAP Business Planning and Consolidation models,
allowing users to manage both management and legal consolidation reporting. This section also discusses the
configuration of business rules.
The finance department of a corporation uses legal consolidation to consolidate numbers from its subsidiaries
and produce consolidated financial statements of this group of legal entities at the end of a financial period.
Features
You can 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
● Validate data
● 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 the 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 consolidation (legal) environment and set the necessary parameters; see Create an
Environment (Standard only) [page 167].
● Set up master data (dimensions); see Master Data (Dimensions) Setup (Standard only) [page 179].
● Create the model; see Create or Modify the Model (Standard only) [page 180].
● Enable business rules; see Business Rule Setting (Standard only) [page 184].
● Update rate data and ownership data; see Execute Consolidation Task (Standard only) [page 185] and
Loading Data (Standard only) [page 187].
● Set the work status; see Work Status Setup [page 344].
● Set the journal template and validation criteria; see Journal Definition and Validation Setting (Standard
only) [page 188].
1.14.4.1 Create an Environment (Standard only)
Use this to set up an environment for legal consolidation.
Use
If you already 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 (for example, account) with your
consolidation environment.
1.14.4.2 Dimension Setup in Dimension Library (Standard

only)
Set up dimensions for legal consolidation.
Features
For the consolidation model, the dimensions listed in the tables below are mandatory requirements. Therefore,
it is recommended that you verify that all the dimensions are available in the dimension library of your
consolidation environment created from EnvironmentShell.
 Note
Whereas the dimension names can be chosen as desired, it is mandatory that the dimension types match
with the ones described below for the corresponding models.
The MAIN legal consolidation model requires the following dimensions:
Dimension Description
ACCOUNT Members of this dimension are, for example, Revenue or Salaries.
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 ver
sions, such as BudgetV1, and BudgetV2.
Audit Used in the business rules of a reporting consolidation model to seg

regate input data.
Subtable (Flow) Breaks down account activity or flow into subunits.
Entity Contains the business units that are used to drive the business proc
ess.
Depending on your model design, the Entity type can be for example
an operating unit, a cost center, or a geographic entity.
Intco Contains the intercompany codes for the entities.
Time Contains the periods for which you store data.
Currency The currency type dimension is required if the customer reports on

local currency and translated values.
Groups The group represents the relationship of entities and consolidation

scopes for a given consolidation result.
The RATE model containing exchange rates requires the following dimensions:
ACCOUNT Members of this dimension are used to detail the different types of
rate (for example, Average or End-of-period).
sions, such as BudgetV1, and BudgetV2.
Entity This is used to store multiple tables of rates, if desired; otherwise, the
R_Entity dimension may just be limited to one dummy member, typi
cally named GLOBAL.
Time Contains the time periods for which you store data.
Currency This dimension is used to store each applicable local currency.
 Note
Time and Category dimensions must be shared by all the models involved in consolidation.
The OWNERSHIP model storing the ownership details requires the following dimensions:
ACCOUNT Members of this dimension are for example METHOD (consolidation

method),POWN (ownership percentage), and PCON (control percent
age).
sions, such as BudgetV1 and BudgetV2.
Entity Contains the business units that are used to drive the business proc
ess. Depending on your model design, the Entity type can be for ex
ample an operating unit, a cost center, or a geographic entity.
Groups The group represents the relationship of entities and consolidation

scopes for a given consolidation result.
The following table indicates the dimensions required in various models:
Name Type MAIN OWNERSHIP RATE
Account (Consolida A X
tion)
Account (Ownership) A X
Account (Rate) A X
Flow S X
Category C X X X
Entity E X X
Entity (Rate) E X
Intercompany I X X
Time T X X X
Group G X X
Name Type MAIN OWNERSHIP RATE
InputCurrency R X
Audit D X
Currency R X
Activities
● Create a new dimension

1. In the home page, go to Administration and under the Dimensions and Models section, choose
Dimensions.
2. Click New.
3. Choose a unique ID, provide a description, and select the dimension type.
1.14.4.3 Create or Modify Dimension Properties (Standard

only)
When you create a new dimension, all the required properties are created automatically based on the
dimension type. However, to ensure the correct operation of consolidation and related processes (such as
currency translation, simulation, and eliminations and adjustments), additional dimension properties are
needed to ensure the filtering, flagging, and calculation of the target data. You should ensure that these
properties are maintained with the expected values for the consolidation process according to the business
requirements.
Features
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 model
The following table details the 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.
 Note
Several DIMLIST properties can be
used for one dimension.
RATETYPE 10 Used by the currency translation busi

ness rules. This property determines
the business rules to be applied when
translating any given account from local
currency to reporting or group cur
rency. A value is optional.
The following special values of RATE

TYPE are possible:
● blank
All accounts are translated with a
factor of 1.
● NOTRANS
Accounts are not translated.
ELIMACC 20 Used in the elimination process and

represents the difference account to
which the accounts to be eliminated are
posted.
 Note
This property is used only with the
US Eliminations business rule.
Category Dimensions
All models require a category type dimension. The properties required in this dimension as described in the
following table 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 cube, 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 cube, simulated translations are stored in additional
members of the Category dimension. These categories have non-blank values for one or more of the following
properties:
Any dimension that is assigned the type C is considered to be a Category dimension.
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 (-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 (such as

DEC, or FEB) or a relative value (-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:
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
the last period of the year.
● Not blank
Contains the period from which to
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 only works if you have a base level value
of data source type A.
● Optional for the currency business rules. It is not used in the business rules for currency translation.
● 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:
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
Used for top adjustments of con
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
The following table details the entity dimension properties:
Description of appropriate property

Property Name Length value
CURRENCY 20 Local currency used by the entity.
This currency must be defined in the In

putCurrency dimension.
FX_TYPE 20 Assigns a set of translation rules to an

entity. Different entities can use differ
ent sets of rules.
Optional.
OWNER 60 Used for work status.
Optional.
Intercompany Dimension
The Intercompany dimension ( I) defines the intercompany codes for entities in consolidation and ownership
models.
Currency
The currency type dimension is required if the customer reports on local currency and translated values. You
can use the currency type dimension for both currency and groups, or you can split it into a Group dimension
(type G) and a pure Currency dimension (type R) to allow reporting in multiple group currencies.
The required properties for a separate group dimension are the following:
Dimension Property Name Length Description of Appropriate Property Value
G GROUP_CURRENCY 20 Can be any valid reporting currency. Used for cur

rency translation.
This property can only be used on CURRENCY

members with the property CURRENCY_TYPE of G
and, in this case, it must contain a valid ID from the
CURRENCY dimension with the property CUR
RENCY_TYPE of R.
G PARENT_GROUP 20 Must be a valid ID from the Groups dimension.
If you want to do the consolidation by level, you

must indicate here the higher level from the group.
If you want to use this property to define the hierar

chy, enter the same code as the ID for your top
group. If this property is blank, the ownership-based
hierarchy from the OWNERSHIP model is used.
G ENTITY 20 Blank or a valid Entity ID.
This is used to define the link between the Group

and the Entity or to indicate the Entity where the ag
gregation should be stored.
If this property is filled with valid ID, and the prop

erty STEntityORE_ENTITY is set to Y, the results of
the currency translation for the current Group are
also copied into this Entity.
G STORE_GROUP_CURR 1 Used for currency translation.
● Y
By default the results of the translation into a
Group currency are written in both the Group
member and in the Currency member of the
currency dimension.
● N (or blank)
If only the Group member 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 multilevel conversion
of groups.
This property can only take the values Y, E, or N

(blank).
G and R CURRENCY_TYPE 1 ● L - local currency

● R - reporting currency
● T - transaction currency
● G - group
Used for the currency translation.
FIRST_CONS_DATE 10 ● Blank
Management model.
● YYYYMMM
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 the 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 the model, it can be used 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_TYPE 12 ● OPENING - opening

● TRANSLOPE - change diff on open
ing
● ALLOCINC - allocation
● MERGER - merger
● INCOME - net income from the pe
riod
● CHANGE - variation.
● TRANSFER - transfer
● TRANSFLOW - translation change
on flow
● 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
Activities
● To manage dimension members and their property values
1. In the home page, go to Administration and under the Dimensions and Models section, choose Dimensions.
2. Select the row containing the dimension member required:
○ to manage dimension members - click Edit Members
○ to manage the property values - click Edit Structure
1.14.4.4 Master Data (Dimensions) Setup (Standard only)
Create the model for legal consolidation.
Features
The consolidation engine leverages the following models to retrieve the information necessary to perform its
calculations:
● The Legal or MAIN model

This consolidation type model is the model within which the respective consolidation entries for items,
such as currency conversion or intercompany eliminations, are written.
● The RATE model
The currency conversion process uses a RATE model to look up the appropriate exchange rates for each
relevant currency.
● The OWNERSHIP model
The consolidation process uses an OWNERSHIP model, to store the definitions of each consolidation
parameter. In particular, such definitions may include:
○ The list of companies being consolidated in each group
○ The consolidation method used in each case
○ The consolidation percentage for each case
○ The ownership percentage (how much of each is owned by the group)
○ The control percentage (how much of each is controlled by the group)
The MAIN, RATE, and OWNERSHIP models can be named as desired. Within the same environment, multiple
MAIN models may exist, each one pointing to its own RATE and OWNERSHIP models. Multiple MAIN models
can also share the same RATE or OWNERSHIP models, if appropriate.
The RATE model, associated with a given model, is defined as an option upon the creation of a new MAIN
model in Planning and Consolidation Administration.
The OWNERSHIP model, associated with a given model, is defined as an option upon creation of a new
Consolidation model in Planning and Consolidation Administration.
If this value does not exist, the consolidation procedure searches for a model named OWNERSHIP.
Each one of the above models must contain some required dimensions, while some other dimensions are
optional. For more information, see Dimension Setup in Dimension Library (Standard only) [page 167].
The required and optional dimensions are based on the standards used in the business rules. Other dimensions
can coexist in a reporting model but do not impact the business rule function.
All models must contain the following four required dimensions: ENTITY, CATEGORY, TIME, and ACCOUNT.
They can be renamed as desired.
The CATEGORY and TIME dimensions can be the same across the MAIN, RATE, and OWNERSHIP models.
Alternatively, they must contain the appropriate matching members.
The ENTITY dimension of the MAIN model can be the same as that used in the OWNERSHIP model or it must
contain the appropriate matching members if different.
The GROUP dimension used must be the same in the OWNERSHIP model and the MAIN model. Here are some
of the common member requirements between these dimensions for the Legal consolidation environment
setup described below:
In most cases, it is recommended that you use the same dimensions across models as it is easier to maintain.
 Note
The RATE model is delivered with EnvironmentShell. Most dimension properties required for the
consolidation setup are delivered with the dimensions. However, it is recommended that you verify this
before proceeding further.
1.14.4.5 Create or Modify the Model (Standard only)
When working with a model, the model type tells the system which properties to associate with the model.
Features
In SAP Business Planning and Consolidation, a model is either Reporting or Non-reporting. Non-reporting
models support reporting models by holding data such as prices or rate information.
Following are the three types of reporting model in SAP Business Planning and Consolidation:
● Financial
A financial reporting model performs management consolidation functions, such as currency conversions,
and intercompany eliminations.
This model must reference a rate-type model.
● Consolidation
A consolidation reporting model performs legal consolidations. This is similar to a financial model, but with
legal consolidation rules instead of management.
This model must reference an ownership-type model and a rate-type model.
● Generic
A generic reporting model has no special requirements (other than to include a minimum of the four
required dimensions).
The non-reporting types of models can be associated with only the financial and consolidation type models.
Following are the two types of non-reporting model:
● Rate
This model stores exchange rates that support currency conversions for reporting models. The model
must include a currency-type dimension to store the exchange rates by currency.
● Ownership
An ownership model stores information such as the consolidation methods, ownership percentages, and
group roll-up information used for legal consolidation.
Within the same environment, multiple reporting models may exist, each one pointing to its own RATE and
OWNERSHIP models. Multiple reporting models can also share the same RATE or OWNERSHIP models, if
appropriate.
The RATE or OWNERSHIP model associated with a given reporting model is defined when a new consolidation
type model is created.
 Note
You can report on non-reporting model data, but you cannot assign work status codes to the data. In
addition, you cannot define business rules to these model types. All models require at least the four main
dimension types: Entity, Account, Time, and Category.
In SAP Business Planning and Consolidation, a consolidation scenario requires at least the following models:
● Legal or MAIN
This is the main model containing all financial data. All consolidation postings such as eliminations, and
minority interest calculations are posted in this model.
● OWNERSHIP
The OWNERSHIP model manages the organization structure and ownership percentages.
● RATE
This contains all currency exchange rates for the different rate types such as average, and sport rate.
Currency translation can run on any type of reporting model. Currency conversion applies to both financial
and legal consolidation models to which a corresponding RATE model has been referenced. The reporting
model must contain a currency (type R) dimension.
RATE Model
A rate model is a supporting model for financial and consolidation reporting models. It is used to store
exchange rates that support currency conversion in consolidation models. EnvironmentShell comes with a
RATE model, so you can leverage this by just modifying the Category dimension from Category to C_Category.
The time dimension must be identical to the dimension used by the models using the RATE model to store their
foreign currency exchange rates and must have the same category member IDs.
This model must include a currency dimension detailing the exchange rates by each input currency. The
currency dimension in a rate model does not need to have the REPORTING property. The currency conversion
process makes use of a RATE model, where the appropriate exchange rates are searched for each relevant
currency. This cube can be named as desired.
 Note
The master data (dimension) can be shared by any model within an environment.
The RATE model requires the following dimensions:
● Account (account dimension for the RATE model)

This details the different types of rate (Average, End-of-period, and so on). Account is specific to and used
only by a RATE model.
● Entity (entity dimension for the RATE model)
This stores multiple tables of rates, if required. Alternatively, the Entity dimension can be limited to one
dummy member, typically named GLOBAL. For example, if there is an entity C1000 for which a special
exchange rate needs to be applied, it is defined here and the special rates are applied.
Entity is specific to and used only by a RATE model.
● Currency
This dimension stores each applicable local currency.
● Time and Category
These dimensions can be shared by all or the models involved in consolidation.
OWNERSHIP Model
Any consolidation type model must refer to a RATE and an OWNERSHIP model. EnvironmentShell is delivered
only with PLANNING and RATE models. Therefore, the OWNERSHIP model needs to be created before you can
create the consolidation model. Refer to the model creation wizard to understand the steps of the creation
process.
The business rule process uses an ownership type model when calculating the ultimate ownership or during
the minority interest calculation. This model must be associated with a consolidation type model. The
OWNERSHIP model contains the values of each consolidation parameter. In particular, such definitions may
include:
● The list of companies being consolidated in each group

● The consolidation method for each company
● The consolidation percentage for each company
● Their ownership percentage (how much each company is owned by the group)
● The control percentage (how much each company is controlled by the group)
The OWNERSHIP model can be named as desired.
The OWNERSHIP model defines ownership details such as the consolidation scope, method, percentage of
shares owned by the holding company or groups.
For the OWNERSHIP model, the only dimension that is specific to the OWNERSHIP cube is the Ownership
Account that the consolidation engine uses to get the information listed above. To pass the information, several
required members need to be defined. The required members are as follows:
● Method defines consolidation method

● POWN defines the percentage of ownership
● PCON defines the percentage of consolidation
● PCTRL defines the percentage of control
Consolidation (MAIN) Model
Any consolidation type model must refer to a RATE and OWNERSHIP model.
Activities
Associate the desired RATE and OWNERSHIP models with the consolidation model and select all the
consolidation business rules that need to be implemented. You can select from the following list of business
rules:
Conversion of local currency data to the desired reporting currencies.
● Calculations
To calculate and store amounts which are required for purposes of account-based calculations.
Matching intercompany transactions
● US Eliminations
Specifically designed to address the posting of intercompany eliminations in simpler scenarios where a full
legal consolidation model is not required
● Carry Forward
Initialization of beginning balances when a new fiscal cycle starts
● Validation
Validation of input data
● Eliminations and Adjustments
Generation of all the 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.
Select only the desired dimensions required for legal consolidation and deselect any others.
Set dimensions to be included in the consolidation model and also set the secured dimension to control the
security through SAP Business Planning and Consolidation member access profiles.
Normally the Entity and Category dimensions are set as secured dimensions for member access control.
The Group dimension stores group currency, reporting currency and consolidation groups. The MAIN cube
must contain a CURRENCY dimension to store the translated amounts. The consolidation entries, as generated
by the consolidation process, are also stored by Group dimension.
Any additional dimension is optional in the MAIN cube, as far as the currency translation is concerned. For
consolidation purposes, however, there are some other requirements. These are described below:
● The model may have an Intercompany dimension.

● The model may have a FLOW dimension. This dimension is optional, but, if it exists, it can be used by the
following procedures:
○ The currency translation procedure details the changes in the balance sheet generated by fluctuations
in the exchange rates.
○ The consolidation procedure details the eliminations applied to the movements of the balance sheet
accounts.
● An Audit dimension may exist in the MAIN cube, but it is not required by the currency translation. If it
exists, however, the currency translation can recognize which members of the dimension should be
translated, and which ones should just be copied as is to the destination currency. However, this dimension
is required for the consolidation procedure to work.
Additional (user defined) dimensions can be added to the MAIN cube (such as product, market, or division), as
desired. The consolidation engine can recognize their existence and take them into account in the process, and
apply custom behavior to their members.
1.14.4.6 Business Rule Setting (Standard only)
SAP Business Planning and Consolidation delivers predefined functions to calculate and post amounts
required to support common accounting activities, such as currency translation as well as matching and
elimination of inter-unit balances.
Features
For each predefined data package and script logic, there are one or more Business Rule tables, in which a
business user can configure rules. The consolidation engine uses these rules to perform all the appropriate
calculations on a user-selectable region of data, and write the calculated results into the database
Business rules provide the flexibility for a business user to customize the delivered logical functions, to meet
specific business needs, without having to understand either scripting or programming.
To run these programs, use the Data Manager packages.
The following table lists the consolidation process tasks and the corresponding business rules:
Consolidation Task Process Chain Name Script Logic Files Name Business Rule Name
Balance carry forward /CPMB/OPENING_BA LAN COPY_OPENING.LGF Carry-forward rules

CES
Currency translation /CPMB/FX_RESTATM ENT FXTRANS.LGF Currency translation rules
Intercompany reconciliation /CPMB/ICDATA ICDATA.LGF No rules needed
Intercompany balance book /CPMB/ICBOOKING ICBOOKING.LGF Intercompany booking

ing
Legal consolidation /CPMB/LEGAL_CONS OLI CONSOLIDATION.LGF Eliminations and adjust

DATION ments and details
(elimination and adjustment)
Account calculation /CPMB/RUNCALCAC CALCACCOUNT.LGF Account-based calculation

COUNT
(cash flow function)
US widely used /CPMB/IC_ELIMINATI ON ICELIM.LGF US elimination
Intercompany elimination
For each process, the predefined Data Manager packages with their associated logic scripts and rule tables are
executed, performing the consolidation task according to the business rule customization. Any specific
business requirement needs to be configured in the corresponding business rule.
1.14.4.7 Execute Consolidation Task (Standard only)
Data Manager packages allow you to manage data within SAP Business Planning and Consolidation models
and dimensions.
Context
Data Manager packages are implemented as process chains and allow common data manipulation activities.
The packages that come with SAP Business Planning and Consolidation are designed to be dynamic so you do
not need to modify the packages for them to work with your models and dimensions.
The Financial packages that can be used for the consolidation process, apart from the Standard and
Administrative packages, are in the following table:
Process Chain Template Description Technical Name
Planning and Consolidation Default For Executes default formulas stored in /CPMB/DEFAULT_FORMULAS
mulas Logical your default.xls file.
Planning and Consolidation FX Restate Allows you to perform currency transla /CPMB/FX_RESTATMENT
ment tion. The package runs the FXTrans
logic.
Planning and Consolidation IC Elimina Allows you to perform intercompany /CPMB/IC_ELIMINATION

tion eliminations. The package runs the ICE
lim logic.
Planning and Consolidation: ICBooking Runs the ICBooking logic. /CPMB/ICBOOKING
Planning and Consolidation ICData Runs the ICData logic. /CPMB/ICDATA
Planning and Consolidation Legal Con Runs the LegalConsolidation logic. /CPMB/LEGAL_CONSOLIDATION
solidation
Planning and Consolidation Opening Runs the OpeningBalances logic. /CPMB/OPENING_BALANCES

Balances
Planning and Consolidation Run Cal Runs the CalcAccount logic. /CPMB/RUNCALCACCOUNT
cAccount
Planning and Consolidation Clear the Clears journal tables and creates an /CPMB/CLEAR_JOURNALS
Journal Tables output file.
Planning and Consolidation Export the Exports journal tables to an output file /CPMB/EXPORT_JOURNAL
Journal Tables
Planning and Consolidation Restore Allows you to load journal tables from a /CPMB/RESTORE_JOURNALS
Journal Tables file
Procedure
1. Add the Data Manager packages for a consolidation model:
For more information, see the SAP BusinessObjects EPM solutions, add-in for Microsoft Office help.
2. Create script logic files (LGF).
Script logic allows users to define formulas that perform calculations on SAP Business Planning and
Consolidation members and data.
You can create the following types of logic:
○ Dimension Member Formulas

○ Script logic
Each type has advantages and disadvantages. Logic is modelspecific and all script logic statements are
case-insensitive.
1. In the home page, go to Administration and under the Rules section choose Logic Scripts.
2. Select Scripts for CONSOLIDATION and click Open.
3. Click New.
4. Create an LGF file by using the script logic supported by SAP Business Planning and Consolidation.
 Note
The Logic File name must be identical to the string defined with the data package.
3. Maintain the business rule table.
SAP Business Planning and Consolidation delivers predefined functions designed to calculate and post
amounts required to support common accounting activities such as:
○ Currency translation
○ Matching and elimination of inter-unit balances.
To allow a customer the flexibility to customize these functions to meet specific requirements table-based
logic is used.
For each predefined function, there are one or more Business Rule tables, in which the business user can
configure rules such as:
○ What balances should be read in order to calculate an amount to be posted.

○ What are the posting rules for the calculated amount (meaning, to what account and data source is the
calculated amount posted).
Table-based logic (Business Rules) provides the flexibility for a customer to customize delivered functions
(logic), to meet specific business needs, without having to understand either scripting or programming.
The following Business Rule (table-based logic) functions are delivered with SAP Business Planning and
Consolidation:
Currency Translation Convert local currency data into the desired reporting cur
rencies
Account-based Calculations Calculate and store amounts, which are required for pur
poses of account-based calculations
Intercompany Bookings Match intercompany transactions
US Eliminations US eliminations
Specifically designed to address the posting of intercom

pany eliminations in simpler scenarios where a full legal
consolidation model is not required.
Carry-Forward Initialize the opening balances when a new fiscal cycle

starts
Eliminations and adjustments Generate all the consolidation entries for the desired
groups of entities (such as eliminations, adjustments, re
classifications, and minority calculations)
The procedure to maintain the business rules is as follows:

1. In the home page, go to Administration and under the Rules section choose Business Rules.
2. Select the CONSOLIDATION Model and click Add/Remove Rule Types in the toolbar.
3. In the Add/Remove Rule Types dialog box, select the rule types you require and click OK.
4. Click the business rule type under the CONSOLIDATION model in the table grid.
Alternately, select the row of the business rule and click Open in the toolbar.
5. In the Business Rule Editor, click New to create a new rule, or select an existing rule and click Edit in the
toolbar to modify the content of an existing rule according to business requirements.
1.14.4.8 Loading Data (Standard only)
Procedure
1. Load the exchange rate to the RATE model.
The RATE model stores the exchange rates for currency translation. There are several ways to upload the
data to the RATE model, such as using the Data Manager import package, or using dynamic templates to
send data from the input schedule. For more information, see Currency Translation Rule (Standard only)
[page 271].
2. Input ownership data and calculate ultimate ownership.
SAP Business Planning and Consolidation provides an ownership-based hierarchy editor in Consolidation
Central so you can update the OWNERSHIP model directly.
3. Load the financial data.
After loading the financial data, use an SAP Business Planning and Consolidation report to validate that the
numbers loaded reconcile with the numbers in the source system.
1.14.4.9 Journal Definition and Validation Setting (Standard
only)
Journals allow users to make adjustments to data in the database, typically as part of the month-end or
quarter-end process. During the review and analysis step, journals allow users to capture an audit trail of
changes and adjustments made to the database. The purpose of validation is to prevent incorrect records
being saved to the cube.
Features
Journal Template Definition
The primary requirement for journals is to track changes to data after the initial source data is input into the
model. For example, the general ledger information is loaded into the model through the Data Manager. The
model users can adjust this data and also track and report on the changes by, for example, amount, date, and
user. Once a journal template is created, neither the dimension nor the data in the model can be deleted from
the model.
For information about setting up journals and defining a journal template, see the related links below.
Validation Setting
Validations are designed to prevent incorrect cube intersections from being saved. You cannot get data into a
cube without going through the Write-Back module. Therefore, validations are implemented in write-back, to
ensure that invalid records cannot get into the cube from any source, including journals, Data Manager
packages, and manual data input. For example, a specified intercompany account with an empty Trading
Partner dimension is blocked from being written into the cube.
To customize validation, in the SAP ABAP system enter the transaction code UJ_VALIDATION to configure the
validation framework and customize the validation rules according to your business requirements. For more
information, see Breakdown Validation.
 Caution
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 through posted 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.
Related Information
Journal Administration [page 353]

Journal Template Creation [page 353]
Example of Journal Validation (Standard only) [page 189]
1.14.4.9.1 Example of Journal Validation (Standard only)
After loading general ledger data into a model using Data Manager, the processor should be able to review the
data and use journal entries to make adjustments if there is any correction or reclassification needed.
When journal entries are saved and posted, all adjustments to data can be tracked and reported on. For
example, it is possible to run reports on the changes by amount, date, user, and several other properties to
review and analyze.
Validations, on the other hand, are designed to prevent incorrect records from being saved to the cube. The
user controls what is deemed an incorrect record. An example of an incorrect record is one where you have
specified an intercompany account, but you have left the Trading Partner dimension empty.
Related Information
Journal Definition and Validation Setting (Standard only) [page 188]
1.14.5 Consolidation (Embedded only)
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 embedded type environment and set the necessary parameters. See Create an Embedded
Environment (Embedded only) [page 190].
● Create required InfoObjects and InfoProviders and maintain required InfoObject attributes on the Business
Warehouse backend. See Create InfoObjects and InfoProviders (Embedded only) [page 191] and Maintain
InfoObject Attributes (Embedded only) [page 195].
● Create the consolidation model. See Create or Modify a Consolidation Model (Embedded only) [page 206].
● Enable business rules. See Business Rules Management (Embedded only) [page 289].
● Make sure the EXCHANGE RATE InfoProvider and OWNERSHIP InfoProvider are maintained in Business
Warehouse. See Create or Modify a Consolidation Model (Embedded only) [page 206].
● Define tasks order in task sequences. See Set Task Sequence (Embedded only) [page 206].
● Set the work status, which is optional.
● Set the journal template and validation criteria. See Journal Administration [page 353].
1.14.5.1 Create an Embedded Environment (Embedded only)
Use this to set up an embedded environment for legal consolidation.
If you already 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.
1.14.5.2 Set up a Consolidation Model (Embedded only)
Since SAP Business Planning and Consolidation in the embedded configuration 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 (Embedded only) [page 191].
2. Maintain the InfoObjects with required attributes. See Maintain InfoObject Attributes (Embedded only)
[page 195].
3. Create required InfoCubes (InfoProviders) and input relevant InfoObjects. See Create InfoObjects and
InfoProviders (Embedded only) [page 191].
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 (Embedded only) [page 206].
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.
1.14.5.2.1 Create InfoObjects and InfoProviders (Embedded

only)
Follow these guidelines to create InfoObjects and InfoProviders that can be used by the Consolidation engine of
In SAP Business Planning and Consolidation in the embedded configuration, 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 InfoProviders, you must make sure they contain inputable InfoProviders, such as
cube or CompositeProviders that contain cubes.
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
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.
Currency (CONSOLIDATION) The currency type dimension is required if the customer re
ports on local currency and translated values.
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 √
Business Planning
and Consolidation Di
mension Dimension Type CONSOLIDATION OWNERSHIP RATE
Category C √ √ √
Entity (Consolidation) E √ √
Entity (Rate) E √
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 BW modeling tools.
2. Refer to the required Business Planning and Consolidation dimensions and create corresponding
InfoObjects for each.
3. Maintain the required attributes of the InfoObjects. See Maintain InfoObject Attributes (Embedded only)
[page 195].
4. Create four InfoCubes (InfoProviders) in the type of CONSOLIDATION, OWNERSHIP, RATE, and SOURCE.
5. Input corresponding InfoObjects to each InfoCube (InfoProvider).
6. Create aggregation levels based on the InfoCubes (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 (Embedded only) [page 206].
1.14.5.2.2 Maintain InfoObject Attributes (Embedded only)
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
The following table details the account dimension properties:
Account Dimension Properties
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 Used by the currency translation busi

ness rules. This property determines
the business rules to be applied when
translating any given account from local
currency to reporting or group cur
rency. A value is optional. The following
special values of RATETYPE are possi
ble:
● blank - All accounts are translated

with a factor of 1.
● NOTRANS - Accounts are not
translated.
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 cube, 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 cube, 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
the year before the current year.
● Not blank
Contains the year from which to
be an absolute or a relative
amount.
OPENING_PERIOD 10 ● Blank
the last period of the year.
● Not blank
Contains the period from which to
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
¡aæI¤[{xÒ²|KÙµQ&L`»¯àð÷Œ>í "N'%®ˇ)addyðaÀAº“u*
?ö“ÌÛ?}`¡łBPÛš
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
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 userspecified 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 of ENTITY di
mension in the model.
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
● YYYYMMM
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 ENABLEJRN, see Limits to Dimension Members for Journal Entries [page 358].
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 Business Warehouse
using BW modeling tools.
● To make sure the dimension master data is correct, you can maintain the master data either in Business
Warehouse using 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 (Embedded only) [page
142] 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 (Embedded only) [page
206].
1.14.5.2.3 Create or Modify a Consolidation Model
(Embedded only)
In the embedded configuration of SAP Business Planning and Consolidation, 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 home page, go to Administration and choose 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. Then go back to the Model Creation page. In Advanced Settings, select superior compounding members for
each dimension member. For Account and Time type dimension members, you must specify fixed superior
compounding dimension members. For others, this value is optional. Once a fixed superior compounding
member is selected, users 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.
1.14.5.3 Set Task Sequence (Embedded only)
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: ;
 Note
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 userdefined
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 taskspecific 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.
 Note
There are some special settings for dimension members defined in the Other Dimension Filter field of the
US Elimination type task:
● If you do not specify members for the group dimension (G type), then the US Elimination will both
execute on G_NONE and the member you selected and its subgroup members in Consolidation
Monitor.
If you define the group member as G_NONE, US Elimination will be executed on G_NONE no matter
what group type dimension member you select in Consolidation Monitor.
If you do not specify members for the currency dimension (R type) in the Other Dimension Filter, the
US Elimination will execute on group currency and LC in Consolidation Monitor.
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 .
1.14.5.4 Preparations for Executing Consolidation Tasks

(Embedded only)
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:
1. Go to RSA1, open the BI Content tab, then install the InfoObjects (IOBJ) /CPMB/RULE and /CPMB/RENT.
2. Within RSA1 on the BI Content tab, install the planning function types (PLST) /CPMB/LAUNCH_LOGIC, /
CPMB/WRITE_BACK and /CPMB/READ_CTRL_DATA.
For detailed steps, refer to the section in the Installation Guide.
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 (Embedded only) [page 289].
1.14.5.5 Load Data (Embedded only)
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 the 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.
1.14.6 Rules
Perform data calculations using business rules and logic.
Use
You can perform calculations on your data using the following methods:
● Business rules, in both the embedded and standard configurations of Business Planning and Consolidation
Business rules are parameter-driven functions within models for calculating and posting monetary
amounts in support of common accounting activities.
● Logic, in the standard configuration of Business Planning and Consolidation
With logic, you define formulas that perform calculations on dimension members and data.
1.14.6.1 Member Formulas (Standard only)
Use
Member formulas allow you to create and execute formulas and calculations on dimension members.
Prerequisites
The Enable Member Formulas option is selected for the dimension to which you are applying the member
formula. See Dimension Properties [page 124].
Features
Use the following guidelines when implementing formulas:
● The system calculates formulas at retrieval time. Formulas can slow retrieval performance if used
incorrectly.
● Implement member formulas only for members that need calculating after aggregations, such as ratios.
Do not use formulas on members that need to aggregate.
● Use formulas only for ratios that need to be calculated at both the base and parent level. If the resulting
value is aggregated to the parent, use logic scripts to write the results to the database.
You cannot reference MDX functions, also known as userdefined functions, from a library file.
For information about restrictions pertaining to member formulas, see 1356081 .
Activities
You can view the member formulas added to a dimension in the administration panel, by choosing Member
Formulas, under the Rules section, and then choosing the name of a dimension.
You can add a formula to a dimension, as well as edit and delete a formula assigned to a dimension.
1.14.6.1.1 MDX Formula Syntax (Standard only)
Use
The basis for a dimension and advanced rule formulas is the multi-dimensional expression language called
MDX.
Features
You can use the following features of MDX formula syntax:
Syntax basics
● You can write the dimension ID using both uppercase and lowercase letters case, and the member ID
should be the identical case of the member.
● You must enclose all member IDs in [square brackets].
● You must fully-qualify all member IDs, preceded by the names of their related dimension enclosed in
square brackets, unless the dimension is ACCOUNT, in which case you may omit the dimension name.
MDX syntax exceptions
The following are exceptions to MDX syntax:
● Replace the keyword AS with an equal (=) sign.

● Do not use single quotes around expressions.
Note that the following structure is the normal syntax for calculated members required by MDX queries:
{member} = {expression}[, solve_order = n]
The only exceptions are the equal sign (=) in place of the “AS” keyword and the lack of single quotes around the
expression.
More Information
For examples of simple MDX formulas that can be used in the Formula column for an account, see Simple Rule
Formula Examples [page 211].
For examples of movement calculations and allocating expenses based on entity type, see Advanced Rule
Formula Examples [page 213].
1.14.6.1.1.1 Simple Rule Formula Examples (Standard only)
Use
The following are examples of simple MDX formulas that can be used in the Formula column for an account:
Features
Task Syntax and Example
Adding two accounts Syntax:
[DIMENSION].[ACCOUNT1] + [DIMENSION].[ACCOUNT2]
 Example
PreTax Income:
[ACCOUNT].[OPERATING INCOME] + [ACCOUNT].

[OTHEREXP].
Task Syntax and Example
Adding a range of accounts Syntax:
[DIMENSION].[ACCOUNT1]:[DIMENSION].[ACCOUNT2]
 Example
Total Personnel Exp:
SUM([ACCOUNT].[SALARIES]:[ACCOUNT].[COMMISSION])
Calculating a percentage Syntax:
[DIMENSION].[ACCOUNT1] / [DIMENSION].[ACCOUNT2]
or (to prevent division by zero):
IIF([DIMENSION].[ACCOUNT1] = 0, NULL, [DIMENSION].

[ACCOUNT2]/[DIMENSION].[ACCOUNT1])
 Example
Gross Margin Pct:
IIF([ACCOUNT].[REVENUE] = 0, NULL, [ACCOUNT].

[GROSS MARGIN]/[ACCOUNT].[REVENUE])
Multiplying by a factor Syntax:
[DIMENSION].[ACCOUNT1]*[DIMENSION].[ACCOUNT2]
 Example
Taxes:
[ACCOUNT].[PRETAX INCOME] * -0.35
Calculating a YTD value Syntax:
[DIMENSION].[ACCOUNT1],[MEASURES].[YTD]
 Example
Current Year Net Income:
([ACCOUNT].[NET INCOME], [MEASURES].[YTD])
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and
are not intended to be used in a productive system environment. The Code is only intended to better explain and
visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and
completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of
the Code, except if such damages were caused by SAP intentionally or by its gross negligence.
1.14.6.1.1.2 Advanced Rule Formula Examples (Standard only)
Use
Advanced rule formulas include movement calculations and expense allocation based on entity type.
Features
You can use the following features of advanced rule formulas:
Movement calculations
Movement calculations define the copying or movement of data from one time period to another. In the
formula examples below, [ AccRec] is the accounts receivable account, and [ AccPay] is the accounts payable
account.
 Example
Account Description Formula
Mvmt Acc Rec Movement in Ac IIF([TIME].CURRENTMEMBER.PROPERTIES("CALC")="N",

counts Receivable [ACCOUNT].[ACCREC] - ([ACCOUNT].[ACCREC],
[TIME].PREVMEMBER),
SUM(DESCENDANTS([TIME].CURRENTMEMBER, 20, LEAVES)))
With the formula, you are checking whether the current TIME member is
parent or not by checking the property CALC = NO. If it is not a parent, then
we take the current TIME member's Account Receivables (ACCREC) and
subtract the previous month's Account Receivables. If the current TIME
member is parent, then you simply sum up all of the children.
Mvmt Movement in In IIF([TIME].CURRENTMEMBER.CHILDREN.COUNT=0,

Inventory ventory [ACCOUNT].[INVENTORY] - ([ACCOUNT].[INVENTORY],
[TIME].PREVMEMBER),
The formula checks inventory.
Mvmt Acc Pay Movement in Ac IIF([TIME].CURRENTMEMBER.CHILDREN.COUNT=0,

counts Payable [ACCOUNT].[ACCPAY] - ([ACCOUNT].[ACCPAY],
[TIME].PREVMEMBER),
Mvmt Work Cap Movement in Work SUM([ACCOUNT].[MVMT ACC REC]:[ACCOUNT].[MVMT ACC

ing Capital PAY])
Allocating expenses based on entity type
The following examples assume there is an Entity property named Function. If an entity has the function SM,
the Total Department Expense is allocated to the S&M Exp account. If an entity has the function RD, the Total
Department Expense is allocated to the R&D Exp account. If an entity has the function CORP, the Total
Department Expense is allocated to the G&A Exp account.
 Example
Account Description Formula
S&M Exp Sales & Marketing Expense IIF([ENTITY].CURRENTMEMBER.PROPERTIES("CALC"

)="N",
IIF([ENTITY].CURRENTMEMBER.PROPERTIES( FUNCTIO
N) = SM, [ACCOUNT].[TOTAL DEPT EXP], NULL),
SUM(DESCENDANTS([ENTITY].CURRENTMEMBER,
[ENTITY].[LEV1], LEAVES)))
You first check if the current ENTITY member is parent or not.

Then, you read the property FUNCTION of the current ENTITY
member to see whether it is "SM" or not. If it is "SM", then, you are
taking the Total Department Expense as a Sales & Marketing ex
pense. Otherwise, it will be assigned with zero. If current ENTITY is
parent, a sum of all children appears.
R&D Exp R&D Expense IIF([ENTITY].CURRENTMEMBER.PROPERTIES("CALC"

)="N",
N) = RD, [ACCOUNT].[TOTAL DEPT EXP], NULL),
In this formula, you are taking the "RD" values of FUNCTION prop
erty.
G&A Exp G&A Expense IF([ENTITY].CURRENTMEMBER.PROPERTIES("CALC")=

"N",
N) = CORP, [ACCOUNT].[TOTAL DEPT EXP], NULL),
1.14.6.1.1.3 Nested Formulas (Standard only)
In a nested formula, a given part of that formula is calculated by another formula.
The functionality described in this topic applies only to systems based on SAP HANA, which enhances
capabilities and improves performance of SAP Business Planning and Consolidation in a standard
configuration. If you are not using an SAP HANA-based system, disregard the information in this topic.
Prerequisites
You must have the SAP HANA Component for Business Planning and Consolidation HANABPCSP05 installed on
your system.
Use
You can create a nested formula in which the different parts of that formula are calculated by other formulas.
 Example
A=B+C
B=D-6
C=F*E
In the example above, the formula A is calculated by B and C. In turn B and C are also calculated by formulas.
Nested formulas are only supported by the HANA MDX engine. The HANA MDX engine significantly improves
the performance when executing complex calculations on large amounts of data.
1.14.6.2 Script Logic (Standard only)
Use
Script logic is a feature that allows you to create files called logic scripts containing instructions for performing
calculations on planning and consolidation data.
Features
You can perform logic calculations on base level members only. In addition, logic is specific to each model.
Business Planning and Consolidation provides a library of MDX formulas, and the EnvironmentShell sample
environment contains a number of logic functions.
 Note
Logic keywords are not case-sensitive. However, all environment, model, dimension, and member names in
K2 are case-sensitive.
You have the following two files for each piece of script logic you create:
● An .LGF file, which is an ASCII file you create and edit when setting up logic calculations. You access
the .LGF file through the logic editor.
● An .LGX file, which is the compiled logic file created by the system when you validate and save your logic.
This is an executable version of the .LGF file that is not stored in Business Planning and Consolidation.
Default logic is a special logic statement that is executed on every writeback to a model. All logic in
Default.LGF is run after data sends. Data is first committed to the model and then, Default.LGF is run on
model data. Having all of your logic in the Default.LGF logic file might become unmanageable. Therefore you
can create other logic files, such as FXTrans.LGF for foreign currency translation and ICElim.LGF for
intercompany eliminations. Your default logic can contain an INCLUDE statement to execute specific logic in
real-time, such as currency translation if desired, rather than having to run a separate batch process.
You access logic files from the Script Logic subdirectory within the hierarchy of a model.
Logic Library
Business Planning and Consolidation has a library of standard logic functions available for your use. The file
has the extension .LGF, which can be called at validation by using the INCLUDE function in your logic file. The
logic module scans the library file for the appropriate formulas to use based on the information in the .LGF file.
The following are examples of logic delivered with Business Planning and Consolidation:
● Allocation.lgf: runs an allocation

● Calcaccount.lgf: used to prepare Cash Flow; runs an Account Calculation business rule
● Consolidation.lgf: used to run a Legal Consolidation business rule
● Copy_Opening.lgf: used to run a Balance Carry Forward business rule
● FX_Trans.lgf: used to run currency conversion
● ICBooking.lgf: used for running Intercompany reconciliation and difference posting
● ICData.lgf: used to run Intercompany reconciliation
● ICElim.lgf: used to run Intercompany reconciliation
● MDXlib.lgf: library of MDX financial functions
● System_Constants.lgf: stores constant values for use within script logic. See the System Constants File
section that follows for more information.
● System_Library.lgf: includes basic examples of a set of keywords
● Validation.lgf: used for running a Validation rule
System Constants File
The system constants file is the logic file that maps your dimension names for a model to the standard
Business Planning and Consolidation logic. By updating the dimension constants file with your dimensions, you
avoid having to change or rewrite any of the standard functions that are included with Business Planning and
Consolidation.
The system constants file is located in the \\root\Webfolders\ <Environment>\systemlibrary
\logiclibrary folder. You can edit this file using download and upload functions from transaction UJFS in
the ABAP interface.
Running Script Logic
Script logic can be automatically invoked each time the system sends data to the database. Instructions in the
default logic file are executed immediately after data is sent and you can see the results immediately. Script
logic can be run from Data Manager for batch processing of formulas. Using Data Manager to execute Logic
module formulas is useful for calculations that do not need to be executed immediately. For example, you may
decide to wait until all data has been entered in the local currency before generating the translated amounts in
reporting currencies.
Activities
From the Planning and Consolidation Administration screen, you can view all logic scripts for a model by
choosing Logic Scripts under the Rules section. After that select a model and choose Open. All logic scripts that
have been set up for that model display.
You can create a new logic script for the selected model by choosing New, then assigning a name to the logic
script. You can type directly into the logic editor. You can also insert Business Planning and Consolidation
keywords, MDX keywords, dimension names, and member names from the dropdown lists, replacing variables
in the keywords as appropriate. To add a keyword from the dropdown lists to a line in a script, you can double-
click on a keyword, you can select a keyword and then select Insert Keyword, and you can drag and drop a
keyword from the dropdown list into a line in the logic editor.
You can comment out and uncomment blocks of script logic, as well as individual lines, in the logic editor.
When you create new logic script and edit an existing script, you can validate its syntax. Any problems with the
logic display in the lower portion of the logic editor with line numbers to make locating and resolving the
problems easier.
You can copy an existing logic script by selecting a file, then providing a name for the new script, and modifying
it as you need.
You can use the following color coding in the logic editor to assist in writing and troubleshooting logic scripts:
● Keywords display in blue

● Constant values display in green
● Comments display in grey
● Incorrect syntax, such as parenthesis errors, misspelled keywords and dimension names, and
unrecognized words, displays in red
You can easily resolve errors in script logic using the error lines in the lower portion of the logic editor window.
Errors in a script appear by line number.
More Information
For more detailed documentation of script logic and examples, see the section Business Planning and
Consolidation, version for the SAP NetWeaver Platform in the Enterprise Performance Management (EPM) How-
to Guides section of the SAP SDN at: http://wiki.sdn.sap.com/wiki/display/BPX/Enterprise+Performance
+Management+%28EPM%29+How-to+Guides .
1.14.6.2.1 Library of MDX Functions (Standard only)
Use
Business Planning and Consolidation provides several multidimensional expressions ( MDX) functions you can
use in your dimension rule formulas. You can also use some of these MDX functions in advanced rule formulas.
A majority of the MDX functions define industry-standard financial ratios. You can use ratios to evaluate the
performance of your business and identify potential problems. Ratios expose factors such as the earning
power, solvency, efficiency, and debt load of your business.
Features
The following table describes some of the more common MDX functions:
MDX Function Description Parameters
Ancestor Returns the ancestor of a member at a specified <Member>, <Level>

level
ClosingPeriod Returns the last sibling among the descendants of [<Level>[, <Member>] ]
a member at a level
Cousin Returns the member with the same relative posi <Member1>, <Member2>
tion under a member as the member specified
Current Member Returns the current member along a dimension (none)

during an iteration
Default Member Returns the default member of a dimension (none)
FirstChild Returns the first child of a member (none)
FirstSibling Returns the first child of the parent of a member (none)
IsEmpty Determines if an expression evaluates to the empty <Expression>

cell value
Item Returns a member from a tuple <Numeric Expression>
Lag Returns a member prior to the specified member <Numeric Expression>

along the member's dimension
LastChild Returns the last child of a member (none)
LastSibling Returns the last child of the parent of a member (none)
Lead Returns a member further along the specified <Numeric Expression>

member's dimension
Members Returns the member whose name is specified by a (none)

string expression
NextMember Returns the next member in the level that contains (none)
a specified member
OpeningPeriod Returns the first sibling among the descendants of [<Level>[, <Member>] ]
a member at a level
ParallelPeriod Returns a member from a prior period in the same [<Level>[, <Numeric Expression>[,
relative position as a specified member <Member>] ] ]
Parent Returns the parent of a member (none)
PrevMember Returns the previous member in the level that con (none)
tains a specified member
Aggregate Returns a calculated value using the appropriate <Set>[, <Numeric Expression>]
aggregate function, based on the context of the
function
Avg Returns the average value of a numeric expression <Set>[, <Numeric Expression>]
evaluated over a set
CoalesceEmpty Coalesces an empty cell value to a number <Numeric Expression>[, <Numeric

Expression>...]
Correlation Returns the correlation of two series evaluated <Set>, <Numeric Expression>[, <Nu
over a set meric Expression>]
Count Returns the number of tuples in a set, empty cells <Set>[, EXCLUDEEMPTY | INCLU
included unless the optional EXCLUDEEMPTY flag is DEEMPTY]
used
IIf Returns one of two values determined by a logical <Logical Expression>, <Numeric Ex
test pression>, <Numeric Expression>
LinRegIntercept Calculates the linear regression of a set and re <Set>, <Numeric Expression>[, <Nu
turns the value of b in the regression line y = ax + b meric Expression>]
LinRegPoint Calculates the linear regression of a set and re <Numeric Expression>, <Set>, <Nu
turns the value of y in the regression line y = ax + b meric Expression>[, <Numeric Ex
pression>]
LinRegR2 Calculates the linear regression of a set and re <Set>, <Numeric Expression>[, <Nu
turns R2 (the coefficient of determination) meric Expression>]
LinRegSlope Calculates the linear regression of a set and re <Set>, <Numeric Expression>[, <Nu
turns the value of a in the regression line y = ax + b meric Expression>]
LinRegVariance Calculates the linear regression of a set and re <Set>, <Numeric Expression>[, <Nu
turns the variance associated with the regression meric Expression>]
line y = ax + b
Max Returns the maximum value of a numeric expres <Set>[, <Numeric Expression>]
sion evaluated over a set
Median Returns the median value of a numeric expression <Set>[, <Numeric Expression>]
evaluated over a set
Min Returns the minimum value of a numeric expres <Set>[, <Numeric Expression>]
sion evaluated over a set
Sum Returns the sum of a numeric expression evalu <Set>[, <Numeric Expression>]
ated over a set
For additional NW BI MDX keywords, run function module BAPI_MDPROVIDER_GET_FUNCTIONS via

transaction SE37.
1.14.6.2.1.1 Custom Logic and BADI (Standard only)
Use
You use this instruction to call any custom ABAP programming you have written.
Activities
Run the following instruction to call custom ABAP programs:
*CALL_CUSTOM_LOGIC <filter_value_of_the_BADI>
where filter_value_of_the_BADI is the name of the filter you provided during the BADI implementation of
UJ_CUSTOM_LOGIC BADI.
Custom logic example
*CALL_CUSTOM_LOGIC COMPLEX_ALLOCATION
BADI examples
*START_BADI / *END_BADI call any custom ABAP programming written using UJ_CUSTOM_LOGIC BADI
(Transaction SE19) and allow you to export parameters to ABAP codes in the BADI.
Syntax
*START_BADI <filter_value_of_your_BADI_implementation>
<key1> = <value1>
<key2> = <value2>
*END_BADI
where filter_value_of_your_BADI_implementation is the name of the filter you provided during the
BADI implementation of UJ_CUSTOM_LOGIC BADI.
Syntax example
The following example shows how to call an implemented BADI, with CALC_ACCT as the filter value, for adding
two accounts to a destination account:
*START_BADI ROUND
DECIMAL = 2
*END_BADI
The DECIMAL parameter is visible in the IT_PARAM internal table inside the EXECUTE method. In the EXECUTE
method, you can write custom code to change the incoming transactional data of CT_DATA.
Optional Parameters
You can use the following optional parameters within a *START_BADI / *END_BADI instruction:
● Query - Performs the default query. Valid values are On, the default, and Off. Set Query to Off if you want to
perform your own query.
● Write - Automatically writes back the data. Valid values are On, the default, and Off.
Example
Implementing code (in EXECUTE method of the implemented class) for declining depreciation
 Note
Before you can use a BADI in script logic, implement UJ_CUSTOM_LOGIC BADI from transaction SE19. See
the ABAP online help at http://help.sap.com/saphelp_nw70/helpdata/en/32/
a83942424dac04e10000000a1550b0/content.htm . for information on how to implement a BADI.
METHOD if_uj_custom_logic~execute.
DATA: ls_param TYPE ujk_s_script_logic_hashentry,
l_log TYPE string,
l_ast_acct(16) TYPE c,
l_year(3) TYPE n,
l_percentage(3) TYPE p,
lo_model TYPE REF TO if_uj_model,
lo_dim TYPE REF TO if_uja_dim_data,
ls_dim TYPE uja_s_dim,
time_dim(16) TYPE c,
lr_rec TYPE REF TO data,
lr_result_rec TYPE REF TO data,
l_intermediate_value TYPE uj_sdata,
lt_final TYPE REF TO data.
FIELD-SYMBOLS: <ls_rec> TYPE ANY,
<ls_result_rec> TYPE ANY,
<ls_time> TYPE ANY,
<ls_signed.data> TYPE ANY,
<lt_final> TYPE STANDARD TABLE
* Make sure all the parameters are passed.
CLEAR ls_param.
READ TABLE it_param WITH KEY hashkey = 'YEAR' INTO ls_param.
IF sy-subrc NE 0.
l_log = 'You have not specified the parameter ''YEAR'' which is required.'.
cl_ujk_logger=>log( i_object = l_log ).
RAISE EXCEPTION TYPE cx_uj_custom_logic.
EXIT.
ENDIF.
l_year = ls_param-hashvalue.
CLEAR ls_param.
READ TABLE it_param WITH KEY hashkey = 'PERCENTAGE' INTO ls_param.
IF sy-subrc NE 0.
l_log = 'You have not specified the parameter ''PERCENTAGE'' which is required.'.
cl_ujk_logger=>log( i_object = l_log ).
RAISE EXCEPTION TYPE cx_uj_custom_logic.
EXIT.
ENDIF.
l_percentage = ls_param-hashvalue.
* Get name of the account dim
cl_uj_model=>get_model( EXPORTING i_appset_id = i_appset_id
RECEIVING ro_model = lo_model ).
CALL METHOD lo_model->get_dim_data_by_type
EXPORTING
i_dim_type = uj00_cs_dim_type-time
i_appl_id
= i_appl_id
RECEIVING
ro_dim_data = lo_dim.
TRY.
CALL METHOD lo_dim->get_info
IMPORTING
es_dim_info = ls_dim.
ENDTRY.
time_dim = ls_dim-dimension. TRANSLATE time_dim TO UPPER CASE.
CREATE DATA lt_final LIKE ct_data.
ASSIGN lt_final->* TO <lt_final>. CREATE DATA lr_result_rec LIKE LINE OF ct_data.

ASSIGN lr_result_rec->* TO <ls_result_rec>. CREATE DATA lr_rec LIKE LINE OF ct_data.
ASSIGN lr_rec->* TO <ls_rec>.
* Loop through incoming data and create a result set
LOOP AT ct_data ASSIGNING <ls_rec>.
<ls_result_rec> = <ls_rec>.
ASSIGN COMPONENT time_dim OF STRUCTURE <ls_result_rec> TO <ls_time>.
<ls_time>+0(4) = is <ls_time>+0(4) + l_year.
ASSIGN COMPONENT 'SIGNEDDATA' OF STRUCTURE <ls_result_rec> TO <ls_signeddata>.
DO l_year TIMES.
l_intermediate_value = l_intermediate_value + ( <ls_signeddata> -

l_intermediate_value ) * l_percentage / 100.
ENDDO.
<ls_signeddata> = <ls_signeddata> - l_intermediate_value.
APPEND <ls_result_rec> TO <lt_final>.
ENDLOOP.
* Send the result data back.
 Note
Business Planning and Consolidation always overwrites existing values.
ct_data = <lt_final>.
ENDMETHOD.
Script logic file content to call the BADI:
*START_BADI DECD
QUERY = ON
WRITE = ON
YEAR = 1
PERCENTAGE = 10 *END_BADI
 Note
ET_MESSAGE in the BADI logs the messages to the Data Manager.
If you want to stop the execution, raise the cx_uj_custom_logic exception within a BADI implementation.
More Information
For instructions about creating an SAP Business Add-In, see the ABAP model help in the SAP NetWeaver
Library.
1.14.6.2.2 Logic Keyword Reference (Standard only)
Use
This reference contains descriptions of all the logic keywords you can use in the standard configuration of this
product.
More Information
*ADD / *ENDADD [page 225]
*BEGIN / *END [page 226]
*DESTINATION_APP [page 227]
*FOR / *NEXT [page 229]
*FUNCTION / *ENDFUNCTION [page 230]
*INCLUDE [page 231]
*REC [page 232]
LOOKUP [page 235]
*RUNALLOCATION [page 238]
*SELECT [page 249]
*SELECTCASE / *ENDSELECT [page 250]
*SUB( ) / *ENDSUB [page 251]
*WHEN / *ENDWHEN [page 252]
*XDIM_MEMBERSET [page 253]
*XDIM_ADDMEMBERSET [page 255]
*XDIM_MAXMEMBERS [page 255]
*XDIM_PACKAGEBY (Standard only) [page 256]
*XDIM_FILTER [page 256]
*COMMIT [page 257]
Special Keywords [page 258]
TMVL Parameter [page 261]
1.14.6.2.2.1 *ADD / *ENDADD (Standard only)
This structure allows you to automatically cumulate a set of members to a calculated member as specified in a
comma delimited range. The range can be dynamically derived using a *SELECT( ) instruction. See *SELECT
[page 249].
The syntax is:
*ADD {variable} = {set}
{formula}
*ENDADD
 Example
*ADD %ACC%=[CE0004010],[CE0004020],[CE0004030] [#CE0661000] = %ACC%/[CE0652000]
*ENDADD
*COMMIT
[#CE00661000] = [CE0661000]/[CE0652000]
The ADD statement expands into:
[P_ACCT].[#CE0661000] =[P_ACCT].[CE0004010]/[P_ACCT].[CE0652000]+[P_ACCT].
[CE0004020]/[P_ACCT].[CE0652000]+[P_ACCT].[CE0004030]/[P_ACCT].[CE0652000]
 Note
The expression to the right of the equals sign ( = ) currently does not support more complex expressions.
Only one formula can be written inside the ADD/ ENDADD structure.
1.14.6.2.2.2 *BEGIN / *END (Standard only)
The BEGIN/ END structure can be used to split long formulas across multiple lines to improve readability. The
validation process trims and joins all lines between the BEGIN and END statements.
 Example
*BEGIN
[P_ACCT].[#CE0661000] =
[P_ACC].[CE0004010] + [P_ACCT].[CE0004020] + [P_ACCT].[CE0004030] )
[P_ACCT].[CE0652000]
*END
1.14.6.2.2.3 *DESTINATION_APP (Standard only)
The DESTINATION_APP keyword allows you to write the results of calculations to a different model.
Syntax
*DESTINATION_APP = {app name}
Often, the destination model shares only some of the dimensions of the original model. In this case, the
missing dimensions can be dropped from the original records with the instruction:
*SKIP_DIM= {dimension name}[,{dimension name},…]
When the original model has dimensions that are not found in the destination model, the SKIP_DIM keyword is
mandatory. Validation cannot pass without the SKIP_DIM keyword.
Multiple dimension names can be supplied to the instruction separated either by commas or by multiple
SKIP_DIM instructions entered on separate lines.
If the destination model has dimensions that do not exist in the original model, these can be added to the
passed records, using the instruction:
*ADD_DIM {dimension name}={value}[,{dimension name}={value} [, {dimension name} =

{dimension name(source): Property name}, #]
Multiple dimension names and values can be supplied to the instruction separated either by commas or by
multiple ADD_DIM instructions entered on separate lines. Dimension properties (dimension from the source
model) are also supported.
Example:
To explain DESTINATION_APP with SKIP_DIM, ADD_DIM, and RENAME_DIM, another model DETAIL_PLAN is
created by copying the PLANNING model from the delivered EnvironmentShell. It is necessary to do the
following steps:
● Create new dimensions PRODUCT and MARKET and add these to the DETAIL_PLAN model
● Replace P_ACCT with P_ACCTDETAIL
● Remove the P_ACTIVITY dimension from the DETAIL_PLAN cube using the following syntax:
*XDIM_MEMBERSET TIME = 2006.AUG

*XDIM_MEMBERSET CATEGORY=ACTUAL
*DESTINATION_APP=DETAIL_PLAN
*SKIP_DIM = P_ACTIVITY
*ADD_DIM P_DATASRC=INPUT, MARKET = PRODUCT:MARKET
*RENAME_DIM P_ACCT=P_ACCTDETAIL
*WHEN CATEGORY
*IS "ACTUAL"
*REC(EXPRESSION=%VALUE%)
*ENDWHEN
Explanation: DETAIL_PLAN is the target model, which has all dimensions of PLANNING except for P_ACCT.
This dimension is replaced with P_ACCTDETAIL. Also, DETAIL_PLAN has two additional dimensions, namely
P_DATASRC and MARKET. The above script logic moves the data into DETAIL_PLAN with:
● P_DATASRC defined by the keyword INPUT

● MARKET by using the value of the property 'MARKET' of the dimension PRODUCT, which must exist in the
source model
● The corresponding values of P_ACCT are copied to P_ACCTDETAIL
The keyword RENAME_DIM can be used, to change name of one or more dimensions. The syntax is:
*RENAME_DIM {dimension name}={value}[,{dimension name}={value},…]
This instruction can be used when data is to be written into a model where a dimension is named with a
different ID.
Multiple dimension names and values can be supplied to the instruction separated either by commas or by
multiple RENAME_DIM instructions entered on separate lines.
Any combination of the three keywords, above, is supported.
Examples
Example 1
Environment: EnvironmentShell_V
Model: PLANNING
In this example, EnvironmentShell_V is a copy of EnvironmentShell and COPY_PLANNING is a copy of the

PLANNING model. You can execute the script, shown in this example, in a PLANNING model to copy ACTUAL
data to the COPY_PLAN model.
If the *DESTINATION_APP command appears once in the middle of the script, all remaining data writing of the
script logic file occurs in the referenced destination model. Any data writes before the *DESTINATION_APP are
written in the model where the script is currently being run.

*DESTINATION_APP=COPY_PLANNING
*WHEN CATEGORY
*IS "ACTUAL"
*ENDWHEN
Example 2
To explain DESTINATION_APP with SKIP_DIM, ADD_DIM, and RENAME_DIM, another model DETAIL_PLAN is
created by copying the PLANNING model from the delivered EnvironmentShell. It is necessary to:
● Create new dimensions PRODUCT and MARKET and add these to the DETAIL_PLAN model
● Replace P_ACCT with P_ACCTDETAIL
● Remove the P_ACTIVITY dimension from the DETAIL_PLAN cube

*DESTINATION_APP=DETAIL_PLAN
*SKIP_DIM = P_ACTIVITY
*ADD_DIM P_DATASRC=INPUT, PRODUCT = NO_PRODUCT, MARKET = NO_MARKET
*RENAME_DIM P_ACCT=P_ACCTDETAIL
*WHEN CATEGORY
*IS "ACTUAL"
*ENDWHEN
Explanation
DETAIL_PLAN is the target model, which has all dimensions of PLANNING except for P_ACCT. This dimension is
replaced with P_ACCTDETAIL. Also, DETAIL_PLAN has two additional dimensions, namely PRODUCT, and
MARKET.
The above script logic moves the data into DETAIL_PLAN with:
● Blank data in the PRODUCT and MARKET dimensions

● P_DATASRC defined by the keyword INPUT
● corresponding values of P_ACCT copied to P_ACCTDETAIL
1.14.6.2.2.4 *FOR / *NEXT (Standard only)
*FOR / *NEXT is used to repeat certain scripts written between a FOR and an immediate NEXT for a set of
members. Sets of members can be provided either directly in the FOR statement or through variables.
The Logic Module supports any number of FOR… NEXT loops in the body of the logic files. The syntax is the
following:
*FOR {variable1} = {set1} [ AND {variable2={set2}]
{text}
{text}
*NEXT
 Example
In a logic file, you may need to repeat some calculation for a set of entities. This works automatically when
you write:
*XDIM_MEMBERSET TIME = 2006.JAN
*XDIM_MEMBERSET CATEGORY = Q1FCST_LOAD
*FOR %Q1% = 2006.JAN, 2006.FEB, 2006.MAR
*RUNALLOCATION
*FACTOR=1/3
*DIM TIME WHAT = 2009.JAN; WHERE = %Q1%;
*DIM CATEGORY WHAT=Q1FCST_LOAD; WHERE=FQ1;
*ENDALLOCATION
*NEXT
Assuming the forecast data for Q1 is loaded in 2006.JAN, the above script allocates this data into each
period in Q1 equally.
 Note
Only one variable is allowed per *FOR statement.
1.14.6.2.2.5 *FUNCTION / *ENDFUNCTION (Standard only)
A userdefined function is the name of a placeholder that a user can insert in formulas in place of a
corresponding MDX statement or part of one. This can greatly improve the readability of a logic statement.
The definitions of the logic functions can be inserted anywhere in a logic file or in an included file. Their syntax
is the following:
For single line functions
*FUNCTION {functionname}({Param1}[,{Param2}…]) = {Function Text}
For multi-line functions
*FUNCTION {functionname}({Param1}[,{Param2}…])
{Function text}
{Function text}
*ENDFUNCTION
An unlimited number of functions can be defined within a script logic file.
An unlimited number of parameters can be passed to a function to dynamically modify the corresponding MDX
string.
Functions currently cannot be nested, meaning a function cannot contain another function.
The position of the functions in the logic file is irrelevant, unless the same function is redefined, in which case
the new definition of the function applies only from the point of the redefinition.
The values of the passed parameters are replaced in the function text without any validation, even if they are
embedded in longer words, like in the following example:
Use caution when defining the names of the parameters to avoid the risk of conflicts with MDX reserved words
and with the text surrounding them in logic. The best practice is to always surround the name of the
parameters with a delimiter, as in the following example:
 Example
*FUNCTION Price(%COST%,%HOUR%)
%COST%/%HOUR%
*ENDFUNCTION[#CE0661000] = Price([CE0004000],[CE0652000])
The example calculates the Price. You do not have to check the denominator for Zero to avoid divide-by-zero
error. The Script Logic engine automatically replaces the divide by zero error with zero.
You can also use *FUNCTION to substitute members or dimensions to make scripts more readable.
*FUNCTION PERSONAL_COST = CE0004000
*FUNCTION LAB_HOUR = CE0652000
*FUNCTION PER_PRICE = CE0661000
*FUNCTION ACCOUNT = P_ACCT
Price(%COST%,%HOUR%)
%COST%/%HOUR%
*ENDFUNCTION
[ACCOUNT].[#PER_PRICE] = Price([ACCOUNT].[PERSONAL_COST],[ACCOUNT].[LAB_HOUR])
The following characters, plus the blank character, are invalid in logic functions names:
+-/*^%><=()[]{},.;':&\|#~"
1.14.6.2.2.6 *INCLUDE (Standard only)

Multiple files can be combined into one logic file by the use of the instruction INCLUDE. During the LGX
generation of the script logic execution step, the statements in the INCLUDE file are combined with the main
file.
 Example
*INCLUDE FUNCTION_DEFINITIONS.LGF
[ACCOUNT].[#PER_PRICE] =
Price([ACCOUNT].[PERSONAL_COST],[ACCOUNT].[LAB_HOUR])
A FUNCTION_DEFINITIONS.LGF file can include all definitions:
*FUNCTION PERSONAL_COST = CE0004000
*FUNCTION LAB_HOUR = CE0652000
*FUNCTION PER_PRICE = CE0661000
*FUNCTION ACCOUNT = P_ACCT
Price(%COST%,%HOUR%)
%COST%/%HOUR%
*ENDFUNCTION
1.14.6.2.2.7 *REC (Standard only)
The *REC( ) instruction tells the program what to do once the specified criteria has been met. Each REC
instruction generates one new record to post to the database. Each source record can generate as many
records as desired, even pointing to the same destination cell.
The parameters of the REC( ) function specify what to modify of the original record. Any dimension member
can be modified using the following syntax:
{DimensionName}={member}
 Example
*XDIM_MEMBERSET P_ACCT = CE0004010
*WHEN CATEGORY
*IS ACTUAL *REC(FACTOR = 1.1, CATEGORY="FORECAST")
*ENDWHEN
You can use property values in WHEN statement.
 Example
*XDIM_MEMBERSET CATEGORY = PLAN
*WHEN TIME.YEAR
*IS "2007"
*REC(FACTOR = 1.1, CATEGORY="FORECAST")
*ENDWHEN
The above script copies the 2007 plan data to Forecast. You can also read property values and assign them
to dimensions.
 Example
*XDIM_MEMBERSET P_ACCT = CE0004010,CE0652000
*WHEN P_ACCT
*IS "CE0004010"
*REC(EXPRESSION=([P_ACCT].[CE0004010],[P_ACTIVITY].[NONE])/([P_ACCT].[CE0652000],
[P_ACTIVITY].[LABPRD]), RPTCURRENCY=[ENTITY].CURRENCY, P_ACCT=CE0661000)
*ENDWHEN
Restrictions For Using the REC Instruction
● You cannot use other MDX keywords (such as PARENT and DESCENDANTS) in FACTOR or EXPRESSION
instructions. The only permitted operations are addition (+), subtraction (-), multiplication (*), and division
(/), combinations of these operators, and parenthesis for tuple and priorities of the operations.
● You cannot use the GET() function to refer to another source value. The MDX tuple format acts as a GET
function.
● You cannot use NOADD or FLD functions within REC.
● Dynamic properties such as HLEVEL, PARENTH are not supported in the REC statement.
● REC always needs to be accompanied by WHEN / IS / ENDWHEN. Stand-alone REC statements do not
have any effect.
● You cannot use SIGNEDDATA or any measure name in a WHEN statement to write a condition on a
measure value.
● WHEN / IS / REC / ENDWHEN cannot be used in SELECTCASE / ENDSELECT.
Using Multiple REC Statements
You can write multiple REC statements within one WHEN/ IS/ ENDWHEN statement.
Syntax
*WHEN {dim}
* IS {condition_value}
*REC({FACTOR or EXPRESSION instruction},dim=…)
*ENDWHEN
 Example
*XDIM_MEMBERSET TIME = 2006.AUG,2006.SEP
*XDIM_MEMBERSET P_ACCT=CE0004010
*WHEN P_ACCT
*IS "CE0004010"
*REC(EXPRESSION=%VALUE%/1.5098, RPTCURRENCY="EUR")
*REC(EXPRESSION=%VALUE%/1.0666, RPTCURRENCY="CAD")
*REC(EXPRESSION=%VALUE%/1.9183, RPTCURRENCY="GBP")
*ENDWHEN
The script shown above creates EUR, CAD, and GBP posts in the cube.
Referring To Another Source Value Within A FACTOR/EXPRESSION Instruction
You can assign a source value from the scoped data for a FACTOR or EXPRESSION instruction to calculate a
new value inside a *REC( ) statement. To refer to another source value, you must use fully qualified MDX
formatting, including an Account dimension.
 Note
You have the ability to use implicit Account members in direct MDX statements within script logic.
Syntax
*WHEN {dim}
* IS {condition_value}
*ENDWHEN
 Example
Environment: EnvironmentShell_V (Copy of EnvironmentShell)
Application: Planning
*WHEN P_ACCT
*IS "CE0004010"
*REC(EXPRESSION=%VALUE%/[P_ACCT].[CE0004020], P_ACCT="CE0661000")
*ENDWHEN
You can use tuples as well.
 Example
Environment: EnvironmentShell_V (Copy of EnvironmentShell)
Application: Planning
*WHEN P_ACCT
*IS "CE0004010"
*REC(EXPRESSION=%VALUE%/([P_ACCT].[CE0652000],[P_ACTIVITY].[LABPRD]),
P_ACCT="CE0661000")
*ENDWHEN
1.14.6.2.2.8 LOOKUP (Standard only)

Referring to Another Source Value Using the LOOKUP Function
To calculate a new value inside a *REC( ) statement, you can use the LOOKUP function to assign a source
value that is outside the scoped data for a FACTOR or an EXPRESSION instruction.
Syntax
*LOOKUP {Model}
*DIM [{LookupID}:]{DimensionName}="Value" | {CallingDimensionName}[.{Property}]
*DIM MEASURES="MeasureName"
*ENDLOOKUP
 Example
In the following example, you are reading RATE information and using it in the calculation. You can also use
FOR/NEXT to look up multiple values.
Environment: EnvironmentShell_V (Copy of the EnvironmentShell sample environment)
Model: Planning
*LOOKUP RATE
*DIM TIME="2006.AUG"
*DIM CATEGORY="ACTUAL"
*DIM R_ACCT="AVG"
*DIM R_ENTITY="GLOBAL"
*DIM RATEEUR:INPUTCURRENCY="EUR"
*DIM MEASURES="PERIODIC"
*ENDLOOKUP
*WHEN P_ACCT
*IS "CE0004010"
*REC(EXPRESSION=%VALUE%/LOOKUP(RATEEUR), RPTCURRENCY="EUR")
*ENDWHEN
 Example
In the following example, you are first reading all reporting currencies in the *SELECT statement and
assigning the values to variable %CUR%. Using FOR/NEXT, you read their rates from RATE model. Then,
you use them in the calculation.
Values in the models before the execution of the script:
PLANNING model data:
TIME P_ACCT ENTITY P_ACTIVITY CATEGORY Currency P_DATASRC SignData
2006.AUG CE0004010 C9000 NONE ACTUAL LC UPLOAD 157,915.81
Rate model data:
Category InputCurrency R_ACCT R_ENTITY TIME SignData
ACTUAL EUR AVG GLOBAL 2006.AUG 1.5022
ACTUAL USD AVG GLOBAL 2006.SEP 1.0000
*XDIM_MEMBERSET TIME=2006.AUG
*SELECT(%CUR%, "[ID]", RPTCURRENCY, "[REPORTING]=Y")
*LOOKUP RATE
*DIM R_ACCT="AVG"
*DIM TIME="2006.AUG"
*FOR %LOOP_CUR%=%CUR%
*DIM C_%LOOP_CUR%:INPUTCURRENCY="%LOOP_CUR%"
*NEXT
*ENDLOOKUP
*WHEN P_ACCT
*IS "CE0004010"
*FOR %LOOP_CUR%=%CUR%
*REC(EXPRESSION=%VALUE%/LOOKUP(C_%LOOP_CUR%), RPTCURRENCY=%LOOP_CUR%)
*NEXT
*ENDWHEN
Values in the model after the execution of the script:
2006.AUG CE0004010 C9000 NONE ACTUAL EUR UPLOAD 105,123.03
2006.SEP CE0004010 C9000 NONE ACTUAL USD UPLOAD 157,915.81
You can also pass property values to scope members to look up data.
 Example
In this example, the corresponding Entity's currency is read from master data and this is used to look up
the rate value.
*XDIM_MEMBERSET ENTITY=C9000
*LOOKUP RATE *DIM TIME="2006.AUG"
*DIM R_ACCT="AVG"
*DIM RATE:INPUTCURRENCY=ENTITY.CURRENCY
*ENDLOOKUP
*WHEN P_ACCT
*IS "CE0004010"
*REC(EXPRESSION=%VALUE%/LOOKUP(RATE), RPTCURRENCY=ENTITY.CURRENCY)
*ENDWHEN
Restriction
● Reading multiple measures within a single LOOKUP by assigning different lookup IDs is not supported.
1.14.6.2.2.9 *RUNALLOCATION (Standard only)
Allocation helps distribute data from a source region to a target region using the specified driver.
Syntax
*RUNALLOCATION
*FACTOR=<driver>
*DIM P_ACCT WHAT=<soure>; WHERE=<target>; USING=<distribution key>;

[TOTAL=<distribution key>]
*DIM <other dimensions>
*ENDALLOCATION
WHAT (Source)
The source value represents the range of data values to be allocated by the allocation function. This value is
qualified by one or several tuples in the model.
Possible WHAT options are:
Options Descriptions Example
Member A specified dimension base member. *DIM Region WHAT = US
[property]="property value" A filter to select dimension members based *DIM Product_Group = [Fruit]
on a specified property and a given value for = "apples"
that property.
BAS All leaf level members of a specific dimen *DIM Product_Group =

sion parent member BAS(TotalProduct)
same as WHERE Use the same members defined in the *DIM Account WHERE = Rent
WHERE parameter for the specified dimen
*DIM Account WHAT = Rent
sion
<> member The <> operand references all members not *DIM Region USING <> Corp
equal to a defined member.
In the <>member mode, the member

should be base member in the dimension.
If the <> is used, all other base members in

that dimension should be included in the re
gion.
Restriction of WHAT
● You cannot use blank or [ALL] in WHAT condition.

● You cannot use non-base members with <>.
USING and TOTAL (Distribution key)
The basis of the allocation is the definition of a portion or complete source value to be allocated. The method of
defining the basis is the use of a factor. A factor can be the value or values that can be multiplied or divided to
derive a value (added or subtracted potential future support).
A factor can also derive values based on a defined region of data referred as using, or the basis region.
Possible USING and TOTAL options are:
Member A specified dimension base member. *DIM Region USING = US

same as WHERE Use the same members defined in the *DIM Account WHERE = Rent
WHERE parameter for the specified dimen
*DIM Account USING =
sion. The same dimension must be for both
PercentAcct
WHERE and USING.
 Note
WHERE only supports a single member
reference.
<> member The <> operand references all members not *DIM Region USING <> Corp
equal to a defined member.
In the <>member mode, the member

should be base member in the dimension.
If the <> is used, all other base members in

that dimension should be included in the re
gion.
that property.
Restriction of USING
● You cannot use >0. For example, USING = Amount >0 is not supported.
● USING and TOTAL must have the same definition.
● You cannot use non-base members with <>.
● You cannot use parent member directly in USING. BAS(parent) is still allowed as described above.
FACTOR (Driver)
FACTOR can be used to define any arithmetic expression, written in the {expression} parameter, and can
contain operands, parentheses, constants, and one or both of the keywords USING and TOTAL, representing
respectively the amount coming from the USING region, the amount of the driver, and the amount coming from
the TOTAL region, the sum of the drivers.
● If FACTOR is omitted, the FACTOR defaults to 1.

● If the arithmetic expression is omitted, the default is multiplication.
Possible FACTOR options are:
.8 Only a fixed amount is to be applied to the Tuple value of the WHAT is 10 for product A
source value for allocation.
10*.8 = 8
USING The value of the USING region defined is Tuple value of the WHAT is 10 for product A,
used as the basis of the allocation. This pro tuple value of the USING is .8
vides the ability to change values without
10*.8 = 8
having to edit the definition of the alloca
tion.
-1 * USING/100 Calculation takes the defined region as Tuple value of the USING region is 70 for
USING, and reverses the value (negative), product A.
Or
then divides the value by 100.
-70/100 = -.7
1 * USING/100
(-70%) (1-70)/100 = -.69 (-69%)
 Note
This is used with driver accounts not re
porting values.
USING/TOTAL Calculation takes the region defined as Tuple value of USING region is 70 for prod
USING, and divides the total value for the re uct A. The total of the TOTAL region (tuples)
gion defined as TOTAL. is 700, assuming that the using region is for
all regions not just US.
70/700 = .1 (10%)
Basic Mathematical expression Calculation takes the region defined as Tuple value of the USING region is 70 for
with USING & TOTAL USING, and does the necessary mathemati product A.
cal operations with the total value for the re
(For example, 1 + USING, US 1+70 = 71
gion defined as TOTAL.
ING -1 , and 1 - USING)
70 -1 = 69
1-70 = -69
Restriction of FACTOR
● You cannot use any script logic keywords in FACTOR expression.
WHERE (Target)
The target identifies the tuples to which the values should be allocated. It represents dimension member
combinations to which the values should be distributed. The target identifies the dimension for which the value
of the members is modified as compared to the source, and only explicitly mentioned and characterized
dimension should be modified.
The keyword WHERE is used in combination with the keyword *DIM to identify the target dimension members
(the values to be modified against the source).
Possible WHERE options are:
Member A specified dimension base member. *DIM Region WHERE = US

same as WHAT Use the same members defined in the WHAT *DIM Account WHAT = Rent
parameter for the specified dimension
*DIM Account WHERE = Rent
blank or [All] The ability to assume all base members for *DIM Entity =
given dimensions either via a blank parame
*DIM IntCo = [ALL]
ter or [ALL] key word
that property.
Common Restriction
● *APP (ability to write in different model if needed), COUNT and LIST keywords inside RUNALLOCATION or
any other options not mentioned above are not supported.
Examples
Example 1
The account RENT is entered in entity GLOBALOPS, inter-company NON_INTERCO. This amount must be
allocated using a percentage of allocation that is entered by the user in account PERCENT in the appropriate
entities and for the desired members of the CATEGORY, TIME, DATASRC, and RPTCURRENCY dimensions.
This allocation demonstrates the following features:
● It uses the {dimensiontype}DIM keyword to identify the dimensions by type

● It uses the <<< and >>> keywords to reference the definitions used to the left or to the right
Before Allocation
Source Account ( RENT) data:
RENT CHINA China
RENT JAPAN Japan
RENT INDIA India
RENT ASAREST Rest of Asia
RENT ASA Asia 50,000,000.00
Driver (Percent Account) data:
PERCENT CHINA China 10.00
PERCENT JAPAN Japan 32.00
PERCENT INDIA India 8.00
PERCENT ASAREST Rest of Asia 50.00
*XDIM_MEMBERSET TIME=2006.SEP
*XDIM_MEMBERSET P_ACCT=RENT,PERCENT
*XDIM_MEMBERSET ENTITY=ASA,INDIA,CHINA,JAPAN,ASAREST
*RUNALLOCATION
*FACTOR=USING/100
*DIM P_ACCT WHAT=RENT; WHERE=<<<; USING=PERCENT
*DIM ENTITY WHAT=ASA; WHERE=INDIA,CHINA,JAPAN,ASAREST;
USING=<<<
*ENDALLOCATION
After Allocation
RENT CHINA China 5,000,000.00
RENT JAPAN Japan 16,000,000.00
RENT INDIA India 4,000,000.00
RENT ASAREST Rest of Asia 25,000,000.00
RENT ASA Asia 50,000,000.00
Example 2
The account RENT is entered in entity GLOBALOPS, inter-company NON_INTERCO. This amount must be
allocated on the basis of the square meters of rented space used by all European entities.
● Allocation uses historical rent as the driver

● It uses the BAS( ) keyword to build a list of members
Before Allocation
Below is the history data shown for the 2008.JAN period. Asia is the parent node.
Entity CATEGORY 2008.JAN
Asia all ACTUAL
Asia ACTUAL
China ACTUAL 1,500.00
Japan ACTUAL 7,000.00
India ACTUAL 500.00
Rest of Asia ACTUAL 5,000.00
Planning Asia ACTUAL
Source Account ( RENT) data:
● To allocate 50,000 to base countries

● This input can be received in the Planning Asia entity
Driver data:
● The historical data is the Driver
*XDIM_MEMBERSET TIME=2008.JAN,2009.JAN
*XDIM_MEMBERSET P_ACCT=RENT
*XDIM_MEMBERSET CATEGORY=ACTUAL,PLAN
*XDIM_MEMBERSET ENTITY=ASA,BAS(RASA)
//Create total rent data to be allocated.

*WHEN ENTITY
*IS "ASA"
*REC (EXPRESSION=50000,TIME=2009.JAN,CATEGORY=PLAN)
*ENDWHEN
*COMMIT
//Allocate to base countries.

*RUNALLOCATION
*FACTOR=USING/TOTAL
*DIM P_ACCT WHAT=RENT; WHERE=<<<; USING=<<<; TOTAL=<<<
*DIM ENTITY WHAT=ASA; WHERE=BAS(RASA); USING=<<< TOTAL=<<<
*DIM TIME WHAT=>>>; WHERE=2009.JAN; USING=2008.JAN;
TOTAL=<<<
*DIM CATEGORY WHAT=>>>; WHERE=PLAN; USING=ACTUAL;
TOTAL=<<<
*ENDALLOCATION
//Clear the total rent account.

*WHEN ENTITY
*IS "ASA"
*REC (EXPRESSION=0,TIME=2009.JAN,CATEGORY=PLAN)
*ENDWHEN
After Allocation
Entity CATEGORY 2009.JAN
Asia all PLAN 50,000.00
Asia PLAN 50,000.00
China PLAN 7,500.00
Japan PLAN 35,000.00
India PLAN 2,500.00
Rest of Asia PLAN 5,000.00
Planning Asia PLAN
2009.JAN is posted with rents for individual countries based upon their historical share.
Example 3
The sum of all ADVERTISING expenses incurred by all European operations must be reallocated to each
European operation based on their external SALES.
● It uses the DOT({type}) keyword to identify the dimensions by type

● It demonstrates the ability to perform aggregations in the WHAT region ( SALESEUROPE and ALL_INTCO are
parent members)
● It shows a many-to-one redirection of a dimension (it reads the sum of the Inter-company members and
writes it in the NON_INTERCO member of the INTCO dimension)
● It shows a one-to-one redirection of a dimension (it reads the INPUT member and writes the results in the
ALLOCATED member of the DATASRC dimension)
Before Allocation
Source data - History data for External Sales:
Actual - Periodic 2008.JAN
Planning Asia
China 500,000
Japan 600,000
India 200,000
Rest of Asia 800,000
Asia 2,100,000
Asia all 2,100,000
Data to be allocated ( ADVERTISING):
Plan - Periodic 2009.JAN
Planning Asia 500,000
China
Japan
India
Rest of Asia
Asia
Asia all 500,000
Factor: USING/TOTAL
APP or (Dim) or
VALUE WHAT WHERE USING TOTAL
DOT(A) ADVERTISING <<< EXTSALES <<<
DOT(E) SALESEUROPE BAS(SALESEUROPE) <<< <<<
DOT(I) ALL_INTERCO NON_INTERCO >>> BAS(ALL_INTERCO)
DATASRC INPUT ALLOCATED INPUT <<<
*RUNALLOCATION
*FACTOR =USING/TOTAL
*DIM P_ACCT WHAT=ADVERTISING; WHERE=<<<; USING=EXTSALES;
TOTAL=<<<
*DIM ENTITY WHAT=ASA; WHERE=BAS(RASA); USING=<<<;
TOTAL=<<<
*DIM INTERCO WHAT=WORLD_INTERCO; WHERE=I_NONE; USING=>>>;
TOTAL=BAS(World_InterCo)
*DIM P_DATASRC WHAT=MANUAL; WHERE=ALLOCATED;
USING=MANUAL; TOTAL=<<<
*DIM TIME WHAT=2009.JAN; WHERE=2009.JAN; USING=2008.JAN;
TOTAL=<<<
*ENDALLOCATION
After Allocation
Planning Asia
China 119,048
Japan 142,857
India 47,619
Asia 500,000
Asia all 500,000
Example 4
This example implements the same scenario as example 3, but using a system variable for year. (%YEAR%).
This returns current calendar year. Assume that the script is for year 2009.
Before Allocation
Source data - History data for External Sales:
Actual - Periodic 2008.JAN
Planning Asia
China 500,000
Japan 600,000
India 200,000
Asia 2,100,000
Asia all 2,100,000
Data to be allocated ( ADVERTISING):
Planning Asia 500,000
China
Japan
India
Rest of Asia
Asia
Asia all 500,000
Factor: USING/TOTAL
APP or (Dim) or
VALUE WHAT WHERE USING TOTAL
DOT(A) ADVERTISING <<< EXTSALES <<<
DOT(E) SALESEUROPE BAS(SALESEUROPE) <<< <<<
DOT(I) ALL_INTERCO NON_INTERCO >>> BAS(ALL_INTERCO)
DATASRC INPUT ALLOCATED INPUT <<<
*RUNALLOCATION
*FACTOR =USING/TOTAL
*DIM P_ACCT WHAT=ADVERTISING; WHERE=<<<; USING=EXTSALES;
TOTAL=<<<
*DIM ENTITY WHAT=ASA; WHERE=BAS(RASA); USING=<<<;
TOTAL=<<<
*DIM INTERCO WHAT=WORLD_INTERCO; WHERE=I_NONE; USING=>>>;
TOTAL=BAS(World_InterCo)
*DIM P_DATASRC WHAT=MANUAL; WHERE=ALLOCATED;
USING=MANUAL; TOTAL=<<<
*DIM TIME WHAT=%YEAR%.JAN; WHERE=%YEAR%.JAN; USING=%YEAR%
(-1).JAN; TOTAL=<<<
*ENDALLOCATION
After Allocation
Planning Asia
China 119,048
Japan 142,857
India 47,619
Asia 500,000
Asia all 500,000
Example 5
All accounts in the profit and loss of category ACTUAL, for the three entities ITALY, FRANCE and UK, are copied
into the corresponding accounts of the entity GLOBALOPS for category BUDGET. This allocation is basically an
example of a simple copy action, which does not use FACTOR at all. In this example the engine performs a one-
to-one copy ( ACTUAL into BUDGET) and a many-to-one copy ( ITALY, FRANCE and UK are added up and copied
into GLOBALOPS).
Before Allocation
Actual - Periodic 2007.DEC
UK (Great Britain) 30,000
Italy 10,000
France 10,000
Budget - Periodic 2008.FEB
Global Operations
Factor:
APP or (Dim) or VALUE WHAT WHERE
ACCOUNT [GROUP] = "profit & loss" <<<
CATEGORY ACTUAL BUDGET
ENTITY SALESITALY; SALESFRANCE; SALESUK GLOBALOPS
DOT(R) LC <<<
A property not supported in ALLOCATION is replaced by a variable using a *SELECT statement. Ensure that the
*SELECT statement selects only base members.
*XDIM_MEMBERSET ACCOUNT=ADVERTISING,EXTSALES
*XDIM_MEMBERSET ENTITY=UK,ITALY,FRANCE,GLOBAL
*XDIM_MEMBERSET P_DATASRC = INPUT
*XDIM_MEMBERSET TIME = 2007.DEC,2008.JAN
*XDIM_MEMBERSET CATEGORY = ACTUAL,BUDGET
*XDIM_MEMBERSET INTCO= I_NONE
*XDIM_MEMBERSET RPTCURRENCY = LC
*SELECT(%ACCT%, "[ID]",ACCOUNT,"[CALC]='N'","[GROUP]='PL'")
*RUNALLOCATION
*FACTOR=
*DIM ACCOUNT WHAT=[GROUP]="PL" AND [CALC]="N"; WHERE=<<<
*DIM CATEGORY WHAT=ACTUAL; WHERE=BUDGET
*DIM ENTITY WHAT=UK,ITALY,FRANCE; WHERE=GLOBAL
*DIM DOT(R) WHAT=LC; WHERE=<<<
*DIM TIME WHAT=2007.DEC; WHERE=2008.FEB
*ENDALLOCATION
After Allocation
Budget - Periodic 2008.FEB
Global Operations 50,000
1.14.6.2.2.10 *SELECT (Standard only)

The special instruction *SELECT allows the user to retrieve a list of elements from a dimension and save it in a
userdefined variable for use somewhere else in the logic.
*SELECT ({variable}, {[What]}, {From dimension}, {Where})
 Example
With the following instruction, the user can retrieve the ID of all members in the CURRENCY dimension
where the property CURRENCY TYPE has the value R.
*SELECT(%CURRSET%, "[ID]", RPTCURRENCY, "[REPORTING]='Y'")*XDIM_MEMBERSET

RPTCURRENCY = %CURRSET%
The *SELECT statement fills the variable %CURRSET% with the list of reporting currencies defined in the
current model. The content of the resulting variable is then used in the XDIM_MEMBERSET statment.
The SELECT instruction is not specific to a given logic section, but it can be written once anywhere in the logic
and used across multiple commit sections.
The SELECT statement is fairly limited, as it only supports the equal sign (=) , not equal to (<>) and cannot be
used to combine multiple filter criteria with AND or OR keywords.
1.14.6.2.2.11 *SELECTCASE / *ENDSELECT (Standard only)
To write formulas containing several nested IIF( ) statements, use the following syntax:
*SELECTCASE {expression}
*CASE {value1}[,{value2},…]
{formulas}
[*CASE {value1}[,{value2},…]
{formulas}
[*CASEELSE]
{formulas}
*ENDSELECT
where
{expression} is the condition to be evaluated
{value1},.. is the range of comma-delimited results that satisfy the condition for the current case
With such a structure, the readability of a logic statement can be significantly improved.
 Example
*BEGIN
#A = IIF([ACCOUNT].[E]=1 OR [ACCOUNT].[E]=2,X+Y,
IIF([ACCOUNT].[E]=3 OR [ACCOUNT].[E]=4,X-Y,X*Y))
*END
#C = IIF([ACCOUNT].[E]=1 OR [ACCOUNT].[E]=2,W+Z,null)
#B = IIF([ACCOUNT].[E]=3 OR [ACCOUNT].[E]=4,W*Z,null)
The following formulas could be written as follows:
*SELECTCASE [ACCOUNT].[E]
*CASE 1,2
#A=X+Y
#C=W+Z
*CASE 3,4
#A=X-Y
#B=W*Z
*CASEELSE
#A=X*Y
*ENDSELECT
 Note
SELECTCASE structures currently CANNOT be nested.
1.14.6.2.2.12 *SUB( ) / *ENDSUB (Standard only)
A SUB structure allows the user to define reusable logic sections anywhere in the body of the logic to make the
logic easier to read and maintain.
A *SUB( ) structure is declared like a multi-line *FUNCTION( ) structure with the following syntax:
*SUB {SubName}({Param1,[,{Param2}…])
{body text}
{body text}
{body text}
[…]
*ENDSUB
When a SUB is then used somewhere else in the logic, its body lines are inserted in the logic with all the values
passed to its parameters appropriately replaced.
A SUB behaves similarly to included files, to which any number of parameters can be passed. When the logic is
validated, the subs are inserted in the body of the logic as if they were included with an *INCLUDE instruction.
However, to use a SUB structure, no special keyword is required. A SUB is called by inserting a line with the
name of the SUB, followed by the values assigned to its parameter enclosed in brackets. The other important
difference from included files is that a SUB does not need to be written in a file of its own, but can be written in
any part of the logic, more similarly to a FUNCTION.
 Example
Here the sub is defined:
*SUB MYSUB(Param1,Param2,Param3,Param4)
[%ACCOUNT_DIM%].[#Param1]=[%ACCOUNT_DIM%].[Param2]+[%ACCOUNT_DIM%].[Param3]
[%ACCOUNT_DIM%].[#Param4]=[%ACCOUNT_DIM%].[#Param1]*[%ACCOUNT_DIM%].
[Factor_Param4]
*ENDSUB
Here the sub is used:
MySub(A1,B1,C1,D1)
MySub(A2,B2,C2,D2)
MySub(A3,B3,C3,D3)
Similarly to a FUNCTION, a SUB is not position sensitive, and can be defined anywhere in a logic, as well as, if so
desired, stored in separate library files that must then be merged with the logic using an INCLUDE instruction.
A SUB can be used in any commit section of the logic without the need to be redefined in each section.
However, if a SUB is redefined in a logic file, its new definition applies to all lines following the redefinition.
A SUB without parameters is supported, but they must always be followed by brackets.
1.14.6.2.2.13 *WHEN / *ENDWHEN (Standard only)
See also *REC.
A WHEN / ENDWHEN structure works in the same way as the SELECTCASE / ENDSELECT structure, with *REC( )
statements that generate new records. The syntax is the following:
*WHEN {criteria}
*IS [=]{value1}[,{value2},…] | <>{value}
*REC(FACTOR={Real number}|EXPRESSION={Expression}[,{dim1}={member},{dim2}=…])
[ *REC(FACTOR={Real number}|EXPRESSION={Expression}[,{dim1}={member},{dim2}=…])]
[*ELSE]
*ENDWHEN
where
{criteria} is what to test. Typically, this is a property of the current member of a dimension. The syntax is
DimensionName.Property | DimensionName, such as *WHEN ACCOUNT.RATETYPE. If Property is not
specified, the ID property is assumed. For example, *WHEN ACCOUNT equals to *WHEN ACCOUNT.ID.
{ValidCondition} is one or more values that meet the criteria. You can enclose them in double quotes to
treat them as strings. Omit the quotes if they represent numeric values. For example:
*IS "AVG","END"
*IS 10,20,30
If no operator is specified, the *IS clause assumes the presence of an equal sign (*IS = "AVG", "END").
The {value} must be literals only, not variables. Therefore, the following sample is not supported:
*IS dimension.property
 Note
There should be no space between the two characters of the unequal sign operator (<>). You can insert one
or more blanks between the operators and the value.
If an unequal sign (<>) is used, you can pass only one value. Therefore, the syntax *IS <> 2,3,4 is invalid.
Other relational operators like AND, OR and NOT are not currently supported.
Nesting of WHEN / ENDWHEN
WHEN / ENDWHEN structures can be nested by as many levels as desired and in any sequence, as shown in the
following sample:
*WHEN xxx
*IS "A"
*REC(…)
*REC(…)
*IS "B"
*REC(…)
*WHEN yyy
*IS "C","D","E"
*REC(…)
*ELSE
*REC(…)
*ENDWHEN
*ENDWHEN
1.14.6.2.2.14 *XDIM_MEMBERSET (Standard only)
*XDIM_MEMBERSET defines the scope of the data in which subsequent business logic will be applied.
Syntax
*XDIM_MEMBERSET {Dimension name} = {Members Set}
* XDIM_MEMBERSET {Dimension}<>{MemberSet}
 Example
*XDIM_MEMBERSET TIME = 2006.DEC
*XDIM_MEMBERSET P_ACCT = bas(CE0004000)
[TIME].[#2009.DEC] = [TIME].[2006.DEC] * 1.1
*COMMIT
This example first reads all children of CE0004000 in the 2006.DEC period, increases them by 10%, and
then copies them to the 2009.DEC period.
Other valid use cases:
*XDIM_MEMBERSET P_ACCT = CE0004010, CE0004020, CE0004030
*XDIM_MEMBERSET P_ACCT = CE0004000, where all children values are summarized to one parent
record.
*XDIM_MEMBERSET P_ACCT = BAS(CE0004010, CE0004210) The scope is defined by the base

members of both CE0004010 and CE0004210. The string inside the parentheses () can also be replaced
by a variable defined in the Data Manager prompt.
*XDIM_MEMBERSET P_ACCT = DEP(CE0004010) All direct children of CE0004010.
*XDIM_MEMBERSET P_ACCT = ALL(CE0004010) All children of CE0004010.
*XDIM_MEMBERSET P_ACCT <> CE0004010
You cannot combine bas() with any other member set.
*XDIM_MEMBERSET P_ACCT = bas(CE0004000), CE0004210 This is not a valid use case.
Use *XDIM_ADDMEMBERSET to add more members to the scope of the member set defined by bas().
Forcing a dimension to read all members without member formulas
Using the <ALL> keyword, you can force a dimension to read all base members without member formulas.
Example
*XDIM_MEMBERSET P_ACCT = <ALL>
*XDIM_MEMBERSET TIME = 2006.DEC
[P_ACCT].[#CE0661000] = [P_ACCT].[CE0004000] / [P_ACCT].[CE0652000]
1.14.6.2.2.15 *XDIM_ADDMEMBERSET (Standard only)
With the keyword XDIM_ADDMEMBERSET, the logic can merge a specific set of members with the members
passed in the region for which the logic should be executed. This instruction is similar to the instruction
*XDIM_MEMBERSET. The difference is that, while XDIM_MEMBERSET redefines the region passed by the user,
XDIM_ADDMEMBERSET adds the defined set to the passed region.
*XDIM_ADDMEMBERSET {dimension} = {members set}
 Example
*XDIM_MEMBERSET P_ACCT = bas(CE0004000)
*XDIM_ADDMEMBERSET P_ACCT = CE0004210
[TIME].[#2009.DEC] = [TIME].[2006.DEC] * 1.1
*COMMIT
In the above example, CE0004210 is scoped along with all children of CE0004000.
1.14.6.2.2.16 *XDIM_MAXMEMBERS (Standard only)
When the number of records being processed is too large, performance can deteriorate significantly. Also,
processing too much data in the memory will slow down the system for other uses and eventually run out of
memory. For example, an TSV_TNEW_PAGE_ALLOC_FAILED ABAP dump can occur even with high Roll
memory settings. In this case, you can break the action into multiple packets and execute them sequentially
using the following syntax:
*XDIM_MAXMEMBERS {dimension} = {max number of members}
 Example
*XDIM_MEMBERSET TIME = 2009.JAN
*XDIM_MEMBERSET CATEGORY = FCST_LOAD
*XDIM_MAXMEMBERS P_ACCT = 5
*RUNALLOCATION
*FACTOR=1/12
*DIM TIME WHAT = 2009.JAN; WHERE = BAS(2009.TOTAL);
*DIM CATEGORY WHAT = FCST_LOAD; WHERE = FORECAST;
*ENDALLOCATION
Assuming the whole year's forecast initially loaded 2009.JAN and FCST_LOAD, the above script allocates
the data equally to each period in 2009. The script logic engine reads the data in packages split by P_ACCT
members, with each package containing a maximum of five P_ACCT members, until it reaches the end in
P_ACCT dimension members.
1.14.6.2.2.17 *XDIM_PACKAGEBY (Standard only)
Defines the dimension for which to partition packages during script logic execution. Packages start in parallel
mode for better performance.
You can specify the server group using a parameter in IMG. Run transaction SPRO, then choose Business
Planning and Consolidation Global setting PARALLEL_SERVER_GROUP .
*XDIM_PACKAGEBY {Dimension name} [ = {Package number} ]
Package number is an optional parameter having a default value of 2.
 Example
*XDIM_PACKAGEBY ENTITY
In the example above, two packages are created and partitioned by the dimension ENTITY.
 Example
*XDIM_PACKAGEBY ACCOUNT = 4
Four packages are created are partitioned by the dimension ACCOUNT.
 Note
● You can use the *XDIM_PACKAGEBY keyword only once in each script.
● Parallel mode is triggered ONLY when the member number for the dimension that is defined with
*XDIM_PACKAGEBY is greater than 1.
● The following keywords do not support PACKAGEBY: *RUN_PROGRAM, *RUNALLOCATION,
*CALL_CUSTOM_LOGIC, and *START_BADI.
1.14.6.2.2.18 *XDIM_FILTER (Standard only)
XDIM_FILTER brings all members when the specified condition is met. This keyword returns only base
members.
 Example
*XDIM_MEMBERSET Category = PLAN
*XDIM_MEMBERSET Entity = C3000
*XDIM_MEMBERSET P_DataSrc = MANUAL
*XDIM_MEMBERSET RptCurrency = LC
*XDIM_MEMBERSET P_Activity = EMPL1
*XDIM_MEMBERSET P_ACCT = CE0004220
*XDIM_FILTER Time = [Time].properties("MONTHNUM") = "2"
*WHEN P_ACCT
*IS CE0004220
*REC (EXPRESSION = 888)
*ENDWHEN
*COMMIT
The code in this example writes only FEB records for CE0004220.
1.14.6.2.2.19 *COMMIT (Standard only)
A logic file can contain formulas that depend on the result of calculations performed by the model, and these
calculations in turn depend on the results of other formulas in the same logic.
 Example
[P_ACCT].[#CE0004030] = ( [P_ACCT].[CE0004010] + [P_ACCT].[CE0004020] ) * 0.15
[P_ACCT].[#CE0661000] =
( [P_ACCT].[CE0004010] + [P_ACCT].[CE0004020] + [P_ACCT].[#CE0004030] ) /

[P_ACCT].[CE0652000]
In this example, CE0661000 depends on the first calculation, and this calculation in turn depends on the
calculation of CE0004030.
The logic, if written in the above format, does not work correctly, because CE0004030 cannot be retrieved
from the model until its result has been posted to the model. To get the right results, CE0004030 must be
calculated AND stored in the model. THEN, the calculated result can be retrieved from the model and be used
to calculate CE0661000.
To force a write back of the result of the calculation of CE0004030 into the model before the calculation of
CE0661000, you can insert the instruction *COMMIT between the two calculations. The logic then works when
written as follows:
 Example
[P_ACCT].[#CE0004030] = ( [P_ACCT].[CE0004010] + [P_ACCT].[CE0004020] ) * 0.15
*COMMIT
[P_ACCT].[#CE0661000] =
( [P_ACCT].[CE0004010] + [P_ACCT].[CE0004020] + [P_ACCT].[CE0004030] ) /

[P_ACCT].[CE0652000]
In this case CE0004030 in the second formula does not have the pound sign (#), because it is a stored
amount read from the model.
 Note
Any number of commit instructions can be entered in a logic file. However, the number of commit
instructions should be kept to the minimum, because they have a negative impact on the overall
performance of the logic execution due to increased communication between the database and script logic
engine. The ideal case is to have one commit at the end.
1.14.6.2.2.20 Special Keywords (Standard only)
The following are special keywords:
SET
An implied keyword is available for each dimension, which holds the set of members passed to the logic engine
for a given dimension. This keyword can be used as a replacement string anywhere in the logic.
%{DimName}_SET%
{DimName} is the name of a valid dimension in the model. For example the keyword %INTCO_SET% contains
the set of members passed to the logic for the dimension INTCO.
This keyword can be used anywhere in the logic and not just within some specific statement like
XDIM_MEMBERSET.
This keyword is not modified by the XDIM_MEMBERSET instruction, as it always returns the original set passed
to the logic.
This keyword does not return a default set if no set is passed. Its default is an empty set.
DIM
Another type of implied keywords is available for each nonuserdefined dimension. This keyword holds the
actual name of a dimension of a given type, and can be used as a replacement string to use anywhere in the
logic.
%{DimType}_DIM%
{DimType} is the type of dimension.
 Example
If, in a model, the category dimension is called SCENARIO, the keyword %CATEGORY_DIM% returns the
word SCENARIO.
Valid types are:
● ACCOUNT
● CATEGORY
● TIME
● ENTITY
● INTCO
● CURRENCY
● DATASRC
Using Data Manager Prompts
In most of the script executions, you need to get user selection and use that value inside the logic script. For
this purpose, you can use Data Manager prompts inside the logic.
Syntax
$DM_PROMPT$...
 Example
*XDIM_MEMBERSET P_ACCT= CE0004020, CE0004010
*XDIM_MEMBERSET CATEGORY = ACTUAL
*XDIM_MEMBERSET TIME=2006.SEP
*XDIM_MEMBERSET ENTITY= C9000
*XDIM_MEMBERSET P_ACTIVITY=NONE
*XDIM_MEMBERSET P_DATASRC=UPLOAD
// Increase Wage and Salary, and Personnel Expense by entered percentage
[P_ACCT].[#CE0004020] = [P_ACCT].[CE0004020] * ( 1 + $WS_PERCT$ / 100) [P_ACCT].

[#CE0004010] = [P_ACCT].[CE0004010] * ( 1 + $EXP_PERCT$ / 100)
The percentage to be increased for the above two accounts is provided by the user.
 Note
Additional configuration is required in the Data Manager to pass these parameters to script logic. In
transaction RSPC in the ABAP layer, the corresponding process chain's BPC:Run Logic step, Process
Variant, needs to be maintained with additional parameters like TAB, SUSER, and REPLACEPARAM.
Then, the dynamic script of Data Manager needs to be adjusted to accept the prompts.
PROMPT(SELECTINPUT,,,,"%ENTITY_DIM%,%CATEGORY_DIM%,%CURRENCY_DIM%,%TIME_DIM%")
PROMPT(TEXT,%WS_PERCT%,"Input W/S Percent in decimals",)
PROMPT(TEXT,%EXP_PERCT%,"Input Exp. Percent in decimals",)
INFO(%EQU%,=)
INFO(%TAB%,;)
TASK(ZBPC_PROT_EXP_RUN_LOGIC,TAB,%TAB%)
TASK(ZBPC_PROT_EXP_RUN_LOGIC,EQU,%EQU%)
TASK(ZBPC_PROT_EXP_RUN_LOGIC,SUSER,%USER%)
TASK(ZBPC_PROT_EXP_RUN_LOGIC,SAPPSET,%APPSET%)
TASK(ZBPC_PROT_EXP_RUN_LOGIC,SAPP,%APP%)
TASK(ZBPC_PROT_EXP_RUN_LOGIC,SELECTION,%SELECTION%)
TASK(ZBPC_PROT_EXP_RUN_LOGIC,LOGICFILENAME,TESTING0123.LGF)
TASK(ZBPC_PROT_EXP_RUN_LOGIC,REPLACEPARAM,WS_PERCT%EQU%%WS_PERCT%%TAB%EXP_PERCT%EQU
%%EXP_PERCT%)
 Note
Read the restriction around Validation when DM prompts are used in your script in OSS note 1334695.
Script Logic System Variables
%USER% - Returns the current Business Planning and Consolidation user
%APPSET% - Returns the current Business Planning and Consolidation environment
%APPLICATION% - Returns the current Business Planning and Consolidation model
%YEAR% - Returns the current calendar year
You can use %YEAR% to derive the member values. For example, %YEAR%.TOTAL, and %YEAR%.Q1. You can also
use to offset years like %YEAR%(-2).TOTAL.
1.14.6.2.2.21 TMVL Parameter (Standard only)
Use
This optional parameter returns a time value after taking into consideration an offset value from a given time
period.
Prerequisites
This function works only with base member values.
Activities
The format for this parameter is TMVL(offset, base_period). Utilize this parameter following these guidelines:
● Offset can be either negative or positive. Only integers are allowed.

● The base period can be a hardcoded value such as 2009.MAY, a Time script variable such as %TIME_SET%,
or a Data Manager Prompt variable such as $CURPER$.
 Note
Nested TMVL parameters such as TMVL(-1, TMVL(-3, 2009.JAN)) ) are not supported.
You can use TMVL in:
● FACTOR/EXPRESSION within REC

● FOR/NEXT loops
● IS conditions inside WHEN/ENDWHEN.
● variables, like %TIME_SET%
The first period of the TIME_SET is used as the base period for a negative offset and the last period of
the TIME_SET is used as the base period for a positive offset.
● scope statements
Multiple separate (not nested) TMVLs can be used in one scope statement.
When 0 is used as offset, no offset will be done for the provided time member.
 Example
In this example, Actual data records are copied over to the same period in the following year with a 10
percent increase. The existing data is shown in the following table:
Category Entity P_ACCT P_Activity P_DataSrc RptCurrency Time SignData
ACTUAL C9000 CE0004010 NONE UPLOAD LC 2006.APR 100,891.26
The script used is the following:
*XDIM_MEMBERSET P_ACCT= CE0004010, CE0004020, CE0004210
*XDIM_MEMBERSET CATEGORY = ACTUAL
*XDIM_MEMBERSET ENTITY= C9000
*XDIM_MEMBERSET P_ACTIVITY=NONE
*XDIM_MEMBERSET P_DATASRC=UPLOAD
*XDIM_MEMBERSET TIME = 2006.APR
*WHEN CATEGORY
*IS ACTUAL
*REC(FACTOR=1.1, TIME=TMVL(12,2006.APR))
*ENDWHEN
The data that results from running the logic script is shown in the following table:
1.14.6.3 US Eliminations as Script Logic (Standard only)
You use this to control where the results of eliminations are stored in an Entity dimension.
Activities
The intercompany eliminations process is handled by a program called US_ELIM. This program is launched
using the following logic statement:
*RUN_PROGRAM US_ELIM( <parameters list>)
Example
*RUN_PROGRAM US_ELIM
CATEGORY = %C_CATEGORY_SET%
GROUP = %GROUPS_SET%
TID_RA = %TIME_SET%
OTHER = [ENTITY=%ENTITY_SET%]
*ENDRUN_PROGRAM
Related Information
US Eliminations Rule (Standard only) [page 280]
1.14.6.4 Carry-Forward as Script Logic (Standard only)
You use this program 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.
Activities
The copy-opening process is handled by a class called CL_UJP_COPYOPENING. This program is launched using
the following logic statement:
*RUN_PROGRAM COPYOPENING( <parameters list>)
Example
*RUN_PROGRAM COPYOPENING
CURRENCY = %GROUPS_SET%
TID_RA = %TIME_SET%
*ENDRUN_PROGRAM
Related Information
Carry-Forward Rule (Standard only) [page 279]
1.14.6.5 Intercompany Booking as Script Logic (Standard
only)
You use this to run Intercompany booking as well as difference posting.
Activities
Intercompany reconciliations processes are handled by a program called ICBOOKING.
Running the following in an ICDATA.LGF logic file runs Intercompany reconciliation:
*RUN_PROGRAM ICBOOKING ( <parameters list>)
 Example
*RUN_PROGRAM ICBOOKING
CATEGORY = %CATEGORY_SET%
CURRENCY = %GROUPS_SET%
DATASRC = INPUT// value of datasrc dimension member that represents the input
datasrc
TID_RA = %TIME_SET%
ENTITY = %ENTITY_SET%
ACCOUNT = %ACCOUNT_SET%
FLOW = %FLOW_SET%
TYPE = I
*ENDRUN_PROGRAM
Running the following in an ICBOOKING.LGF logic file runs Intercompany reconciliation and difference
posting:
*RUN_PROGRAM ICBOOKING ( <parameters list>)
 Example
*RUN_PROGRAM ICBOOKING
GROUP = %CATEGORY_SET%
TID_RA = %TIME_SET%
*ENDRUN_PROGRAM
Related Information
Intercompany Booking Rule (Standard only) [page 278]

Eliminations and Adjustments Rule for Legal Consolidation (Standard only) [page 282]
1.14.6.6 Currency Conversion as Script Logic (Standard only)
You use this to run a new logic file currency conversion. Currency conversion typically runs by default when
default logic runs.
Activities
Currency conversion is handled by a program called CURR_CONVERSION. This program is launched using the
following logic statement:
*RUN_PROGRAM CURR_CONVERSION( <parameters list>)
You must also set up the following list of attributes for relevant dimensions in addition to the required
attributes:
Dimension Attribute
ACCOUNT RATETYPE
DATASRC DATASRC_TYPE (I, M, A, or L)
IS_CONVERTED (Y, G, or N)
ENTITY CURRENCY (local currency)
FLOW FLOW_TYPE (used to find the closing flow)
CURRENCY CURRENCY_TYPE (currency type - Reporting, Local, or

group)
Dimension Attribute
TIMEID YEAR
PERIOD
TIMEID
MONTHNUM
INPUTCURRENCY (with Rate cube) MD (indicator of multiple or divide)
The Datasrc dimension is not mandatory for planning, and currency translation can be run without this
dimension. If you choose to include a Datasrc dimension in a planning cube, the attributes must be set up as
they are checked in the currency conversion program.
In addition, the Flow dimension is not mandatory for planning, and currency translation can be run without this
dimension. If you choose to include a Flow dimension in a planning cube, the attribute needs to exist in the
flowtype dimension to enable currency conversion.
Example
*RUN_PROGRAM CURR_CONVERSION
CATEGORY = %C_Category_SET%
GROUP = %GROUPS_SET%
TID_RA = %TIME_SET%
RATEENTITY = Global
*ENDRUN_PROGRAM
 Note
Global should be the valid member ID that is set in the RATEENTITY dimension.
The example shown above contains the line OTHER = [ENTITY=%ENTITY_SET%]. The Other filter
supports the dimensions ENTITY, DATASOURCE, and AUDIT. The OTHER filter does not support user
defined dimensions.
Related Information
1.14.6.7 Account-based Calculations as Script Logic

(Standard only)
You use this to run an account-based calculation rule.
Activities
You run this program using the following logic statement:
*RUN_PROGRAM CALC_ACCOUNT( <parameters list>)
Example
*RUN_PROGRAM CALC_ACCOUNT
CURRENCY = %CURRENCY_SET%
TID_RA = %TIME_SET%
CALC=A
OTHER = [ENTITY=%ENTITY_SET%]// or OTHER=[ENTITY=C1000] or [ENTITY=%ENTITY_SET

%;INTCO=%INTCO_SET%...]
*ENDRUN_PROGRAM
 Note
If there is no other scope against which you need to run the program, delete the OTHER line in the script.
Related Information
Account-based Calculation Rule (Standard only) [page 271]
1.14.6.8 Business Rules Management (Standard only)
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:
● Intercompany booking to match intercompany transactions
● 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.
Activities
You can run a business rule as follows:
● Perform a data send.

When you send data using the EPM add-in for Office or SAP Business Planning and Consolidation, the
system runs the default logic indicated in default.lgf. For example, the default logic can execute the
currency translation business rules. While you can add any logic or business rule execution to the default
script, it is not recommended, as performance may decrease when sending data.
● Run a Data Manager package that contains a reference to a logic file (*.LGF).
Logic can be applied to a specified region of data that is stored in the database using any type of logic. You
can create new logic files or modify existing ones. For example, an Import package runs against the default
logic unless the Import package is modified to include other logic files. Each logic file contains one or more
ABAP programs that run a specific set of logic commands. Business rules execution can be triggered in
any logic file.
● Post a journal entry.
Upon posting a journal, the system runs logic that is specific to journal processes. To overwrite the default
journal logic, you can create a new script logic file called Journal.lgf. Business rules execution can be
triggered in the journal logic file.
In SAP Business Planning and Consolidation, currency translation and consolidation processes can also be
executed from the Consolidation Monitor.
Related Information
Account-based Calculation Rule (Standard only) [page 271]

Intercompany Booking Rule (Standard only) [page 278]
Carry-Forward Rule (Standard only) [page 279]
US Eliminations Rule (Standard only) [page 280]
Eliminations and Adjustments Rule for Legal Consolidation (Standard only) [page 282]
1.14.6.8.1 Account-based Calculation Rule (Standard only)
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.
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)
● Datasource (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 both financial and legal consolidation models.
Example
You can use this business rule to calculate and post values that you need for cash flow reporting.
Related Information
Account-based Calculations as Script Logic (Standard only) [page 268]
1.14.6.8.2 Currency Translation Rule (Standard only)
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 as a separate task using a Data Manager package. They can also be
executed from the Consolidation Monitor in the Consolidation Central area.
Prerequisites
Currency translation applies to both financial and legal consolidation models to which a corresponding rate
model 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.
If you need to store data in the local currency of the entity and also convert it to one or more reporting or group
currencies, a currency type dimension must exist. In addition, the system must access a rate model that stores
the exchange rates used for the automatic translation. The following list provides a summary of the
environment requirements to support currency translation:
● The environment must include a rate model where exchange rates are stored. You must assign this rate
model to any model that utilizes it.
● The model itself must include a currency type dimension and possibly a Group dimension.
● The Currency (R type) dimension must include 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. The value G for group currency is used only if the currency dimension is also used to
manage groups. This value is only relevant for models migrated from a previous version of SAP
● For Consolidation type 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 listed in the currency dimension of the Rate model.
● The Account (A type) dimension must include the property RATETYPE, whose values are valid accounts in
the rate model.
● The Time (T type) dimension must include the properties YEAR, PERIOD, TIMEID, and MONTHNUM.
● The Audit dimension is not mandatory for currency translation, but if you include it, the dimension must
include the following properties:
○ DATASRC_TYPE, whose values include the following:
○ I - Input
○ M - Manual Adjustment
○ A - Eliminations and Adjustments
○ L - Audit level (use only for consolidation)
○ 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
● 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 rate model must include the property MD, whose values
are M for multiply rates or D for divide rates.
● The appropriate FXTRANS logic must be available.
The default translation reads all values in local currency where currency = LC, applies the correct exchange rate
according to the applicable rate model, 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 and converts all accounts with a blank rate type with a factor 1.
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.
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

● the ability to distinguish between Multiply currencies and Divide currencies
Conditions 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. For this mode, make sure the script is similar to the following:
CURRENCY = %RPTCURRENCY_SET%
TID_RA = %TIME_SET%
RATEENTITY = GLOBAL
......
*ENDRUN_PROGRAM
Pay attention to the keyword CURRENCY. If running currency translation for the reporting currency, the
keyword on the left side should be CURRENCY. If running currency translation for a group, use the keyword
GROUP.
● Group mode
Group mode converts subsidiaries' data to a group's currency. This is mainly used before consolidation.
Whatever mode the currency translation runs in, the following conditions must be satisfied:
● The model must contain only one Currency (type R) dimension.

● The model must contain only one Group (G type) dimension if the model is a Consolidation model.
For consolidation models migrated from previous versions of SAP Business Planning and Consolidation,
this dimension is not mandatory, in order to ensure compatibility with the current version.
● The reporting model must reference the RATE model.
● 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 a valid key
member in the rule table for
currency translation, 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
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)
Main Time YEAR The YEAR property contains

the year information of the
ID. For example, if the ID is
2016.AUG, YEAR is 2016.
Main Time PERIOD The PERIOD property de

notes the period to which
the current time belongs.
For example, if the ID is
2016.AUG, PERIOD is AUG.
Main Time TIMEID The TIMEID property is a

numerical value for the cur
rent time. For example, for
2016.AUG, the TIMEID is
20160800.
Main Time MONTHNUM The MONTHNUM is defined to

identify the closing period of
a year. It's a number that
stands for the chronological
sequence of the base mem
ber in a Time dimension hi
erarchy during the same
year. For example, for
2016.AUG, the MONTHNUM is
8.
The base member can be ei

ther a month or a day, de
pending on your cofigura
tion.
When optional dimensions such as Audit and Flow (S type dimension) do not exist, currency translation still
runs successfully. However, if they do exist, they impact the translation process. In this case, the following
properties in these 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.
To run currency translation in reporting currency mode, the mandatory condition mentioned previously should
be satisfied. If optional dimensions such as Audit and Flow (S type dimension) exist, the condition of the
optional dimension is also necessary.
To run currency translation in group mode, beside the same requirement as reporting currency mode, the
following additional conditions are mandatory:
● The Ownership model must be set up and referenced.

● In migrated consolidation models only, Group information must be maintained in a separate Group
dimension (except for models migrated from previous versions, where Groups can be maintained in a
Currency dimension).
When using the Currency dimension, Currency and Group information resides in the same dimension. The
following properties are needed in Currency 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 CURRENCY 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 gGoup, 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.
When currency and group reside in one dimension, make sure the script file is similar to the following
before running currency translation for the group:
GROUP= %GROUPS_SET%
TID_RA = %TIME_SET%
RATEENTITY = GLOBAL
......
*ENDRUN_PROGRAM
Pay attention to the keyword GROUP. If running currency translation in group mode, the keyword GROUP
should be used instead of CURRENCY.
In SAP Business Planning and Consolidation, when building a consolidation, both a group dimension and a
currency dimension are required. Therefore, consolidation group members and currency members are
held separately.
A new dedicated dimension, for example, Group, should be type G.
When maintaining time properties, note that consolidation-related programs are allowed to run against base
members in the same year only. The four properties of 'TIMEID', 'YEAR', 'PERIOD' and 'MONTHNUM' of base
members affect those programs.
● Properties of parent nodes have no effect on those programs, and the value for these 4 properties should
not be empty.
● The value for 'TIMEID' should be unique for each base member.
● The value for 'YEAR' should be a four digit number for each base member.
● The value for 'PERIOD' should be unique for each base member in the same 'YEAR'. SAP suggests that
'JAN', 'FEB', and so on are used for Month members and that 'week01' or 'W01' for are used for week
members.
● The value for 'MONTHNUM' should be unique for each base member in the same 'YEAR'. It should be a
number that stands for the chronological sequence of the corresponding base member during the same
year.
● Example for DAY members:
ID Period TIMEID MONTHNUM PARENTH1
2016.TOTAL TOTAL 365
2016.Q1 Q1 90 2016.TOTAL
2016.JAN JAN 031 2016.Q1
2016.08.01 DAY1 20160801 213 2016.AUG
ID Period TIMEID MONTHNUM PARENTH1
2016.08.20 DAY20 20160820 232 2016.AUG
● In addition, the following is an example of a time dimension for Jan 12th 2016:
ID TIMEID Year Period MONTHNUM Base Period
2016.1.12 20160112 2016 D12 012 012
Related Information
Currency Conversion as Script Logic (Standard only) [page 266]

1.14.6.8.3 Intercompany Booking Rule (Standard only)
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 are 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 allows intercompany details to be entered for any account and 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
Intercompany booking records the declarations and reported balances by other entities against a particular
entity. This allows business users within each reporting entity to run a report that matches all of its
declarations and reported balances against the balances of the rest of the entities, without having to assign to
each owner read-access for other entities. Bookings that make the Intercompany declarations match can be
automatically generated and details can be posted to the consolidation model.
You use the Intercompany Booking business rule table to define the posting rules the system uses in generating
the entries to match the Intercompany balances and declarations.
The consolidation engine supports a mechanism to perform the matching of the intercompany declarations
among the entities of a group. This mechanism is split into two independent procedures as follows:
● ICDATA: This procedure copies the declarations of all entities versus a given entity by intercompany
account. 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 of its declarations against everything
else that has been declared against it, without the need to assign to each owner read permision into other
entities.
● Intercompany Booking: This procedure can be used to automatically generate the bookings that 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 larger than this maximum value are kept for manual adjustment later.
Intercompany bookings are executed from the Consolidation Monitor in the Consolidation Central area.
Related Information
Intercompany Booking as Script Logic (Standard only) [page 265]
1.14.6.8.4 Carry-Forward Rule (Standard only)
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 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.
In a legal consolidation model, such flows are often identified as members of a dedicated dimension. In simpler
models, however, it is also possible to store them as additional accounts in the Account dimension.
Related Information
Carry-Forward as Script Logic (Standard only) [page 264]
1.14.6.8.5 US Eliminations Rule (Standard only)
US eliminations functionality addresses the posting of Intercompany US eliminations in scenarios where a full
legal consolidation model is not required, such as within a standard financial model.
Prerequisites
The following are required to perform Intercompany eliminations within a model:
● The model must include a dimension of type I, Intercompany.

● The Intercompany dimension must include the property ENTITY, whose values are entity names.
● The account dimension must include the property ELIMACC, whose values are account names.
● The entity dimension must include the property ELIM, whose values are Y or blank.
● A Data Manager package executing the Intercompany logic must be available. 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.
Features
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 model is not required, such as within a standard financial model. When utilizing a legal
consolidation model, Intercompany eliminations are normally handled as part of an eliminations and
adjustments function.
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.
US eliminations are normally used in financial models as opposed to legal consolidation models.
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
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 (entities having the property ELIM <> Y).
● In case the model has a currency dimension, restricts its action to all reporting currencies only (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 (accounts having property ELIMACC<>blank) into the
desired plug account (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 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 in the immediate descendants of the common parent for a valid elimination
entity (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 (hierarchy) of the entity
dimension. This can be modified to have the elimination performed in all hierarchies existing 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.
More Information
For the execution of the US Elimination rule, refer to US Eliminations as Script Logic (Standard only) [page 263]
and Execute Consolidation Task (Standard only) [page 185].
1.14.6.8.6 Eliminations and Adjustments Rule for Legal

Consolidation (Standard only)
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 as a separate task using a Data Manager package. They can also be
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 cube, 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 environment before performing the eliminations and adjustments:
● Ownership Model
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
 Note
You can use a common dimension for both currency and group ONLY in models migrated from version
7.5. In SAP BusinessObjects Planning and Consolidation 10.0 and 10.1, you must use two separate
dimensions - one for group and one for currency.
● Method-based multipliers
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 model.
When eliminations and adjustments rules are executed for a given group, the system performs the following:
● Reads from the ownership model 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
○ D: for entities that leave the group/scope in the middle of the year
○ 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 (Standard only) [page 288].
● 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 userdefined 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.
Related Information

Method-based Multipliers and Consolidation Methods (Standard only) [page 285]
1.14.6.8.6.1 Method-based Multipliers and Consolidation
Methods (Standard only)
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:
● Consolidation methods
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 model in the environment.
Consolidation methods
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.
1.14.6.8.6.2 Integration Rule for Consolidation (Standard

only)
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 by checking the Consolidation-Use Integration Rules option.
4. Save the change.
1.14.6.9 Business Rules Management (Embedded only)
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:
● Intercompany booking
● Carry-forward processing to initialize beginning balances when a new fiscal cycle starts
● 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 for source members of dimension type account
(A), category (C), audit (D), flow (S), but not for destination members of dimension type account (A),
category (C), audit (D), flow (S), 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 (Embedded only) [page 206]
1.14.6.9.1 Account-based Calculation Rule (Embedded only)
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.
1.14.6.9.2 Currency Translation Rule (Embedded only)
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, whose values are valid accounts in
the EXCHANGE RATE InfoProvider.
● 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:
Main Account RATETYPE The value of the RATETYPE

property must be a valid key
member in the rule table for
currency translation, 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
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.
1.14.6.9.3 Intercompany Booking Rule (Embedded only)
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 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.
1.14.6.9.4 Carry-Forward Rule (Embedded only)
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.
1.14.6.9.5 US Eliminations Rule (Embedded only)
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.
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:
Account ELIMACC 20 A valid account against which

the actual intercompany ac
count to be eliminated
should be offset
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 (Embedded only) [page 48]
1.14.6.9.6 Eliminations and Adjustments Rule for Legal
Consolidation (Embedded only)
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 (Embedded only) [page 305].
● 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 userdefined 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.
1.14.6.9.6.1 Method-based Multipliers and Consolidation
Methods (Embedded only)
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
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.
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.
1.14.6.9.6.2 Integration Rule for Consolidation (Embedded

only)
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.
1.14.6.10 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 Number Step Additional Information
Business Planning and Con 1. Associate a level to each entity in the entity
solidation Administration dimension
2. Enable controls for a selected model
3. Create controls Define control level, toler

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

nation
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, which is given as follows.
● In a standard configuration of Business Planning and Consolidation, you can go to Security Task
Profile to create and assign corresponding tasks to teams or users.
● In an embedded configuration of the product, 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. For more information, see Control Set Status (Standard only) [page 26].
Enable controls
Controls can be enabled or disabled at the model level in Planning and Consolidation Administration. In an
embedded configuration of Business Planning and Consolidation, controls can be enabled only in a
consolidation type model.
Before enabling controls, do the following:
● In a standard model, make sure the Entity dimension contains two properties: Control Level and
CTRL_CURRENCY_NOT_LC (Bypass LC in Ctrls).
● In an embedded model, 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 309].
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 319].
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 319].
1.14.6.10.1 Create a Control
This topic contains information about creating a control.
Prerequisites
For an embedded model, an administrator has given you the Edit Controls Manager right.
In a standard model, you need to make sure that a value has been specified for the MONTHNUM property in the
Time dimension.
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 (Embedded only)
● Tolerance Threshold
● Expressions
● Documents （Standard only）
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. See Execute a Control
Set (Standard only) [page 25]. 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. For more information on entity control levels, see
Control Set Status (Standard only) [page 26].
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 (Embedded only)
As data stored in an embedded configuration of the system 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 (defined in the upper panel) is compared to
zero.
Documents (Standard only)
In a standard configuration of the system, Microsoft Excel input schedules and reports, as well as input forms
and web reports from Business Planning and Consolidation, can be attached to controls. Later, if you have
failed to run a control in Control Monitor and you then choose Open Controls Results, you can directly navigate
to the attached document to aid you in problem-solving the issue.
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.
1.14.6.10.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 316]
Copy a Control Set [page 317]
Delete a Control Set [page 318]
Assign a Control Set [page 319]
Additional Actions Involving Control Sets [page 319]
1.14.6.10.2.1 Create a Control Set
Prerequisites
To edit controls in Planning and Consolidation Administration, you must have the Edit Controls Manager
right. In a standard configuration of the product, you can go to Security Task Profile to create and assign
corresponding tasks to teams or users. In an embedded configuration, you can follow the steps in
“Authorization for Performing Consolidation Tasks” in the Security Guide 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 314]

1.14.6.10.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

1.14.6.10.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

1.14.6.10.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

1.14.6.10.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

1.14.6.10.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

1.14.7 Business Process Flow Management
Use
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. It allows the
user to see only the tasks relevant for that user, given his or her role and data access privileges.
Prerequisite
In Business Planning and Consolidation in a standard configuration, you must have the Manage BPFs task
profile assigned to you in order to manage business process flows.
In Business Planning and Consolidation in an embedded configuration, 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 322].
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.
Function More Information
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 in the
left-right corner.
Archive process templates (standard only) You can archive process templates. When you archive a
process template, all processes based on the template must
be completed beforehand because they will also be archived.
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
342].
1.14.7.1 Creating New Process Templates
Use
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. In
Business Planning and Consolidation in a standard configuration, you must also enter the controlling
model. See Process Settings [page 323].
4. On the Activities tab add activities to represent the flow of the business process. See Activities [page 325].
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 335].
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 339].
1.14.7.1.1 Process Settings
Use
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.
Features
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.
Item Description
Model (standard only) The model governs both identity dimensions, including the
time dimension for process instances and the available di
mensions for activity context.
If, for example, you select the Planning model, whose Time
dimension is in monthly increments, the process template
works in monthly time increments, as well.
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 the identity dimension(s) must be specified
every time a new BPF instance is created.
 Note
In Business Planning and Consolidation in a standard
configuration the system automatically selects the
Time dimension, since it is required for all processes.
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 (embedded When this checkbox is selected, you can reopen the current
activity if you are the performer or reviewer of the activity.
only)
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 332].
Check only the current step when reopening (standard only) By default you must be the performer or reviewer of both the
current activity and the next open activity to reopen the cur
rent activity.
For detailed information about how to change default set

tings so you can reopen the current activity as the performer
or reviewer of the activity, refer to Criteria for Reopening Ac
tivities [page 332]
You can use navigation attributes in an embedded configuration of Business Planning and Consolidation, which
allows you to select certain attributes as identifying dimensions or driving dimensions in a process template.
When you define an attribute as a navigation attribute in an InfoObject, the navigation attribute displays in the
corresponding InfoProvider. Then, when you enable the checkbox in the On/Off column of the navigation
attribute, you can use the attribute in the Business Planning and Consolidation web client. For detailed
information about using navigation attributes, refers to the chapter “Attribute” available in SAP NetWeaver 7.5
help page on help portal.
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 325].
1.14.7.1.2 Activities
Use
You can create activities that form part of a process. For guidelines on defining activities, see Criteria for
Defining Activities [page 328].
Features
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 330].
Allow Reopen To allow authorized users to reopen an activity, select the

checkbox.
For more information, see Criteria for Reopening Activities

[page 332].
Driving Dimension
Item Description
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.
 Note
In a standard configuration of Business Planning and
Consolidation, this dimension must have a defined Re
viewer property.
For more information, see Defining Activity Context Criteria

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

opens the Criteria 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 329].
Map Driver to (embedded only) Create a mapping between the driving dimension and an in
ternal dimension. For more information, see Internal and Ex
ternal Driving Dimensions (Embedded only) [page 335].
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
In an embedded configuration of Business Planning and
Consolidation, a property of a dimension is an attribute
of a characteristic in BW. You can maintain BW charac
teristics in BW modeling tools. For more information,
see the BW documentation that is available at http://
help.sap.com/nw75.
For more information, see Defining Actions [page 335].
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 334].
Activity Workspace By choosing Create you can create hyperlinks. In a standard

configuration of Business Planning and Consolidation, you
can also create reports and input forms.
Activity Reviewer
Require Reviewer If required, select this checkbox and select a property that
defines the reviewer for each member.
Item Description
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 335].
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 334].
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 335].
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 334].
1.14.7.1.2.1 Criteria for Defining Activities
Use
You define activities for a BPF template in the Administration screen. For more information, see Activities [page
325].
Each process must contain at least one activity.
The following are guidelines for defining activities:
● Activities have defined criteria to control the activity context, opening of activities, review criteria, and
reopening of activities if required.
● In Business Planning and Consolidation in a standard configuration you must associate at least one
action with an activity.
● 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 performers 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.
1.14.7.1.2.2 Defining Activity Context Criteria
Use
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.
 Note
In Business Planning and Consolidation in a standard configuration the driving dimensions are
displayed according to the model that you selected in the Process Settings tab.
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 (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, it defaults to
Single Member, which just includes 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.
 Note
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).
3. In Business Planning and Consolidation in a standard configuration, select the property of the
dimension, which contains valid user IDs for the owner. For more information, see Owner Property
1.14.7.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:
1 Entity Italy Complete
1 Entity France Open
2 Entity Italy Open
2 Entity France Pending
1.14.7.1.2.4 Criteria for Reopening Activities
Use
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.
Features
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 instance owner you can reopen an activity, regardless of performer 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 steps:
● In Business Planning and Consolidation in an embedded configuration, select the option Check only the
current step when reopening in the Process Settings page when creating or modifying a process template.
● In Business Planning and Consolidation in a standard configuration, trigger the reopen rule in BW IMG by
perform the following steps:
● 1. Log on to Business Warehouse and enter transaction SPRO to open the IMG page.
2. Click SAP Reference IMG.
3. First expand the Planning and Consolidation tree, then expand the Confuration Parameters tree node.
4. Click Set Global Parameters.
5. Click Insert to add the parameter BPF_NOT_CHECK_PRE_STEP_AUTH.
6. Set the value of this parameter to Y and save the parameter.
7. Navigate back to the Configuration Parameters page and click Set Environment Parameters.
8. Enter the ID of your environment.
9. Add the same parameter BPF_NOT_CHECK_PRE_STEP_AUTH, set its value to Y, and save the
parameter.
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
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
Activity sion Activity Context Performer Reviewer Status
1 Entity US A B Complete
1 Entity Canada C D Reopen
2 Entity US A B Complete
2 Entity Canada C D Delayed
1.14.7.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 13].
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.
1.14.7.1.2.6 Internal and External Driving Dimensions

(Embedded only)
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.
1.14.7.1.3 Defining Actions
Use
You can assign actions to activities. You can also 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
1. Choose the Create button in the Workspaces field of the Activities tab.
2. Add hyperlinks to target actions and configure them according to the desired outcome.
Note that in the embedded configuration of Business Planning and Consolidation, you can add hyperlinks
only to perform actions of existing elements, such as opening reports or input forms. Therefore, you must
make sure these elements already exist before you start defining actions.
The embedded configuration of Business Planning and Consolidation supports the following types of
hyperlinks:
○ 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.
○ Microsoft Excel - define a hyperlink to an EPM Add-in report or input form. If there are variables set in
the report/input form, you can assign values to them.
○ Library and Document - define a hyperlink to a report or input form. If there are variables set in the
report/input form, you can assign values to them.
○ Analysis Office:
○ Define a hyperlink to a BW query. If the query has variables set in it, you can assign values to these
variables.
○ Define a hyperlink to an AO 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 these
variables once for all by selecting Merge Variables.
○ 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 338].
○ 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 337] (embedded only).
3. Choose Stop Editing and then Save to save your changes.
Repeat for all the actions to be associated with each activity in the process template.
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.
1.14.7.1.3.1 Configuring Links to External Web Applications
(Embedded only)
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).
Note: In version 10.1 SP05, the term "semantic object” was changed to “role”.
Prerequisites for BPF Navigation
You must first configure the web-based application that you want to use as a role in User Interface Add-On for
SAP NetWeaver.
1. Enter Tcode LPD_CUST.

2. Click Create New Launchpad, then input the role name, instance, and description. Use uppercase 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.
For more information, see the documentation of User Interface Add-On for SAP NetWeaver, available on the
SAP Help Portal.
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.
1.14.7.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
In addition, 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.
1.14.7.2 Creating Process Instances
Use
An authorized user can create a process in the Administration screen. You can create up to 24 processes for
each process template.
Generating a process creates all required activities and activity contexts. Once generated, the process 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 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
334].
 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.
Archive To delete process instances that are no longer needed. The

processes to be archived must not be in the status Running.
Refresh To refresh the display after changes have occurred.
1.14.7.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.
When a business process flow activity contains only one action, the email notification contains a link to bring
the user directly to the activity, which supports direct navigation 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. Do one of the following tasks:
○ If you are configuring Business Planning and Consolidation in a standard configuration, execute the
UJB_MAINTAIN_EMAIL_TMPL program.
○ If you are configuring Business Planning and Consolidation in an embedded configuration, 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 C for the standard configuration or Customizing Email Template for the embedded configuration 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]
1.14.7.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.
1.14.7.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.
1.14.8 Work Status Setup
Use
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.
In Business Planning and Consolidation, 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. In a standard
configuration, the owner dimension has an OWNER property to define the work status owner who can change
work statuses. In an embedded configuration, 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 (embedded only) 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.
● Permitted data entry method (standard only) - The manner in which users enter and update data. See
Method of Data Entry 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 (embedded only)
● 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 (embedded only)
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.
Method of Data Entry (standard only)
The areas of Planning and Consolidation for which you can control the level of security are as follows:
● Data Manager (DM) - Controls data input from running a Copy, Import, or Move package
● Journal (JRN) - Controls data input from posting journal entries
● Manual Entry (MAN) - Controls data input manually when creating reports or input forms
● Comments (COM) - Controls data input from posting comments (unstructured data)
● Documents (DOCS) - Controls posting documents with model context to the Document view (unstructured
data)
External Hierarchy Nodes (embedded only)
● 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 in Business Planning and Consolidation in a standard configuration are defined for the entire
environment, not per model.
Work statuses in Business Planning and Consolidation in an embedded configuration 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). In Business Planning and Consolidation in a standard
configuration, you can change the method of update for this state, but not the order or the Controlled by value.
In Business Planning and Consolidation in an embedded configuration you cannot change the Controlled by
value. You can change the text description.
In Business Planning and Consolidation in a standard configuration, the default state allows you to have a
customized behavior for the environment. For example:
● LOCKED for all methods is equivalent to preventing any data update until the work status is advanced to
the next status (1).
● ALL for all methods is equivalent to having all data open for update. This is the default behavior.
● SETUP applies to ALL of the models in the environment.
● WRITEBACK always checks for locks; if there are no locks in the lock table, the system behaves based on
the setup of status (0).
You can change the order of work states. When you do that in Business Planning and Consolidation in a
standard configuration, the system deletes all locks for all models in the environment; in an embedded
configuration, 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. NetWeaver does not support top-down.
● 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 (embedded only)
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 (embedded only)
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.
In Business Planning and Consolidation in a standard configuration, go to the Administration screen and under
the Features section, choose Work Status New .
In Business Planning and Consolidation in an embedded configuration, 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.
In Business Planning and Consolidation in an embedded configuration, select the Set Work State by
InfoProvider checkbox, so that only a given provider is affected by the work status change.
In Business Planning and Consolidation in a standard configuration, you can enable as well as view data lock
settings by model on the lower half of the Work Status screen. To enable or modify them for a model, select the
model and choose Edit. You can enable data locking and select the dimensions to lock the process context, or
disable data locking.
Related Information
Work Status Example (Standard only) [page 350]
1.14.8.1 Work Status Example (Standard only)
Use
The following information is used for the examples shown below.
Work status codes
● Default code is set to Both.

● All methods are open, that is, set to All.
Work State DM JRN MAN COMM DOCS ControlledBy
Locks Not Set All All All All All Both
Started All All All All All Owner
Upload All Locked Locked Locked Locked Manager
Submit Locked Owner All All All Owner
Journal Locked Locked Locked All All Owner
Approve Locked Locked Locked Locked Locked Manager
Model work status dimensions
● Entity is used as the owner dimension.

● Dimensions with Yes are non-owner dimensions.
● Remaining dimensions are not considered when defining the scope or region of the lock.
Code Model Dimension Name Work State
CATEGORY Yes
ENTITY Owner
P_ACCT No
P_ACTIVITY No
P_DATASRC Yes
RPTCURRENCY No
TIME Yes
Entities structure
● Owner of Top entity L1 is the tester's internal user TESTUSER_ALL.

● Remaining parents and children have test owners to help demonstrate the example.
ID CURRENCY DESCRIPTION OWNER PARENTH1
L1 EU Top TESTUSER_ALL
LD1 US Parent 10 TESTUSERC L1
L9000 US Parent 19 TESTUSERD LD1
L9100 US Child 191 TESTUSERE L9000
LD2 US Parent 20 TESTUSERF L1
L8000 US Parent 28 TESTUSERG LD2
L8100 US Child 281 TESTUSERF L8000
L7000 US Child 201 TESTUSERF LD2
Examples
To begin, a user enters data into the model.
● This example uses data for children of entity member L1.

● There are no locks set, so data can be entered freely.
Lock is set by owner
1. Owner TestUserE can set their own entity L9100, and set a parent level non-owner dimension member
2017.Q1.
2. However, the owner cannot view the current status of the entity L9100 and 2017.Q1 since the state is
expanded to the child members for non-owner dimensions (no storage of parent members for non-owner
dimension).
3. The owner can view the individual state by the base member 2017.JAN.
An owner must set Controlledby work states in consecutive order. Upload can be set to Submit, but not to
Journal, as the next work state after Upload is Submit.
This is also true in reverse: an owner cannot set a Controlledby owner work state that is not in order. You
cannot set Journal to Started as this violates two rules:
● The state before Journal is Submit. Therefore, this is the only valid selection.
● Upload is a Controlledby Manager work state, and is in between the Submit and Started work states. The
owner cannot skip a work state that is controlled by a manager.
Lock is set by manager 1
As the first status is an Controlledby Owner status, which is defined as open ( Locks Not Set), the next step is
to have the manager progress to a locking status of Upload.
1. Sign on as TestUserD, the manager of L9100 (owner of L9000).

2. Do not choose On All Descendants in the data region. As a manager, you can update the status for
individual members as long as the status is set to Controlledby Manager.
3. You cannot update the data after the lock is set, as this status locks out manual data entry.
Lock is set by manager 2
1. Sign on as TestUserC, the manager of LD1 (owner of L9000).

2. Attempt to set Controlledby Manager work state for a specific child of L9000 (for example, L9100).
○ Only an immediate parent can set individual children. An error appears: User is not an owner/
manager, work status cannot be updated.
○ If you choose On All Descendants in data region, you can set all children (multi-level setting).
Controlled By Rule
1. Parent L9000 is set to Locks Not Set.

2. If the parent owner attempts to set the work state to Approve, this violates the Controlledby rule as
Approve is a Manager work state. An error appears: The Controlledby rule is violated.
 Note
The owner of a parent is not its own manager. The only exception to this is the top member of the hierarchy.
Bottom Up Rule
● Parent L9000 is set to Locks Not Set.

● Child L9100 is set to Upload; other children are set to None.
1. The owner of parent L9000 attempts to set to the work state to Started, which is Controlledby Owner.
2. This fails due to violation of the bottom up rule: a parent cannot have a status higher than its children. An
error appears: The Bottom-up rule is violated.
Pushing 1
● L9000, a parent owner (manager), can set the work state of all of its children using On All Descendants in
the data region.
1. A manager can skip work states, but they must be Controlledby Manager.
2. If a manager selects a work state that is Controlledby Owner, this violates the Controlledby rule.
3. If the user setting the work state is neither the owner nor the manager of either the specific member or
children of the specified member, an error appears: User is not an owner/manager, work status
cannot be updated.
Pushing 2
● L9000, a parent owner (manager) can set the work state of all its children using On All Descendants in the
data region.
○ The parent member work state is not set when On All Descendants is chosen.
○ Only the parent of L9000 ( LD1) can set a Controlledby Manager work state.
Reversing
● Assume all children of LD1 are approved for 2017.Q1 (JAN, FEB, MAR).
1. The owner of a child member cannot set a work state lower than their parent. This violates the Bottom-up
rule.
2. A parent can reverse the status to any of the Controlledby Manager work states.
All Regions Must Pass Rule
● Assume all children of LD1 are set to Approve for 2017.Q1 (JAN, FEB, MAR).
1. The parent sets all base members for Jan to Locks Not Set.
2. The parent sets remaining months to Approve.
3. The owner of one dimension attempts to set Q1 to Started. This fails because it violates the Bottom-up
rule for January.
1.14.9 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 353].

● Set journal model parameters. See Journal Model Parameters [page 356].
When using the embedded configuration of Business Planning and Consolidation, users must be granted
corresponding authorization objects on the Business Warehouse side to perform these tasks. For detailed
information, refer to the topic “Authorization for Performing Consolidation Tasks (Embedded only)” in the
Security Guide.
1.14.9.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 (cube 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 355].
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 356]
1.14.9.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.
Related Information
Reopen Journal Entries (Standard only) [page 38]
1.14.9.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.
1.14.9.2 Journal Security (Standard only)
Journal security is a component of task security that uses model member access rights to enforce your journal
creation and posting policy.
Features
Journal security involves defining users that can administer (AdminJournal), create (CreateJournal), post
(PostJournal), or unpost (UnpostJournal) journal entries. With AdminJournal rights, a user can create
templates as well as clear journal tables by deleting all journal entries.
You set up journal security in Planning and Consolidation Administration.
Activities
Set up journal task security by performing the following steps:
● Create journal task profile:

1. Go to Administration and under the Security section, choose Task Profiles. To create a new task profile,
choose New in the toolbar.
2. In the Assign Tasks step expand the Journals folder in the Available Tasks list, then select one or more
journal tasks.
3. Once you have reviewed the task profile, click Finish to create it.
● Assign journal task profile to a user:
1. Go to Administration and under the Security section, choose Users. Select a user and choose Edit in
the toolbar.
2. In the Task Profiles tab, click Add/Remove in the Assigned to User list.
3. In the dialog box, choose the required journal task profiles from the Available Profiles list and add them
to the Selected Profiles list.
4. Click OK.
 Note
If users have create access, but not write access to a data region, they cannot create journal entries for that
data region.
To assign one or more journal task profiles to multiple users, create a team and add the required users by
selecting Security Team in Planning and Consolidation Administration. Once created, open the team
for editing and in the Task Profiles tab, add the required journal task profile(s) to the team.
Related Information
Journal Template Creation [page 353]
Delete All Journal Entries from Model [page 358]
1.14.9.3 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.
1.14.9.4 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.
1.14.9.5 Data Modification by Journal Entries Only (Standard

only)
You can set a work status to lock data so users are limited to modifying data only through journal entries, not
input schedules.
This enforces a separation between SAP BusinessObjects EPM solutions, add-in for Microsoft Office input
schedules that send data to the database and your review and analysis phase where all data modifications are
made by journal entries.
Activities
To lock data so business users can modify it in journal entries only, do the following:
1. Set up a work status code to lock out EPM add-in for Microsoft Office changes to entities. During this
process, assign owner and manager rights to set status to journal changes only.
2. Since owners or managers set work status, entities can be set for journal input only. You can test this by
logging into SAP Business Planning and Consolidation with a manager ID, setting the status for an entity to
Journal Only, then trying to send data to that entity via an input schedule and a journal entry.
Example
Set up a code named Journal Only, in which the entity owner can change a status from Unlocked to Submitted
and set it back to Unlocked if desired. The manager can change it from Submitted to Journal Only, which locks
the data from changes by EPM add-in for Microsoft Office input schedules or Data Manager data loads, but
allow changes by journal entries. The manager can then set the status to Approved, which locks changes from
any source, including journals.
1.14.9.6 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
1.14.10 Context Defaults (Standard only)
Use
Context is the model, dimensions, and associated members authorized to a user and applicable to what is
displayed in a workspace, folder, or view. Administrators can set the default context that users automatically
work in when accessing in the Web client.
Prerequisites
You have accessed the environment for which you want to set the context defaults.
Activities
To set context defaults, perform these steps:
1. In the Administration screen, choose Features Context Defaults .

2. To set a specific model as the default, select the model, then choose Set as Default.
3. To set the context defaults for a specific model, do the following:
1. Choose a model in the list, then choose Edit above the list of dimensions.
2. For any dimension for which you want to set defaults, select reporting and data input members,
whether to display the dimension and its name, and how to display the member. You can display a
member by its name, description, or both.
3. Save the context defaults for the model.
1.14.11 Drill-Through Setup (Standard only)
Use
You use this function to set up drill-through definitions. Drill-through definitions allow users to access source
data from a report. Source data includes content that can be accessed from a URL.
Prerequisites
You must have proper security rights to define drill-through definitions. See the Business Planning and
Consolidation Security Guide for more information.
Features
Setting up Drill-Through to a URL
You set up URL-based drill-through definitions within a model. After you set up at least one drill-through for a
model, it is available to users of reports that reference that model.
You can map the URL parameters to dimensions or userdefined values.
When you map a parameter to a dimension, you also choose a dimension property, such as ID or
DESCRIPTION. When the user performs a drill-through in a report, the parameter value is taken from the
property value of the selected data cell. For example, if you select the ID property of a dimension, the member
IDs are mapped. If you select another property of a dimension, that property value is mapped. Therefore, you
can send either the dimension member or the value of a property.
When you map a parameter to a userdefined value, you can hard code a value or use %CurrentUser% or
%CurrentDate%. If you specify a userdefined value in the mapping, when the user performs a drill-through in
a report, the parameter value is based on the userspecified value.
 Note
The system supports the variables Current Date and Current User in the mapping. The format of Current
Date is %CURRENTYYYYMMDD%, where YYYYMMDD is replaced by the current year, month, and day. You
could then use %CURRENTYYYY% for sending out only the current year. The format for Current User is
%CURRENTUSER%.
The system supports using environment parameters and model parameters in a URL. The format is
%parameter%. When an environment parameter and model parameter have the same name, drill-through
uses the model parameter prior to the environment parameter.
Executing a Drill-Through
You can use the EvMNU macro MNU_eTOOLS_DRILLTHROUGH_RUN to execute a drill-through using the
syntax MNU_eTOOLS_DRILLTHROUGH_RUN("drillthrough id").
If you have defined a drill-through in the Administration view for a model, a menu item appears under the Drill-
Through menu in the menu bar of the report. This menu item has the same name as the description that was
entered in the Administration view when the drill-through was defined. To access the drill-through information,
select a cell in the report and then select the menu item from the Drill-Through menu. A web browser opens.
The information that displays depends on the following items:
● The URL specified in the Administration view

● The URL parameters specified in the Administration view
● The data cell that you selected in the report
 Note
The URL and the URL parameters appear in the address bar of the browser. Also, even if the selected cell
does not contain data, the drill-through is performed.
Activities
To define a drill-through for a URL:
1. In the Planning and Consolidation Administration screen, under the Features section, choose Drill-Through.
2. Select New, then enter a drill-through ID and description.
3. Enter the target URL, select the model from which the drill-through can be launched, and enter parameter
mapping information to indicate one or more dimensions and associated properties or userdefined values.
 Example
You can specify http://www.google.com/search? as the URL and q, which is a known Google
parameter.
4. Save the drill-through.
You can also edit and delete drill-throughs in the Planning and Consolidation Administration screen by selecting
Drill-Through under the Features section.
Example
Example 1
This example describes a scenario of drilling through to a URL.
You want to search the member of Category in a Web site called MySite. You can define a drill-through, setting
the URL as www.MySite.com. The parameter for MySite is q so in the Parameter column, you enter q. In the
Dimension or User-defined Value column, select the Category dimension.
In the report, users can execute this drill-through to see the search results.
Example 2
This example describes another scenario of drilling through to a URL.
When SAP BusinessObjects Financial Information Management (FIM) is used to load data into Business
Planning and Consolidation from external data sources (flat files, tables, 3rd party applications, or other EPM
applications), this data is often transformed and aggregated. Business Planning and Consolidation stores only
the final data, and you may want to drill-through into the details of the data that is stored in a FIM repository
(staging area). A URL-based drill-through makes this possible.
When defining the drill-through, the URL is set to the <FIM Application>. URL parameters are dimensions in the
Business Planning and Consolidation model that pass the context (for example, time, account, etc.), of the
data being queried. All data associated with the context is returned and displayed in the FIM drill-through
report.
1.14.12 Document Types and Subtypes (Standard only)
Use
Document types and subtypes categorize Documents view postings. This is useful if you want to filter them to
see only certain types.
Features
Document subtypes help you to further categorize documents when you post them in the Content Library.
Administrators can define a list of subtypes from which users choose, and users can create their own as
needed.
While document types always appear in an alphabetical list, document subtypes appear in the order in which
they were created. You can change the order of the subtypes.
Activities
To add or remove document types and subtypes within a model, go to Administration and under the Features
section, choose Document Types. Then select a document type or subtype, then choose Edit.
To rearrange the order of subtypes while in Edit mode, select a subtype, then choose Move Up or Move Down.
While in Edit mode, you can rename and remove document types and subtypes.
1.14.13 Auditing
Use
Use this function to configure data auditing.
Features
You can perform data auditing to track changes to transactional data at the InfoProvider level.
More Information
Audit Reports [page 76]
Activity Auditing [page 368] (standard only)
1.14.13.1 Data Auditing
Use
In Business Planning and Consolidation in a standard configuration this function tracks changes to
transactional data at the model level, such as when and by whom records were changed within a model.
In Business Planning and Consolidation in an embedded configuration this function tracks changes to
transactional data at the InfoProvider level, such as when and by whom records were changed within an
InfoProvider.
Features (standard only)
Administrators control whether data auditing is active or not.
For each model within an environment, you select a category and one or more of the following tasks to audit:
● EPM Add-in
● Data Manager Import
● Data Manager Clear
● Script Logic Execution
● Web Report Input
● Journal Input
● Business Rules Execution
● Ownership
● FIM Import
When selecting the tasks to audit for a category within a model, you can indicate whether you want to retain the
logs of the data audits indefinitely or for a specific number of days. Business Planning and Consolidation does
not delete the logs; rather, it archives them after the number of days you indicate.
Activities
To enable data auditing in Business Planning and Consolidation in a standard configuration, go to

Administration and under the Audit section, choose Data Changes. Select a model, and change its status to On.
To enable data auditing in Business Planning and Consolidation in an embedded configuration, go to

Administration and under the Audit section, choose Data Changes. Select an InfoProvider, and change its status
to On.
 Note
Before you can set data auditing in Business Planning and Consolidation in an embedded configuration,
the InfoProvider(s) must be set to auditable. You can set them as auditable in the BW back-end.
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 78]).
In Business Planning and Consolidation in a standard configuration you can also set up Data Manager
packages to archive data audit information. See the EPM add-in help.
In Business Planning and Consolidation in an embedded configuration you can create a BW Query with audit
characteristics, and create multi-dimensional audit report with the EPM Add-in or with web reporting.
1.14.13.2 Activity Auditing (Standard only)
Use
This function tracks administrative and user tasks at the environment level.
Features
Administrators control whether activity auditing is enabled or not. The system can track changes for the
following activities, showing the previous and new values as well as the IP address and machine name
associated to the user making a change:
● Administration activities, including:

○ Security-related changes such as adding, changing, and deleting users, teams, task profiles, and
member access profiles
○ Create, modify, delete, and copy operations for models and dimensions; dimension processing; create
and delete operations for dimension members; changes made to property or hierarchy values for a
dimension member; delete and copy operations on environments and on drivers for driver based
calculations
○ Changes to environment and model setup options, global configuration settings and KPI definitions for
automated performance analysis, document types and subtypes, activity audit settings, and data audit
settings
● User activities, such as setting data locks
● Business Process Flow activities, such as adding, deleting, and modifying business process flows, and
saving business process flows to new names
● User activities in business rules management
Activities
To enable activity auditing for the current environment, go to Administration and under the Audit section,
choose the types of activity auditing to enable.
Once the system records an activity, you can run a report that shows activity based on specified criteria (see
Reporting on Administration Activity [page 82]).
You can set up Data Manager packages to archive activity audit information. See the EPM add-in help.
1.14.14 Time-Dependent Hierarchies (Standard only)
When you use the time dependent hierarchy feature, you can modify a hierarchy and still keep its history. Thus,
you can create, modify, and delete different versions of one hierarchy. You can display the different versions of
that hierarchy by selecting key dates in EPM solutions, add-in for Microsoft Office.
The following information pertains to hierarchy version maintenance within various areas of Business Planning
and Consolidation.
Admin Console
Using the hierarchy view of the dimension master data maintenance screen, you can create, modify, and delete
time-dependent hierarchy versions.
● Create a new hierarchy version by specifying a start date. A new version will be created starting with the
date selected and end at the original end date of the hierarchy version to which the start date originally
belongs. In addition, it is possible to select a reference hierarchy version to indicate how the new version of
hierarchy should look at the beginning.
● By selecting an existing hierarchy version from the dropdown list, you can modify any existing hierarchy
version. It is also possible to modify an existing hierarchy version in the list view.
● You can select any hierarchy version to delete by selecting a previous version or the next version with which
to merge it.
Data Manager
When you use the process chain /CPMB/MANAGE_TDH_VERSION to create and execute a Data Manager
package, you can either create a new time-dependent hierarchy version or delete an existing time-dependent
hierarchy version.
When you load a master data hierarchy either from a flat file or from an InfoObject to a time-dependent
hierarchy enabled dimension, you can select which hierarchy version to modify by selecting either a date or a
version.. If you select a date, the system takes the version to which the selected date belongs. If you select a
version, your selection is based on a time range.
Reporting
As long as there is at least one dimension from a model that has time-dependent hierarchy enabled, you can
select a key date reporting and input forms.
● EPM add-in
○ You can select Key Date in the context bar or report editor when the current model has at least one
dimension with a time-dependent hierarchy enabled.
○ The selected key date affects all time-dependent hierarchy dimensions, meaning the version of the
hierarchy of the time-dependent hierarchy dimension depends on the selected key date.
○ You can specify only one key date for a report. Multiple reports from the same worksheet or workbook
can have different key dates.
○ The default key date is the current date.
○ By default, three versions of the hierarchy for each time-dependent hierarchy dimension are cached on
the client machine. The number of cached versions can be changed by modifying in the client-side
configuration file FPMXLClient.dll.config the line:
<add key="LimitTDHCountInCache" value="3"/>
The configuration file can be found in Microsoft Windows 7 at C:\Program Files (x86)\SAP
BusinessObjects\EPM Add-In\ if the EPM add-in is installed for all users, or at C:\Users\<username>
\AppData\Local\Programs\SAP BusinessObjects\EPM Add-In\ if EPM the add-in is installed for a
single user.
● Web Reporting
○ You can select a key date from the dropdown menu by choosing Manage Context when the current
model has at least one dimension with time-dependent hierarchy functionality enabled.
○ The selected key date affects all the time-dependent hierarchy dimensions, meaning the version of the
hierarchy of the time-dependent hierarchy dimension depends on the selected key date.
○ The default key date is the crrent date.
Security
A data access profile is always defined with the hierarchy version of the current date. At run-time, data security
is always resolved with the hierarchy version of the crrent date, no matter what key date is selected from the
Reporting user interface.
Data Manager Packages
A key date selection is available when executing a Data Manager package if the model has at least one time-
dependent hierarchy enabled dimension.
Logic Scripts
● There is no keyword with logic script; it is not possible to specify a key date in a script file.
● When a script is triggered by a Data Manager package, a key date is derived from the selection screen
when the package is executed.
● For default logic, a key date is derived from the input form.
● For the script logic test transaction UJKT, the key date can be specified in the field PARAM with the format
KEYDATE = yyyymmdd.
Consolidation
Consolidation always uses the current date to resolve a hierarchy.
Transport
● A time-dependent hierarchy can be transported with dimension master data.
● The global setting ENABLE_TIME_DEPENDENT_HIER cannot be transported. You must maintain this
manually in all systems.
● The Time-dependent Hierarchy setting in a dimension structure can be transported together with
dimension transport. Note that the import process might fail if the global setting
ENABLE_TIME_DEPENDENT_HIER is not set to X in the target system.
Backup and Restore
All versions of a time-dependent hierarchy can be backed up and restored together with master data.
1.14.14.1 Enabling Time-Dependent Hierarchy Functionality
Prerequisites
To use time-dependent hierarchy functionality, you must have the following software installed:
● Planning and Consolidation for the NetWeaver platform 10.0 SP09 or later
● EPM solutions, add-in for Microsoft Office 10.0 SP13 Patch 1 or later
Procedure
1. To activate the necessary global setting, perform the following steps:

a. Go to the SAP NetWeaver backend using transaction SPRO.
b. Choose SAP Reference IMG Planning and Consolidation Configuration Parameters Set Global
Parameters .
c. Insert a new flag with the field name ENABLE_TIME_DEPENDENT_HIER.
d. Set its value to X, then save the entry.
2. To enable the time-dependent hierarchy functionality by dimension, perform the following steps. Note that
all dimensions can enable time-dependent hierarchy functionality except dimensions with the dimension
type TIME.
a. Log onto the Planning and Consolidation web client.
b. Choose Administration Dimensions .
c. Choose the dimension, then select Edit Structure.
d. Choose Time-dependent Hierarchy, then save your selection.
1.14.15 Parallel Execution (Standard only)
Parallel execution can improve your system's performance by making better use of its processing capabilities.
You can use parallel execution for some of the functions that you run in Business Planning and Consolidation.
Parallel execution can improve your system's performance significantly by making better use of its hardware
and the resulting CPU time and memory. When you enable parallel execution, the framework splits the logic of
the processed data when possible. The split parts are allocated to dialog sessions that the framework executes
in parallel. This reduces the overall time necessary to complete a whole process. Parallel execution does not
affect the business logic of your operations; it affects only the performance.
Parallel execution is available for the following functions:
● Loading data from an InfoProvider

● Business rules for elimination and adjustment
● Data Manager
1.14.15.1 Enabling Parallel Execution
To enhance Business Planning and Consolidation in terms of scalability and performance, you can enable
parallel execution to leverage system resources such as CPU, memory, and so on.
Procedure
1. Go to the SAP NetWeaver backend using transaction SPRO.

2. Set the following parameters:
Parameter Name Description
ENABLE_PARALLEL_EXECUTION Enables parallel execution mode.
PARALLEL_SERVER_GROUP The name of the server group where the dialog sessions
will run.
MAX_SESSION_COUNT The maximum number of dialog sessions that parallel exe

cution can use. Default: 12
BUFFER_ROW_SIZE The amount of data in a package. Default: 40000
BUFFER_MAX_ROW_SIZE The maximum amount of data in a package. Default:

90000
REFRESH_STATUS_INTERVAL The amount of time in seconds between session synchro

nization. Default: 10
BUFFER_MAX_PART_COUNT The amount of partitions at most one input buffer in

stance can handle. Default: 1000
BUFFER_WAIT_TIME_TO_EXIT The amount of time in seconds an input buffer should wait

if there is no data. Default: 5
MONITOR_WAIT_TIME_TO_EXIT The amount of time in seconds the main session should

wait before exiting if it cannot start an instance. Default: 10
3.  Note
You have the option of enabling parallel execution for Data Manager to obtain better performance when
processing large amounts of data. The transaction data related process chains benefit from this
framework to varying degrees. Among them, the process chain that loads data from the InfoProvider
sees a significant benefit.
Optional - Apply the following line into the Data Manager dynamic script by performing the following steps:
a. Choose EPM client Data Manager Organize Organize Package List .

b. Select a package.
c. Choose Modify Package Modify Script Advanced .
d. Apply the line PARALLEL_EXECUTION(ON).
1.14.16 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.
Important: All of the BAdIs listed in this topic, except for BADI_RSBPCB_SETUSER, apply only to the standard
configuration of Business Planning and Consolidation. BADI_RSBPCB_SETUSER applies to both the embedded
and standard configurations of the application.
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, and can be used in both the embedded and standard
configurations of the application.
● BADI_UJ_BPF_REVIEW_VALIDATION - Overrides the system logic if the current user is able to approve or
reject a BPF activity. This BAdI is triggered when the activity list is displayed and the user chooses Approve
or Reject as a reviewer.
● BADI_UJ_BPF_REVIEW_LOGIC - With this BAdI you can implement custom logic. It is triggered when the
user chooses Approve or Reject.
● BADI_UJ_BPF_SUBMIT_LOGIC - With this BAdI you can implement custom logic. It is triggered when the
user chooses Submit.
● Using the same Business Add-In BADI_UJ_BPF_SUBMIT_LOGIC, if you add a filter IS_COMPLETE and set
it to 'X', you can implement custom logic for the Complete button as well. For details, refer to 2628363 .
Script Logic
● BADI_UJ_CUSTOM_LOGIC - With this BAdI you can implement custom calculation logic. It is triggered from
script logic.
● BADI_UJCTRL_RUN_CONTROL (Enhancement spot UJCTRL_RUN_CONTROL) - Allows you to write your
own control logic via ABAP.
SQE
BADI_UJ_SQE_POST_PROCESS
● Method POST_PROCESS - Triggered after data is read from the database. You can implement custom logic
to manipulate the data before it is sent to the frontend.
● Method CUSTOMIZE_PROPERTIES - Triggered by master data properties in the BAdI implementation,
before a web report is displayed. You can change the member description and input enablement of
Planning and Consolidation web reporting.
Write Back
BADI_UJR_WRITE_BACK - Triggered when the write back module is started. The data sent from other modules
is sent to the BAdI interface and you can manipulate that data within the BAdI implementation. The processed
data goes through all standard validations and is posted to BW.
Data Manager
● BADI_UJD_RETRACT - Triggered from Data Manager. You can use this BAdI to export Planning and
Consolidation data to an external source, for example, to write planning data back to ECC for budget
control.
● BADI_UJD_ROUTINE - Triggered during transformation when loading data from an external data source.
You can use this BAdI to run complex data transformations which are not possible with a transformation
file.
Validation
BADI_UJ_VALIDATION_RULE_LOGIC - Triggered by the write back module. You can use this BAdI to validate
input data with ABAP code instead of defining validation rules.
Security
● BADI_UJE_DYNAMIC_DAP - Triggered after a static data access profile (DAP) setting is read from the
database. You can use this BAdI to dynamically define data security for a user and reduce the number of
static DAPs to be created.
● UJE_DIM_PROCESSED_BADI - Triggered after dimension master data is processed. Can be used to
automatically update DAP settings based on a change in the master data.
Journals
BADI_UJJ_CALCULATED_AMOUNT - Triggered when you save or post a journal. Can be used to generate
additional journal entries.
Work Status
● BADI_RSBPCB_SETUSER - You can implement customized logic that provides the owner and manager for
work status to Work Status. This BAdI applies to both Business Process Flows and Work Status, and can be
used in both the embedded and standard configurations of the application.
● UJW_LOCKOUT_SCHEDULE_BADI - Triggered when the work status is checked by internal models. Can be
used to provide work status lock information programmatically.
Parameter
BADI_UJ_PARAM_CHANGE - Triggered when a user changes a parameter in IMG. Mainly used by Planning and
Consolidation internal logic to apply specific checks.
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 genderspecific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.
376 PUBLIC Important Disclaimers and Legal Information
Important Disclaimers and Legal Information PUBLIC 377
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

BPC101NW - S4HANA - en - Optimizado PDF

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

BPC101NW - S4HANA - en - Optimizado PDF

Caricato da

Copyright:

Formati disponibili

PUBLIC

SAP Business Planning and Consolidation for SAP NetWeaver 10.1

Application Help for SAP Business Planning and

THE BEST RUN

1 SAP Business Planning and Consolidation for SAP S/4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . 4

About this Release

HTML5-based web client

SAP BusinessObjects Analysis, Edition for Microsoft Office

Starting the Web Client

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/

● classic - for Business Planning and Consolidation environments in a standard configuration

1.1 Getting Started

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.

● To change the settings, choose Save.

In the home page you can choose the following pages:

● Choose the button to select one of the opened pages.

● Choose the button to return to the home page.

Change the Environment

1.3 Business Process Flows

● 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

1.4 Process Monitor

To access the Library view, in the home page choose Library.

1.6 Documents (Standard only)

Posting Files to the Documents View

Viewing and Managing Content

The following Consolidation features are available:

Consolidation Monitor (Standard only) [page 17]

1.7.1 Consolidation Monitor (Standard only)

Incremental consolidations and currency translations

Category Time Groups Currency translation Consolidation

Actual 2009.DEC G_WORLD 2010/09/01 09:00 2010/09/01 09:01

Actual 2009.DEC G_ASIA 2010/09/01 09:00 2010/09/01 09:01

At 9:05 a.m., the data for the entity Shanghai is updated:

Category Time Entity Data Updated

Actual 2009.DEC Shanghai 2010/09/01 09:05 a.m.

Technical entity storing aggregated data

In the Consolidation Monitor you can do the following:

● Display the control set status

● Set the work status for an entity

1.7.1.1 Run a Currency Translation (Standard only)

To run a currency translation, you must define the following items:

To run a currency translation

Currency Translation Rule (Standard only) [page 271]

1.7.1.2 Run a Consolidation (Standard only)

To run a consolidation, you must define the following items:

To run a consolidation, do the following:

1.7.1.3 Working with Periodic Consolidations and Currency

Run a Consolidation (Standard only) [page 21]

The Controls Monitor enables you to execute and monitor controls.

The Controls Monitor is split into the following areas:

An administrator has given you the View Controls access right.

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 306]