Professional Documents
Culture Documents
Configuracion BW4 - BPC11
Configuracion BW4 - BPC11
1 Application Help for SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Grid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
My Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.4 Consolidation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Consolidation Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Journals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Ownership Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Environment Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Dimension Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Model Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Legal Consolidation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Auditing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
2 PUBLIC Content
1 Application Help for SAP Business
Planning and Consolidation, version for
SAP BW/4HANA (Embedded)
Application help for an embedded configuration of SAP Business Planning and Consolidation, version for SAP BW/
4HANA.
Product Information
Table 1:
SAP Business Planning and Consolidation provides everything you need to meet your bottom-up and top-down
financial and operational planning requirements through a single application and user interface.
SAP Business Planning and Consolidation 11.0, version for SAP BW/4HANA is a new product based on SAP BW/
4HANA. The product supports the HANA database and uses SAPUI5 user interface technology. The SAP UI5 user
interface is based on standard HTML5, which provides all the benefits of HTML5 and supports languages such as
Hebrew and Arabic that are written and read from right to left. BW/4HANA is a new, next-generation data
warehouse product that is optimized for the SAP HANA platform, delivering real-time, enterprise-wide analytics
that minimizes the movement of data and connecting all the data in an organization into a single logical view.
SAP Business Planning and Consolidation 11.0, version for BW/4HANA also introduces the new SAP Belize user
interface that has a clean and consistent layout. Belize is the refined SAP Fiori visual language whose calm color
tones help users stay focused on daily business tasks and content. With delightful visual details and typography,
Belize conveys content with clarity and makes the user experience richer.
Administrators can configure the installation of SAP Business Planning and Consolidation in one of two ways:
● In an embedded configuration, Business Planning and Consolidation is integrated with SAP HANA-optimized
processing, through which you can perform SAP HANA-optimized planning. For details about SAP HANA-
optimized processing and the BW planning processor, refer to .
● In a standard configuration, you can use all the functionality that is available in the standard configuration of
SAP Business Planning and Consolidation, version for SAP NetWeaver.
Note
Information within a single topic that differs between the configuration types is clearly explained within the
relevant content.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 3
Integration
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.
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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4 PUBLIC 4HANA (Embedded)
1.1 Getting Started
The following features are available to help you get started using SAP Business Planning and Consolidation:
● You can change the user preferences to customize the display of your UI. See Preferences [page 5].
● You can replace the SAP logo with your company logo, See Change Company Logo [page 6].
● You can change the way data displays in table format on various pages within the application. See Grid [page
6].
● You can customize your own home page and navigation to different functions through the main navigation
panel. See Home Page and Navigation [page 6].
1.1.1 Preferences
You can change user preferences to customize the display of your user interface. You can make changes to the
language, date format, and others settings.
Table 2: My Preferences
Feature Description
Theme The theme that you want to use for the application UI
Time The time zone that you want to use in the application
Name Format The format in which the logged in user's name appears
Activities
To view and edit user preferences, in the upper right part of the screen, click your user name and choose
Preferences.
Note
Your changes will take effect upon your next logon. If you want to apply the changes immediately, you must
restart the application.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 5
1.1.2 Change Company Logo
You can replace the SAP logo in the upper left corner of Business Planng and Consolidation with your company
logo.
To replace the SAP logo with your company logo, follow these steps:
To directly change your company logo back to the default SAP logo, follow these steps:
1.1.3 Grid
A grid is a table that displays data and allows you to alter the display of that data.
● Where available, you can filter the data displayed in a table. Click the column header tab and then in the drop
down list enter a value in the Filter field.
By entering a specific value, you can narrow the data displayed to include only the ones with that value.
● Display or hide certain columns using the (View Settings) button in the upper right corner of a table, where
available.
All columns are displayed by default. To hide a particular column, deselect the checkbox for that column.
● Sort the data in the table according to a particular column by clicking the column header tab.
In the drop down list, the data can be sorted in ascending or descending order.
When you log in to the web client of Business Planning and Consolidation, you can use the main navigation panel
on the left side to navigate to the functionality that you want to access.
● Home - Displays your favorite pages and snapshots of charts, and reminds you of the activities approaching a
deadline. For more information, see the Home Page section below.
● My Activities - Displays the activities requiring action by you as the currently logged-on user. For more
information, see My Activities [page 9].
● Process Monitor - Displays a complete list of the process instances for you as the process owner of
corresponding process templates to monitor. See Process Monitor [page 11].
● Consolidation - Provides information about generating and managing consolidated data to give you an
accurate view of the financial situation of your organization. See Consolidation [page 12].
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
6 PUBLIC 4HANA (Embedded)
● Administration - Enables administrators to perform setup and maintenance tasks for Business Planning and
Consolidation. See Administration [page 44].
● System Reports - Provides information about reporting on system information and activity. See System
Reports [page 40].
● 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 .
Home Page
You can navigate to home page from the main navigation panel. The home page is composed of the following tiles:
Favorites - provides direct links to specific Business Planning and Consolidation web pages that you bookmarked
as favorites
Timeline - provides the activities requiring action by you as the currently logged-on user in deadline order
Charts - provides a snapshot of charts that you pinned to the home page
Navigation
This release of Business Planning and Consolidation is a single page application. You can jump to a certain page in
two ways:
● From the main navigation panel – To jump to a new page, click the icon from the upper left corner and
choose a page.
● From the breadcrumb bar – The navigation path in the breadcrumb bar indicates the position of a page in the
application. By clicking the Drill Down button, you can jump to other relevant pages at the same level.
To go back to the previous page, we recommend you use the button inside the application other than the back
button on your web browser as we make some customized enhancement to the back button inside the application.
Click the button from the upper right corner of the screen and your current environment displays. Click on the
environment name to change to another environment.
Setting Preferences
To set individual preferences, click on your name in the upper right corner of the screen and choose Preferences.
For more information, see Preferences [page 5].
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 7
Show Access Right (Standard only)
To view your own access right, click on your user name in the upper right corner of the screen and choose Show
Access Right. You can also print and export details about your access rights.
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 9].
● 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 11].
● E-mail notifications
The system automatically generates e-mail notifications to the people who are involved in a process or activity
to keep them informed of its progress and of tasks that need to be performed. The e-mail notifications
automatically sent to users contain a link to bring them directly to the activity or process monitor, or to
navigate to external applications to perform further actions.
E-mail notifications occur in the following situations:
○ Process monitors are the users who can monitor all the instances created from a process template.
Process monitors receive an e-mail notification when a new process instance is:
○ Created
○ Suspended
○ Resumed
○ Reset
○ Ready to be finalized
○ The owner of an activity receives an e-mail notification when the activity is:
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
8 PUBLIC 4HANA (Embedded)
○ 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 127].
1.2.1 My Activities
My Activities displays the activities requiring action by you as the currently logged-on user. The actions might
include performing activities assigned to you or reviewing activities submitted by others.
Features
By clicking an activity, you can open the associated activity workspace to perform or review your activity. The
activity workspace contains hyperlinks to begin executing your tasks.
Before any action is taken, activities can have the following statuses:
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:
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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 9
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. The search box in the upper right corner supports cross-column searching, which means
anything in the page that matches your input will be displayed and highlighted.
Using (View Settings), you can choose the columns to display for all activities, as well as sort and group
activities on your own, which enables you to manage activities in a more organized way.
Numbers such as in each process show the total number of open activities that require your attention in this
process. Click See more to view the detailed activity numbers for each status.
Choose a process and the Details window displays all the activities of that process requiring your action. Then, if
you the assigned performer of an activity, you can click the activity names to open the activity workspace where
you perform any required tasks. When you have completed the required actions, choose Complete in the activity
workspace. The status in the My Activities view automatically updates; if any further reviews are required, the
status will change to Submitted. Otherwise, the activity status will be directly changed to Completed.
You can enter and review comments when changing the status of a BPF activity.
If you are the assigned reviewer of an activity, you can approve or reject the activity. Approve changes the status of
the activity to Completed. Reject changes the status of the activity to Rejected and the responsible user may
resubmit the activity for approval.
Reopening Activities
You can reopen a completed activity or specific activities for which reopening criteria have been met. For more
information, see Criteria for Reopening Activities [page 120]. If you are a process instance owner, you can reopen
activities of the processes you own without any limitations. To reopen an activity, go to the process instance and
click See more. Then choose the Reopen button to select activities.
Work status 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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
10 PUBLIC 4HANA (Embedded)
1.3 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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 11
1.4 Consolidation
The Consolidation module in SAP Business Planning and Consolidation enables you to generate and manage
consolidated data, giving you an accurate view of the status of the collected and consolidated data within your
organization as well as a unified environment to perform consolidation tasks over the web.
Features
● 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
The Consolidation Monitor is a global dashboard for monitoring the consolidation progress of a specific
consolidation scope, which is made up of a category, period, group, or sub-group.
The Consolidation Monitor is a key component in executing consolidations since it communicates to the
consolidation engine about the entities on which to execute business rules. For more information about setting up
your consolidation environment with dimension properties, model settings, and journal definitions, see Legal
Consolidation [page 60].
The Consolidation Monitor displays the Group/Entity hierarchy created in the Ownership Manager (only
Consolidation type models). For information on configuring an ownership-based hierarchy, see Ownership
Manager [page 36].
The scope context area displays the selected dimension members: Time (T-type), Category (C-type) and Group
(G-type).
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
12 PUBLIC 4HANA (Embedded)
Prerequisites
An administrator has assigned relevant authorization objects to you for managing Consolidation Monitor and
executing business rules. To perform control type tasks, you also need to be assigned the relevant authorization
objects. For detailed information about how to assign the authorization objects, see the topic “Authorization for
Performing Consolidation Tasks” in the Security Guide available on the SAP Help Portal.
Before running relevant business rule tasks, corresponding dimensions and attributes must be maintained by your
administrator. For detailed information, see Business Rules Management [page 79].
Since Consolidation Monitor is the central place to trigger tasks defined by certain business rules on different
consolidation models, before you perform any tasks in Consolidation Monitor, your administrator is expected to
have defined business rule types for the consolidation model in Rules Business Rules and chosen the tasks
to be run on the model in Rules Task Sequences . For detailed information, refer to Business Rules
Management [page 79] and Set Task Sequence [page 76].
Features
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 13
Activities
Example
If you want to run currency translation on Entity 1, you first select the intersection cell of the Currency
Translation task type and Entity 1 and then click Execute on the tool bar.
Related Information
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
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
14 PUBLIC 4HANA (Embedded)
Default member: time period on the context bar.
● E – Entity
Default member: the selected entity
● R – Currency
Default member: the first member in the currency dimension of the CONSOLIDATION InfoProvider.
● Currency Rate Entities
Default member: Global. If Global is not defined, then the first member of Entity in the RATE InfoProvider
displays.
You should be able to select multiple entities, currencies and time periods.
After defining all the members for these dimension types, click OK and execute a currency translation by following
the steps in Consolidation Monitor [page 12].
If you execute currency translation on a group, then a currency conversion dialogue 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.
● 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.
After defining all the members for these dimension types, click OK and execute a currency translation by following
the steps in Consolidation Monitor [page 12].
Related Information
Prerequisites
An administrator has assigned relevant authorization objects to you to manage a consolidation and execute
business rules in Consolidation Monitor. For detailed information about how to assign the authorization objects,
refer to the topic “Authorization for Performing Consolidation Tasks” in the Security Guide available on the SAP
Help Portal.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 15
You can run a consolidation at a group level if you have Write access to the group.
Activities
If you execute carry forward on an entity, then a carry forward dialogue box 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: 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 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
● G – Group
Default member: the selected 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 following
the steps in Consolidation Monitor [page 12].
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
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: group currency on the context bar
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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
16 PUBLIC 4HANA (Embedded)
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
Default member: category member on the context bar
● T – Time periods
Default member: time period on the context bar
● G – Group
Default member: the selected 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.
After defining all the members for these dimension types, click OK and execute currency translation by following
the steps in Consolidation Monitor [page 12].
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
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: group currency on the context bar
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
Default member: category member on the context bar
● T – Time periods
Default member: time period on the context bar
● G – Group
Default member: the selected 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.
After defining all the members for these dimension types, click OK and execute currency translation by following
the steps in Consolidation Monitor [page 12].
If you execute elimination and adjustment on an entity, then an Elimination and Adjustment dialogue box appears
with the following dimension types and corresponding default members:
● C – Category
Default member: category member on the context bar
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 17
● T – Time periods
Default member: time period on the context bar
● G – Group
Default member: the direct group of the selected entity
If you execute elimination and adjustment on a group, then an Elimination and Adjustment dialogue box 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
● G – Group
Default member: the selected group
You should be able to select multiple time periods and multiple group members.
After defining all the members for these dimension types, click OK and execute currency translation by following
the steps in Consolidation Monitor [page 12].
Click on the intersection cell of the task type and the entity or group for which you want to change the work status
or run controls, and choose the Execute button. You can then change the work status to the desired work status or
run a control for an entity or for a group along with all entity members under that group.
For rules about changing work statuses and executing controls, refer to Work Status Setup [page 131] and Create
a Control [page 99].
Related Information
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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
18 PUBLIC 4HANA (Embedded)
Related Information
Use
Controls are run on a selected entity or group of entities. If you select a Group, you can run the controls for all the
aggregated entities belonging to this Group. Controls are executed in the order in which they appear in the control
set.
The Controls Monitor displays the Group/Entity structure based on the hierarchy created in the Ownership
Manager (only Consolidation type models). For information on configuring an ownership-based hierarchy, see
Ownership Manager [page 36].
● 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
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 19
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.
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.
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:
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 99]; for more information on control
status, see Control Set Status [page 22].
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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
20 PUBLIC 4HANA (Embedded)
You can also set the context of the control monitor on the parent node level.
Activities
● To run controls for the selected entity or entities, see Execute a Control Set [page 21].
● 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
Prerequisites
An administrator has assigned relevant authorization objects to you to execute controls in Control Monitor. For
detailed information about how to assign the authorization objects, refer to the topic “Authorization for Performing
Consolidation Tasks” in the Security Guide for SAP Business Planning and Consolidation, version for SAP BW/
4HANA available on the SAP Help Portal.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 21
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 104].
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
A control set has only one output - the control set status.
● 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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
22 PUBLIC 4HANA (Embedded)
○ 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.
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
The control status of a parent member or group depends on the control status of the child entities.
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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 23
Example
Table 3:
Control Type Control Name Control Level Entity Control Entity Control Entity Control Entity Control
Level 1 Level 2 Level 3 Level 4
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:
First assume that after executing each entity by the related Time and Category, the control status turns out as
below:
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:
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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
24 PUBLIC 4HANA (Embedded)
Related Information
1.4.3 Journals
You use journals to record and make adjustments to data in the database.
This is typically done as part of the month-end or quarter-end process. For example, administrators load general
ledger information into a model using Data Manager. Before the close, line managers can review the data and make
adjustments as necessary using a journal entry form.
Prerequisites
● At least one journal template has been created for the model.
● An administrator has assigned relevant authorization objects to you to manage journals. For detailed
information about how to assign the authorization objects, refer to the topic “Authorization for Performing
Consolidation Tasks” in the Security Guide available on the SAP Help Portal.
Features
The following table describes the available journal tasks and explains how to perform each one. You perform these
tasks in Consolidation Central Journals .
Table 4:
Create a journal entry Click New in the toolbar of the Journals For more information, see Journal En
page. tries [page 28].
Modify a journal entry Select a journal entry from the list in the You can modify saved and unposted jour
Journals page and click Open in the tool nal entries. For more information, see
bar. In the Journal Entries tab, make your Journal Postings [page 31].
changes to one or more journal entry
rows, then click Save.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 25
Task Navigation What You Should Know
Copy one or more journal entries Select one or more journal entries in the You can copy selected entries to another
Journals page. To select non-contiguous member of one of the header dimen
journal entries, hold down the CTRL key sions.
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 entry Select a journal entry from the list on the You can review detail lines of a journal
Journals page and select the Preview op entry for the entries to which you have
tion in the toolbar. The details on the View rights. For more information, see
journal entries appear below the list of Journal Queries [page 33].
journal entries.
Open one or more journal entries Select a journal entry from the list on the You open journal entries to view or edit
Journals page and click Open in the tool them. For more information, see Journal
bar. You view the details of the journal Entries [page 28].
entries in the Journal Entries tab. You can
open additional journal entries and tog
gle between them using the tabs that ap
pear 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 the
Post in the toolbar. All the selected en database, so that model data is ap
tries are posted. To select non-contigu pended. You can configure a journal en
ous journals, hold down the CTRL key try to be posted with multiple header di
as you make your selections. mensions or multiple values. For more
information, see Journal Postings [page
31].
Unpost one or more journal entries Select one or more journal entries from The system reverses the original entry to
the list on the Journals page and click the model. For more information, see
Unpost in the toolbar. All the selected Journal Postings [page 31].
journal entries are unposted. To select
non-contiguous journal entries, hold
down the CTRL key as you make your
selections.
Ungroup journal entries Select one of the journal entries in a jour For more information, see Journal
nal group and click Ungroup in the tool Groups [page 32].
bar. All the journal entries in the group
are ungrouped.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
26 PUBLIC 4HANA (Embedded)
Task Navigation What You Should Know
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 Advanced
OK. Query searches through both header and
detail dimensions. If you have multiple
journal entries, they are grouped under
the first entry. For more information, see
Journal Queries [page 33].
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 en
the list on the Journals page and click tries to new single journal entries in a
Reopen in the toolbar. subsequent time period, see Reopen
Journal Entries [page 34].
Require balanced journal entries Select the Enforce Balanced Journals op A balanced journal entry is one in which
tion in the journal model parameters. the debits equal the credits in the journal
entry. If this option is set, you cannot
post the journal entry until it is balanced.
For more information, see Journal Model
Parameters [page 139].
Print a journal report Select one or more journal entries from You can generate reports based on jour
the list on the Journals page and click nal entries. As long as you can view the
Report in the toolbar. To select non-con journal report, you can print the journal.
tiguous journals, hold down the CTRL For more information, see Print Journal
key as you make your selections. In the Reports [page 35].
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 Deleted.
Delete in the toolbar. To select non-con When you delete saved entries, they are
tiguous journals, hold down the CTRL deleted from the system. An entry that
key as you make your selections. has been posted cannot be deleted until
it is unposted. For more information, see
Journal Entries [page 28].
Define journal reopen rules In Planning and Consolidation Adminis Design a template of translation informa
tration, select Features Journal tion for the dimensions you want to re
open. For more information, see Journal
Templates . Open a journal template
Reopen Rules [page 137].
and click the Reopen Rules tab.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 27
1.4.3.1 Journal Entries
You create and maintain journal entries using the journal entry template built by your administrator.
Features
Postings
You can post journal entries after they have been saved. For more information, see Journal Postings [page 31].
Reports
Once you save and post journal entries, you can track and report on all adjustments to data. For more information,
see Print Journal Reports [page 35].
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.
You can enter standard journal entries, which have one member defined for each header dimension and one credit
or debit value.
Activities
To create a journal entry, select Consolidation Journals , then click New in the toolbar. For more information,
see Journals [page 25].
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
28 PUBLIC 4HANA (Embedded)
1.4.3.2 Journal Entry Form
You use the journal entry form to create, modify, and post journal entries.
Features
Use the journal entry form as described in the following table to enter journal entries:
Table 5:
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 clicking the
entry cell to display the Member Selector dialog box.
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 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 repre
sents one detail line. You can enter the members associated
with the data values you want to change, and the debit or
credit amount. When you create multiple entries with multiple
values from a single header item, a set of debit and credit col
umns displays for each additional member specified.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 29
Form fields Description
Multi Posting tab The journal entry is posted to the database under each dimen
sion member defined for Multiple Headers and Multiple Values.
This tab is grayed out until one of the aforementioned options
is selected.
Journal options These options allow you to perform advanced functions on the
journal entry:
Note
This option sets up a new journal; it does not create
postings.
Related Information
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
30 PUBLIC 4HANA (Embedded)
1.4.3.3 Journal Postings
You post journal entries to enter the details of a transaction into the database.
Prerequisites
An administrator has assigned relevant authorization objects to you to post journals. For detailed information
about how to assign the authorization objects, refer to the topic “Authorization for Performing Consolidation
Tasks” in the Security Guide available on the SAP Help Portal.
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.
You can repost journal entries that you accidentally delete. Only journal entries that have previously been posted
can be reposted.
You can unpost one or more journal entries to make changes to them.
You can configure a journal entry to be posted to the DataStore Object (advanced) under multiple dimension
members that you define in the journal entry page. You can choose one or both of the following:
● Multiple headers: the same amounts need to be posted to more than one member in one of the dimensions in
the data region. For example, the journal entry needs to be posted to both the actual and forecast categories.
● Multiple values: different amounts need to be posted to more than one member in one of the dimensions in
the data region.
Activities
● To post one or more standard journal entries, in the Journals page, select a journal entry and click Post in the
toolbar. All of the selected journal entries are posted.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 31
● To find a specific entry to post, from the Journals page, select Advanced Query from the Filter by dropdown
menu, and build a query to find the entries that you want to post. Select all entries that you want to post, and
then click Post in the toolbar. To select non-contiguous journal entries, hold down the CTRL key as you make
your selections.
● To unpost a journal entry, in the Journals page, select a journal entry and click Unpost in the toolbar. When you
unpost a journal entry, the following events occur:
○ The system keeps the same journal ID.
○ The status of the journal entry changes to Unposted.
● To configure a journal entry for multi-posting mode
1. In the Journals page open the journal entry. Select one or both of the following options, and select the
dimension member from the corresponding member lookup:
○ Multiple Headers
○ Multiple Values
2. Click the Multi Posting tab to add additional headers or values:
Note
The Multi Posting tab is greyed out until you select one of the options listed above.
○ To add additional headers, in the Multiple Headers list click Add, then select the dimension members
you require from the Member Selector dialog box.
○ To add additional values, in the Multiple Values list click Add, then select the dimension members you
require from the Member Selector dialog box.
Related Information
When you enable multiple headers in a journal entry, you create a journal group.
You can add two or more journal entries to a journal group. See Journal Entry Form [page 29].
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.)
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
32 PUBLIC 4HANA (Embedded)
● 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
Related Information
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:
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 33
Activities
Note
The query settings are saved until you deselect Advanced Query in the Filter by menu.
Related Information
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 137].
The system is set to allow for reopening of journals using the Allow Journals to be Reopened journal parameter. See
Journal Model Parameters [page 139].
Features
You can reopen one or more journal entries to new journal entries.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
34 PUBLIC 4HANA (Embedded)
Activities
In the next period, all the journals in the selected member range will be reopened to the target member range.
You can generate and print reports based on journal entries. These reports, which are web-based, represent an
audit trail of all journal entries.
Features
The printed journal entry report contains all postings for the selected journal entries.
You can filter the journal report by creating a journal query based on multiple parameters, including but not limited
to dimension member such as account, journal status, posted date, or group ID. You can then select the journal
entry from the filtered list. For more information, see Journal Queries [page 33].
Activities
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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 35
1.4.4 Ownership Manager
The Ownership Manager in the Consolidation Central module enables you to create and manage ownership-based
hierarchies used for performing statutory consolidations.
An ownership-based hierarchy combines Groups and Entity members, where entities can be differently connected
to or disconnected from groups according to Category and Time. Groups are nodes whereas entities are base
members.
You define ownership-based hierarchies in the system to set up and report on entity hierarchies that cannot be
managed by a fixed hierarchy.
While management reporting entity structures are fixed, and children roll up 100% to their associated parent,
ownership-based hierarchies support the legal structure of statutory consolidations that cannot be managed by a
fixed hierarchy.
Features
The static hierarchies exist above the ownership-based portion of a hierarchy, which is attached below a base-level
member in the static hierarchy. The Groups dimension is used to identify consolidation sequences and for
reporting.
● The ownership relationships required for legal reporting may exceed a one-to-one relationship in their
reporting structure or they may change frequently.
● There are two scenarios where you should define ownership-based entity hierarchies:
○ If a child member is owned by more than one parent
○ If the child is partially owned by a parent (not 100%)
● In the Ownership Manager you define an ownership-based hierarchy entity structure. The Ownership Manager
allows you to create period-specific hierarchies of corporate entities to use in statutory consolidation, or in
cases where hierarchy changes for an application need to be tracked by Category and Time.
● When you set up a Statutory model, the system tracks hierarchies for statutory reporting. Statutory models
have an upper-level static hierarchy associated with a Group dimension.
● Ownership-based hierarchies are only available in consolidation type models.
Activities
Related Information
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
36 PUBLIC 4HANA (Embedded)
1.4.4.1 Create Ownership-based Hierarchies
You create ownership-based hierarchies using the Ownership Manager, which is an ownership-based hierarchy
editor provided in Consolidation Central.
Procedure
To create ownership-based hierarchies in SAP Business Planning and Consolidation, select Consolidation
Ownership Manager Edit .
● The top of the window shows the Category, Time, and Groups setting for the active current view. Use the
member lookup in these fields to change the Category and Time members for which you want to create an
ownership-based hierarchy. Use the member lookup in the Groups field to specify the member that you want
to use as the parent in the hierarchy. If this Group dimension member is defined as part of a fixed hierarchy for
a statutory consolidation, this fixed hierarchy is imported intact into the Ownership Manager. In the tree
structure to the left, expand the parent member to view any existing children.
You can also maintain children for each group level by choosing a group and clicking Add to add entities to or
remove entities from the group. Currently you cannot choose an external entity members to add to the group.
● To display all members that have detail but are not used in a hierarchy, select the Show empty option in the
toolbar. This function helps assure that you do not forget to specify the method and percentage for newly
inserted members.
● After you create the desired hierarchy, you can enter detail for each child member, as described in the
following section, and run ownership calculations.
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.
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.
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.
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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 37
Related Information
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:
Table 6:
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:
Table 7:
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
38 PUBLIC 4HANA (Embedded)
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:
Table 8:
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:
Table 9:
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:
Table 10:
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 39
USA Full 100% 100%
Related Information
You can prepare reports containing system information and a history of business user activities.
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:
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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
40 PUBLIC 4HANA (Embedded)
More Information
You can generate reports on Business Process Flows (BPFs). Reports can be viewed online and printed.
Features
● Instance
● Activity
Activities
To view a business process flow audit report, select go to System Reports, and from the list of reports, choose the
type of report that you want to create. Set the appropriate reporting options, and display the report.
Business Planning and Consolidation records audit information on who changed transactional data in the
InfoProvider.
Features
The report shows who changed the data, what time they made the change, how they made the change (for
example, through SAP EPM solutions, add-in for Microsoft Office), and the details of the record that was changed.
You can choose from the criteria listed below to fine tune your report. In the report, the columns correspond to
these parameters.
Table 11:
Option Description
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 41
Option Description
Dimension Members Select the dimension and dimension members the audit infor
mation is stored against.
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).
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
42 PUBLIC 4HANA (Embedded)
Activities
To view a data changes report, go to System Reports, and from the list of reports, choose Data Changes. Set the
appropriate reporting options and display the report.
More Information
The report on work status allows you to display the work status codes for a set of given criteria.
Work status is a feature that allows you to lock regions of data from being overwritten. You define “work states”, for
example, Locked, Submitted, or Approved, so users can control input to specific data regions.
You can filter the report to the specific region of the model for which you want the work state.
Features
The work status report shows Data State, which is the current work state for the data. It tells you the current stage
of the data in the overall approval process.
It also shows the dimensions for which you define work status as being applicable. There can be 1 to 14
dimensions; the report adjusts dynamically based on the active application.
Table 12:
Option Description
Dimension Members Select dimensions and dimension members that the work sta
tus is stored against.
Date and Time You can choose start and end dates for the report.
Additional Criteria User ID - Enter the User ID for which you need the work status
report.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 43
Activities
To view a work status report, go to System Reports, and from the list of reports, choose Work Status. Set the
appropriate reporting options and display the report.
Related Information
1.6 Administration
Setup and maintenance of Business Planning and Consolidation consist of the following tasks:
● Environment management
● Dimension management
● Model management
● Legal consolidation
● Security management, which is explained in the Security Guide available on the SAP Help Portal.
● Management of controls
● Set up of business process flows
● Set up of work statuses
● Set up of auditing
Related Information
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
44 PUBLIC 4HANA (Embedded)
1.6.1 Environment Management
An environment is a virtual concept of a container that holds different planning scenarios in the form of models.
Company-wide planning processes can be built on top of an environment.
Features
Administrators create new environments from scratch in the Manage All Environments screen.
Administrators can use an e-mail notification service to send e-mails to users or teams defined in the system. The
appropriate SMTP parameters must be set up correctly. For detailed information, refer to the SMTP Configuration
Guide available on the SAP Help Portal.
Deleting Environments
You can delete environments after choosing Manage All Environments and selecting an environment.
Caution
When you delete an environment, you will delete all objects under this environment:
● Models
● BPF templates and instances
● Work status settings and data
● Worksheets
● Analysis Office add-in reports
However, all BW modeling and settings done in the BW back-end transactions will still be available.
You create new environments from scratch in the Manage All Environments dialog.
Activities
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 45
2. Click the name of the current environment.
3. In the dialog that appears, choose Manage All Environments.
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.
A dimension is a collection of related data members that represent one aspect of a business, for example,
accounts, products, or entities.
Table 13:
Displaying Dimension You can modify an existing dimension. When you modify a dimension, you can change the name,
Structures description, dimension type, reference dimension, and dimension properties as well as enable
member formulas for the dimension.
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.
Processing Dimensions When you create a dimension or make changes to an existing dimension, you need to process
the dimension.
Maintaining Hierarchies You can add a new hierarchy, maintain an existing hierarchy structure, or delete an existing hier
archy.
Maintaining Dimension Se You can manage dimension member security at the dimension level using Business Warehouse
curity and a Business Planning and Consolidation data access profile.
Creating Local Dimensions You can create local dimensions based on existing central dimensions, as well as remove unnec
essary properties and add new properties during the creation process. Local dimensions can
also be deleted when they are no longer useful.
See Creating Local Dimensions [page 51] and Deleting Local Dimensions [page 53].
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
46 PUBLIC 4HANA (Embedded)
Activities
To manage dimensions, go to the Administration screen and under Modeling choose Dimensions. Once you select a
dimension, you can perform one of the available tasks.
Security
For information about the authorizations needed to maintain master data for dimensions, see the Security Guide,
which is available on the SAP Help Portal.
Related Information
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.
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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 47
Features
A dimension contains a set of predefined properties based on its type. You can add new properties by using the BW
modeling tools, if desired.
You can add, delete, and modify members in dimensions within an environment in the Administration section.
Under the Modeling section, choose Dimensions , select a dimension, and then choose Edit Members.
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.
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.
● 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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
48 PUBLIC 4HANA (Embedded)
1.6.2.3 Dimension Processing
Whenever you add a new dimension member, modify an existing dimension member, or delete a dimension
member, you must process the dimension.
Activities
You can process dimensions in the Administration screen. In the Modeling section, choose Dimensions , select
one or more dimensions, then choose Process.
You can also process dimensions when you maintain a dimension member by choosing Save and Process.
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.
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.
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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 49
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 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:
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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
50 PUBLIC 4HANA (Embedded)
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.
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.
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:
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 51
● 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
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
52 PUBLIC 4HANA (Embedded)
Related Information
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.
A model is a representation of the relationships, calculations, and data of an organization or business segment.
Models can be categorized as ‘planning models’ or ‘consolidation models’. Planning models are used for generic
planning-related activities. Consolidation models are designed for performing legal consolidation tasks.
Consolidation type models must have specific components defined to fullfil legal consolidation requirements. For
detailed information, see Planning and Consolidation Models [page 56] and Set up a Consolidation Model [page
61].
Features
To create a model, go to Administration and under the Modeling section, choose Models. On the screen that
appears, choose New.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 53
When you create a new model, you set references to InfoProviders that exist in SAP Business Warehouse (BW).
You can choose an arbitrary number of InfoProviders to include in the model. When creating a new model you can
use the following types of InfoProviders:
Recommendation
We recommend that you familiarize yourself with the documentation of SAP BW as all InfoProviders that you
can use for creating models in Business Planning and Consolidation are delivered by BW.
Note
You cannot create new InfoProviders through the web interface of Business Planning and Consolidation. If you
want to create InfoProviders that you could later use in your models, you must create them in the BW modeling
tools. For more information, see the documentation of .
To add a new InfoProvider to a model, or to remove an InfoProvider that is already included in the model, follow the
steps below:
You can review the structure of each individual InfoProvider that is included in a model. To do this, follow the steps
below:
Note
The Business Planning and Consolidation web user interface displays only simple aggregation levels. These
aggregation levels are set on DataStore Objects (advanced). The complex aggregation levels (aggregation
levels that are created on CompositeProviders) are not displayed.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
54 PUBLIC 4HANA (Embedded)
● Related MultiProviders - shows the MultiProviders that exist for the selected InfoProvider.
You can add business rules to a model in the Business Rules area of the Administration screen. You activate the
rule types you need for the model and add the new business rules of each type to the model. For more information,
see Business Rules Management [page 79].
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 131].
Deleting Models
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 55
1.6.3.1 Planning and Consolidation Models
The following table describes the different types of models and lists the InfoProviders available for each.
Table 14:
Planning Planning models are used for reporting No specific InfoProviders are required for
a planning model.
and planning.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
56 PUBLIC 4HANA (Embedded)
1.6.3.2 Working with Local Providers
Local providers work in a similar way to central InfoProviders. You can use local providers for different purposes, for
example, as a basic information holder for an ad-hoc planning application.
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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 57
○ Map to a global BW InfoObject and select the checkbox Generate Local InfoObject to create a local
InfoObject
○ Map to an existing local InfoObject, which are InfoObjects created in the current environment
For information about how to create a local dimension directly from a dimension list, refer to Creating
Local Dimensions [page 51].
A local InfoObject (dimension) has the same metadata as the global BW InfoObject from which it was created.
The local InfoObject inherits master data from the global BW InfoObject; master data changes in the global
BW InfoObject are reflected in the related local InfoObject. Also, new members are visible only in the local
InfoObjects and overwrite the property values of global members (members from the global BW InfoObject).
Choose Next.
6. In the Create Model step you can create a new model that uses the local provider. If you do not need to create a
model at this time, you can skip this step.
Note
Models that contain a local provider cannot be exported.
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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
58 PUBLIC 4HANA (Embedded)
Choose Next.
5. Review your changes and choose Done.
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.
Besides the default aggregation level that is generated automatically, you can also create new aggregation levels
with transaction RSPLAN.
You can also create new queries on aggregation levels with BW modeling tools. Queries can be consumed through
the Business Planning and Consolidation Web client or the Analysis Office add-in.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 59
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.
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:
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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
60 PUBLIC 4HANA (Embedded)
To set up your consolidation environment, you do the following:
● Create the legal consolidation environment and set the necessary parameters. See Creating an Environment
for Legal Consolidation [page 61].
● Create required InfoObjects and InfoProviders and maintain required InfoObject attributes in BW modeling
tools. See Create InfoObjects and InfoProviders [page 62] and Maintain InfoObject Attributes [page 65].
● Create the consolidation model. See Create or Modify a Consolidation Model [page 76].
● Enable business rules. See Business Rules Management [page 79].
● Make sure the EXCHANGE RATE InfoProvider and OWNERSHIP InfoProvider are maintained in Business
Warehouse. See Create or Modify a Consolidation Model [page 76].
● Define tasks order in task sequences. See Set Task Sequence [page 76].
● Set the work status, which is optional.
● Set the journal template and validation criteria. See Journal Administration [page 136].
If you have an existing environment, for example for planning or reporting, you can use this environment to host
your legal consolidation. Using the environment for planning or reporting as a basis to build consolidations allows
you to share the relevant dimensions, such as account, with your consolidation environment.
Since SAP Business Planning and Consolidation directly consume Business Warehouse data, you must prepare
InfoObjects (dimensions) and related attributes (properties) in BW to be used by the consolidation engine of SAP
Business Planning and Consolidation.
1. Create the required InfoObjects. See Create InfoObjects and InfoProviders [page 62].
2. Maintain the InfoObjects with required attributes. See Maintain InfoObject Attributes [page 65].
3. Create required InfoProviders, such as DataStore Objects (advanced) and CompositeProviders and input
relevant InfoObjects. See Create InfoObjects and InfoProviders [page 62].
4. Create aggregation levels based on the InfoProviders. See Aggregation Level.
After that you can create a Consolidation model and define it in the SAP Business Planning and Consolidation web
client, including adding InfoProviders with aggregation levels predefined in BW to the Consolidation model,
mapping InfoObjects to corresponding Business Planning and Consolidation dimension types and mapping
attributes of the InfoObjects to related Business Planning and Consolidation dimension properties. For detailed
settings, refer to Create or Modify a Consolidation Model [page 76].
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
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 61
● 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.
Follow these guidelines to create InfoObjects and InfoProviders that can be used by the Consolidation engine of
Business Planning and Consolidation.
In SAP Business Planning and Consolidation, a consolidation model requires the following types of InfoProviders to
be mapped from Business Warehouse:
Note
For the two mandatory CONSOLIDATION and OWNERSHIP InfoProviders, you must make sure they contain
inputtable InfoProviders, such as DataStore Object (Advanced) or CompositeProviders that contain DataStore
Objects (Advanced).
You also need to create the InfoObjects required by the Consolidation engine of Business Planning and
Consolidation that match various Business Planning and Consolidation dimension types and input them into
different types of InfoProviders. You can choose the names of these InfoObjects, but we suggest that you name
them according to the dimensions you are going to match in the Business Planning and Consolidation web client.
These dimension include:
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
62 PUBLIC 4HANA (Embedded)
Table 15: Business Planning and Consolidation dimensions
Dimension Description
Account (CONSOLIDATION) Members of this dimension are, for example, Revenue or Sal
aries.
Account (RATE) Members of this dimension are used to detail the different
types of rate, for example, Average or End-of-period.
Account (OWNERSHIP) Members of this dimension are, for example, METHOD (con
solidation method), POWN (ownership percentage), and
PCON (control percentage).
Category Contains the types of data you are going to track, such as Ac
tual, Budget, and Forecast. You can also set up categories to
store versions, such as BudgetV1 and BudgetV2.
Entity (CONSOLIDATION) Contains the business units that are used to drive the business
process. Depending on your model design, the Entity type can
be, for example, an operating unit, a cost center, or a geo
graphic entity.
Entity (RATE) Used to store multiple tables of rates, if desired; otherwise, the
R_Entity dimension may be limited to one dummy member,
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 currency.
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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 63
● 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:
Account (Consolida A √
tion)
Account (Ownership) A √
Account (Rate) A √
Audit D √
Flow S √
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
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
64 PUBLIC 4HANA (Embedded)
1. Go to the BW Modeling Tools.
2. Refer to the required Business Planning and Consolidation dimensions and create corresponding InfoObjects
for each. For more information about creating InfoObjects, refer to .
3. Maintain the required attributes of the InfoObjects. See Maintain InfoObject Attributes [page 65].
4. Create the following four InfoProvider in the types of: CONSOLIDATION, OWNERSHIP, RATE, and SOURCE.
5. Input corresponding InfoObjects to each InfoProvider.
6. Create aggregation levels based on the InfoProviders.
Note
When adding the InfoProviders to the Consolidation model you want to create, you must select an
aggregation level based on the InfoProvider to make sure only the desired dimensions required for legal
consolidation are selected.
After these InfoProviders and InfoObjects are correctly maintained, you can further add and map them when
creating or modifying a consolidation model in SAP Business Planning and Consolidation. For detailed settings,
refer to Create or Modify a Consolidation Model [page 76].
Several dimension properties are required by the consolidation engine of SAP Business Planning and
Consolidation.
When you map the required InfoProviders into a consolidation model, all the underlying dimensions will
automatically be referred into the dimension library. To ensure the correct operation of consolidation and related
processes, such as currency translation, simulation, and eliminations and adjustments, several dimension
properties are required by the consolidation engine of SAP Business Planning and Consolidation, and you need to
ensure that these properties are maintained in Business Warehouse so that they could be further mapped while
creating the consolidation model in SAP Business Planning and Consolidation. You should also ensure that these
properties are maintained with the appropriate values of the consolidation process for your business
requirements.
Account Dimensions
The Account dimension defines the chart of accounts for the model and how these accounts are calculated and
aggregated. Any dimension that is assigned the type A is considered an Account dimension. Each InfoProvider can
have only one account-type dimension.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 65
Table 17: Account Dimension Properties
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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
66 PUBLIC 4HANA (Embedded)
This can be done by either creating an additional simulation CATEGORY, such as Actual_at_Budget_rate or similar,
or adding an extra dimension to the MAIN InfoProvider, where all the simulated cases can be stored.
There is no need to copy the input values to all models for all the desired simulations. A few definitions stored in
some specialized properties of the CATEGORY or the FX simulation dimension inform the translation procedure
where to read the input values and where to write the translated results.
To minimize the impact of the different simulations on the size of the database, it is also possible to tell the system
to store only the difference between the default results and the simulated scenarios.
When using the simulation categories in the MAIN InfoProvider, simulated translations are stored in additional
members of the Category dimension. These categories have non-blank values for one or more of the properties in
the table below.
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:
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 67
Table 19: Special Properties for Category Dimensions
CATEGORY_FOR_OPEN 20 ● Blank
The category for the opening balan
ces is the same.
● Not blank
The ID of the category from which to
read the opening balances.
OPENING_YEAR 4 ● Blank
Read the opening balances from the
year before the current year.
● Not blank
Contains the year from which to
read the opening balances. It can be
an absolute or a relative amount.
OPENING_PERIOD 10 ● Blank
Read the opening balances from the
last period of the year.
● Not blank
Contains the period from which to
read the opening balances. It can be
an absolute or a relative amount.
Audit Dimension
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
68 PUBLIC 4HANA (Embedded)
Table 20: 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 cur
rency. That is, the members are
copied from the reporting currency
of the GROUP that is being trans
lated into the currency member cor
responding to the specified group.
IS_CONSOL 1 ● Blank
YiKó[÷©ºpŸ1e=ˆ¯r¦vžÏêíIGVì²Ł´7á›ójw=hþ ¤öþ ïT‡Òq0−4p‘vt`ñŠ˜í
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 eliminations into
a data source with property DA
TASRC_LEVEL of Y in the GROUP di
mension.
OPENING_DATASRC 20 ● Blank
The data source is the same as the
source member.
● Non-blank
Contains the ID of the desired desti
nation data source for the copy.
Entity Dimension
The Entity dimension defines the organizational structure of the business units for your model and how the units
aggregate. Any dimension that is assigned the type E is an Entity dimension. Each model can have only one entity-
type dimension.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 69
The following table details the entity dimension properties:
Optional
Intercompany Dimension
The Intercompany dimension (I) defines the intercompany codes for entities in consolidation and ownership
InfoProviders.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
70 PUBLIC 4HANA (Embedded)
Table 22: Intercompany Dimension Properties
Currency
The currency type dimension is required to report on local currency and translated values. The required property
for currency dimension is the following:
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:
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 71
Dimension Type Property Name Length Description of Property Val
ues
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
72 PUBLIC 4HANA (Embedded)
Dimension Type Property Name Length Description of Property Val
ues
Note
The ENTITY attribute
should use the same In
foObject as the ENTITY di
mension in the model.
Also, the value entered in
the ENTITY attribute
should be a valid entity ID.
● 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 cur
rency dimension.
● N (or blank)
If only the Group mem
ber is to be stored, set
this property to N.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 73
Dimension Type Property Name Length Description of Property Val
ues
G STORE_ENTITY 1 ● Y
If you want to store in the
ID entered in the Entity
property.
● Blank
If you do not want to
store in the ID entered in
the Entity property.
● G - Group member
● N - Non-group member
G FIRST_CONS_DATE 10 ● Blank
Management model
● YYYYMM
Indicates the month and
year of the consolidation.
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.
● 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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
74 PUBLIC 4HANA (Embedded)
If you choose to use a flow type dimension, the following properties are required:
Flow dimensions should contain dimension members that require the following FLOW_TYPE property values:
● OPENING
● CLOSING
● VARSCP
Optional - All dimensions could be mapped with the ENABLEJRN property and the DIMLIST property. For detailed
information about the property ENABLEJRN, refer to Limits to Dimension Members for Journal Entries [page 140].
Activities
● To make sure every dimension (InfoObject) possesses the required dimension attributes for a consolidation
scenario, you need to maintain the dimension structure beforehand in BW modeling tools. For detailed
information, refer to .
● To make sure the dimension master data is correct, you can maintain the master data either in BW modeling
tools, or you can maintain the dimension master data directly in the SAP Business Planning and Consolidation
web client. Refer to Dimension Management [page 46] for details on how to maintain dimension master data.
After dimension (InfoObject) attributes and its master data are correctly maintained, you can further map those
attributes when creating or modifying a consolidation model in SAP Business Planning and Consolidation. For
detailed settings, refer to Create or Modify a Consolidation Model [page 76].
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 75
1.6.4.2.3 Create or Modify a Consolidation Model
A model is either a planning model or a consolidation model. After completing relevant Business Warehouse back-
end settings, you can create and define a consolidation model in the Business Planning and Consolidation web
client.
Within the same environment, multiple consolidation models may exist, each one pointing to its own
consolidation, rate, and ownership InfoProviders. Multiple consolidation models can share the same consolidation
or rate or ownership InfoProviders, if appropriate.
To create a consolidation model, you must map BW InfoProviders to a CONSOLIDATION InfoProvider and an
OWNERSHIP InfoProvider. You have the option to map BW InfoProviders to an EXCHANGE RATE InfoProvider and a
SOURCE InfoProvider. Then, you need to map InfoProvider dimensions to dimension types required by the SAP
Business Planning and Consolidation consolidation engine, as well as map InfoObject attributes to dimension
properties required by the consolidation engine.
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
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
76 PUBLIC 4HANA (Embedded)
● 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:
Example
The superior dimension of C1000 and C2000 is China. If you want to choose C1000 and C2000 of the entity
dimension ZPAKENT from the V1 version of hierarchy H1 and you select P1 from the user-defined dimension
PRODUCT, you enter the formula below in the Other Dimension Filter field:
Through the task-specific settings you can customize tasks of the same task type and use different task names to
identify these tasks. For example, you can define two account-based calculation tasks and give them different task
names. Then you can go to Consolidation Monitor and select either of the account-based calculations to trigger
the corresponding task.
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
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 77
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 .
SAP Business Planning and Consolidation leverages Business Warehouse planning functions to execute
consolidation tasks.
Before implementing a scenario for consolidation, you first need to install all necessary InfoObjects including /
CPMB/RULE and /CPMB/RENT and required planning functions including /CPMB/LAUNCH_LOGIC and /CPMB/
WRITE_BACK. For detailed steps, refer to the section “Install InfoObjects and Planning Function Types Necessary
for Consolidation (Embedded only)” in the Installation Guide available on the SAP Help Portal.
After you enable these InfoObjects and planning function types, you can trigger consolidation tasks either through
the planning function in the Business Warehouse backend or in Consolidation Monitor in the Business Planning
and Consolidation web client.
Consolidation tasks, such as currency translation as well as matching and elimination of inter-unit balances, are
predefined functions in Business Planning and Consolidation to calculate and post amounts required to support
common accounting activities.
For each predefined function, there are one or more business rule tables that provide the flexibility for you to
customize the functions to meet your specific business needs without having to understand scripting or
programming. For more information about the business rules delivered with SAP Business Planning and
Consolidation, see Business Rules Management [page 79].
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
78 PUBLIC 4HANA (Embedded)
The RATE model stores the exchange rates for currency translation. You should make sure the exchange rate
data is already correctly maintained inside the RATE InfoProvider that is referenced by your consolidation
model.
2. Input ownership data and calculate ultimate ownership.
SAP Business Planning and Consolidation provides Ownership Manager in Consolidation Center so you can
update the Ownership InfoProvider directly.
3. Load the financial data.
After loading the financial data, use an SAP Business Planning and Consolidation report to validate that the
numbers reconcile with the numbers in the source system.
1.6.5 Rules
Business rules are parameter-driven functions within models for calculating and posting monetary amounts in
support of common accounting activities.
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
When you create or modify a model, you can add business rules to it. You can add the following types of business
rules:
● Account-based calculation
● Currency translation
● Intercompany booking
● Carry-forward processing to initialize beginning balances when a new fiscal cycle starts
● US Eliminations
● Eliminations and adjustments when generating consolidation entries for a group of entities, such as
eliminations, adjustments, reclassifications, and minority calculations
After adding a business rule type to a model, you must customize it to meet your needs by specifying parameter
values. For example, in Eliminations and Adjustments, you can indicate which balances to read before calculating
an amount, or under which account and audit member to post the calculated amount. In addition to customizing
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 79
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.
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:
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.
You can verify the detail records of a business rule after modifying it by clicking Validate in the <Rule Name> page.
A message appears displaying a successful status or any errors encountered.
Note
Currently you can choose text nodes and external nodes as source members of the dimension types account
(A), category (C), audit (D), and flow (S), but not as destination members unless the source and destination
dimensions share exactly the same hierarchy.
Activities
In SAP Business Planning and Consolidation, all business rules need to be run through Consolidation Monitor. To
do this, you need to first define a task sequence after setting up all the business rules and then trigger these tasks
from Consolidation Monitor.
Related Information
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
80 PUBLIC 4HANA (Embedded)
1.6.5.1.1 Account-based Calculation Rule
Account-based calculations read and aggregate the values posted to specific combinations of accounts, flow
types, and audit members in order to post the aggregated amount under an alternate destination account, flow
and audit member combination. You may apply this rule for cash flow reporting.
Features
The following dimensions can be specified in order to define source and target members in the calculation:
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.
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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 81
● 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
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
82 PUBLIC 4HANA (Embedded)
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.
● Some dimensions, such as Account, Entity, and Currency, must contain appropriate properties as noted in the
following table:
Table 26:
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 83
Model Dimension Property Description
○ L (local currency)
○ R (reporting currency)
○ G (group, for compati
bility on migrated mod
els only)
○ G (Group)
○ N (Non-Group, used for
data input)
The following properties in the Audit and Flow dimensions are mandatory:
Table 27:
● I (input)
● M (manual adjustment)
● L ( audit level, for consolidation
only)
● A (eliminations and adjustments)
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
84 PUBLIC 4HANA (Embedded)
Dimension Property Description
● 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.
The Intercompany booking function supports the overall Intercompany reconciliation process.
Prerequisites
● 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
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 85
○ C1 – Their Credit
○ C2 – My Credit
● The appropriate business rule table must be set up.
● The Account dimension must define a dedicated hierarchy to include all accounts for Intercompany booking.
This configuration not only allows intercompany details to be entered for any account, but it also supports an
automatic elimination-by-level for all desired accounts.
Note
Although not mandatory, Intercompany reconciliation is normally performed in a separate Intercompany
matching application apart from the actual Consolidation application.
Features
The consolidation engine supports a mechanism to perform the matching of the inter-company declarations
among the entities of a group. This mechanism is split into two independent procedures as follows:
● ICDATA: this procedure can be used to copy the declarations of all entities versus a given entity by inter-
company account. Essentially it concentrates into each single entity the declarations of all other entities
versus each entity. This mechanism allows the owners of an entity to run a report matching all its declaration
against what the rest of the world has declared against him, without the need to assign to each owner read
permits into other entities.
● Intercompany Booking: this procedure can be used to automatically generate the bookings that will make the
intercompany declarations match.
By defining “Seller”, “Buyer”, or “Greater” in the business rule booking type, the system can automatically book the
difference by assuming the correct value is Seller, Buyer, or either one with the greater booking value.
By configuring the “Maximum Booking” amount, you can set up the maximum threshold for automatic booking.
Any differences bigger than this maximum value will be kept for manual adjustment later.
Intercompany bookings are executed from the Consolidation Monitor in the Consolidation Central area.
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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
86 PUBLIC 4HANA (Embedded)
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.
Prerequisites
The following are required to perform intercompany eliminations within the Consolidation InfoProvider of a model:
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
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 87
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:
Table 28:
● 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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
88 PUBLIC 4HANA (Embedded)
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
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
● 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
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 89
● Eliminations and Adjustments rules
Define the balances upon which eliminations and adjustments are made and the items such as accounts and
flow to which calculated amounts are posted
Features
The most important of the necessary adjustments for legal consolidation relate to the elimination of intercompany
activity between the various reporting units, and reclassifications and supporting the model of the applicable rules
for the accounting of long-term investments. Eliminations and adjustments rules support the calculation and
generation of these postings.
Eliminations and adjustments rules are applicable only to a legal consolidation model to which you attach a
corresponding ownership InfoProvider.
When eliminations and adjustments rules are executed for a given group, the system performs the following:
● Reads from the ownership InfoProvider which entities make up the group, the applicable consolidation
method, and the ownership and consolidation percentages.
● Determines for each elimination and adjustment defined in the business rules the base amount upon which
the elimination and adjustment is to be calculated based on the source data.
● Identifies for each elimination and adjustment the corresponding method-based multiplier from the business
rules.
● Based on the identified method-based multiplier and the method of consolidation assigned to a given entity,
determines the formulas to apply in calculating the amounts to post. Ownership and consolidation
percentages can be applied in the calculations.
● Posts the calculated amounts based upon the posting rules defined in the Eliminations and Adjustments
business rules tables.
The following information describes the fields of the General tab in the Business Rules interface of Eliminations
and Adjustments:
● Source Audit ID: Restricts the type of transaction data to which the rule applies. This can be a member of the
audit dimension, or a DIMLIST in the audit dimension. This field can also be blank to represent all audit
members with an audit type of I or M. (You can use Adjustment Level to apply further restriction.)
● Destination Audit ID: Indicates the kind of data the rule generates. This should be one base member with an
audit type of A.
● Group Type Filter: Restricts the rule to specific group or scope members.
● Entity Property Filter: Similar to Group Type Filter, this restricts the rule to specific entity members.
● Adjustment Type: Defines the rule type. Possible values are the following entries:
○ Blank: generic rule type
○ N: for new entities in the group/scope; similar to a generic rule
○ P: for proportional entities
○ E: for equity entities
○ L: for entities that leave the group/scope in the beginning of the year
○ I: for integration consolidation, which deals with the inconsistencies that occur when some consolidation
rules are defined using periodic mode while the ownership hierarchy changes during the fiscal year. For
more information, see Integration Rule for Consolidation [page 95].
● 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
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
90 PUBLIC 4HANA (Embedded)
rule with a lower adjustment level can be the input of an elimination rule with a higher adjustment level. The
source audit ID for an elimination rule with an adjustment level larger than 0 has further restrictions.
● Other Dimension Filter: A string in this field indicates filters or special restrictions on other dimensions. For
example, if you have a user-defined dimension called Product and you want to run an elimination for only one
of its members called Pro1, you would enter Product = Pro1.
● Force Destination Member: When filled, indicates the value to which the system should force the elimination
result. For example, if you enter Product = ALL, then for the generated elimination result, the system
populates the dimension Product to ALL, no matter what the original value was.
● Ownership Filter: Filters the ownership value. For example, to apply a rule to only those entities whose
ownership percentage in a group or scope is larger than 70%, you enter POWN > 0.7.
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
● Methods
● Method-based multipliers
Global Definitions
You can add a new Global Definition in Planning and Consolidation Administration by:
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.
Table 29:
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
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 91
Field Name Description
Example
Leaving, Equity, Proportional, Global, Holding.
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.
Table 30:
Example
RULE01
Example
Equity, 100% Minority part, Dividends, Stock Holder Equities, Inter
company elimination
Type The consolidation method using the method-based multiplier can be re
stricted to:
● Proportional
● Equity
● Leaving
● Disposed
● New
● or blank
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
92 PUBLIC 4HANA (Embedded)
Field Name Description
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 multiplier
applies.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 93
Field Name Description
ALL Formula An expression that represents the percentage (or formula) to apply to the
Destination All account property from the Eliminations and Adjustments
business rule.
Example
[POWN], [PCTRL], [POWN]
Example
[PPOWN], [PPVOTE]
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.
There are two options for obtaining results: system calculations and
manual updates. There is also an option to change from system to
manual while calculating. This gives you the means to manage secur
ity by protecting system calculations that cannot be overwritten by
manual updates.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
94 PUBLIC 4HANA (Embedded)
Field Name Description
Group formula An expression that represents the percentage (or formula) to apply to the
Destination Group account from the Eliminations and Adjustments busi
ness rule. The value can be an arithmetic expression combining any de
fined 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 Adjustments
business rule. An arithmetic expression combining any defined percent
age 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.
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:
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.
When the integration mode is enabled for a model, the currency translation does not generate results on the group
level.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 95
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.
Procedure
1.6.5.2 Controls
Controls enable you to test the validity of data gathered in a reporting process.
Use
Controls can be applied to any type of data. For example, a control can be used to check whether assets equal
liabilities for data entered in data entry schedules or for adjustments entered in journals.
Controls are run on the data available in the model in loaded data (local currency), translated data, or consolidated
data, on base entities. If a dimension is deleted from the model, all control results relevant to that dimension are
also deleted.
The main steps to follow when setting up your controls are as follows:
Business Planning and Consolida 1. Associate a level to each entity in the entity dimen
tion Administration sion
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
96 PUBLIC 4HANA (Embedded)
Location Step Additional Information
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 execute controls in Consolidation Central Controls Monitor . You can also execute tasks in a business
process flow, provided that the relevant tasks are set up in the business process flow definition.
Prerequisites
To view the Controls page in Planning and Consolidation Administration, you must have the View Controls
Manager right. You can follow the steps in the topic “Authorization for Performing Consolidation Tasks” in the
Security Guide of this release to assign relevant authorization objects to target users.
Features
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 97
Enable controls
Controls can be enabled or disabled at the model level in Planning and Consolidation Administration. Controls can
be enabled only in a consolidation type model.
Before enabling controls, make sure two properties of the Entity dimension, namely Control Level and
CTRL_CURRENCY_NOT_LC (Bypass LC in Ctrls) are mapped to corresponding InfoObjects in Business
Warehouse. For detailed information, refer to the topic “Map Dimension Properties” in the Business Warehouse
application help.
Note
To enable controls, work status dimensions must be set with at least three main dimensions: Category, Time,
and Entity. For more information, see Create a Control [page 99].
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 108].
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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
98 PUBLIC 4HANA (Embedded)
● 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 108].
Prerequisites
Procedure
You create controls in the Controls page of Business Planning and Consolidation Administration.
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.
● ID
● Description
● Rule Type
● (Control) Type
● Execution Level
● Equation Type
● Control Level
● Breakdown Dimensions
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 99
● Absolute Value
● Calculate on YTD
● Tolerance Threshold
● Expressions
ID
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
● 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
● 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.
● Basic: Level 1
● Standard: Level 2
● Advanced: Level 3
● Comprehensive: Level 4
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
100 PUBLIC 4HANA (Embedded)
Controls are executed according to the control level associated with the selected entity. If an entity has no control
level defined, it is automatically assigned Level 4, meaning all controls are run when a control set is executed.
Breakdown Dimensions
Choose up to two dimensions for which the control should be executed on all members. Breakdown dimensions
allow you to define controls to be run on any type of data, for example, input, manual adjustments, automatic
adjustments.
Example
CTRL1 is defined as TOTAL_ASSET = TOTAL_LIABILITIES, breakdown dimension: DATASOURCE with member
TOTAL_INPUT specified in the control expression. TOTAL_INPUT is the aggregation of INPUT, INPUT_ADJ1 and
INPUT_ADJ2.
When the control is executed, it compares TOTAL_ASSET versus TOTAL_LIABILITIES for both members INPUT,
INPUT_ADJ1 and INPUT_ADJ2. As a result, if two members generate an error, the following information is
generated:
● One row appears displaying the aggregated information for the control, without data in any of the columns
except for the status, which displays as Failed.
● Two rows appear for the given control to display the detailed calculations with data for both lines.
Note
Any dimension can be used as a breakdown dimension, except for dimensions used as driving dimensions in the
Work Status setting, currency dimensions, and group dimensions.
Absolute Value
Selecting Absolute Value indicates that the system should treat the value for the control as an absolute (non-
negative) value regardless of whether it is positive or negative.
Example
Result A is 100 and result B is -125. If you set the rule to check whether result A is larger than (>) result B and
you do not select Absolute Value, then it passes. If you select Absolute Value for this rule however, the system
compares 100 and 125, and the result fails.
Calculate on YTD
As data stored is supposed to be periodic data, this option indicates the type of data on which the control runs.
When the option is checked, the control runs on year-to-date data when YTD aggregation is performed during the
execution of the control. When unchecked, controls are run on periodic data.
Tolerance Threshold
The tolerance threshold is an amount that is compared to the difference between the two amounts (the "control
result"). If the control result is less than or equal to the amount defined in the tolerance threshold, then the
difference is considered to be insignificant and the control status is considered to be OK.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 101
Example
Table 32:
Amount x: 1,000,000
Amount y: 1,000,000.5
Difference: 0.5
Amount x: 1,000,000
Amount y: 1,000,000.5
Difference: 0.5
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
102 PUBLIC 4HANA (Embedded)
x≤y < Tolerance Valid Tolerance entered: 1
Amount x: 1,000,000
Amount y: 1,000,000.5
Difference: 0.5
Expressions
The expression is the formula used for identifying the two amounts to be compared. In the Expressions tab, the
upper panel contains the formula for identifying the first amount to be compared. All the dimensions must be
specified.
When breakdown dimensions are specified, an icon appears in the column header identifying that dimension as a
breakdown dimension.
The lower panel contains the formula for identifying the second amount to be compared, which can be from
another Category, Time, or Group.
In the Category field you can enter any member from the Category dimension. In the Year Offset field, you can
enter an integer preceded by "+" or "-". In the Period field you can enter an integer which is associated to the
MONTHNUM property of the Time dimension. For relative periods, "+" or "-" signs can be used; for example, for the
previous month you enter "-1".
If the lower panel is left blank, the first member of the expression that was defined in the upper panel is compared
to zero.
Follow these steps to make the Execution Level field visible in the Web client:
1. Go to transaction SPRO.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 103
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.
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.
● 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
Prerequisites
To edit controls in Planning and Consolidation Administration, you must have the Edit Controls Manager
right. You can follow the steps in “Authorization for Performing Consolidation Tasks” in the Security Guide available
on the SAP Help Portal to assign relevant authorization objects to target users.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
104 PUBLIC 4HANA (Embedded)
Context
Procedure
Related Information
Prerequisites
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 105
Context
Procedure
Related Information
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
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
106 PUBLIC 4HANA (Embedded)
Procedure
The copied control set contains the same controls as the original control set. You can then modify the control
set as needed.
Related Information
Prerequisites
Context
Procedure
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 107
3. In the Control Sets: <Model name> page, select all control sets you want to delete and click Delete in the
toolbar.
Related Information
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
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
108 PUBLIC 4HANA (Embedded)
1.6.5.4.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.
There are two ways to display the category/time pair assignments for control sets:
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.
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
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 109
Assign a Control Set [page 108]
Additional Actions Involving Control Sets [page 109]
This function enables you to create and manage business process flow (BPF) templates - also called process
templates - and manage the processes created from these templates.
A process template is the specification of a single enterprise-wide business process, containing tasks that can
span across the various modules of Business Planning and Consolidation. It defines the business processes that
are presented to users as a prepackaged set of application tasks. For an additional level of control over the
workflow, you can integrate work status rules.
Once you have completed a process template, you can create a process based on the template, in the
Administration screen. A process represents an iteration of the enterprise-wide business process, which allows the
user to see only the tasks relevant for that user, given his or her role and data access privileges.
Prerequisite
You must have the BPF authorization object RSBPC_BBPF assigned to you in order to manage business process
flows. For detailed information about how to assign the authorization object, refer to the topic “Authorization
Objects” in the Security Guide available on the SAP Help Portal.
Features
Table 33:
Create new process templates You can create a new process template on which to base proc
esses, copy existing process templates, and modify existing
templates. For more information, see Creating New Process
Templates [page 111].
Validate process templates When you create a new process template, the system auto
matically validates the template for completeness before sav
ing 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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
110 PUBLIC 4HANA (Embedded)
Function More Information
Unlock process templates If the system automatically locks a template because you un
expectedly logged off while editing, you can unlock it by select
ing the template and clicking Unlock.
Deploy a template If a template is not locked and has a status of Valid, you can
deploy it so that it can be used for creating processes. Select
the template, and click Deploy.
Copy a template and create new version If you want to create a new template based on an existing tem
plate, select the template you want to copy and choose Copy.
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 se
lected template. To view an obsoleted version of a template,
select a template in this window and click View.
Integrate external workflows with BPFs You can integrate external workflows with BPC BPF processes
to accommodate complicated planning processes. For more
information, see External Process Integration [page 129].
With the correct authorization, you can use this process to create a new process template. You can define up to
100 process templates for each environment.
Process
1. Go to Administration and under the Business Process Flows section, choose Process Templates.
2. Choose New to start the creation of a new process flow.
3. On the Process Settings tab, provide details such as name and description of the business process flow. See
Process Settings [page 112].
4. On the Activities tab add activities to represent the flow of the business process. See Activities [page 113].
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
123].
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 111
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.
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 126].
Before creating a process template, you provide basic information that identifies the process template. If you want
to further modify a process template, you can use the same features as the setup process described in this topic.
The following table describes the information you need to complete the setup process in the Process Settings tab:
Table 34:
Item Description
Process Monitors These are the users that have rights to monitor and change
processes created from the process template.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
112 PUBLIC 4HANA (Embedded)
Item Description
Check only the current step when reopening When this checkbox is selected, you can reopen the current
activity if you are the performer or reviewer of the activity.
Otherwise, you must be the performer or reviewer of both the
current activity and the next open activity to reopen the cur
rent activity. For detailed information, refer to Criteria for Re
opening Activities [page 120].
Navigation attribute is now supported in the embedded configuration of Business Planning and Consolidation,
which allows you to select certain navigation attributes as identifying dimensions or driving dimensions in a
process template. After you define an attribute as a navigation attribute in an InfoObject, the navigation attribute
displays in the corresponding InfoProvider. Then enable the checkbox in the On/Off column of the navigation
attribute and you can then use it in the Business Planning and Consolidation web client. For detailed information
about the usage of navigation attribute, refers to .
Activities
To create a process template from scratch, go to Administration and under the Business Process Flows section,
choose Process Templates. Choose New to start the creation of a new template.
You can also use Copy or New Version to create a process template based on an existing template.
To define activities within the business process flow, choose the Activities tab. For more information, see Activities
[page 113].
1.6.6.1.2 Activities
For guidelines on defining activities, see Criteria for Defining Activities [page 116].
The following table summarizes the information that you need to supply for each activity:
Table 35:
Item Description
General
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 113
Item Description
Opening Criteria Select the appropriate radio button to open by All activity con
texts or Matched activity contexts.
Driving Dimension
Map Driver to Create a mapping between the driving dimension and an inter
nal dimension. For more information, see Internal and External
Driving Dimensions [page 122].
Activity Performer
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
114 PUBLIC 4HANA (Embedded)
Item Description
Performer Select the property that defines the performer for each mem
ber.
Note
A property of a dimension is an attribute of a characteristic
in BW. You can maintain BW characteristics using BW mod
eling tools. For more information, see .
Activity Reviewer
Require Reviewer If required, select this checkbox and select a property that de
fines the reviewer for each member.
Reviewer You select the reviewer in the same way as selecting a per
former, but you can select a different property to determine
the reviewer users.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 115
Item Description
Deadline You can define a deadline for the activity’s reviewer in BPF
templates. The deadline is calculated in days by default start
ing 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 Deadlines
for Activities [page 121].
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 123].
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 121].
Activities have defined criteria to control the activity context, opening of activities, review criteria, and reopening of
activities if required.
● 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 owner and reviewer
property for each activity context. The owners 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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
116 PUBLIC 4HANA (Embedded)
● Up to one thousand activities per process template or process can be defined.
● Up to one million activity contexts per process can be defined. The activity contexts can be calculated as a
product of the number of activities and number of process contexts.
Related Information
To complete the creation of an activity in a process template, you must define the activity context criteria for that
activity.
Procedure
You define activity context criteria in the Driving Dimension of the Activities tab by performing the following steps:
1. Select the driving dimension. Each activity has only one driving dimension, and this determines which
members can be selected for that activity.
2. In the Member's drop down list, choose Select Members and set member criteria for the activity context using
the Criteria Editor. There is a limit of six member definitions per step:
○ Select specific valid member IDs from the list. This list is generated depending on the driving dimension
you have selected. You can make multiple dimension member selections.
○ If you select a parent ID, which is a node that has subnodes, in the dialog box that appears, you can
generate dimension members based on the dependent (Children), or base (Base Members) nodes of
the parent ID. If you do not select Children, Base Members, or All Members, the selection defaults to
Single Member, which includes only the selected node.
Note
Dependent members are all entries one level below the parent node.
Base members are all entries at the lowest level below the parent node.
In some cases you will have to manually enter the members that you want to use in the activity.
In the member Criteria Editor page, you can also click the button to filter members by selecting properties
of the driver dimension and add them to the Selected Members list in a batch.
The logical relationship of selections is:
○ All selected members are on one hierarchy: OR
○ Filtered by the same property: OR
○ Filtered by different properties: AND
○ Selected from different hierarchies and filtered by different properties: AND
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 117
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).
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.
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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
118 PUBLIC 4HANA (Embedded)
● 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:
Table 36:
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:
Table 37:
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 119
1.6.6.1.2.4 Criteria for Reopening Activities
You can reopen a completed activity to perform actions in that activity once again. You enable the reopen function
when you are defining activities in the Process Template Designer interface.
When choosing a reopening criterion for an activity, consider the following guidelines:
● The Allow Reopen checkbox must have been selected in the activity that you want to reopen when designing
the process template.
● You reopen activities one by one starting from the most recently completed activity, which means that except
for the last open activity, the reopen function is available only for the activity prior to the one that is now active;
you cannot reopen an activity that is not consecutive.
● By default, you must be an owner or reviewer in both the current activity and the next open activity to be able
to reopen the currentactivity. If you are the process owner you can reopen an activity, regardless of owner or
reviewer assignment, from the process monitor. To change the default setting, you can following the steps
described in Check Only Current Step when Reopening below.
● You cannot specify which activity context to reopen; it is an activity operation.
● You cannot reopen an activity once it has been finalized.
By default, if you act only as a performer or a reviewer instead of the process owner of a process, you must be an
owner or reviewer in both the current activity and the next active activity to be able to reopen the current activity.
To enable a performer or a reviewer to directly reopen the current activity, perform the following step:
● Select the option Check only the current step when reopening in the Process Settings page when creating or
modifying a process template.
The following sections describe how All and Matched criteria affect activities.
Choosing All Activity Contexts as the reopening criterion for an activity introduces the following constraints:
Example
When you reopen activity 1, all activity contexts for activity 2 change to status Delayed:
Table 38:
1 Entity US A B Reopen
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
120 PUBLIC 4HANA (Embedded)
Activity Driving Dimen Activity Context Owner Reviewer Status
sion
2 Entity US A B Delayed
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.
(The process owner can ignore this).
● 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 process owner can ignore this).
● 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:
Table 39:
1 Entity US A B Complete
2 Entity US A B Complete
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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 121
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.
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 11].
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.
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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
122 PUBLIC 4HANA (Embedded)
1.6.6.1.3 Defining Activity Workspaces
After you finish editing an activity workspace, you can assign review actions to activities, which require the
approval of a reviewer.
Prerequisites
Procedure
1. When creating a process template, choose the Create button in the Workspaces field of the Activities tab.
2. Click the Add button and choose Add Action Group.
You can add hyperlinks only to perform actions of existing elements. Therefore, you must make sure these
elements exist before you start defining actions.
Business Planning and Consolidation supports the following types of actions:
○ Consolidation – Define a hyperlink to perform various kinds of actions in Consolidation including opening
a journal list, creating a new journal, opening Consolidation Monitor, opening Ownership Manager, opening
Controls Summary, and opening Controls Details.
○ Analysis Office Plug-in:
○ Define a hyperlink to a Business Warehouse query. If the query has variables set in it, you can assign
values to these variables.
○ Define a hyperlink to an Analysis Office workbook. If the workbook contains a query that has variables
set in it, you can assign values to these variables. If the workbook contains queries with the same
variables, you can assign values to these variables for each query. You can also assign values to all of
the variables once by selecting Merge Variables.
○ Work Status - Set a target work state for a context and define a target work state for a specific activity
status. When there is a change of a certain activity status, the system can automatically change the work
state to the defined target state. For more information about work status integration, seeIntegrating with
Work Status [page 125].
○ 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 124].
3. Choose Stop Editing. You can then click the hyperlink to test the action of the activity.
4. Repeat these steps for all of the actions to be associated with each activity in the process template.
5. After all the actions have been defined, go back to the process template and save it.
You can specify that the reviewer uses the same workspace or that a reviewer has a specific workspace, which you
can define in the same way.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 123
Result
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).
You must first configure the web-based application that you want to use as a role in the User Interface Add-On.
Maintaining Links
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
124 PUBLIC 4HANA (Embedded)
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.
When configuring workspaces for the owner 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.
When defining a target action for Set work status, you can set this action to be executed automatically when
there is a change of activity state.
Context
You can specify one of the following desired target work states for all possible Business Planning and Consolidation
activity states:
● On Submit
● On Approve
● On Reject
● On Complete
● On Reopen
Procedure
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 125
1.6.6.2 Creating Process Instances
A process instance is a process that has been created based on a process template.
Use
An authorized user can create a process instance in the Administration screen. You can create up to 24 process
instances for each process template.
Generating a process creates all required activities and activity contexts. Once generated, the process instance is
no longer associated with the template. Any changes to the template definition do not impact previously generated
processes.
Prerequisites
Procedure
In the Process Instances screen, choose New. This opens the New Process Instance wizard that has the following
steps:
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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
126 PUBLIC 4HANA (Embedded)
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:
Table 40:
Function Description
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 sta
tus within the process so users must perform the steps again.
The system does not, however, reset changes made to your
metadata or transaction data.
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 monitor user, activity owner, or activity reviewer maintained in Business Warehouse via
transaction SU01. You must make sure that proper SMTP settings are configured via transaction SCOT to allow the
system to automatically send out the emails. For detailed information, refer to the SMTP Configuration Guide
available here on the Help Portal.
The email notifications automatically sent to users contain a link to bring them either to the activity or process
monitor directly, or to external URL-based applications including transactions, Fiori, and ABAP Web Dynpro
applications.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 127
To turn on and turn off e-mail notifications, administrators can perform the following steps:
Besides the default e-mail templates, administrators can also customize an e-mail template by performing the
following steps:
1. On the e-mail template page, click the Change button and choose New Entries (F5).
2. Choose Customizing Email Template in E-mail Template Type.
3. Choose an e-mail template ID for the customized email template. Later, if both this customized email template
and the default email template sharing the same ID are activated, the customized email template takes
priority.
4. Type an e-mail template title in which two variables can be included:
○ %PROCESS_NAME%: Process instance name
○ %STEP_REGION_NAME%: Activity name
5. Select a Smart Form body or directly enter an e-mail body.
Smart Forms are predefined via transaction SMARTFORMS. For detailed information, refer to the section below
called “Manage Smart Form Body”.
An e-mail body is simply made up of a single line text. If both Smart Form and e-mail body are defined, the
Smart Form body will be used.
6. Use the same URL Callback RSBPCB_SF_XSF_URL_CALL_BACK or UJB_SF_XSF_URL_CALL_BACK as in the
default template to call the proper URL.
7. Choose a corresponding BPF Operation.
8. Activate and save the template. The responsible person will receive e-mail notifications based on the
customized template.
Administrators can change the Smart Form body by using the Smart Form Editor.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
128 PUBLIC 4HANA (Embedded)
Table 41:
Variable Description
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
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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 129
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.
Steps for integrating workflows that are outside of Business Planning and Consolidation with the system's
business process flow functionality.
Procedure
A performer can reopen an activity in a BPF. When the reopened activity is submitted, a new external workflow
is initiated.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
130 PUBLIC 4HANA (Embedded)
1.6.7 Work Status Setup
This function allows you to lock a region or slice of data in a model. The work status setting overrides the member
access privileges of a user to write to a given region.
Use
The region of data to be locked is defined by several dimensions per model that are composed of one Owner
dimension and a number of Other dimensions. You can predefine an attribute of the owner InfoObject as the owner
property on the Business Warehouse backend to maintain work status owners. An InfoObject can be used as an
owner dimension only when some criteria are met. Refer to the section Owner Dimension and Hierarchy below for
detailed information.
● Work states - Physical statuses of data that can be customized according to your business needs, such as
unlocked, submitted, and approved.
● Level of security - The users or teams who can change data in the system, which is All, None (locked for all),
Manager, or Owner. See Controlling Who Can Change Data below.
The users or teams who can change the work status, which is Owner, Manager, or Owner and Manager. See
Controlling Who Can Set Work Status below.
● Push - Equivalent to the check box On All Descendants when setting work statuses, the option allows you to set
one work state to all descendants of a member. This does not includet the selected parent member.
After you set up work statuses, other users can use them to apply a state to a current view and lock its data for
review, approval, and so on. For example, your month-end close business process requires that a specific set of
data is locked down so that accurate month-end reports can be created. After a data submission, the owner sets
the work status to Submitted, which has a security level of None. This locks the data intersection from subsequent
submissions.
Features
Derive Owner
You can either specify an attribute of the owner dimension as Owner (the value should be a user ID) or as Team
(the value should be a team's ID); you can also specify both.
The user(s) derived from the owner attribute, or the team member(s) derived from the team attributes, or from
both attributes, are considered owners of the current member ID of the owner dimension.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 131
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
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
Controlled By Rule
● 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.
● 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
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
132 PUBLIC 4HANA (Embedded)
○ 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.
● 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.
There is no limit to the number of work states you can create, but there is a practical limit.
There is a default work state that must be first. It has an internal code of 0 and is controlled by the Manager and
Owner (Controlled by is set to Owner and Manager). You cannot change the Controlled by value. You can change
the text description.
You can change the order of work states. When you do that, the system deletes all locks for the model to which the
work status belongs. Deleting states also deletes all locks. Adding states to the bottom of the list or changing a
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 133
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.
Note that in this section the term member denotes the members of the owner dimension.
● The default method for managing work status is bottom-up. That is, the status of a parent cannot be higher
than the status of its children.
● The maximum status a parent can be set to is the lowest status of its immediate children.
● If the status of a parent is set to Locked, you cannot unlock the children.
● The minimum status a child can be set to is the status of its immediate parent. For example, if the parent
status is Submitted, the child status must be at least Submitted.
● The owner of an entity can set the work status to any status designated as an Owner status, where Owner
status means that the status is controlled by the owner or the owner and the manager.
● The manager of an entity can set the work status to any status designated as a Manager status where
Manager status means that the status is controlled by the manager or the owner and the manager.
● A manager is the owner of a parent-level member. The owner of a parent level member is the manager of all its
descendants.
● When setting a lock on the parent members of multiple dimensions, locks are set for all members under all
parents, specifically, the Cartesian product is stored as locked. For example, the following table shows the
locks that are set when including all children for entity:p1, category:actual and time 2016.Q1.
Table 42:
● 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.
Table 43:
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
134 PUBLIC 4HANA (Embedded)
P1 Actual 2016.Jan Upload
● When applying rules, if the model encounters any error, it rejects the entire user request. In this case, no
records are updated.
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.
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.
The system can send an e-mail notification to corresponding owners and managers to notify them when a work
status changes.
The e-mail address to which the notification is sent is defined in Business Warehouse. To add or modify the default
e-mail address for an owner or manager, an administrator can run transaction SU01, choose the name of the user,
and then enter an e-mail address in the Address tab. You also need to make sure proper SMTP settings are
configured via transaction SCOT for the e-mails to be automatically sent out. For detailed information, refer to the
SMTP Configuration Guide.
Then you can compose an e-mail notification template and trigger the e-mail notification for work status changes
in the Planning and Consolidation web client by choosing Notifications and checking Activate E-mail Notifications in
the Work Status Settings page. You can either directly use the default message template or customize a new
message.
Activities
You create work statuses to reflect statuses of different data entry levels with the progress of your business, such
as unlocked, submitted, and approved. No predefined work statuses exist within Business Planning and
Consolidation.
Go to the Administration screen and under the Work Status section, choose Work Status Configuration. After that
select the model, whose work status you want to configure.
You can modify the order in which work statuses display in the system by using the up and down arrows.
You can delete a work status that is not currently in use by selecting the work status and choosing Delete.
Select the Set Work State by InfoProvider checkbox, so that only a given provider is affected by the work status
change.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 135
1.6.8 Journal Administration
Administrators set up and manage the Journals component of SAP Business Planning and Consolidation.
Prerequisites
Before users can adjust data in the database using the Journals feature, an administrator must perform the
following tasks:
Users must be granted corresponding authorization objects on the Business Warehouse side to perform these
tasks. For detailed information, refer to the topic “Authorization Objects for Performing Consolidation Tasks
(Embedded only)” in the Security Guide available on the SAP Help Portal.
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
● 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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
136 PUBLIC 4HANA (Embedded)
○ Balanced by Currency: If you select this option, for each currency in the journal entry, credits must be
equal to debits. There can be multiple reporting currencies in a journal entry.
Note
If you have already created a journal template, creating a new template that changes the structure of the
journal entries deletes the old template and all journal entries associated with that template. This removes
your audit trail, even though changes made to the model data (InfoProvider data) through posted journal
entries are maintained. If you recreate the journal template, all transaction data is deleted. However, if you
add or remove one or more dimensions from a model, the corresponding journal template is automatically
updated and the journal entries are maintained. If you recreate the journal template, but do not change the
structure of the template keeping all header and detail dimensions the same, you have the option to keep
the existing journal entries.
● Reopen Rules
Define translation information for the dimensions used in the reopen tasks. For more information, see Journal
Reopen Rules [page 137].
Activities
Related Information
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.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 137
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:
Table 44:
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 ad
ditional 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 template
creation.
Table 45:
Sign Enter plus ( +) to keep the value in the same credit or debit po
sition. 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 template
creation.
Activities
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
138 PUBLIC 4HANA (Embedded)
1.6.8.1.2 Journal Model Parameters
Features
Activities
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
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 139
Activities
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.
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.
When saving a journal, you can add or calculate extra amounts by implementing the Business Add-In (BAdI)
UJJ_CALCULATED_AMOUNT.
Features
Enhancement Spot
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
140 PUBLIC 4HANA (Embedded)
When implementing a new BAdI, a filter must be set with the following parameters:
● Appset_id: Model ID
● Application_id: Environment
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
Method CALCULATE_AMOUNTS:
Table 46:
Table 47:
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.
Table 48:
Exception Description
Data Types
UJJ_T_BADI_CA_JOURNAL
UJJ_S_BADI_CA_JOURNAL
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 141
The following fields are defined in the structure:
Table 49:
USERP UJ_USER_ID The ID of the user who has posted the journal
UJJ_T_BADI_CA_AMOUNT
UJJ_S_BADI_CA_AMOUNT
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
142 PUBLIC 4HANA (Embedded)
The following fields are defined in the structure:
Table 50:
MEMBERS UJJ_T_KEYMEM This table contains the list of dimensions that de
fines the journal amount. Both detail and header
dimensions are included in this table.
UJJ_T_KEYMEM
Table of UJJ_S_KEYMEM.
UJJ_S_KEYMEM
Table 51:
IS_HDR_FLD UJ_FLG CHAR Set the value to True if the dimension is a header
dimension; otherwise it is a detail dimension.
UJJ_T_BADI_CA_JOURNAL_AMOUNTS
UJJ_S_BADI_CA_JOURNAL_AMOUNTS
Table 52:
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 143
1.6.9 Auditing
You can perform data auditing to track changes to transactional data at the InfoProvider level.
More Information
This function tracks changes to transactional data at the InfoProvider level, such as when and by whom records
were changed within an InfoProvider.
Activities
To display data auditing, go to Administration and under the Audit section, choose Data Changes. Select an
InfoProvider, and change its status to On.
Once a data change is recorded, you can run a report that shows that change based on specified criteria (see
Reporting on Data Changes [page 41]).
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.
● BADI_RSBPCB_SETUSER - Provides the performer and reviewer of a BPF activity. This BAdI applies to both
Business Process Flows and Work Status.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
144 PUBLIC 4HANA (Embedded)
Work Status
● BADI_RSBPCB_SETUSER - You can implement customized logic that provides the owner and manager for work
status. This BAdI applies to both Business Process Flows and Work Status.
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Application Help for SAP Business Planning and Consolidation, version for SAP BW/
4HANA (Embedded) PUBLIC 145
Important Disclaimers and Legal Information
Coding Samples
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, unless damages were caused by SAP
intentionally or by SAP's gross negligence.
Accessibility
The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a
binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does not
apply in cases of willful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.
Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales
person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not
exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.
Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not
warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages
caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency (see:
http://help.sap.com/disclaimer).
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
146 PUBLIC Important Disclaimers and Legal Information
Application Help - SAP Business Planning and Consolidation, version for SAP BW/4HANA
(Embedded configuration)
Important Disclaimers and Legal Information PUBLIC 147
go.sap.com/registration/
contact.html