Application Help BPC MS

10/24/2019
Application Help for SAP Business

Planning and Consolidation, version for
the Microsoft platform
Generated on: 2019-10-24
SAP Business Planning and Consolidation, version for the Microsoft platform | 10.1
PUBLIC
Warning
This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.
For more information, please visit the SAP Help Portal.
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20204029&topics=a781a5d88e2445019dbbd592ff5… 1/86
10/24/2019
SAP Business Planning and Consolidation

Product Information
Product SAP Business Planning and Consolidation, version for the Microsoft
platform
Release 10.1 SP08
Changes in this application help: February 28, 2018
Updated the product name “BusinessObjects Planning and

Consolidation” to “Business Planning and Consolidation”.
October 12, 2017
Updated the topic Setting Task Sequences.
October 9, 2017
In Model Parameters, added the parameter

JRN_VALIDATION_FILTER. Also added this as a
requirement in the topic Journal Validation Rules.
In Environment Parameters, added the paramters

ReadLogDim and ReadLogEnable.
In Journal Queries, mentioned the advanced query

matching types CONTAINS and STARTS WITH.
In Journals, added that you can select Copy whole group

with same structure to maintain the group structure when
copying journal groups.
In Journal Entry Form, added Display to the list of available

journal options.
In Home Page and Navigation, added a reference to the

Administrator's Guide for information about the
Management Console.
Modi ed the topic Administration to include the subtopics

Administration Page and Administration Client.
SAP Business Planning and Consolidation provides everything you need to meet your bottom-up and top-down nancial and
operational planning requirements, as well as complete consolidation and reporting through a single application and user
interface.
Integration
There are two versions of Business Planning and Consolidation: a version for the Microsoft platform and a version for SAP
NetWeaver. This application help focuses on the Microsoft platform.
Two client components are included with Business Planning and Consolidation: a Web Client, which is installed with the Business
Planning and Consolidation server, and an Administration Client, which requires a separate install. The Web Client is primarily for
business users, while the Administration Client is primarily for administrative users.
There is a separate installation for business users that are power users - the SAP BusinessObjects EPM solutions, add-in for
Microsoft Office. For more information, see the SAP BusinessObjects EPM solutions, add-in for Microsoft Office help at
10/24/2019
http://help.sap.com/boepmms.
Features
Web Client
When you rst open the Web Client, you are presented with the Library view in which you store and organize Business Planning
and Consolidation objects such as workspaces, reports, and input forms, SAP Crystal Dashboards, and books created in the EPM
Add-in.
You can also access the following components using the navigation pane if proper authorization exists:
Business Processes Flows, which guides you through a set of application tasks. For information about setting up process
templates, see Business Process Flow Management.
Consolidation, which helps you manage consolidated data to obtain an accurate view of the nancial situation of your
organization.
System Reports, which lets you gather data on system information and activity.
Documents, which allows you to post, share, and retrieve les, and to manage the display of content. The Documents view
contains documents that users have uploaded manually.
Administration Client
The Administration Client enables administrators to perform setup and maintenance tasks for Business Planning and
Consolidation environments and models. For more information, see Administration.
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 at http://help.sap.com/bopacms101.
Activities
To start the Business Planning and Consolidation Web Client, do one of the following:
From the Windows Start menu, select SAP BusinessObjects Planning and Consolidation Planning and Consolidation .
Open a browser and connect to the URL http://PC_server:port/sap/bpc, where PC_server:port is the server name or
IP address and port number of the Planning and Consolidation application location.
To log on directly to a speci c environment, enter http://PC_server:port/sap/bpc/web/environment ID.
To start the Business Planning and Consolidation Administration Client, do the following:
From the Windows Start menu, select SAP BusinessObjects Planning and Consolidation Planning and Consolidation
Administration Client .
From the Web Client, select Start Page, then select Planning and Consolidation Administration from the Launch area.
Related Information
Creating and Modifying Workspaces
More Information about Business Planning and Consolidation
10/24/2019
Administration
You use the Administration Page to set up task sequences for rules and to perform tasks such as monitoring the server, managing
logs, examining server diagnostics, and viewing license usage.
You use the Administration Client to perform setup and maintenance tasks for Planning and Consolidation environments and
models.
Administration Client
The Administration Client enables administrators to perform setup and maintenance tasks for Planning and Consolidation
environments and models.
Features
You use the features in the Administration Client to set up and maintain the following parts of Planning and Consolidation:
Environments
Dimensions
Models
Security
Business rules
Business Process Flows
Logic
More Information
Starting the Administration Client

Procedure
To start the Administration Client, do one of the following:
From the Windows Start menu, select Programs SAP Business Planning and Consolidation SAP Business Planning and
Consolidation SAP Business Planning and Consolidation Administration Client .
Open a browser and connect to the URL http://PC_server:port/sap/bpc/Web, where <PC_server:port> is the server
name or IP address, and port number of the Planning and Consolidation application location.
From the Launch area of the Home workspace, select Planning and Consolidation Administration.
More Information
Connection Wizard
10/24/2019
Connection Wizard
Use
The Connection Wizard provides a way to set defaults for, or change your Planning and Consolidation connection settings.
Features
Using the Connection Wizard
Use the Connection Wizard in the following scenarios:
The rst time you log on to the system, so you can establish default connection settings
When you want to log on to the system with a different user ID and password than your default credentials or the ID and
password you supplied the last time you logged on
When you want to connect to a different server than your default server or the last server you logged on to
When a new environment has been added, and you want to access it
Required Information
You must have the following information to use the connection wizard:
Server name or IP address
Whether or not your system uses a default or secure port
Your ID and password
Domain name, if your system requires it
Note
If you do not use the Sarbanes-Oxley options, you can select My Windows User ID is the same as above if you are
logging on to a multiserver environment, and your Planning and Consolidation credentials are the same as your network
credentials.
Name of the environment you want to log on to or set as your default
If an alternate service provider has been installed on the server, you can select the service provider through which to
connect.
Activities
To log on to Planning and Consolidation using the Connection Wizard, select the Connection Wizard button from the Login
window.
Environment Management
Use
10/24/2019
An environment is a grouping of shared metadata, such as dimensions, common con gurations, and security, which becomes the
basis of one or more models.
Features
You can perform the following tasks when managing environments:
Task More Information
Add New Environments Administrators create new environments by copying information from the sample environment,
EnvironmentShell, provided with Planning and Consolidation. See New Environments and EnvironmentShell
Sample Environment.
View Environment You can view the following environment statistics by selecting View Environment Statistics in the Manage
Statistics Environments action pane:
Real time, short term, and long term model storage count
The storage count comes from the row count of each the table in the Microsoft SQL Server
Management Studio.
Model processing status
Current model optimization status
Dimension processing status
Set the Environment The environment status determines when and how users can log on and interact with the data in the client. See
Status Environment Status.
Refresh Environment You can get information about the current environment, such as dimension les, task security, and so on,
Information without logging in again.
Delete Environments You can delete environments in the Administration Client. Select the environment name at the top of the tree,
then choose Delete Environments from the Manage Environments action pane. Select one or more
environments in Delete Environments, then choose Delete Selected Environments.
Caution
You can delete an environment when it contains data. You cannot, however, delete a dimension member
when there is data associated to that member in a model.
Display Who is Online You can view a list of all users currently using Planning and Consolidation together with a summary of their
recent actions by choosing Display Who is Online from the Manage Environments action pane.
Additional Tasks Additional tasks include the following:
Set Environment Parameters (see Environment Parameters)
Manage Document Types (see Managing Document Types and Subtypes)
Manage Document Subtypes (see Managing Document Types and Subtypes)
Manage Activity Audit (see Activity Auditing)
Manage Logging (see Log and Trace File Management)
Edit Drill-through Table (see Edit Drill-Through Table)
Context Defaults (see Setting Context Defaults)
Transport Content with The Change and Transport System (CTS) supports the movement of transportable content between Planning
CTS and Consolidation servers. See Transporting Content with CTS.
10/24/2019
Activities
To manage environments, log on to the Administration Client and select the top node from the navigation pane.
More Information
New Environments
Use
You can add can new environments to the system by copying information from the EnvironmentShell environment.
When you create a new environment, the system does the following:
Copies the environment WebFolders/data within File Service
Copies all transactional and master data from the source environment to the new environment
Copies security and metadata
Copies the environment database
Features
You can copy model data, Library and Documents content, and journal templates from the source (EnvironmentShell)
environment. You can also copy business process ows.
You can modify the descriptive text associated with an environment. For example, you might want to change the description if you
have made a signi cant change to the environment, such as adding a new model that performs new functions for your business.
Activities
Add an environment by doing the following:
1. Choose Add a new environment in the Manage Environment action pane.
2. Enter a name and description, and select the name of the environment to copy.
After the copying completes, you can begin to modify the default models, add new ones, and assign users to them.
More Information
EnvironmentShell Sample Environment
EnvironmentShell Sample Environment

Use
Use the EnvironmentShell environment to build your own environments.
10/24/2019
Because it is a shell, it needs to be populated with publications and reports to become a fully functioning environment.
EnvironmentShell does not contain any data except Time dimension information, and has only a limited amount of master data in
the form of dimension members. The dimension master data is limited to default members in most dimensions so the
environment works when an administrative task is run.
When you install a new version of Planning and Consolidation, EnvironmentShell and its components are overwritten.
Caution
You must not modify EnvironmentShell.
Features
EnvironmentShell contains the following components needed to build a functioning environment:
Four sample models - Planning, Rate, Ownership, and Consolidation - that contain most of the functionality you need to
start building your own environment.
The Planning model is a multi-currency nancial model. It is designed, by default, to accommodate currency translation.
The Rate model, which stores the currency rates, is assigned to it as a supporting model. The combination of the two
models allows for the calculation of currency conversions.
If you need to build more complex environments, you can build an environment using the components included within
EnvironmentShell.
A set of dynamic report and input form templates
Data Manager packages
Blank Library and Document views
Required environment and model parameters
All required dimensions with the properties needed to create a basic planning and consolidation environment
Dimensions in the EnvironmentShell sample environment
Dimensions for planning and consolidation models:
Dimensions Models
Type ID Dimension ID Dimension Planning Consolidation Rates Ownership

Description
C CATEGORY Category X X X X
T TIME Time X X X X
E ENTITY Entity X X X
A ACCOUNT Account X X
D DATASOURCE Data Source X X
R RPTCURRENCY Reporting X X
Currency
I INTERCO Intercompany X X X
Partner
10/24/2019
Dimensions speci c to Consolidation:
Dimensions Models

Description
G SCOPES Scopes X X
S FLOW Flow X
Dimension of speci c to Planning:
Dimensions Models

Description
U PRODUCT Product X
Dimensions speci c to the Rates model:
Dimensions Models

Description
A R_ACCOUNT Rate Account X
E R_ENTITY Rate Entity X
R INPUTCURRENCY Input Currency X
Dimension speci c to the Ownership model:
Dimensions Models

Description
A O_ACCOUNT Ownership Account X
More Information
New Environments
Dimension Types
Environment Status
Use
Environments have a status of either Available or Not available. An environment have an available status until an administrator
takes it offline, or a system function automatically takes it offline. If an environment is not available (or offline), users may be
10/24/2019
restricted from performing certain data retrieval and export tasks.
Features
The following conditions determine who and when users can perform certain tasks when the environment is set to Not available:
Users have Use System When Offline task security:
When users attempt to log on to the EPM add-in for Microsoft Office, the prompt "The environment is not available. Do you
want to continue?" is displayed. A response of Yes allows them to log on. A response of No does not.
If RETRIEVE_ON_OFFLINE is set to 1, the prompt "Environment is unavailable. Do you want to continue?" is displayed
when they try to retrieve data. A response of Yes allows users to see data. A response of No does not allow them to see
data.
When users do not have Use System When Offline task security:
When users attempt to log on to the EPM add-in for Microsoft Office, the prompt "The model is not available this time;
contact your administrator" is displayed. Users cannot log on.
If the user is logged on when the administrator takes the environment offline and RETRIEVE_ON_OFFLINE is set to 1,
the user cannot retrieve data.
If RETRIEVE_ON_OFFLINE is set to 0, users cannot retrieve data while the system is offline, regardless of task security.
For information about tasks that open the prompt, see the RETRIEVE_ON_OFFLINE parameter in Environment Parameters.
Activities
You can manually set the status of an environment by doing one of the following:
Set to Not Available - From the Manage Environments action pane of the Administration Client, choose Set Environment
Status Not Available Update environment status .
You can enter informative text to display to users who try to perform a restricted task while the environment is unavailable.
We recommend including the current date and time so that users can see that the message is current, and to give an
estimated time when they can log back on again.
Set to Available - From the Manage Environments action pane of the Administration Client, choose Set Environment
Status Available Update environment status .
Change the AVAILABLE_FLAG on the Set Environment Parameters page to 1 for Available and 2 for Unavailable.
More Information
Environment Parameters
Use
Environment parameters allow you to customize the settings that apply across an environment.
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20204029&topics=a781a5d88e2445019dbbd592ff… 10/86
10/24/2019
Prerequisites
You have Environment task security rights to view and change environment parameters.
Features
The parameters that require a value contain Required in the Type column. Parameters that do not require a value contain Optional
in the Type column. If an environment parameter is required, you can leave it blank to accept the default, but if you delete the
parameter, the system may not work correctly. If an environment parameter is optional, you can leave it blank or delete it.
The following table describes the parameters you can set:
Type Key ID Description
Optional ALLOW_EXTENSIONS The le extensions the system allows users to upload by. The default values
are: .HTM, TXT, TMP, ESF, XLTM.
Optional ALLOW_FILE_SIZE The maximum le size the system permits users to upload. A warning message
appears if the le size exceeds the parameter value when you upload a le.
The default value is 100 MB.
This parameter is used:
When posting documents in the Documents view
When sending data
System ALLOW_SSO_HTTP Allows single sign-on for HTTP.
Optional APPROVALSTATUSMAIL De nes whether owners and managers receive an e-mail when there is a
change to an assigned work status.
Theis parameter has the following possible values:
Yes: Send e-mail
N/A: Do not send e-mail
The following SMTP environment parameters must be set up as well to use e-

mail noti cations in the system: SMTPAUTH, SMTPPASSWORD, SMTPPORT,
SMTPSERVER, and SMTPUSER.
Optional APPROVALSTATUSMSG Allows you to de ne a custom e-mail message that is sent to the owners and
managers of a work status when a work status code is changed. The message
is applicable to all models in the environment.
You can customize the message using the following variables:
%USER% - ID of user who changed this status
%STA% - Work status
%OWNER% - Entity owner
%TIME% - Time of change
Example
You can create a message such as “This is to inform you that %USER% has
updated the work status on %TIME%”.
The text of the e-mail can be a maximum of 255 characters. There is no need
for quotes or brackets around parameters.
10/24/2019
Required AVAILABLEFLAG Controls whether the system is offline or not. Yes means the system is online
and available for sending data to the database. You can take the system offline
by changing the value to No.
This parameter is used in the EPM add-in for Microsoft Office - Save Data, DM
Imports
Required AVAILABLEMSG The message that displays to users who try to access an environment that is
offline ( AVAILABLEFLAG = No).
The default value is “Current Environment status is not available”
Example
The message could be “The system is temporarily unavailable due to
scheduled maintenance. Try again later.”
This parameter is used in the EPM add-in for Microsoft Office - Save Data, DM-
Import.
Optional BPFSTEP_COMPLETE_MSG Determines the content of the message that is displayed when a Business
Process Flow step is completed.
The default message is:
[%BPF_STEP_NAME%] step of [%BPF_NAME%] has been completed

by %USER_NAME%.
This parameter is used in Administration Client - Manage Business Process

Flows.
Optional CLR_COMMENTS_HISTORY Deletes all comment history and retains only the latest comment; used in Add
Comments and View Comments. Historical comments are removed after
applying the parameter.
Valid Values: 0 saves the historical comments; 1 deletes the historical

comments and retains the latest comment only.
The default value is 0.
Optional COMMENT_MAX_LENGTH Supports the customized length of comments in Add Comments and View
Comments. If you set a smaller value than the current value, newly input values
do not conform to the eComments length and the previous value still applies,
even though the setting has been successfully updated on the Environment
Parameters page. Therefore, the new setting should be larger than the previous
value.
The default value is 256. You can input integers between 256 and 4,000.
10/24/2019
Optional DEFAULT_EXTENSIONS The system allows the default le type even if you do not set this parameter.
The default le extensions are hard-coded internally.
The le extensions the system allows users to upload by default:
XLS, XLT, DOC, DOT, PPT, POT, XML, MHT, MHTML, HTM, HTML, XLSX, XLTX,
XLSM, XLSB, ZIP, PDF, PPTX, PPTM, POTX, POTM, DOCX, DOCM, DOTX,
DOTM, CDM, TDM, PNG, GIF, JPG, CSS, MRC.
See ALLOW_EXTENSIONS above.
Users can change the value.
This parameter is used in:
Posting documents in the Document view
Sending Data, DM-Import
Optional JREPORTZOOM This parameter allows you to set the default zoom magni cation value on
HTML journal reports.
We recommend that you set the value to 75%.
Required MaxSystemReportQuerySize Used for system reports. Speci es the maximum query size in cells (prior to
zero compression) before the system asks the user to continue or cancel the
query.
Required MaxWebReportQuerySize Used for Web reports. Speci es the maximum query size in cells (prior to zero
compression) before the system asks the user to continue or cancel the query.
Required MEMBERSHEET_VERSION Determines whether you use the .xls Excel workbook type or .xlsx Excel
workbook type for the dimension member sheet. The default value is 2007,
which uses the .xlsx workbook type. You can change it to 2003 to use an Excel
2003 workbook. However, when you change it to 2003, you must run Export
Dimension in the Administration client for all of the dimensions. When you
change the value from 2003 to 2007, however, you do not have to run Export
Dimension because the Administration client converts it automatically.
Optional ReadLogDim Enter a semi-colon delimited list of dimensions; reading this content results in
an audit log entry.
Optional ReadLogEnable To enable logging of speci c read activities by users, enter a value composed
of the sum of the following:
1 to enable logging of user information reads
2 to enable logging of master data dimension reads. Specify which

dimensions in ReadLogDim.
4 to enable logging of document reads
The new log entries appear in the AuditActivityHdr[<Environment>]

table of the [<Environment>]Extra database.
Optional SESSIONTIME De nes the session time (in minutes) for the Who's Online feature.
The default value is 3000 minutes.
10/24/2019
Required SMTPAUTH The authentication method of the SMTP server.
This setting does not change the method on the SMTP server, but must match
the type of authentication enabled on it. Failure to set this appropriately can
result in errors from the e-mail server.
The default value is: 1.
Possible values for this parameter are:
0 = Anonymous
1 = Basic
2 = NTLM
When posting documents, Work status, Alert
EPM add-in for Microsoft Office - Distribution
Optional SMTPPASSWORD The password for the user name de ned as the SMTPUSER.
This parameter is Optional except when SMTPAUTH is "1" (basic), this

parameter is Required
The default value is blank.
The user can enter the SMTP password.
When posting documents, Work status
Required SMTPPORT Port number for your SMTP e-mail server.
The default is port 25, the default SMTP server port number.
The user can enter the port number.
When posting documents, Work status
Required SMTPSERVER The name or TCP/IP address of the SMTP e-mail server the system uses to
send e-mail.
The user can input the SMTP Server name or TCP/IP address.
10/24/2019
Required SMTPSSL The parameter indicates whether SMTP is using Secure Sockets Layer (SSL) or
not.
1 = use SSL
0 (default) = do not use SSL
Required SMTPUSER The user name from which e-mail from the system originates.
The user can input the User name.
Required SYSTEM_LANGUAGE This parameter indicates what language is used for system messages and logs.
All messages coming from the server are localized by the client's language, but
there are two areas where messages and logs are written in the language of
this parameter: logic logs and the Data Manager package log viewer.
Optional WS_CHECKNOOWNERDIM Use this parameter to validate combinations of work status settings for all child
members of the selected members, which are included in dimensions that
have a work state set to "Yes" in order to see the possible statuses when
changing work status.
To get the new status for the work status, when working from the bottom up,
the system has to validate other combinations of the work status setting for all
child members of the selected members of dimensions that have a work status
set to "Yes". When, however, the dimensions have a large number of members,
performance can be affected. Normally, the system deos not validate other
combinations of work status settings of all child members and validates only
the selected member. If you need to obtain the accurate status for selected
members regardless of performance, set this parameter.
The value is not case-sensitive. When changing work status, if this parameter is
not set, the system validates just the status of the selected member.
Valid values are:
[all] - Validate other combinations of work status settings for all child
members that are included in dimensions that have a work state set to
Yes.
Dimension name - Validate other combinations of work status settings

for all child members of the dimensions that are inserted as values. If
the system needs to validate multiple dimensions, separate them with
a comma, such as "time,category".
Activities
To update the value of a parameter, start the Administration Client, and select the environment name at the top of the navigation
pane, then select Additional Tasks Set Environment Parameters . Modify the parameters, as desired, and then click Update.
To add a new parameter (you can add any 'optional' parameter if it is not already displayed), add a new row, enter the parameter
name, then enter the desired value.
10/24/2019
Managing Document Types and Subtypes

Use
Document types and subtypes allow you to provide a set of categories for the Document view in the Web Client. This is useful if
you want users to be able to lter the display of documents.
Features
Managing Document Types
You can add or remove document types in the Administration Client by choosing the environment ID, then selecting Additional
Tasks Manage Document Types .
Enter the name of the document type, then click Update.
Note
The character length of the name of the document type must not exceed 20 characters.
Delete a document type, by selecting the checkbox in the Delete column, and then clicking Update.
Managing Document Subtypes
Document subtypes allow you to provide further categorization of documents that are posted in the Documents view.
Administrators can de ne a list of subtypes from which users choose, and users can create their own, as needed.
You can add or remove document types in the Administration Client by choosing the environment ID, then selecting Additional
Tasks Manage Document Subtypes . Enter the name and order in which you want the subtype to appear in the subtypes list, then
click Update.
Note
The character length of the name of the document subtype must not exceed 20 characters.
While document types always appear in an alphabetical list, document subtypes appear in the order in which they were created.
You can change the order of the subtypes by entering numbers in the Order column. The sequence automatically adjusts so the
new sequence number exchanges with the subtype that had that number.
Example
If the original order of subtypes is 1- Apr03, 2- Aug03, and 3- Dec03, and you change Apr03 to 3 (three) in the sequence,
Dec03 is assigned 1 (one) in the sequence.
More Information
Documents
Activity Auditing
10/24/2019
Use
This function tracks administrative tasks at the environment level.
Features
The system can track activity for the following administrative tasks, showing the previous and new values, as well as the IP address
and machine name associated to the user making a change.
Administration Activity
All security-related changes, such as adding, changing, and deleting users, teams, task pro les, and data access pro les
Add, modify, delete, and copy operations for models and dimensions. Delete and copy operations on environments and
drivers for driver-based calculations are also tracked.
Dimension processing activity
Changes to environment parameters, model parameters, global con guration settings, document types and subtypes,
activity audit settings, and data audit settings
Changes to business rules for models
Process Template Activity
Business process ow management, adding, deleting, and modifying process templates, and saving templates to new names
User Tasks Activity
When work status is set, the work status setting value is audited as a USER type.
Activities
Administrators control whether activity auditing is enabled or not. To enable activity auditing, from the Administration Client,
choose Additional Tasks Manage Activity Audit .
Choose one or more types of activities to audit.
Once the system records an activity, you can run a report that shows activity based on speci ed criteria (see Audit).
Log and Trace File Management

Use
This function enables message logging and activity tracing for troubleshooting purposes.
Features
The system can capture various categories of message logging and activity tracing for speci ed users, or for all users. For more
information, see the Planning and Consolidation Administrator's Guide.
Message Logging
10/24/2019
You can create log les for troubleshooting purposes. By default, Planning and Consolidation log les are stored in
<drive>/logging/log (where <drive> is the folder name that was created at installation), but you can specify a different
location.
The possible values for the logging level are:
None - logging is turned off
Info - all information, warning, error, and fatal messages are added to the log
Warning - warning, error, and fatal messages are added to the log
Error - error and fatal messages are added to the log
Fatal - only fatal messages are added to the log
The default value is None.
Activity Tracing
You can trace activities for troubleshooting or monitoring purposes. You can apply tracing to all users, a group of users or to a
single user. By default, Planning and Consolidation trace les are stored in <drive>/logging/trace (where <drive> is the
folder name that was created at installation), but you can specify a different location.
The possible values for the tracing level are:
None - tracing is turned off
Debug - all activities are written to the trace log
Path (in the Microsoft version) - path, info, warning, and error activities are written to the trace log
Info - information, warning, and error activities are written to the trace log
Warning - warning and error activities are written to the trace log
Error - only error activities are written to the trace log
The default value is Error.
Activities
You can access the function in the Administration Client by choosing the environment ID, then selecting Additional Tasks Manage
Logging . Select the appropriate levels for logging and tracing. For tracing, you can also choose the user or user group. Click
Update to activate the function.
Edit Drill-Through Table

Context
Drill through describes the act of exploring or browsing items like folders, les, or related components. Generally associated with
drill down and drill up, which indicate vertical movements between components, drill through is an action in which you move
horizontally between two items through a related link. An example to drill through is in the case of two reports that are in a master
- detail relation with each other; by clicking a master item on the master report you reach the details of the clicked item on the
details report.
10/24/2019
Procedure
1. In the Administration Client, select Additional Tasks Edit Drill Through Table .
2. Complete the following elds:
Field Description
Drill Key The value speci ed in the DrillKey property column for the
dimension member on which you would like to Drill-Through.
Title The title appears at the top of the Drill-Through page.
File Name The name of your SQL Query le (.dqy). This le must reside in
the QueryFiles directory under the model at \\
[FileServer]\OSoft\Webfolders\[Environment]\
[model]\QueryFiles). For journals, a Journal.dqy le is
automatically built for you. For all other external databases, you
must create your own SQL Query le.
Max Rows The maximum number of rows to display on one page. The
default is 30 rows.
User ID and Password A valid user ID and password on the database to which you are
querying.
3. Click Update.
Setting Context Defaults

Use
You de ne the context for a model by the setting of the dimensions of the model.
Features
You can set context defaults for a model by choosing the following parameters of each dimension of the model:
Whether the dimension is a reporting or a data input dimension
Whether or not the dimension is displayed
Whether or not the dimension name is displayed
How the members are displayed - as an ID, a description, or ID and Description
You can select a model as the default model.
Activities
Choose <Environment> Model , and then display context defaults by choosing Context Defaults from the Manage Models action
pane.
Select the model, for which you wish to set the context, and select the desired parameters for each dimension and choose Refresh
to update the table. Choose Apply to apply the changed context.
Set a model as the default for the context by selecting a model and then choosing Set as default.
10/24/2019
Change and Transport System

Use
The Change and Transport System (CTS) is a tool that allows you to organize development projects in the ABAP Workbench and in
Customizing, and then transport the changes between the SAP Systems in your system landscape.
Transporting Content with CTS++

Use
The Change and Transport System (CTS+) supports the movement of transportable content between Planning and Consolidation
servers.
Prerequisites
CTS+ requires the following applications:
Application More Information
SAPJco3 The SAP Java Connector (SAP Jco) is a toolkit that allows a Java
application to communicate with any SAP system. It combines an
easy to use API with unprecedented performance and exibility. The
package supports both, Java to SAP System as well as SAP System
to Java calls.
Download SAPJco from SAP Service Marketplace

(http://service.sap.com/connectors ) and move it to a directory
on the server.
di_cmd_tools This is part of the SAPJco toolkit.
Download di_cmd_tools from SAP Service Marketplace

(http://service.sap.com/connectors ) and move it to a directory
on the server.
Java JDK The Java Development Kit (JDK) includes the required Runtime
Environment (JRE) so a separate download is not necessary.
Download the latest version of JDK from the Oracle web site
(http://www.oracle.com ) and install it.
Vcredist_x86.exe Microsoft Visual C++ redistributable version.
Download from the Microsoft web site (http://www.microsoft.com

) and install it.
Environment Variable Settings
After downloading and installing the prerequisite applications, you should set the server environment variables:
Go to My computer Properties .
In Windows 7 or Windows Vista, choose Advanced system settings, and then select the Advanced tab.
In Windows 2003, choose the Advanced tab.
10/24/2019
Select Environment Variables.
In User Variables, edit the Path variable to add the full path of di_cmd_tools\transportconsole (for example, C:\
di_cmd_tools\transportconsole).
In System Variables, edit the CLASSPATH variable to add the full path of sapjco3\sapjco3.jar (for example,
C:\sapjco3\sapjco3.jar).
Add the following new system variables:
Variable Value
JAVA_HOME C:\Program Files\Java\jdk1.6.0_21
JCO30_HOME C:\sapjco3 (if you copied it directly to C:\)
NWDITOOLLIB C:\di_cmd_tools\lib (if you copied it directly to C:\)
Open C:\WINDOWS\system32\driver\etc\services and add the following line:
sapmsDAB 3600/tcp
Con gure CTS+ Settings
You need to insert the CTS server and the basic information for translation in Con gure CTS+ of the server manager.
Open the server manager, and choose Options Con gure CTS+ . Check the following settings:
Item Description
Enable If enable is selected, the CTS menu option Transport Content with
CTS is activated in the Administration client.
Communication System The system identi er (SID) of the Transport Management System
(TMS) communication system
Client Client of the TMS communication system
Normally, this is set to 000.
Target System Directory Message Server of the TMS communication system
Logon Group The name of the logon group
Node Name Name of the node in the transport system.
File Type The le type for translation.
Normally, this is set to ZIP because CTS usually uses a zip le.
Transport Organizer Link This is the site information that con rm CTS in the TMS server. That
is, this site is enabled to upload a le and release it to TMS server.
Batch le path To export, a batch le named transportconsole.bat, is

needed. It is located in the di_cmd_toos\transportconsole
folder.
Features
The purpose of transporting content with CTS is to ensure that you have two or more Planning and Consolidation servers with the
same content, and the same look and feel by transporting con gurations and content from one system into another. This means
10/24/2019
that, for example, you can duplicate the look and feel of your development environment in the testing and production
environments.
CTS is an export tool. You need to select the con gurations and content for transport, and CTS creates a transport package. You
can download this transport package and import it on the target server.
You can use the CTS tool for the following activities:
Selecting the content to include in the transport
Attaching additional objects to a transport request
Viewing the objects in a transport request
Exporting the selected content to the transport package
Organizing the transport
CTS does not provide any means of tracking or monitoring between the source and target systems. You must ensure that you
always use the correct transport packages, or existing content on the target system may be overwritten.
Activities
To transport content with CTS, the administrator needs to arrange and monitor the following tasks:
Select con gurations and content for export
Export the transport package to a le share
Track and plan imports
You can do this manually or develop a custom tool.
Move the transport package to a le share for import to the target system and save a copy of the transport package for
later import to another system
Import the con gurations and content to the target system, con gure the target system, and assign the content to a user
or users
More Information
You can nd detailed information about CTS and associated topics in SAP help. Go to http://help.sap.com and search on CTS.
Transport Content
Procedure
Select Content for Export
1. In the Administration Client, select the required environment, and then choose Transport Content with CTS from the
action pane.
The Transport Content with CTS screen is displayed. The following is an explanation of the elds in this screen:
Type
The following transport types are possible:
10/24/2019
Type Move Type Possible Sync Modes Comment
Reports File Update or Sync Model required
Input form File Update or Sync Model required
Conversion le File Update or Sync Model required
Transformation le File Update or Sync Model required
Data Manager packages File Update or Sync Model required
Script logic File Update or Sync Model required
Dimension Data Sync Model not required
Table driven logic Data Sync Model required
Security pro le Data Update Model required
If member access security

changes from [ALL] to a
speci c member, the import
result shows both [ALL] and
speci c member. It should
be synchronized after
running import CTS+.
Web Contents File Update Model not required
Note
If the Move type is “File”, you can expand the Type to view a list of the contents.
Model
If required. select a model from a list. You can also select the SyncMode for the model.
Folder
This shows the folder(s) associated with this transport type.
File Count
This is the number of les to be transported. If the move type is not “File”, this is 0.
SyncMode
There are two ways to transport in CTS:
Update replaces the selected item
Sync rst removes all data in the folder of the target server, and then moves the selected les or data
2. Select the transport types to transport and choose Export.
Note
For CTS export, you need an authorized ID and password to access the CTS server. If you select Store Detailed
Message, the whole procedure for CTS exporting will be saved as a le located at Install
Path\Data\Webfolders\AdminTemplates\CTS\Export\Log.
Organize Transport
10/24/2019
1. Start the Transport Organizer.
If the export is successful, a new transport request is in the list.
You can select this new request and choose the Object List tab to view the le; the le name is CTS and date ( yyMMdd)
and "time ( hhmm) .zip.
2. Select the request you want to import, and click Release.
The New Request icon changes to a Transport icon. Click Refresh to remove the request from the list.
Import with CTS
Note
To import with CTS, the service for CTS must be running in target server. This service detects the CTS le and starts
importing automatically.
To import, the Transport Management System (TMS) server must be available in SAP Logon as a Custom Application
Server.
1. Logon to TMS.
2. In the SAP Easy Access view, start transaction STMS.
The Transport Management System window opens.
3. Click the Transport icon to open the Import Overview window.
4. Double-click BPC import system (hdf).
The Import Queuewindow opens.
5. Select the transport request (you may have to refresh the list to make is visible) and click the Transport icon.
6. Enter a start time and click OK, then click Yes in the con rmation window.
If the transport is successful, the icon in the RC column of the Import Queue window is green.
If the transport is not successful, the icon in the RC column of the Import Queue window is red. Double-click this icon to
display the error report.
TMS moves the import le to the Web root\Data\Webfolders\AdminTemplates\CTS directory of the target server.
The Planning and Consolidation CTS Service Manager detects the le to import at that location and automatically starts importing
into the target server.
You can con rm the result of the import in the log le. The log le is in Web
root\Data\Webfolders\AdminTemplates\CTS\LogData and the le name is Import_CTS<export le
name>yyyyMMddHHmm.log. For example, Import_CTS_201101261212_201101220211.log.
Dimension Management
Use
A dimension is a collection of related data members, which represents one aspect of a business; for example, accounts, products,
or currency. You manage dimensions to add and perform other operations on dimensions in your environments, such as de ning
10/24/2019
members and assigning properties. The dimensions can be added to one or more models in the environment.
Features
You can manage dimensions in the following ways:
Adding Dimensions You can add new dimensions to an environment to make them available for use in its models.
See New Dimensions.
Copying Dimensions You can copy an existing dimension to create a new one. When you copy a dimension, you specify the
source dimension, a new ID, and a description.
See New Dimensions.
Modifying Dimensions You can modify an existing dimension. When you modify a dimension, you can save it with a new ID,
description, dimension type, reference dimension, and dimension properties.
See New Dimensions.
Processing Dimensions When you create a dimension or make changes to an existing dimension, you need to manually process
the dimension.
See Dimension Processing.
Deleting Dimensions You can delete a dimension from an environment. However, you cannot delete a dimension when it is
already assigned to a model.
You can delete a dimension from an environment by selecting a dimension and choosing Delete.
Exporting Dimensions You can export dimensions to an Excel workbook. The le is located in the dimension folder, AdminApp.
The system backs up the existing dimension le, and creates a new one with the exported information.
You can use the exported workbook to make changes to the dimension's members. The changes take
effect in the system once the dimensions are processed.
You export a dimension by selecting Export Dimension from the Manage Dimension action pane,
selecting one or more dimensions, and choosing Export Selected Dimensions.
Activities
To manage dimensions, select Dimension Library from the Administration Client's navigation pane. The tasks appear on the
action pane. The dimension tasks are also available from the action pane when you select an individual dimension.
More Information
Dimension Types
Dimension Security
Dimension Processing
Dimension Member Management
Assignment of Dimensions to Models
Reordering User-de ned Dimensions
10/24/2019
Dimension Properties
New Dimensions
Use
You add dimensions to an environment to make them available for use by their models. You can create a new dimension or copy an
existing dimension.
Features
When adding a dimension, you supply the following information. This information is also useful when copying or modifying a
dimension.
Field More Information
Dimension ID Dimension IDs are not case sensitive and display in the case you typed. They must be unique
regardless of case.
You can use any ID you want for a dimension as long as you follow these guidelines:
Do not use special characters such as accented characters or Cyrillic fonts in IDs.
Enter a maximum of 16 characters and without single quotation marks ('), double
quotation marks ("), back slashes (\), or ampersands (&).
Dimension IDs cannot contain a dash (-), but can contain an underscore (_).
Do not use the following names: App, AppAccess, AvlObject, CategoryAccess,

CollabDoc, CollabIcons, CollabRecipient, CollabSupport, CollabType,
DBVERSION, Defaults, DesktopStyleDef, Dimension, DrillDef, DTIParam,
Function, Formula, Group, InvestParam, MemberAccess, MessageLog,
Packages, PageDef, Permission, PublishedBooks, Rate, ReportParam,
SectionDef, Status, StatusCode, TaskAccess, User, UserGroup,
UserPackages, UserPovDef, WebContents, SOURCE, SIGNEDDATA, SCOPE.
Dimension Description Create dimension descriptions with a maximum of 50 characters and without double quotation
marks (").
Dimension Type The dimension type allows you to organize data within models based on the type of information
included.
See Dimension Types.
Reference Dimension Reference dimensions validate the properties of the dimension with the dimension member IDs
of a different dimension.
When you process the dimension, the system checks the values of the reference dimension
property (see Dimension Processing). Validation does not complete if they do not pass
validation.
See the following table for the dimension validation rules.
Dimension properties You can assign new properties to a dimension.
See Dimension Properties.
Dimension Validation Rules
10/24/2019
Dimension Type ID - Reference Type ID - Description Property ID Reference Property ID

Description
A - ACCOUNT A - ACCOUNT RATETYPE ID
C - CATEGORY T - TIME YEAR YEAR
E - ENTITY R - CURRENCY CURRENCY ID
I - INTERCOMPANY E - ENTITY ENTITY ID
Activities
Add a new dimension in the Administration Client by choosing Dimension Library Add a new dimension from the Manage
Dimensions actopm pane, then entering the required data.
Dimension Types
Use
You use dimension types to organize data within models based on the type of information involved. An environment can have
multiple dimensions of one type. Each model within the environment, however, can have only one of each of the required types. For
example, the environment might contain the entity dimensions EntityB and EntityF, with the Budgeting model using EntityB and
the Forecasting model using EntityF.
The following table describes the types of dimensions within the system:
Type ID Type Description More Information
A Account Usually contains chart of accounts and other planning assumption measures. The dimension is
normally represented by a hierarchy of accounts.
C Category This represents the versions or scenarios based on which data would be tracked. It contains the
types of data you are going to track, such as Actual, Budget, and Forecast. You can set up
categories to store versions, such as BudgetV1, BudgetV2, and so on.
D Audit This represents the various data source that could be used to manage the main data and
adustments if any. This can be used very effectively in calculations and in business rules of a
reporting consolidation model to segregate input data
R Currency This contains the currency rates for all currencies in which your company does business. For
validation purposes, all environments must contain a Currency dimension; however, each model
within an environment is not required to have a Currency dimension. The Currency dimension in
a Reporting model must contain the REPORTING property; the Currency dimension in a Rate
non-reporting model does not need to contain the REPORTING property. For information about
reporting and non-reporting models, see Model Management.
E Entity Represents the business units that are used to drive the business process. Depending on your
model design, the Entity type can be an operating unit, a cost center, a geographic entity, and so
on. This represents the organization unit, whether de ned for legal purpose or from a business
angle. This could be cost center, pro t center, legal company or region. The dimension is
normally represented by hierarchy of entities.
10/24/2019
Type ID Type Description More Information
G Group Reports consolidated results in multiple group currencies within a single entity structure. Group
provides multiple currencies for a group member.
Note
Assign both an R and a G identi er to a consolidation model but assign only the G identi er to
the ownership model referred from the consolidation model. You cannot assign both an R and
a G identi er to the same ownership model.
I Intercompany Contains the intercompany codes for the entities. This represents the intercompany codes for
the purposes of legal consolidation intercompany matching and elimination.
S Subtable This is used to break down the account activity or ow. For example, some accounts, such as
Fixed Assets, have a Subtable dimension containing Opening, Additions, Deletions, Transfers and
Ending Balances. The Subtable type dimension is important for writing business rules that
require currency translation amounts to be calculated by account.
T Time Contains the periods for which you store data. This represents the periods based on which data
are stored. The periods could be represented in various forms such as weekly, monthly, quarterly
or custom.
U User-de ned This represents any User-de ned dimension that may be required for the planning process.
Referred to in the system as U1, U2, U3, and so on.
Note
In addition to the dimensions listed above, the system also requires a dimension called Measures. This dimension is included
automatically in all environments. It is not listed as a dimension in the Manage Dimensions task, but is displayed on the context
bar in Planning and Consolidation. The Measures dimension allows you to change the view of your data between Periodic,
Week-to-date (WTD), Month-to-date (MTD), Quarter-to-date (QTD), and Year-to-date (YTD).
More Information
Model Management
Dimension Security
Use
Dimension security controls the access to dimensions and their members, and is implemented at the model level.
Features
You can utilize the features, described below, to secure dimensions.
Secured and Unsecured Dimensions
You can have a mixture of secured and unsecured dimensions in a model. Securing dimensions allows you to control which users
(or teams) have read, write or deny access to dimensions and their members. You need to de ne a dimension as secured if you
want to control data access by speci c dimensions. All users can access unsecured dimension members.
10/24/2019
Access pro les are used to grant model access. At least one dimension in a model should be secured to ensure control over model
and data access. When de ning data access for secured dimensions, be sure to de ne access for all secured dimensions of the
model. Failure to do so results in the inability to access that model for any users or teams assigned to the data access pro le. For
more information about setting up data access pro les, see Data Access Pro le Setup in the SAP Business Planning and
Consolidation Security Guide.
Security for Member-level Dimensions
In addition to de ning dimensions as secure for individual models, you can assign write access to members within the dimension
using data access pro les. Since by default, users do not have access to any members of a secured dimension, data access
pro les must be set up for the users you want to give read-only or write access.
More Information
For more information about Planning and Consolidation security, see the SAP Business Planning and Consolidation Security Guide
available on the SAP Help Portal at http://help.sap.com/bopacms101.
Use
When you create a dimension or make changes to an existing dimension, you must process the dimension manually.
Features
When you process a new dimension, its properties are saved in the database.
Processing an existing dimension saves any changes made to a dimension in the database.
You can process individual dimensions or all dimensions of a model.
You can specify that the processing is scheduled for a less busy time and you can also take the system offline for
processing.
You can use Validate formula only to validate dimension formulas without processing the dimension. You can quickly
validate any formulas in the dimension before saving them to the system.
You can use Show deleted members to display a list of deleted members before processing.
When processing dimensions and members, Business Planning and Consolidation decides what type of processing (Full vs.
Incremental) to perform based on the changes that have been made to the dimension.
Full: The system performs a full processing of a dimension when a property is added to the dimension, a member is
inserted in the middle of the worksheet, and when a change is made to the parent/child relationships (if the
dimension has a hierarchy).
Incremental: The system performs an incremental processing of the dimension when changes are made that do not
affect the structure of the dimension, such as editing a formula, adding a property value, or adding base-level
members to the end of the worksheet. If any of the applications in the Process Application list are selected, and the
dimension needs only incremental processing, applications will not be processed if they do not need processing.
Note
At any time, you can override the system-detected processing option by forcing the full processing of a dimension.
Activities
10/24/2019
To process dimensions, select Dimension Library in the Administration Client navigation pane.
Select Process Dimensions in the Manage Dimensions action pane, and choose desired processing options and dimensions.
More Information

Use
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, your company may open a new office, and the nancial information of
that office must be part of the Entity, Category, and Currency dimensions.
Features
Dimension Member Template (or sheet)
For each dimension in the dimension library, there is a dimension member template, or, what is frequently called a member sheet
(which is short for worksheet). The member sheet is a Microsoft Excel worksheet that you modify using native Excel functionality.
Here are some guidelines for using the member sheet:
You must not change the name of the rst worksheet from Member, or it does not work correctly.
You can save the member sheet on the server. When processing a dimension, you can use an open member sheet or the
member sheet saved on the server.
You must customize the template with the members used in your business processes. For example, when starting from the
sample environment EnvironmentShell and editing a member sheet for the rst time, you must delete any sample
members using Excel. Then add members using the process de ned below.
Based on the dimension type, the template contains a set of prede ned properties. You can add new properties, as desired.
You can assign dimension formulas that calculate and store information based on member values.
Adding Members to Dimensions
You can add a single member or multiple members to a dimension. Typically, when setting up your system, you load bulk members
into a dimension by entering the master data from an existing source. For example, using Excel, you can open an existing
spreadsheet, then copy and paste the members from the source le to the member sheet. With subsequent additions, you can
type a member and its properties in the appropriate row.
You can add members to dimensions within an environment by choosing Dimension Library within the Administration Client.
Select the dimension for which you want to add a member, then choose Maintain dimension members. In the rst empty row (or
you can insert a row in the middle of the sheet), enter the ID of the member and properties in the appropriate columns, or paste
the contents of the clipboard into the sheet. After you have entered the desired members, choose Process Dimension. Be sure to
choose Process members from member sheet.
Note
10/24/2019
If you make changes to any rules in the dimension, such as adding a new formula, you must validate and save those rules, and
process the dimension.
You can also add members to dimensions in bulk using packages within the Data Manager. For more information, see the SAP
BusinessObjects EPM solutions, add-in for Microsoft Office help.
Caution
You cannot rename dimension member IDs.
More Information
Assignment of Dimensions to Models

Use
You assign dimensions to models to make the data from those dimensions available in your model. Each model must have at least
one dimension of the required types: Account (A), Category (C), Entity (E), and Time (T).
Note
Use caution when adding dimensions from a model that already contains data. Assign dimensions only to new models that do
not contain data. If you add a dimension to a model with data, the system nds the rst base member alphabetically, and loads
it into the fact tables, therefore writing all of the data from the model to that member.
Prerequisites
You have added the dimension to the dimension library.
Activities
To assign a dimension to a model, you modify the model in the Administration Client as follows:
Highlight the model and select Modify Model.
Choose one or more shared dimensions, and, using the arrow keys, move the dimensions from the Shared Dimensions
column to the Model Dimensions column.
Select Modify Model again.
More Information
Model Management
Reordering User-de ned Dimensions

Use
10/24/2019
Each user-de ned (U-type) dimension has a unique key, known as an index.
Note
The maximum number of dimensions allowed in the index is 999. For more information about assigning user-de ned
dimensions to a model, see Dimension Management.
You can reorder the list of U-type dimensions displayed in the context for a model by the following procedure.
Procedure
1. From the Administration Client, select a model.
2. Select Modify Model, then select Manage Type.
3. In the Index column, enter the index numbers, for example, 3 , 4 , 1, and 2, indicating the order in which you want the
dimensions to display, then click OK .
4. Select Reassign SQL Index and Process Model, then click Modify Model.
Note
If you change the index of a user-de ned dimension, you must manually update in all model templates the functions that
reference this user-de ned dimension.
Use
By assigning properties to dimensions, you implement powerful features in your reporting, member lookup, formulas, Data
Manager selections, and so on. You can lter on properties in many places in the system. For example, if you want to be able to
easily select entities by geographic region, you simply add a REGION property, and enter a region value for each entity. Then you
can lter and sort by region, apply account logic by region, or de ne a report format based on region.
The system requires various properties depending on the dimension. You can also assign additional properties for your business
needs.
Many of the properties are generic, such as ID and EvDescription, while others can be unique to a dimension, such as
Scale. The properties de ne the behavior of members within the dimension.
Features
You can use the following features when working with dimensions.
Adding Properties to Dimensions
You can add new properties to a dimension by selecting a dimension within the dimension library, selecting Maintain Dimension
Properties, and adding a property ID at the bottom of the property list. When you save the dimension after new properties have
been added, the property names appear as column headings on the dimension's member sheet.
You must also specify the acceptable maximum alphanumeric length of the property values, and whether the property is saved in
the OLAP database (InApp).
10/24/2019
There is no limit to the length of dimension properties you create. However, if you need to reduce the length of an existing
dimension property (for performance reasons), create a new property, copy the values over from the old property, then delete the
old property.
If a property is saved in the OLAP database, you can write MDX queries using that property. This may increase the database size
signi cantly. If you do not need to write MDX queries against a property, you should leave the InApp checkbox unselected.
Note
The system does not permit you to keep columns on a member sheet that are not related to properties. In addition, if you
reorder the columns in the dimension sheet, the system does not maintain the new order when you close the sheet.
Adding Property Values to Properties
After you add a property to a dimension, you can assign property values to members in the dimension. You can add property
values to properties by selecting the desired dimension from the dimension library, selecting Maintain Dimension Members, then
adding the desired values directly in the member sheet under the appropriate property. After you are done, you should save the
member sheet and process the dimension.
Deleting Dimension Properties
You can delete dimension properties from a dimension, as long as they are not required. You delete a dimension property by
selecting a dimension within the dimension library, selecting Maintain Dimension Properties, deleting the text from the Property
Name column, then selecting Modify Dimension Property from the action pane.
Special Properties
SOLVE_ORDER The SOLVE_ORDER property de nes the order in which the system solves calculated members when they intersect
with other calculated members. SOLVE_ORDER determines the order in which the system evaluates and calculates
dimensions, members, calculated members, custom rollups, and calculated cells. The system evaluates the member
with the highest solve order rst, and calculates it last. Zero is the highest priority.
Guidelines for implementing SOLVE_ORDER:
Specify up to three measures and ve members within a SOLVE_ORDER property.
Specify dimensions by dimension ID, making sure that capitalization is correct.
Example
[ACCOUNT].[Account1] / [ACCOUNT].[Account2]
[PRODUCT].[Product1] + [PRODUCT].[Product2]
The only exception to this rule is that you do not need to specify an Account dimension by name.
FORMULA The optional property FORMULA allows you to de ne calculations to perform for dimensions. This powerful feature of
the system gives you the ability to customize data management to meet your business requirements.
More Information
Owner Property
10/24/2019
Use
The owner designating dimension property is created in any dimension used as a driving dimension for a business process ow.
You add the property to the dimension with any name, however, we recommend using a naming convention to note the
relationship to process owners. A dimension can have one or more owner designating properties as long as each is unique.
For example, if your business process dictates that an entity is the differing factor when it comes to entering data, the Entity-type
dimension is the dimension that drives the owner of the activity context. If your process dictates that a department name is the
differing factor, the Department dimension would have a unique owner designating property that drives the owner of the activity
context. The “Owner” property used for work status is a reserved property. The process owner properties must have a unique
name.
Prerequisites
The dimension you select to drive work status has one hierarchy in the base hierarchy of the work status setting. See Setup of
Work Status Dimensions.
Features
The owner designating property takes user and team IDs in brackets as values. You can enter multiple user and team IDs
separated by commas. You must also include the domain or server name in the path.
Activities
You do the following to set up an Owner property:
Set up the owner property by accessing the Dimension Library, choosing Maintain Dimension Property, and adding an
owner.
Assign the owner property to a dimension by accessing Maintain Dimension Members, De ne the owner property on a
dimension such as Entity, then de ne the property values. You can enter multiple user and team IDs separated by commas.
You must also include the domain or server name in the path.
Reviewer Property
Use
The Reviewer property is a property used to identify the person or team that must review an activity performed by another user in
a process. This person or team member can approve or reject the action taken by the user. A reviewer can also reopen the
previous step of a process.
The Reviewer property must be de ned before creating a process template, as the administrator is required to enter it when
setting up the template.
Features
When de ning the property, the following rules apply:
You can de ne the reviewer property on any dimension. It must be named Reviewer
The reviewing process is by process step
One dimension in each model can have a reviewer property

10/24/2019
The dimension for which you de ne the Reviewer property becomes the driving dimension for the process template
When de ning the property values, the following rules apply:
The value can be a user or a team ID, or a combination of both
If de ning multiple property values, you must separate each entry by a comma
A user ID must include its domain, as in domain\ID
A team ID must be enclosed in brackets, as in [TEAM]
The reviewer property is case sensitive
The limit is 255 characters
A reviewer can reopen the previous step of a process, provided that the de nition of the step allows reopen
Activities
To de ne a reviewer property, open the dimension that you want to designate as the driving dimension of the process, then add a
Reviewer property.
After adding the dimension property, add the desired property values using the rules above. For more information about adding
properties and property values to dimensions, see Dimension Properties.
When creating a process template, choose Enable Reviewers, then set a Reviewer property when de ning the activity context
criteria of a new step.
Account Dimension Properties

Use
The account dimension de nes the chart of accounts for your model, and how those accounts are calculated and aggregated. Any
dimension that is assigned the type A is considered an account dimension. Each model can have only one account-type
dimension.
Features
An account dimension has the following required properties:
Property Name Description
ACCTYPE Account type. Can be INC for Income, EXP for Expense, AST for Asset, and LEQ for Liabilities and Equity
RATETYPE Used by the currency conversion business rules. Value is optional.
SCALING Scaling options are Y or N. Used by EPMScaleData, and Web reports. Value is optional, but if a value is not
de ned, scaling is unavailable for the associated member ID.
The following property is required only if the account dimension is used in a consolidation model.
10/24/2019
TYPELIM Speci es that Eliminations and Adjustments details are created

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

multipliers.
More Information
Business Rules Management
Category Dimension Properties

Use
The category dimension de nes the groupings in which you store information in your model. Typical categories would be Budget,
Actual, Forecast, and so on. Any dimension that is assigned the type C is a category dimension. Each model can have only one
category-type dimension.
Features
The following properties are required only if the category dimension is used in a consolidation model.
CATEGORY_FOR_OPE Category of source data to use when performing carry forward (CopyOpening).
FX_DIFFERENCE_ONLY Speci es whether the translation result is calculated normally (blank or N), or if only the
translation difference with the source category is computed ( Y).
FX_SOURCE_CATEGORY Category of source data to be used when running currency translation on a simulation category.
OPENING_PERIOD Period number of source data to use when performing carry forward (CopyOpening). This can
be absolute (for example, 12 for December) or relative (for example, -1 for prior period).
OPENING_YEAR Year offset of source data to use when running carry forward (CopyOpening). This is relative (for
example, -1 for prior period).
OWN_CATEGORY Category of source ownership data to be used when running consolidation on a simulation
category
OWN_YEAR Period number of source ownership data to be used when running consolidation on a simulation
category. This can be absolute (for example, 12 for December) or relative (for example, -1 for
prior period).
OWN_PERIOD Year offset of source ownership data to be used when running consolidation on a simulation
category. This is relative (for example, -1 for prior year).
10/24/2019
RATE_CATEGORY Category of source exchange rate data to use when running currency translation on a
simulation category
RATE_PERIOD Period number of source exchange rate data to use when running currency translation on a
simulation category. This can be absolute (for example, 12 for December) or relative (for
example, -1 for prior period).
RATE_YEAR Year offset of source exchange rate data to be used when running currency translation on a
simulation category. This is relative (for example, -1 for prior year).
STARTMNTH Starting month.
More Information
Currency Dimension Properties

Use
The Currency dimension is required if your company reports on local currency and translated values. These dimensions store the
reporting and input currencies for your organization. Any dimension that is assigned the type R is a currency-type dimension.
Features
The following table describes the required properties for a currency dimension. If you are utilizing the legal consolidation
functionality of Planning and Consolidation, the currency-type dimension requires additional properties.
ENTITY A 20-character eld that can either be left blank or contain a valid member name of the entity dimension
associated to the current model. The ENTITY property is validated against the entity dimension. Blank
elds are allowed.
REPORTING This property is used to specify your reporting currencies. If Y, this member is used for reporting purposes.
More Information
Entity Dimension Properties

Use
The entity dimension de nes 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.
10/24/2019
Features
An entity dimension has the following required property:
CURRENCY De nes the currency used by the

entity.
The following properties are required only if the entity dimension is used in a consolidation model.
FX_TYPE De nes the subset of Currency Conversion rules to apply to the entity, where FX_TYPE
matches the Entity FX Type property of the rules.
ELIM De nes whether the entity is used to store the intercompany elimination for a given node in
the hierarchy. Valid values are Y or N.
OWNER De nes the owner of the entity dimension.
More Information
Group Dimension Properties

Use
The group-type dimension represents the relationship of entities for a given consolidation result. This group is consolidated in a
single currency, so there is no need to have another dimension. You can continue to use the currency-type dimension for this
purpose, or you can split it into a group-type dimension (type G) and use a pure currency-type dimension (type R) to allow
reporting in multiple group currencies.
Note
A group dimension must be assigned to an ownership and a consolidation model. You should assign both a currency and a
group dimension to a consolidation model but you should assign only the group dimension to the ownership model referred
from the consolidation model. You cannot assign both a currency and a group dimension to the same ownership model.
CURRENCY_TYPE This is used for the currency conversion.
N - Non Group
G - group
ENTITY Blank or a valid entity ID. This is used to de ne the link between the Group and the Entity or to indicate
the Entity where the aggregation should be stored.
If this property is lled with a valid entity ID, and the property STORE_ENTITY is set to Y, the results of
the currency conversion for the current Group are also copied into this Entity. (Length = 20.
10/24/2019
GROUP_CURRENCY This can be any valid reporting currency, and is used for currency conversion.
This property can only be used on Currency members with the property CURRENCY_TYPE of G and, in
this case, it must contain a valid ID from the Currency dimension with the property CURRENCY_TYPE
value of R. (Length = 20.)
PARENT_GROUP Must be a valid ID from the Groups dimension. If you want to do the consolidation by level, you must
indicate here the higher level from the group. If you want to use this property to de ne the hierarchy,
enter the same code as the ID for your top group. If this property is blank, the ownership-based
hierarchy from the ownership model is used. (Length = 20.)
STORE_ENTITY 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.
STORE_GROUP_CURR Used for currency conversion.
Y (or blank) - By default the results of the conversion into a Group currency are written in both the
Group member and in the Currency member of the currency dimension.
N - If only the Group member is to be stored, set this property to N. (Length = 1.)
CONSO_TYPE Consolidation type used in consolidation calculation. Link with the property consolidation type in the
consolidation header table.
DATASRC_LEVEL Used in consolidation calculation. Y if you want to apply a datasrc level to the stage.
REPORTING Indicates reporting currency. For example, if Y is set in the property, then the member is set as a
reporting currency.
More Information
Intercompany Dimension Properties

Use
The Intercompany dimension de nes the base members associated with the level at which Intercompany balances are tracked for
Intercompany eliminations.
Features
An Intercompany dimension has the following required properties:
ENTITY A 20-character eld that can either be left blank or contain a valid
member name of the entity dimension associated to the current
model. The ENTITY property is validated against the entity
dimension. Blank elds are allowed.
SCALING Scaling options are Y or N. Used by reports, and the Library view.
Value is optional, but if a value is not de ned, scaling is unavailable
for the associated member ID.
10/24/2019
More Information
Time Dimension Properties

Use
The time dimension de nes the units of time for your model, and how those units aggregate. Any dimension that is assigned the
type T is a time dimension. Each model can have only one time dimension.
Features
A time dimension has the following required properties:
LEVEL Time can be a year, quarter, month, week, or day. The LEVEL property is important in de ning your
periods. You must have the correct level for each member. You must follow the chronological format
throughout the time dimension. The correct format is the following:
YEAR
QUARTER
MONTH
WEEK
DAY
PERIOD The PERIOD property allows you to lter, sort, and report based on the period.
ISBEGINNING The period corresponding to the beginning of a year, such as Q1 or January.
BASE_PERIOD A property generated by the system during migration for environments with a MONTHNUM property;
also used by the Consolidation process
More Information
Dimension Management
User-De ned Dimension Properties

Use
A user-de ned dimension is any dimension, which is not one of the standard system dimensions.
10/24/2019
Features
A user-de ned dimension has the following required properties:
SCALING Scaling options are Y or N. Used by EPMScaleData, reports, and Library view. Value is optional, but if a
value is not de ned, scaling is unavailable for the associated member ID.
More Information
Audit Dimension Properties

Use
The audit dimension tracks the source of input data, and is user-de ned.
Features
An audit dimension has the following required properties:
SCALING Scaling options are Y or N. Used by , EPMScaleData, and Web

reports. Value is optional, but if a value is not de ned, scaling is
unavailable for the associated member ID.
The following property is required only if the audit dimension is used in a consolidation model.
DATASRC_TYPE Speci es whether a data source is used for Input (I), Manual
Adjustments (M) or Automatic Eliminations and Adjustments (A).
IS_CONSOL Speci es whether data is consolidated or not. Typically this is set to

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

yes (Y, G), but set it to no (N) for data sources used in currency-
speci c adjustments (for example, adjustments in EUR, USD, and so
on).
DATASRC_STAGE De nes to which Audit member consolidation adjustments from

lower groups are inherited in higher groups (Parent groups).
DATASRC_ORIG Property used to create a grouping of data sources which can later
be used as lters in Eliminations and Adjustments business rules.
10/24/2019
COPYOPENING Flag used to lter data sources when running carry forward
(CopyOpening).
OPENING_DATASRC Speci es a different destination data source, to which the

corresponding amounts are carried forward. For example, this can
be used where certain entries are posted to a data source that
speci cally identi es these adjustments as audit adjustments in the
current year, but in future years it might be required to simply
include in another standard data source (that is, Input).
More Information
Subtables Dimension Properties

Use
Subtable dimensions break down account activity or ow. For example, some accounts, like Fixed Assets, have a subtable
dimension containing Opening, Additions, Deletions, Transfers, and Ending Balances. The subtable type dimension is important
for writing business rules that require currency translation amounts to be calculated by account. Since the subtable information
can be used for multiple accounts, it requires its own dimension.
Features
A subtable dimension has the following required property:
SCALING Scaling options are Y or N. Used by EPMScaleData, reports, and

Library view. The value is optional, but if a value is not de ned,
scaling is unavailable for the associated member ID.
The following property is required only if the entity dimension is used in a consolidation model:
10/24/2019
FLOW_TYPE De nes the type of ow of the dimension, as follows:
OPENING - Opening
TRANSLOPE - Change difference on opening
ALLOCINC - Allocation
MERGER - Merger
INCOME - Net income from the period
CHANGE - Variation
TRANSFER - Transfer
TRANSFLOW - Translation change on ow
VARSCP - Variation in scope (generic)
VARSCPMETH - Variation in scope method
VARSCPPERC - Variation in scope percentage
VARSCPNEW - Variation in scope new company
VARSCPLEAV - Variation in scope sold company
CLOSING - Closing
NONE - No ow
Blank - All other ows
More Information
Model Management
Use
A model is a representation of the business data that de nes the relationships, calculations, and data of an organization, or
business segment. Planning and Consolidation is shipped with two models as samples: Planning and Rate. See EnvironmentShell
Sample Environment.
Features
You can perform the following tasks when managing models.
Adding New Models You can add new models to an environment.
See Adding New Models.
10/24/2019
Copying Models You can copy a model as a quick way of creating a new model. When you copy a model, its dimensions, data,
and templates are copied from the source model. You can modify the model later.
You copy a model from the Administration Client by choosing Model Copy a Model , selecting a source model,
entering the name of the new model, then choosing Copy a Model.
Modifying Models You can modify models.
See Modifying Models.
Deleting Models Administrators can delete models when necessary.
You delete a model from the Administration Client by choosing Model Delete Model .
Caution
You can delete a model when it contains data. You cannot, however, delete a dimension member when there
is data associated to that member in the model.
Activities
To manage models, log on to the Administration Client, and select the Models node from the navigation pane.
Note
When you create new environments and models, only a small amount of data exists. However, the amount of data you maintain
grows over time, therefore, we recommend you periodically run the optimize function to improve performance. See Optimizing
Models.
More Information
Model Tasks
Adding New Models

Context
You can add a new model to the current environment.
Procedure
1. Choose Model from the left navigation pane, then select Add a New Model from the action pane.
2. Give the model a name and description, then go to the next pane.
3. Choose the type of model you are adding, then go to the next pane.
Models types are 'Reporting' and 'Drivers and Rates'. Reporting models are used for user input and analysis. Drivers and
Rates models store reference data such as currency rates. For information about each models type, see Reporting Models
and Drivers and Rates Models.
4. If you selected a drivers and rates model type (Exchange Rates, Ownership, or Generic) or a Standard reporting model type
in step 3, do the following:
a. Select a source model from which to copy its data, then go to the next pane.
10/24/2019
b. Select Dimensions to copy all the dimensions from the source model, or deselect it to select the dimensions you
want to copy, then go to the next pane. For more information about assigning dimensions to models, see Dimension
Management.
c. Select Add a New Model.
5. If you selected a Financial reporting type in step 3, do the following:
a. Select a source model from which to copy its data.
b. Select a supporting Drivers and Rates model.
c. Select the business rules to associate with it, then go to the next pane. Deselect the checkboxes next to the
business rules you want to remove from the model.
For more information about adding business rules to models, see Business Rules Management.
d. Select Dimensions to copy all the dimensions from the source model, or deselect it to select the dimensions you
want to copy, then go to the next pane. For more information about assigning dimensions to models, see Dimension
Management.
e. Select Add a New Model.
6. The system creates a new model. When the process completes, click OK.
Results
The new model appears under the Models node in the left navigation pane.
Next Steps
Model Tasks
YTD Storage Models
Reporting Models
Use
Reporting models hold nancial data.
Features
The following table describes the different types of reporting models and lists the required dimensions for each:
Type of Reporting Model Description Required Dimensions
10/24/2019
Type of Reporting Model Description Required Dimensions
Financial Financial models perform management and Account (A)

legal consolidation functions. They support
Category (C)
data translations from local currencies to
one or more reporting currencies, Entity (E)
intercompany elimination calculations, and
other calculations. Time (T)
When you create a nancial model, you must

choose an associated exchange rate model
(see Drivers and Rates Models).
You can also choose to set up the following

business rules:
Currency conversion
Account-based calculations
Intercompany bookings
US eliminations
Carry-forward rules
Validations
Consolidation Consolidation models perform more Account (A)

complicated legal consolidation functions
Category (C)
than Financial models. Consolidation can
incorporate complex organizational Entity (E)
structures involving full ownership, partial
ownership, minority ownership and Time (T)
consolidation methods.
Audit (D)
Consolidation models must reference an
ownership model and an exchange rate
model (see Drivers and Rates Models).
You can also choose to set up the following

business rules:
Currency conversion
Account-based calculations
Intercompany bookings
US eliminations
Carry-forward rules
Validations
Eliminations and adjustments
Standard Standard reporting models have no special Account (A)

requirements other than the four required
Category (C)
dimensions. Standard models have no
default business intelligence. Therefore, to Entity (E)
apply logic, create it using script logic.
Time (T)
10/24/2019
Drivers and Rates Models

Use
Drivers and Rates models support reporting models by holding data such as currency exchange rates and ownership percentages.
Features
You can report on Drivers and Rates model data. You cannot de ne business rules to these model types. The following table
describes the different types of Drivers and Rates models and lists the required dimensions for each:
Type of Drivers and Rates Model Description Required Dimensions
Exchange Rate An Exchange Rate model is a supporting Account (A)

model for nancial and consolidation
Category (C)
reporting models. Use it to store exchange
rates that support currency conversion in Entity (E)
nancial models.
Time (T)
The time dimension must be identical to the
dimension used by the models using the Currency (R)
Exchange Rate model to store their foreign
currency exchange rates and must have the
same category member IDs.
This model must include a currency

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

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

requirements other than the four required
Category (C)
dimensions. Generic models have no default
business intelligence. Therefore, to apply Entity (E)
logic, create it using script logic.
Time (T)
Model Tasks
Use
You can perform tasks on existing models to change the way they behave.
Features
10/24/2019
Model Task Action Pane
The following tasks are available from the Manage Models - Model Tasks action pane:
Modify Models Choose whether to modify the selected model or a different model.
See Modifying Models.
Delete Models Choose to delete a selected model or a different model.
See Model Management.
Optimize Models Choose to optimize the selected or other models.
See Optimizing Models.
Set Model Parameters Choose to update model parameters.
See Model Parameters.
Edit Book and Distribution Choose to delete one or more book templates.
Templates
See Deletion of Book Templates.
Manage Data Audit Choose to de ne data audit setup.
See Data Auditing.
De ne Journal Validation Rules Choose to de ne journal validation rules.
See Journal Validation Rules.
De ne Journal Translation Rules Choose to de ne journal translation rules.
See Journal Translation Rules.
Other Tasks
Additional tasks to perform on models are de ned in the nodes beneath the model for which you want to changes its behavior.
These are shown in the following table:
Work Status Settings Choose to de ne work status settings for the model. De ning work status settings involves specifying
who can make changes to the data and who can change the work state on a data set.
You create work states to re ect the status of data as it moves through your business processes.
See Work Status Setup and Setup of Work Status Dimensions.
Concurrent Lock Choose to de ne concurrent locks for a model. Concurrent locks prevent multiple users from sending
data to the same intersection at the same time. The default setting for concurrent locks is the entity,
time and category dimensions. This is typically sufficient, but you can set additional locks if required.
Setting more concurrent locks than necessary does have an impact on performance.
See Concurrent Locks.
10/24/2019
Dimensions Choose to display the dimensions de ned in the model.
To assign dimensions to models, or edit dimensions in a model, see Dimension Management.
For a legal consolidation model to function properly, it must contain the four required entity, category,
time, and account dimensions (but can be named as desired). The remaining dimensions have the
following rules:
The CURRENCY/ GROUP dimension is required for the consolidation and currency business rules.
The INTCO dimension used for matching intercompany activity.
The DATASRC dimension is required for elimination and/or consolidation business rules.
The SUBTABLE ( ow) dimension is optional, and based on your requirements.
For more information, see Legal Consolidation.
Drill Through Choose to add drill through de nitions in the model. You can set up drill through de nitions to view the
source data that make up the content of a selected cell in a report.
See Drill-Through Setup.
Business Rules Choose to add business rules to the model by doing the following: Select the model from the
Administration Client, then select Modify Model Change Model Type Modify Model .
Select the checkboxes next to the business rules tables you want to add to the model, then select
Modify Model. (You can deselect the checkboxes next to the business rules you want to remove from the
model.)
For more information about de ning business rules for models, see Business Rules Management.
Journals Journal Wizard - The journal wizard guides you through the process of creating an new journal. The
process involves the following steps:
Select header dimensions
The defaults are entity, rate, and time.
Set header dimensions order
Adjust the sequence for the header dimensions.
Set detail dimensions
All the remaining dimensions (that is, those that are not selected as header dimensions) are the
rows of the report. You can adjust the sequence of the detail dimensions.
Create additional header items
Use this option to create additional text-based header items if required.
Clear Journal Table - Use this option to clear all journals for a model so that you can create new versions.
Script Logic You can create a new script logic or modify, validate, or debug an existing script logic.
When you choose Create New Logic and entered a name for it, you can use the logic assistant to create
the script. Once created, you can use the validate, debug, and save options.
When you are working with an existing script logic, you can use the same options and the logic assistant
to enhance your script.
See Script Logic.
Activities
10/24/2019
To work with models, log on to the Administration Client, and select the Models node from the left navigation pane.
More Information
YTD Storage Models
Modifying Models
Context
Use this procedure to modify an existing model.
Procedure
1. From the Administration Client, select the Model node, and then the model you want to modify.
2. Select Modify Model from the action pane.
3. Add or remove dimensions, and assign options to the dimensions, as desired. See Dimension Management.
4. Select the source model upon which to base the model, or accept the default.
5. Enter a new description, if desired.
6. Choose a dimension to set a secured dimension and select Secured. Click R/W to set the dimension as read/write.
7. Select Manage Type to rearrange the index of user type dimensions. If you click the index column of the grid, you can
modify the Index value.
8. For the Model Rebuild Options, select Reassign SQL Index to rebuild constraints, indexes, and dependencies on the fact
tables. Select Process Model to enable the system to process the model upon completion of the modify steps.
9. Select Modify Model if you are done, or select Change Model Type to continue.
10. Select a model type, if desired, then click Modify Model.
11. When the process is completed, click OK in the con rmation dialog box.
Optimizing Models
Context
Optimization cleans up data storage which improves the responsiveness of the system.
You can use the procedure described below, or Data Manager to optimize models. In Data Manager, optimization tasks can be
added to Administrative packages and scheduled. The optimization process is included in the AdminTask_Optimize sample
package.
Procedure
1. From the Administration Client, select one or more models to optimize.
2. Select the process type:
Full optimize - Clears both real-time and short-term data storage, moves both to long-term data storage, and
processes the partition. This option takes the system offline and takes longer to run than the Incremental
Optimization. It is best scheduled at downtime periods. You can schedule a Full Process Optimization to be weekly
or less frequently depending upon your requirements.
10/24/2019
Incremental optimize - Clears both real-time and short-term data storage, moves both to long-term data storage,
and processes the short-term and long-term partitions for the moved data. This option takes the system offline, so
it is best run at off-peak periods of activity.
Lite optimize - Clears real-time data storage and moves it to short-term data storage. This option does not take the
system offline, so you can schedule it to run during normal business activity. We recommend a Lite Optimization
when the write-back table exceeds 200 KB.
Note
If you have custom partitions and run Full Process Optimization, only the partition that had data moved from Fac2 and
WB table is processed. For example, you have 3 custom partitions, Fact2008, Fact2009, and Fact2010. Fac2 and the WB
table has only 2009 data. In this case, if you run a Full Process Optimization, only Fact2009 is processed.
3. To compress the database, select Compress Database. The Compress Database option sums multiple entries for the same
context into one entry, so that data storage space is minimized.
4. To defragment the index, select Index Defragmentation. Optimizing the database can cause the database index to become
fragmented. Selecting this option forces a reindex of the database. You can also reindex your database directly from SQL.
5. Select Optimize Models, then in the con rmation dialog box, click OK.
Model Parameters
Use
Model parameters control the way certain features behave in a model.
Prerequisites
Administrators with Administration - Model task security rights can set model parameters.
Features
Model parameters can be different for each model within an environment. If a model parameter is required, you can leave it blank
to accept the default. If you delete the parameter, the system may not work correctly. If a model parameter is optional, you can
delete it.
The following table describes the parameters you can set within the Administration Client using the Model Management action
pane.
The parameters that require a value include (R) in the Type column. Parameters that do not require a value include (O) in the Type
column. If a model parameter is required, you can leave it blank to accept the default. If you delete the parameter, the system may
not work correctly. If a model parameter is optional, you can leave it blank or delete it.
(O) COMMENT_ENABLE Use this parameter to control how comments are used.
Valid values for this parameter are:
1 (default), which means that it is possible to add, edit, and delete

comments.
0, which means that it is only possible to view existing comments.
10/24/2019
(O) CUSTOMFACTTBLINDEX Use this parameter to de ne a dimension list to create a custom index in the
appropriate database table and accelerate import processing.
Valid values for this parameter are: Category, Time, Entity, Account,
and RptCurrency.
Enter a list of dimensions into this parameter, separated by commas.
When you use a custom fact table index, we recommend that when you
modify the model, you select the Reassign SQL Index option.
This parameter is used in Administration Client - Modify model, Add a new

model, Copy a model.
(O) DIMSFORFACTTBLINDEX Use this parameter to specify the elds and the eld order for the indexes
used by the Fact, Fac2 and write-back tables. The Fact and Fac2 tables use a
clustered index; the write-back table uses a composite index.
Valid values are:
Category
Time
Entity
Account
RptCurrency
Enter a list of dimensions into this parameter, separated by commas.
The default value is:
Category, Time, Entity, Account, RptCurrency
If the parameter is blank, the default elds and eld order are used.
This parameter is used in Administration Client - Modify model, Add a new

model, Copy a model.
(O) DTSLOGPAGESIZE Use this parameter to set the number of records that display in the Data
Manager Status View.
Enter the number of records to display.
This parameter is used in Data Manager - Status View.
(O) JRN_ACCDETAIL_DIM Use this parameter to specify a special dimension name used to manage the
Opening, Closing, and Reverse Sign codes.
This is used with JRN_CLOSING_CODE, JRN_OPENING_CODE, and

JRN_REVSIGN_CODE.
This parameter is used in SAP BusinessObjects EPM Solutions, add-in for

Microsoft Office - Journal.
10/24/2019
(O) JRN_BALANCE Use this parameter to control whether it is necessary for Journals to be
balanced.
Valid values are:
0 - Journals need not be balanced
1 - Journals need to be balanced

(O) JRN_CLOSING_CODE Use this parameter to specify the member name for the Closing code. This
member is part of the dimension name speci ed by JRN_ACCDETAIL_DIM.
The member name must be set to use this feature.

(O) JRN_DESC_MODE Use this parameter to allow the display of the description in the journal
template.
Valid values are:
N - Displays the member ID in the journal template for the model.

This provides optimal readability.
Y - Displays the description of member in the journal template
The default value is N.

(O) JRN_IS_STAT_APP Use this parameter to enable or disable subsequent journal elds, if the
model is used for statutory consolidation.
Valid values are:
1 - Enables the subsequent journal elds
0 - Disables the subsequent elds

(O) JRN_MAXCOUNT Use this parameter to specify the maximum number of journal entries
returned from a query in the Journal Manager. This is useful if you have a
large number of Journal Entries and want to protect a user from launching a
long query.

10/24/2019
(O) JRN_OPENING_CODE Use this parameter to specify the member name for the Opening code. This
member is part of the dimension name speci ed by JRN_ACCDETAIL_DIM.

(O) JRN_POST_OVERWRITE Use this parameter to specify whether the system keeps the same Journal ID
when saving journals that were previously set to Posted status, but changed
to Unposted status.
Valid values are:
Y - Preserves the Journal ID when the unposted journal is saved
N - Creates a new ID when the unposted journal is saved

(O) JRN_REOPEN Use this parameter to de ne the default for reopening journals.
Valid values are:
N - Does not allow reopening of journals
Y - Allows the reopening of journals

(O) JRN_REOPEN_PROPERTY Use this parameter to specify the property name in the account dimension
that is used to further lter the journals to reopen.
A valid value is a property in the account type dimension.
The default value is GROUP.
If this parameter is not set, the GROUP property must exist in the account
type dimension. Alternatively, to use a property other than GROUP, change
the value of the ACCOUNT_PROPERTY column in the Journal Translation
template. This value can be any property in the account type dimension, or *.
For more details, see SAP Note 1384731 .
(O) JRN_REVSIGN_CODE Use this parameter to specify the member name that is used to reverse the
sign during posting and unposting. This member is part of the dimension
name speci ed by JRN_ACCDETAIL_DIM.

10/24/2019
(O) JRN_VALIDATION_FILTER Use this parameter to enable dimension ltering in the journal editing web
page.
Valid values are:
Y or 1 - Enabled
N - Disabled
(O) JRN_VALIDATION_SP Use this parameter to specify the SQL stored procedure name to be executed
before posting or unposting data. This stored procedure performs custom
validation on the entire RecordSet to be posted or unposted and returns
go/no-go to the posting engine.

(O) LOCKREPORT Use this parameter to specify a report name to launch when submission
validation for a data region is not 0. The validation template must be located
one of the following folders:
<drive>\webfolders\ <environment>\
<model>\eExcel\input schedules\Templates\
<drive>\webfolders\ <environment>\
<model>\eExcel\input schedules\
A sample validation template provided with EnvironmentShell sample

environment is located in
<drive>\webfolders\EnvironmentShell\Planning\Excel\input
schedules\Templates\Validate.xlt.

Microsoft Office - Validate submission.
(O) LOPTZ_AVAILABLE Use this parameter to determine whether the system is taken offline during a
lite optimization process.
Valid values are:
0 - do not take the system offline
1 - take the system offline
This parameter is used in Administration Client - Lite Optimize.
10/24/2019
(R) ORG_ACCOUNTLIST Use this parameter to specify what account dimension members of the
ownership model represent the legal consolidation method, and the
ownership percentage for the subsidiary company in the ownership-based
hierarchy.
The account dimension members must exist in the ownership type model.
The METHOD member for the consolidation method must be de ned in the
parameter. If you de ne any member other than METHOD, the legal
consolidation fails due to the consolidation business rule referring to a
reserved word.
For the ownership percentage, you can de ne one or one more account
dimension members according to your business needs. At least one member
must be de ned for the ownership percentage.
This parameter is required if the model is an ownership type, and if

performing legal consolidation that refers to the ownership model.
The default value is METHOD,POWN,PCON.
You can enter account dimension members from the ownership type model
separated by a comma (,) delimiter.
This parameter is used in Administration Client - Ownership Manager.
(R) ORG_ACCOUNTOWN Use this parameter to specify the relationship of the parent and subsidiary
companies in the ownership-based hierarchy.
The default value is PGROUP. If the parameter is not de ned, Ownership

Manager does not work.
During processing of the legal consolidation business rule, the rule refers to
the parameter value as well. If the parameter is not de ned, the rule nds the
account dimension member named GROUP or PGROUP during processing.
This parameter is required for ownership type models that are used to
perform legal consolidations.
You can enter account dimension members of ownership type model.
(R) ORG_INTCO Use this parameter to specify a member ID from the INTCO dimension in the
Ownership model.
The default value is I_NONE.
(R) ORG_PARENTPROPERTY Use this parameter to specify the property name of the group dimension for
ownership-based hierarchy statutory models when de ning xed hierarchies.
The value must match the value in the ParentProperty for entities in the
statutory models that support ownership model.
This parameter is required for ownership type models that are used to
perform legal consolidations.
The default value is PARENT_GROUP.
This parameter is used in Administration Client - Ownership Manager,

Business Rules.
10/24/2019
(O) SEND_SGTABLE_COUNT Use this parameter to specify the count of the sgData[Model] table that is
used by the data sending process. It is to be scalable for sending data, and it
processes sending data parallel as the number of the table.
Use this parameter so that the system can split the sgData[Model] table
when it sends large amounts of data.
Valid values are positive integers larger than 0.
After you add or modify this parameter, modify the model in the
Administration Client.
(O) SIGNED_DATA_FORMAT Use this parameter to specify the decimal precision and scale of the
signeddata column of the tables tblFact, tblFac2 and tblFactWB in a
model.
The default value is 25,10 (25 for precision and 10 for scale).
This parameter is used in Administration Client - Add a new model, Modify

model, and Copy a model.
(R) TOPDOWN Use this parameter to de ne how to handle the approval of work status.
Valid values are:
Yes - Top down approval of work status. Work status is approved

regardless of whether subwork status is approved
No - Bottom up approval of work status. Work status can be approved

only if all subwork statuses are approved.
The default value is No.
When you change the value of this parameter, existing work status
information is removed.
This parameter is required if work status setting is enabled in the

Administration Client.
(O) VALIDATE_MBR_LOGIC Use this parameter to specify that the system validates members when
processing logic. The performance of processing logic decreases due to this
validation.
Valid values are:
1 - The system lters records that would otherwise post to a parent

member to a member that no longer exists or a member calculated
dimension formula
0 - The system bypasses this validation
This parameter is used in Script Logic - posting data during running script
logic.
10/24/2019
(O) WORKSTATUSVALIDATE Use this parameter to specify that the system checks the value of a cell for
which a user tries to change the work status. If 0, it passes the validation; if
not, it is rejected.
Valid values are:
Yes - Necessary to check validate
No - Not necessary to check
(O) YTDINPUT Use this parameter to specify whether data is entered in year-to-date (YTD)
format.
Valid values are:
Yes - YTD format
No - Periodic format
This parameter is used in Administration Client - Model process.
(R) if YTDINPUTTIMEHIR Use this parameter to specify the time dimension hierarchy that is used by a
model YTD storage model.
type is
The default value is H1.
YTD input
type
(O) YTD_NECJ_RETRIEVE Use this parameter to specify the query type to improve the performance of
data retrieval when retrieving YTD measures on Periodic models or the
opposite.
This parameter is useful in the following circumstances:
YTD / QTD measures data is retrieved on periodic model or Periodic

/ QTD measures data is retrieved on YTD model.
The retrieval range is huge, but the portion of the data existing cells is
small.
ColKeyRange or RowKeyRange has more than two dimensions.
The retrieval range has no members with a dimension formula.
Valid values are:
1 - To use the NonEmptyCrossJoin query
0 - Not to use the NonEmptyCrossJoin query
This parameter is used in Retrieve data functions EPMRetrieveData,

EPMScaleData, EPMSaveData, and reports.
Activities
To update the value of a parameter, start the Administration Client, select the model, whose parameters you want to update, in the
left navigation pane, and from the Manage Models action pane, select Set Model Parameters. Modify the parameters, as desired,
and then click Update.
10/24/2019
To add a new parameter (you can add any 'optional' parameter if it does not already display), add a new row, enter the parameter
name, then enter the desired value.
Deletion of Book Templates

Use
This function deletes book templates. The deletion has no effect on published books that used the templates.
Features
You can delete book templates.
From the Administration Client, select a model.
From the action pane, select Edit Book and Distribution Templates then delete one or more book templates.
Data Auditing
Use
This function tracks changes to transactional data at the model level, such as when and by whom records were changed within a
model.
Features
Administrators control whether data auditing is active or not. To enable data auditing, ensure an environment is within your
context, then choose Manage Data Audit.
For each model in the environment, you select a category and one or more of the following tasks to audit:
EPM Add-in Input
Data Manager Import
Data Manager Clear
Logic Script Execution
Web Report Input
Journal Input
Business Rule Execution
Ownership
FIM Import
Viewing a summary of data audit settings
When managing data audit settings, you can choose View Audit Settings for All Categories to see a summary of the settings for
the tasks and categories within the model.
10/24/2019
Reporting on data audit information
Once activity is recorded, you can run a report that shows activity based on speci ed criteria (see Reporting on Data Changes).
Purging and archiving data audit logs
When selecting the tasks to audit for a category within a model, you can indicate whether you want to retain the logs of the data
audits inde nitely or for a speci c number of days. You must then run an AuditPurge package in Data Manager. Planning and
Consolidation does not delete the logs; rather, it archives them after the number of days you indicate.
You can also set up Data Manager packages to archive data audit information. For more information, see the SAP
BusinessObjects EPM solutions, add-in for Microsoft Office help.
Enable Schedule
Data auditing can be scheduled per minute(s) or hour(s) and for a certain amount of records. Dividing the load may help
processing time.
Save Data Audit
Data audit can be saved immediately by choosing Save Data Audit.
Journal Validation Rules

Use
You can set up journal validation rules to prevent users from saving invalid journal entries. After you set up journal validation rules,
users who try to submit a journal entry to an invalid member set receive an error, and are not able to save the entry until they enter
valid members.
To de ne journal validation rules, you must do the following tasks:
Enable the model parameter JRN_VALIDATION_FILTER. For more information, see Model Parameters.
De ne a validation property for each dimension you want to use to identify as your driving dimension. For example, if you
want Account as your driving dimension, you can create a new property for it called Validation. For more information, see
Adding properties to dimensions in Model Management.
Assign property values on the members you want the system to validate against. For example, under the property
Validation, you can set up property values called ICRule, and NOIC. The following table shows how a sample member sheet
would look for the Account dimension. There are four account members using the ICRule value and two using NOIC:
ID Description Validation
IICSales Inter-company sales ICRule
IICCost Inter-company cost of sales ICRule
IICAccRec Inter-company Accounts Receivable ICRule
IICAccPay Inter-company Account Payable ICRule
3rd party Third party product NOIC
AccRec Accounts Receivable NOIC
10/24/2019
For each dimension dependency you want to de ne, associate a driven dimension with the driving dimension, that is, the
dimension for which you assigned the validation property. For example, you might want to associate Account with Intco,
and Account with Entity.
You also provide an identi er for the validation property you de ned for the driving dimension. This identi er is the driving
dimension property ID.
Determine which driven dimension members are permitted for associated driving dimension property IDs.
You do this by associating a driven dimension with each driving dimension property ID, and then choose a lter for the
driven dimension. When you match a driven dimension lter with the driving dimension property ID, during validation, the
system looks for a driving dimension member that has the validation property value assigned to it (ICRule, for example),
and the driven dimension associated with it (IntCo, for example).
For example, if you set up <>Non_InterCo with the Intco driven dimension and ICRule property value, and a user tries to
save a journal entry with Account member ICCost, it cannot be posted to IntCo dimension member Non_InterCo.
Activities
Identify which dimensions that you want to de ne as driving dimensions for your model. De ne a validation property for each
driving dimension. For more information about adding properties to dimensions, see Model Management.
In the Administration Client, select the model that you are going to work with and choose De ne Journal Validation Rules from
the Manage Model action pane. To de ne the dimension dependencies, choose Dimension Dependencies. Use the drop down lists
to select the driving dimensions and the driven dimensions, and then enter a Driver Property Value for each driving and driven
property combination. Click Update.
Choose Member Filters. In the Member Filter table, enter the information as de ned in the following table:
Item Description
Driver Property Value Choose a driving dimension property value for which you want to
de ne a rule.
Driven Dimension ID Select a driven dimension to associate with the property value.
Driven Dimension Filtered Values Specify which members of the driven dimension to include (or
exclude). You can use the dropdown list to help de ne the lter.
Select one or more members. You can also select the <> radio
button to prevent users from posting to the member(s) selected.
Click Update to complete your journal validations de nitions.
Journal Translation Rules

Use
You can reopen one or more journal entries from a previous year and post them to another set of accounts for the following year.
Before you can reopen journal transactions, you must de ne translation information for the dimensions used in the reopen tasks.
The translation table de nes the source and destination accounts. You typically do this for speci c accounts, but you can do
translations for other detail dimensions.
Features
10/24/2019
When you open the translation table for the rst time, the system opens an empty table whose columns are derived from the
environment's journal template. You can add values to the table as needed.
The following table describes the contents of the translation table:
Item Description
acctype This must have values of the ACCTYPE property in the Account-type
dimension in the model. You can add additional account types by
adding new rows, but the required account types must remain in the
table.
account_property The property that returns a list of accounts to which the translation
rule is applied.
The default property is Group, but if there is no Group property

de ned in the Account-type dimension, or if you want to use a
different property (other than Group), specify it here.
Enter an asterisk (*) to use the property de ned in the

JRN_REOPEN_PROPERTY environment parameter.
s_ <detail_dimension_ID> Use these columns to enter the name of the detail dimension from
which you are copying the data. By default, an asterisk (*) indicates
that the values are moved from their source accounts to accounts
with the same names. To copy dimension information to a different
dimension, enter the source member ID.
Note: There is no [space] between s_ and the detail dimension ID.
d_ <detail_dimension_ID> Use these columns to enter the name of the detail dimension into
which you are copying the data. By default, an asterisk (*) indicates
that the values are moved from their source accounts to accounts
with the same names. To copy dimension information to a different
dimension, enter the source member ID.
Note: There is no [space] between d_ and the detail dimension ID.
sign Enter one ( 1) to keep the value in the same credit or debit position.
Enter negative one ( -1) to switch the value from the debit to credit,
or credit to debit position.
Activities
From the Administration Client, select the required model in the left navigation pane, and from the Manage Model action pane,
choose De ne Journal Translation Rules.
Use a new row for each additional account type ( AST, LEQ, INC, EXP, and each additional account type that you have created).
When you enter data into the bottom (empty) row of the table, the system adds a New empty row.
For each account or dimension you want to convert, enter the source and destination member IDs under the associated
dimension.
When you have entered all required data, click Update.
When you revisit De ne Journal Translation Rules to update or rede ne your data, you can delete rows by selecting the checkbox
in the Delete column and clicking Update.
Setup of Work Status Dimensions

10/24/2019
Use
Use this function to set up work status dimensions for each model. Setting up the work status dimensions involves identifying
three to ve dimensions that de ne the variables in your business process. These dimensions are known as the work status
dimensions.
Features
Dimension Setup Rules
Use the following rules to de ne the work status dimensions:
Specify a minimum of three and a maximum of ve dimensions from the environment.
The dimensions should be variables in your business process, such as entity, category, and time. These are dimensions
whose members change based on who is submitting data. For example, the time dimension is a typically a work status
dimension, since data is segregated based on time.
Dimensions such as account, data source, reporting currency, and so on, typically remain static, so those are considered
non work status dimensions.
An Account-type dimension cannot be de ned as a work status dimension.
The dimension that contains the Owner property must be de ned as a work status dimension. For more information, see
Owner Property.
Work state settings:
Set to Yes for a work status dimension
Set to Owner for the owner dimension
Set to No for a non work status dimension
De ning Member Validation
Prior to users changing data, you must determine which account you want to use for validation of the data when the work status is
changed. The validation account must be 0 at the intersection of the three to ve environment members, and the members
designated for the non work status dimensions. If the account is not 0, the owner/manager cannot set the work status.
In the Member Validation column, specify a valid member only for each non work status dimension.
Do not set a value in Member Validation for work status dimensions.
Example
Suppose that you set Entity, Category, and Time as the work status dimensions for a given model. You then set your other
context members to the following: Account: Validation, DataSrc: TotalAdj, Intco: All_Intco, and RptCurrency: LC. In addition
to assigning work status dimensions, you also specify which dimension is the owner dimension. The Owner property
determines who can edit a work status setting. The following table shows this setup, where Entity is the owner dimension. All
the selected dimensions have only one hierarchy:
Dimension ID Work Status Dimension Member Validation Value Base Hierarchy Value
Account No Validation
Category Yes 1
10/24/2019
Dimension ID Work Status Dimension Member Validation Value Base Hierarchy Value
Data Source No TotalAdj
Entity Owner 1
Interco No All_InterCo
RptCurrency No LC
Time Yes 1
A user attempts to post data to the context shown in the following table. The system checks the validation account to make
sure the intersection equals zero (0). If so, the data is posted and a success message is displayed. The user can now set the
work state to Submitted on that intersection. Subsequent submissions to that exact intersection are rejected. Users can only
send data to the same intersection if the Entity, Category, or Time member changes.
Account <All>
Category Actual
DataSrc <All>
Entity SalesNE
Intco <All>
RptCurrency <All>
Time Feb.2007
De ning the Base Hierarchy
In the Base Hierarchy column, specify a valid hierarchy number as an integer for each work status dimension. Do not specify a
hierarchy in Base Hierarchy for non work status dimension.
Example
If you set Base Hierarchy to 2 for a dimension has 3 hierarchies, you cannot set work status for members included in hierarchy
1 and 3. You can only set work status for members of hierarchy 2. You should input 1 for Base Hierarchy if the dimension has
only one hierarchy but you can choose dimension hierarchy if dimension has multiple hierarchies. Use caution when you
change work status settings in the Administration Client because work status information is removed when you change Work
State or Base Hierarchy.
Activities
In the Administration Client, expand the Model node and an model, then choose Work Status Settings. Select Owner for the
dimension that contains the owner property (see Owner Property), select Yes for each dimension you want to de ne as a work
status dimension, then select No for each non work status dimension.
Select a member for each non work status dimension in the Member Validation column. (Use the browse button to open the
Member Lookup.) In addition, specify an ID that represents the base hierarchy member for each work status dimension in the
Base Hierarchy column.
See the example above.
More Information
10/24/2019
Work Status Setup
Work Status
Owner Property
Concurrent Locks
Use
You can de ne a concurrent lock setting for each model. Concurrent locks prevent users from sending data to the same data
intersection at the same time.
You de ne a concurrent lock by selecting three or more dimensions. When multiple users try to submit data to the same members
for those dimensions, the data sent rst is accepted. Any data sent concurrently is rejected.
Features
How do you determine which dimensions de ne the concurrent lock? Lets say that you set concurrent locks on Entity, Category,
and Time. Your company has one person that is responsible for the P&L data for an entity, and one who is responsible for the
Balance Sheet data for the same entity. If both users attempt to write to the database at the same time, one is locked out. (Data
submission is based on a rst come rst serve basis.)
In this case, you would want to set your concurrent locks on Entity, Category, Time, and Account. That way, there would be no data
submission con icts between the two individuals.
Activities
To set a concurrent lock:
1. From the Administration Client, expand the Model node.
2. Expand the model for which you want to de ne a concurrent lock setting, then select Concurrent Lock
3. Select Yes for each dimension you want to use to de ne the intersection of data upon which a concurrent lock setting is
applied.
4. Select Con rm Concurrent Lock from the action pane.
Drill-Through Setup
Use
You use this function to set up drill-through de nitions. Drill-through de nitions allow users to access source data from a report.
Source data includes content that can be accessed from a URL, and a database table.
Prerequisites
You must have proper security rights to de ne drill-through de nitions. See the SAP Business Planning and Consolidation Security
Guide available on the SAP Help Portal at http://help.sap.com/bopacms101.
10/24/2019
Features
Setting up Drill-Through to a URL
You set up URL-based drill-through de nitions in a model. After you set up at least one drill-through for a model, it is available to
users of reports that reference that model.
You can map the URL parameters to dimensions or user-de ned values.
When you map a parameter to a dimension, you also choose a dimension property, such as ID or EVDESCRIPTION. When the user
performs a drill-through in a report, the parameter value is taken from the property value of the selected data cell. For example, if
you select the ID property of a dimension, the member IDs are mapped. If you select another property of a dimension, that
property value is mapped. Therefore, you can send either the dimension member or the value of a property.
When you map a parameter to a user-de ned value, you can hard code a value or use %CurrentUser%, or %CurrentDate%. If
you specify a user-de ned value in the mapping, when the user performs a drill-through in a report, the parameter value is based
on the user-speci ed value.
Note
The system supports the variables Current Date and Current User in the mapping. The format of Current Date is
%CURRENTYYYYMMDD%, where YYYYMMDD is replaced by the current year, month, and day. You could then use
%CURRENTYYYY% for sending out only the current year. The format for Current User is %CURRENTUSER%.
The system supports using environment parameters and model parameters in a URL. The format is %parameter%. When an
environment parameter and model parameter have the same name, drill-through uses the model parameter prior to the
environment parameter.
De ning a Drill-Through De nition to a Database Table
A database table drill-through includes data from external databases or the Journals database. You can de ne one drill-through
de nition per dimension. Drill-through is available on any cell that is contained within a report function, as well as cells containing
EPMScaleData, EPMScaleData, and formulas.
Executing a Drill-Through
You can use the EPMExecuteAPI macro MNU_eTOOLS_DRILLTHROUGH_RUN to execute a drill-through using the syntax
MNU_eTOOLS_DRILLTHROUGH_RUN("drillthrough id").
Activities
The activities you perform to set up drill-through depend on whether you are drilling through to a URL or a database value.
To de ne a drill-through for a URL
1. Under the desired model, select Drill Through from the action pane, then select Add Drill Through.
2. Enter a drill-though ID and description.
3. Move to the next window to enter the target URL and mapping information. For example, you can specify
http://www.google.com/search? as the URL. For the parameter, you can enter q, which is a known Google
parameter. Select one or more dimensions and associated properties or user-de ned values.
4. After setting the URL and parameter mapping, click TestRun to enter a value and test the URL you con gured.
5. Move to the Finish step to save the drill-through.
10/24/2019
To de ne a drill-through to a database table
1. In the Administration Client, add a property named DrillKey to the dimension or dimensions for which you want to use
drill-through (see Dimension Properties).
2. Devise a DrillKey value and assign that value to any member of the dimension for which you want to use drill-through
(see Dimension Member Management).
3. If you are using an external database, create a database query in Interface for Excel by doing one of the following:
For Microsoft Office 2003, choose Data Import External Data New Database Query .
a. On the Databases tab, choose New Data Source and give it a name that has some relevance to the database
you are querying.
b. Choose the appropriate driver for the type of database to which you are connecting.
For Microsoft Office 2007, choose Data From Data Source .
a. Select the database type for the connection and give it a name that has some relevance to the database you
are querying.
b. When nished, you see the connection and query information.
i. Choose Data Connection , then choose the connection name.
ii. Choose Properties, then select the De nition tab.
4. After entering the required data, name your query, then save it to <Planning and
Consolidation>/Webfolders/[Environment]/[model]\queryfiles.
The DQY le must have at least four sentences as follows:
The rst sentence is XLODBC.
The second sentence is 1.
The third sentence is the connection string:
For SQLOLEDB:
Provider=SQLOLEDB.1;User ID=%USERID%;Password=%PASSWORD%;Persist
Security Info=True;Initial Catalog=AppServer;Data Source= <Server
Name>
For ODBC:
Provider=MSDASQL.1;User ID=%USERID%;Password=%PASSWORD%;Persist
Security Info=True;Data Source=BPC_ManagementDSN;Initial
Catalog=AppServer
The fourth sentence is the query for getting data, which can be the general SQL query, a stored procedure,
and so on.
While de ning your query, you can set the query lter to vary based on the context of a dimension. You do this
within the Query Wizard when setting lter data. To base the dimension on the context, you can use the syntax
%DimName%, where DimName is the dimension name you are referencing, such as %Entity%.
5. Set up the drill-through and connect it to an environment by editing the following elds in the drill-through table using the
Manage Drill Throughs task on the Administration Client. See Edit Drill-Through Table.
DrillKey
10/24/2019
The value speci ed in the DrillKey property column for the dimension member on which you would like to drill
through.
Title
The title appears at the top of the Drill-Through page.
FileName
The name of your query le. For journals, a Journal query le is automatically built for you. For all other external
databases, you must create a query le.
MaxRows
The maximum number of rows to display on one page.
UserID and Password
A valid user ID and password on the database to which you are querying.
Example
Example 1
This example describes a scenario of drilling through to a database value.
You have a report that has a row de ned for TotalUnitsSold and you want to see this number broken out by customer. As long
as you know where that data resides, you can de ne a drill-through to retrieve it. In the same report, if you have Sales Commission
data in a row, you can de ne a drill-through to show the Journal entries that contributed to the nal numbers for the Commission
member.
Example 2
This example describes a scenario of drilling through to a URL.
You want to search the member of Category in a Web site called MySite. You can de ne a drill-through, setting the URL as
www.MySite.com. The parameter for MySite is q so in the URL Parameters column, you enter q. In the Mapping source column,
select the Category dimension.
In the report, users can execute this drill-through to see the search results.
Example 3
This example describes another scenario of drilling through to a URL.
When SAP BusinessObjects Financial Information Management (FIM) is used to load data into Planning and Consolidation from
external data sources ( at les, tables, 3rd party applications, or other EPM applications), this data is often transformed and
aggregated. Planning and Consolidation only stores the nal data, and users may want to drill-through into the details of the data
that is stored in a FIM repository (staging area). The URL-based drill-through makes this possible.
When de ning the drill-through, the URL is set to the <FIM Application>. URL Parameters are dimensions in the Planning and
Consolidation model that pass the context (for example, time, account, etc.), of the data being queried. All data associated with
the context is returned and displayed in the FIM drill-through report.
YTD Storage Models

10/24/2019
Use
Since most general ledger and other source systems store balances on a periodic basis, default data storage for models is based
on periodic time intervals. With this method, all calculations are on periodic balances. The balances are then accumulated for
year-to-date (YTD) reporting. In some business cases, calculations should occur on a year-to-date basis, like in a model with
foreign currency translation.
Features
If a year-to-date basis is required, you can set your models to store data on a YTD basis, so they accept data entry in the YTD
format. When data is entered into YTD, its periodic values, used for reporting purposes, are derived by calculating the difference
between the current period and the last period, as in the following example.
Example
This example depicts INC or EXP accounts. There is no change in behavior for AST or LEQ accounts.
January February March
Periodic 100 200 0
YTD 100 300 300
Both year-to-date and periodic storage methods support daily, weekly, monthly, quarterly and year-to-date reporting
requirements.
Activities
Create a YTD storage model in the Set Model Parameters screen. Set the YTDINPUT parameter to 1. If you need to add the
YTDINPUT parameter, enter YTDINPUT in the New eld at the bottom of the table. See Model Parameters.
Business Process Flow Management

Use
This function enables you to create and manage business process ow (BPF) templates (or, “process” templates) and manage the
processes created by users. You can manage business process ows if you have the Manage Processes task pro le.
A process template is the speci cation of a single enterprise-wide business process, containing tasks that can span across the
various modules of Planning and Consolidation. It provides the overall rules that govern the process, including sequential steps the
process must follow, links to the activities the users perform, the process context and timing in which the process takes place, and
the participants and their roles in the process. For an additional level of control over the work ow, administrators can integrate
work status rules.
A process is an iteration of the enterprise-wide business process. It allows the user to see only those tasks relevant for that user,
given his or her role and data access privileges. Business users create new process in the Web Client using their unique process
context within the scope of the business process ow.
Example
A process template describes a monthly activity, such as line managers entering monthly actual budget data. Each manager
creates a process and enters actual data for a particular department. In this example, the process context has the same time
10/24/2019
and category, but a different entity. Therefore, the process context, which is the varying entity, serves as the key for identifying
and tracking the process. It allows the process to run simultaneously across various operational units.
Features
An administrator manages business process ows from the Administration Client. The following functions are available:
Ability to create new process templates
See Creating New Process Templates.
Ability to maintain process templates
After a process template has been created, administrators can copy, modify, or delete it. See Process Template
Maintenance.
Ability to manage processes
After a process template has been created, business users can use it to create processes. After process have been created,
administrators can reset, archive, or delete them. See Managing Processes.
Creating New Process Templates

Use
Use this process to create a new process template.
Prerequisites
You have the appropriate task security rights.
You have de ned a Reviewer property in the driving dimension (as described in Setting Up Process Templates), and de ned
appropriate values for it. For more information, see Reviewer Property.
Process
1. From the Administration Client, select Processes from the navigation pane.
2. Select Add a New Process Template from the action pane.
3. From the Setup Process Template window, begin providing basic information about it. See Setting Up Process Templates.
Note
Make sure all setup steps have been completed (A -D) before moving on to Step 2: De ne Steps and Substeps.
4. From the De ne Steps and Substeps window, add steps and substeps to represent the general ow of the process. See
De ning Steps and Substeps.
5. From the De ne Actions window, add actions to de ne the speci c tasks users perform within the steps of the process.
See De ning Actions.
6. From the Finish window, review the information and parameters you provided, then enable the business process ow for
general use. See Finishing and Releasing.
10/24/2019
Setting Up Process Templates

Use
You set up a process template by providing basic information about the business process ow.
The modify process uses the same features described here.
Features
The following tables describe the information you need to complete the setup process.
Setup > A. De ne Process Template
Item Description
Name The name of the process template.
Description A description for the process template.
The description is displayed in the Processes screen when a user

selects a process. Provide enough information in the description to
help users to identify processes correctly.
Controlling model The model that contains the dimensions that are required to de ne
the context, and the Time dimension you want to use for the
processes.
If you select, for example, the Planning model, whose Time

dimension is in monthly increments, the process works in monthly
time increments, as well.
Process template owner The person the system noti es when a user raises an issue about
the process.
The user must have a valid e-mail address. For information about
assigning e-mail addresses to users, see the Planning and
Consolidation Security Guide.
Setup > B. De ne Process Context
Item Description
10/24/2019
Item Description
Driving Dimension The dimension that is common to all process contexts that users
might use in completing the tasks in the process. Every process
needs one driving dimension. This dimension “drives” the execution
of the process. It is mainly used for steps which require reviews. For
these steps, the reviewer is the one assigned to the driving
dimension for the current member of the driving dimension.
Therefore, a driving dimension must have a de ned Reviewer
property.
A common example of a driving dimension is Entity, which has the

following effects:
When this process is executed, users select which member

of the entity dimension they are executing. The reviewer for
each step, requiring a review in this process, is the one
assigned in the reviewer property of the driving dimension
(entity).
This dimension drives the process. The process is different,

depending on this dimension and the associated reviewer,
and requests participation from different users.
Identity Dimension One or more dimensions common to all processes for this template.
The system automatically selects the Time dimension, since it is

required for all processes.
Identity dimensions also identify a process. For example, you create

a process for a speci c period of time. You can execute the process
for each member of the Time dimension.
An identity dimension has no impact on the process once it is

started. It is used to identify the process but does not drive it.
Setup > C. De ne Timing
Item Description
Activation Date and Start Time The date and time the process template becomes active.
Enable Noti cation and number of days Enable Noti cation enables e-mail noti cations. If it is enabled, the
number of days before or after the activation date of the process to
notify the users who are assigned to the template by e-mail.
Setup > D. Set Access
Item Description
Set Access Choose the users and teams to which the process template applies.
Only the people you select in this step see the process template.
Activities
To set up the process template, select Processes from the navigation pane of the Administration Client, then select Add a New
Process Template from the action pane. You can also modify an existing process template by choosing a process in the navigation
pane, then selecting Modify Process Template from the action pane.
10/24/2019
Make sure that you enter data in each setup step (A, B, C, and D) before choosing Next.
Recommendation
It is not necessary to save your data after each step of the procedure. However, this is good practice.
Save your data, then click Next to continue with de ning steps and substeps within the process template. See De ning Steps and
Substeps.
De ning Steps and Substeps

Use
Steps are the general business actions you take when completing a process. Each process must contain at least one step. You can
create substeps to de ne one or more actions under a single step.
Features
Guidelines for De ning Steps and Substeps
The following are guidelines for de ning steps and substeps:
Steps can have substeps, however substeps are not required. If a step has no substeps, you must associate at least one
action with the step. If a step has one or more substeps, you must associate at least one action with each substep, but not
with the step itself.
All steps and substeps can have more than one associated action; if so, the primary action is the Target (launch) action,
and once launched, Related (additional) actions become available in the action pane. For example, the primary action could
be to launch a Web report, and the additional actions could be to add and manipulate data.
Users do not need to perform substeps in sequential order, nor are all substeps required to complete the step.
Steps have criteria de ned that control the process context. They can also have opening and closing criteria, if required.
For example, opening criteria may be applied to a required sequential step before a user can progress in the process. In
addition, steps may require approval (completion criteria) by a reviewer before the system considers the step complete.
Substeps are not subject to approval criteria.
Up to one thousand steps per process template can be de ned.
Adding Steps and Substeps
You add steps and substeps by providing the following information:
Item Description
Name and Instruction Enter the name of the step or substep and the text that displays in
the action pane that describes it.
10/24/2019
Item Description
Allow Reopen Select this option to allow users who have the appropriate
permissions (the Reopen Process Steps task pro le) to reopen
closed or completed steps.
The general rules for reopening a step are the following:
Only the previous step can be reopened, but the steps can
be reopened one by one in sequence. This means that the
last step of a process cannot be reopened after it has been
completed.
Users cannot reopen a step directly if the step has the

Enable Reviewers option set. They can, however, ask the
reviewer to reopen the step for them.
A designated reviewer does not need to have the Reopen

Process Steps task pro le to reopen a step.
Enable Completion Criteria Select this option to enable completion criteria. You can enable
completion criteria only if work status has been enabled in the
controlling model of the process. See Work Status Setup.
If completion criteria is de ned, the selected combinations of

members must be set to the speci ed work status before the step
can be considered complete.
Enable Reviewers Select this option to require a designated reviewer to approve this
step before the process continues to the next step. Reviewers are
de ned in the Reviewer property of the driving dimension.
To de ne an action that a reviewer must perform when reviewing the

step, choose Set/Modify Custom Review Actions. See De ning
Actions.
Send E-mail to Reviewers upon Completion Select this option to send an e-mail message to designated
reviewers informing them that the step has been completed.
To de ne the contents of the message, choose De ne E-mail

Message. Enter your required message or modify the default
message in the popup window.
%BPF_STEP_NAME% is a variable that is converted to the step

name.
%BPF_NAME is a variable that is converted to the BPF template

name.
Note
Do not modify these variables if you want to see the completed
step.
Activities
To de ne a step, from De ne Steps/Sub-Steps, click Add, and choose Add a New Process Step. De ne the properties for each
step, as desired. Reorder the steps, add substeps, and de ne actions for each step.
To de ne a substep, from De ne Steps/Sub-Steps, choose an existing step, click Add then choose Add a New Substep. De ne
the properties for each substep, as desired. Reorder the substeps, and de ne actions for each substep.
10/24/2019
When you have completed de ning your steps and substeps, save your data, then click Next to continue with de ning actions for
the steps and substeps. See De ning Actions.
More Information
Reviewer Property
De ning Actions
Use
You de ne actions in the process template to specify the speci c tasks a user performs when working on a process. An action can
be any user-authorized task, for example, opening an input form or publishing a report.
You can assign actions to steps that do not have substeps, substeps themselves, and reviewer actions to steps when a review is
requested. The reviewer must complete the reviewer actions before approving a step.
Procedure
1. From De ne Actions, choose a step or substep.
2. The name of the step or substep appears as the default action name.
Add additional names or modify the name to be displayed, if desired. The rst action in the list is the one that displays
when the user selects the action (target action).
Related (additional) actions are ltered by what the target (launch) action is. For example, if you select Open Input Form
Library of Microsoft Excel, you can select several Microsoft Excel actions only.
3. Choose an interface and task with the action, entering valid parameters for the speci ed interface or task.
4. Choose a model and specify the source of the values for each dimension.
5. Save the action, then de ne actions for additional steps and substeps, as required.
6. Click Next to nish the process template by reviewing the process and enabling it for use. See Finishing and Releasing.
Note
Since the process context takes precedence over any dimension locks in a workbook, we recommend that process actions do
not reference workbooks that have locked dimensions. This prevents confusion about which dimension and member
combination is being used.
Another reason for this is that the process context applies only on the active sheet. If the person performing the action opens
another sheet in the same workbook, the process context is not transferred, and any dimensions locked in the worksheet
apply. Therefore, if you want to apply a process context to nonactivated sheets (that is, not the initially opened sheet), do not
reference a workbook with locked dimensions.
If you want to use the same context across the workbook (and not the process context), you can use the 'Override context
settings' option in the Workbook Options dialog box. The workbook context settings impact the entire workbook's context, but
do not prevent users from manually changing their context.
Any locked dimensions not speci ed in the process context are still locked in the opened worksheet. For example, if the
process context uses Entity, Category, and Time, and the Entity and Category dimensions are locked in the workbook, the
Entity and Category members are taken from the process, and the Time member is taken from the worksheet.
10/24/2019
Finishing and Releasing

Context
In this nal screen, you can review the new (or modi ed) process template, and release the process, or hold it for use at a later
date.
Once you have released the process template, users can create processes to use.
Procedure
1. From Finish, review the information.
2. Select Enable this process template for users to make the process template available to users, or do not select it to
reserve it for future use.
3. Save the process template, then close the window.
Results
The new or modi ed process template is displayed under the Processes node in the navigation pane.
Process Template Maintenance

Use
Once you have created a process template, there are a number of maintenance actions available to you. These are:
Copying a process template
Modifying a process template
Deleting a process template
Features
These actions become available in the action pane of the Administration Client when you expand Processes and select a process
template.
Copying a Process Template
You copy an existing process template to create a new one that is similar to the original. Copying a process template, and then
modifying it, as needed, can be more efficient than completing all of the steps required for creating an entirely new process
template.
From the action pane, select the process template that you want to copy, then choose Save as Process Template. Enter a new
name and description for the process template, and select Save as New Template.
Once you have made copy of the process template, you can modify the copy, as required.
Modifying a Process Template
10/24/2019
You can modify a process template to open the Modify Process Template window with all the elds completed with the values
from the selected process template.
From the action pane, select the process template that you want to modify, then choose Modify Process Template. Work through
the steps in the same way as creating a new process template, modifying the values, as appropriate. See Creating New Process
Templates. When you save a template using Modify Process Template, all previous process interfaces are removed.
Deleting a Process Template
You can delete a process template to remove it from the environment entirely. Deleting a process template does not delete any of
the processes created from the template.
From the action pane, select the process template that you want to delete, choose Delete a Process Template, con rm that you
are deleting the correct template, then click Yes.
Managing Processes
Use
A process is de ned by the template and the process context in which it is used.
Prerequisites
A business user has created at least one process from the process template.
Features
Within managing processes, you can perform the following tasks:
Reset a process
You can reset a process back to step 1. The system resets the steps and statuses within a process so the users must
perform the steps again. It does not, however, reset changes made to the data.
Delete a process
Deleting a process has no effect on the process template.
Activities
From the Administration Client, expand Processes and select a process template to manage. Select Manage Processes, select
one of the options, then click Go to Next Step.
An administrator can reset or remove a single process, a set of process, or all processes based on the selected template. The
difference between reset and remove is that, once a process has been removed, it no longer appears on the business process ow
reports.
If you want to reset or remove a set of processes, use the Category, Dimension, and Time elds to select the set of processes. For
example, to reset all 2010.Q1 data regardless of Category, you can set Time = 2010.Q1 and Category = [ALL].
Work Status Setup

10/24/2019
Use
This function allows you to lock a region (or slice) of data in a model. The work status setting overrides a user's member access
privileges to write to a given region. A region of data is de ned by three to ve dimensions per model, one with a property called
Owner.
When you set up work status, you de ne the following:
Work States - The codes that refer to a physical state of data (such as Submitted)
Level of security - The teams or users who can change data in the system, which is All, Locked (no one), Manager, or
Owner. See Controlling Who Can Change Data, below.
The users or teams who can change the work state, which is Owner, Manager, or Both. See Controlling Who Can Set Work
Status, below.
Method of data update - The manner in which the customer updates data. See Method of Update, below.
Push - Equivalent to the check box Include all children when setting work states, the option allows you to set one work
status code to all children of a member.
After you set up work states, users can use them to apply a label to a context and lock its data for review, approval, and so on. For
example, your month-end close business process requires that a speci c set of data is locked down so that accurate month-end
reports can be created. After a data submission, the owner sets the work state to Submitted. This locks the data intersection from
subsequent submissions.
Prerequisites
To use this function, you must specify in the Base Hierarchy column of the work status dimensions the hierarchy (H1, H2, H3, ...,
Hn) that uses work status rules. See Setup of Work Status Dimensions.
To implement e-mail noti cation of work status changes, the environment parameters APPROVALSTATUSMAIL,
APPROVALSTATUSMSG, SMTPAUTH, SMTPPASSWORD, SMTPPORT, SMTPSERVER, and SMTPUSER must be set up. For more
information about these environment parameters, see Environment Parameters.
Features
Controlling Who Can Change Data
You de ne who can change the data in the system:
All - All users with the appropriate member access rights can change data
Locked - No one can change the data
Manager - Only managers (parents of owners) can change data
Owner - Only owners can change data
Controlling Who Can Set Work Status
You de ne who can set the set the work state for a region of data:
Both - The owner of the speci c member ID and the owner of the parent to the speci c member ID
Owner - The owner of the speci c member ID
Manager - The owner of the parent to the speci c member ID

10/24/2019
Owner or Manager Determination
Parent member owners act as an owner for that speci c parent member ID
Parent member owners act as a manager for their direct children - the parent owner can change any speci c direct child
work state; can be both parent and base members
When using Include all children - the owner of a parent can update all children (all levels) below
Base (leaf) members owners act as owner only
Members (top of a hierarchy) that have no parent but have children act as their own manager in addition to owner
Controlled By Rule
An owner is de ned by only one dimension hierarchy, the OWNER dimension
A work state can be set on a speci c single member ID, where the manager does not use Include All Children
A work state can be set on a series of member IDs, where the manager uses Include All Children
Setting the Work State
If the user is acting as an owner, they can select a work status controlled by Owner or Both
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 Both
If the user is the parent owner in the role of Manager, then they can use the Include All Children option (to push the work
state to children). This option is not valid for a base member, the Owner role.
Consecutive Work State Rules
You can set work status in a forward direction (progressive) or in a backward direction (regressive)
For a user acting as an Owner, the order matters
The user can only select the next (forward) work state that is controlled by either Owner or Both
The user can select the previous (backward) work state that is controlled by either Owner or Both
The user cannot select a work state that skips a work state 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 state that is controlled by either Manager or Both, either forward or backward
The user can select a work state that skips a work state controlled by Owner, either forward or backward
If you expand all records on the non-OWNER dimensions only, and nd the current work state 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 state cannot be higher than its children (order matters)
The order of work states is determined top to bottom in the work status code screen. The rst code is 0, the next
code is 1, and so on.
A child can have a work state that is greater than or equal to its parent
For a user acting as owner:
10/24/2019
If a child is set to Submit, it parent cannot be set to Approve.
If one or more children have a work state that is lower than the work state being set for a parent (forward), then an
error appears
If the parent's work state has a higher work state, an error appears if you attempt to regress a child's work state
(backward)
The rules above also apply when the user is acting as a Manager (where Include All Children is selected or the Manager
sets a speci c child work state)
For all expanded records (non-OWNER dimensions), the immediate parent is checked to verify that it has a work state that
is less than or equal to its children. If one child fails this rule, all fail.
Method of Update
The areas of Planning and Consolidation for which you can control the level of security are as follows:
Data Manager ( DM) - Controls data input from running a Copy, Import, or Move package
Journals ( JRN) - Controls data input from posting journal entries
Web Client( MAN) - Controls data submissions from Web reports
SAP BusinessObjects EPM Solutions, add-in for Microsoft Office ( MAN) - Controls data submissions from reports and
input forms
Comments ( COM) - Controls data input from posting comments (unstructured data)
Documents ( DOCS) - Controls posting documents with model context to the Documents view (unstructured data)
De ning Work States
Work states (or work state "codes") are de ned for the entire environment (not per model). There is no limit to the number of
codes you can create, but there is a practical limit.
The default code allows you to have a customized behavior for the environment. For example:
LOCKED for all methods is equivalent to preventing any data update until the work status is advanced to the next state (1)
ALL for all methods is equivalent to having all data open for update - this is the current and default behavior
SETUP applies to ALL of the models in the environment
WRITEBACK always checks for locks; if there are no locks in the lock table, the system behaves based on the setup of state
(0)
Work state codes must be 20 characters or less, and their descriptions are limited to 40 characters (this is the same as a member
ID).
You can change the order of work status, but once you change it, the system deletes all locks for all models in the environment.
Deleting codes also deletes all locks. Adding codes to the bottom of the list, changing a code de nition, does not impact existing
locks, but may impact business users. We recommend this only during the testing phase.
For information about how to set up work status dimensions, see Setup of Work Status Dimensions.
Work Status Rules
The following rules describe work status behavior:
10/24/2019
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 state a parent can be set to is the lowest state of its immediate children.
If the status of a parent is set to Locked, you cannot unlock the children.
The minimum state a child can be set to is the state of its immediate parent. For example, if the parent state is Submitted,
the child state must be at least Submitted.
The owner of an entity can set the work state to any state designated as an Owner state.
The manager of an entity can set the work state to any state designated as a Manager state.
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
(speci cally, 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 2009.Q1.
Entity Category Time Work State
Child1 Actual 2009.Jan Upload
Child2 Actual 2009.Jan Upload
Child1 Actual 2009.Feb Upload
Child2 Actual 2009.Feb Upload
Child1 Actual 2009.Mar Upload
Child2 Actual 2009.Mar Upload
If you reorder work state codes in the Administration Client, all locks are deleted. This also applies deleting a work state.
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 2009.Q1.
Entity Category Time Work State
P1 Actual 2009.Jan Upload
P1 Actual 2009.Feb Upload
P1 Actual 2009.Mar Upload
When applying rules, if the model encounters any error, it rejects the entire user request. In this case, no records are
updated.
Sending E-mails to the Owners and Managers
The system can send an e-mail message to owners and managers of a context intersection for which a work status and ownership
dimension have been set up to notify them when a change occurs in the work status.
Work Status Validation
10/24/2019
To use work status validation, you must set up a validation account in the Administration Client. See the WORKSTATUSVALIDATE
model parameter in Model Parameters and Setup of Work Status Dimensions.
Using Business Rules with Work Status Settings
The system checks the work status setting before running the following business rules:
Account-based calculations (SpRunCalcAccount)
Currency Conversion (SpRunConversion, SpRunConversion_Light)
Intercompany Booking (SpICData, SpICBooking)
Elimination and Adjustment (SpRunConso)
Carry-forward (SpCopyOpening)
US Elimination (SpRunElim)
Validation rules (SpRunValid)
Summary (SpCopyCategory)
Deleting Work States
You can delete a work status that is not currently in use by accessing Work Status Tasks and choosing Delete a Work State.
Activities
You create work states to re ect the status of data as it moves through your business processes, such as unlocked, submitted,
and approved. No prede ned work states exist within Planning and Consolidation. From the Administration Client, chose Work
Status Add a new work state .
You can modify the order in which work states display in the system by choosing Work Status within the Administration Client,
then in the Work Status Tasks action pane choosing Reorder work states.
To set up the system to send an e-mail message to owners and managers when a work status changes, set the environment
parameter APPROVALSTATUSMAIL to Yes. To customize the content of the e-mail, modify the environment parameter
APPROVALSTATUSMSG. For detailed information about these environment parameters, see the prerequisites detailed above and
Environment Parameters.
More Information
Setup of Work Status Dimensions
Model Parameters
Work Status Example
Work Status Example

Use
10/24/2019
The following setup is used for the examples.
Work Status Codes
Default code is set to Both
All methods are open, that is, set to All
Work State DM JRN MAN COMM DOCS ControlledBy
Locks Not Set All All All All All Both
Started All All All All All Owner
Upload All Locked Locked Locked Locked Mgr
Submit Locked Owner All All All Owner
Journal Locked Locked Locked All All Owner
Approve Locked Locked Locked Locked Locked Mgr
Model Work Status Dimensions
Entity is used as the owner dimension
Dimensions with Yes are non-owner dimensions
Remaining dimensions are not considered when de ning the region or scope of the lock
Code Model Dimension Name Work State
CATEGORY Yes
ENTITY Owner
P_ACCT No
P_ACTIVITY No
P_DATASRC Yes
RPTCURRENCY No
TIME Yes
Entities Structure
Owner of Top entity L1 is the tester's internal user ID (I#)
Remaining parents and children have test owners to help demonstrate the example
ID CURRENCY EVDESCRIPTION OWNER PARENTH1
L1 EU Top SAP_ALL\I815086
LD1 US Parent 10 DEVWDF46\TESTUSERC L1
L9000 US Parent 19 DEVWDF46\TESTUSERD LD1
L9100 US Child 191 DEVWDF46\TESTUSERE L9000
10/24/2019
LD2 US Parent 20 DEVWDF46\TESTUSERF L1
L8000 US Parent 28 DEVWDF46\TESTUSERG LD2
L8100 US Child 281 DEVWDF46\TESTUSERF L8000
L7000 US Child 201 DEVWDF46\TESTUSERF LD2
Examples
To begin, a user enters data into the model.
This example uses data for children of entity member L1
There are no locks set, so data can be entered freely
Lock is set by owner
1. Owner TestUserE can set their own entity L9100, and set a parent level non-owner dimension member 2008.Q1
2. However, the owner cannot view the current status of the entity L9100 and 2008.Q1 since the state is expanded to the
child members for non-owner dimensions (no storage of parent members for non-owner dimension)
3. The owner can view the individual state by the base member 2008.JAN
An owner must set Controlledby work states in consecutive order. Upload can be set to Submit, but not to Journal, as the next
work state after Upload is Submit.
This is also true in reverse: an owner cannot set a Controlledby owner work state that is not in order. You cannot set Journal to
Started as this violates two rules:
The state before Journal is Submit. Therefore, this is the only valid selection possible
Upload is a Controlledby Mgr work state, and is in between the Submit and Started work states. The owner cannot skip a
Mgr work state.
Lock is set by manager 1
As the rst status is an Controlledby Owner status, which is de ned as open ( Locks Not Set), the next step is to have the
manager progress to a locking status of Upload.
1. Sign on as TestUserD, the manager of L9100 (owner of L9000)
2. Do not choose Include children in the data region. As a manager, you can update the status for individual members as
long as the status is set to Controlledby Mgr
3. You cannot update the data after the lock is set, as this status locks out manual data entry
Lock is set by manager 2
1. Sign on as TestUserC, the manager of LD1 (owner of L9000)
2. Attempt to set Controlledby Mgr work state for a speci c child of L9000 (for example, L9100)
Only an immediate parent can set individual children. An error appears: User is not an owner/manager,
work status cannot be updated.
If you choose Include all children in data region, you can set all children (multi-level setting)
10/24/2019
Controlled By Rule
1. Parent L9000 is set to Locks Not Set
2. If the parent owner attempts to set the work state to Approve, this violates the Controlledby rule as Approve is a Mgr work
state. An error appears: The Controlledby rule is violated.
Note
The owner of a parent is not its own manager (the only exception to this is the top member of the hierarchy).
Bottom Up Rule
Parent L9000 is set to Locks Not Set
Child L9100 is set to Upload; other children are set to None
1. The owner of parent L9000 attempts to set to the work state to Started, which is Controlledby Owner
2. This fails due to violation of the bottom up rule: a parent cannot have a status higher than its children. An error appears:
The Bottom-up rule is violated
Pushing 1
L9000, a parent owner (manager), can set the work state of all of its children using Include children in the data region
1. A manager can skip work states, but they must be Controlledby Mgr
2. If a manager selects a work state that is Controlledby Owner, this violates the Controlledby rule.
3. If the user setting the work state is neither the owner nor the manager of either the speci c member or children of the
speci ed member, an error appears: User is not an owner/manager, work status cannot be updated.
Pushing 2
L9000, a parent owner (manager) can set the work state of all its children using Include children in the data region
The parent member work state is not set when Include children in the data region is chosen
Only the parent of L9000 ( LD1) can set a Controlledby Mgr work state
Reversing
Assume all children of LD1 are approved for 2008.Q1 (JAN, FEB, MAR)
1. The owner of a child member cannot set a work state lower than their parent. This violates the Bottom-up rule.
2. A parent can reverse the status to any of the Controlledby Mgr work states
All Regions Must Pass Rule
Assume all children of LD1 are set to Approve for 2008.Q1 (JAN, FEB, MAR)
1. The parent sets all base members for Jan to Locks Not Set
2. The parent sets remaining months to Approve
3. The owner of one dimension attempts to set Q1 to Started. This fails because it violates the Bottom-up rule for two months
(February and March)
10/24/2019
Rules
Use
In Business Planning and Consolidation, you can perform calculations on your data using the following methods:
Business rules, which are parameter-driven functions in BusinessObjects Planning and Consolidation models for
calculating and posting monetary amounts in support of common accounting activities. See Business Rules Management.
Logic, with which you de ne formulas that perform calculations on BusinessObjects Planning and Consolidation dimension
members and data. See Logic.
Setting up currency translations, intercompany eliminations, copy opening tasks, and other business rules using the
business rules tables and script logic in Business Planning and Consolidation Administration, and setting up Data Manager
packages. See Legal Consolidation.
Import and Export of Security Data

You can use security export and import to conveniently move large amounts of security data involving users, teams, task pro les,
and data access pro les.
Features:
Import and export of data by a tab-delimited text le. In some cases, such as with team, a single column can contain
multiple values. You can use a comma to separate multiple values.
Export of all security information of a selected server
Supports data validation
Provides several options for end user convenience
Within Planning and Consolidation, you can nd Import/Export Users in the action pane below Security in the Admin Client menu.
Once you choose the menu, a new window displays.
First, choose Import or Export.
When exporting, you select which objects – users, teams, task pro les, data access pro les – to export to a le.
When importing, you select a le to import. The le should be in your computer’s le system. Also, you have the following options:
Create the team and pro le if one does not exist. If your le contains a team or pro le (task, data access), importing
creates that team or pro le automatically. If you do not select this option, the record is not inserted.
Append versus Clear and Insert – If you choose Append, records in the import le are inserted after existing records. If you
choose Clear and Insert, all existing records are removed before new records are inserted.

Application Help BPC MS

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Application Help BPC MS

Transféré par

Droits d'auteur :

Formats disponibles

10/24/2019

Application Help for SAP Business

For more information, please visit the SAP Help Portal.

SAP Business Planning and Consolidation

Release 10.1 SP08

Changes in this application help: February 28, 2018

Updated the product name “BusinessObjects Planning and

October 12, 2017

Updated the topic Setting Task Sequences.

In Model Parameters, added the parameter

In Environment Parameters, added the paramters

In Journal Queries, mentioned the advanced query

In Journals, added that you can select Copy whole group

In Journal Entry Form, added Display to the list of available

In Home Page and Navigation, added a reference to the

Modi ed the topic Administration to include the subtopics

To log on directly to a speci c environment, enter http://PC_server:port/sap/bpc/web/environment ID.

Business Process Flows

Starting the Administration Client

Use the Connection Wizard in the following scenarios:

Server name or IP address

Whether or not your system uses a default or secure port

Your ID and password

Domain name, if your system requires it

Name of the environment you want to log on to or set as your default

Task More Information

Model processing status

Current model optimization status

Dimension processing status

Additional Tasks Additional tasks include the following:

Set Environment Parameters (see Environment Parameters)

Manage Document Types (see Managing Document Types and Subtypes)

Manage Document Subtypes (see Managing Document Types and Subtypes)

Manage Activity Audit (see Activity Auditing)

Manage Logging (see Log and Trace File Management)

Edit Drill-through Table (see Edit Drill-Through Table)

Context Defaults (see Setting Context Defaults)

Copies the environment WebFolders/data within File Service

Copies security and metadata

Copies the environment database

1. Choose Add a new environment in the Manage Environment action pane.

EnvironmentShell Sample Environment

A set of dynamic report and input form templates

Data Manager packages

Blank Library and Document views

Required environment and model parameters

Dimensions in the EnvironmentShell sample environment

Dimensions for planning and consolidation models:

Type ID Dimension ID Dimension Planning Consolidation Rates Ownership

D DATASOURCE Data Source X X

Type ID Dimension ID Dimension Planning Consolidation Rates Ownership

Dimension of speci c to Planning:

Type ID Dimension ID Dimension Planning Consolidation Rates Ownership

Dimensions speci c to the Rates model:

Type ID Dimension ID Dimension Planning Consolidation Rates Ownership

A R_ACCOUNT Rate Account X

E R_ENTITY Rate Entity X

R INPUTCURRENCY Input Currency X

Dimension speci c to the Ownership model:

Type ID Dimension ID Dimension Planning Consolidation Rates Ownership

A O_ACCOUNT Ownership Account X

Users have Use System When Oﬄine task security:

The following table describes the parameters you can set: