BPC System Parameters

Business Planning and Consolidation
System Parameters
Document Information
Project ID BPC 5.1 / 7.0M
Version 4.23
Status Released
Last Revision Date 5/27/11
File Name BPC_System_Parameters.pdf
Author Soon Kim
Created Date 1/16/2008
© Copyright 2009 SAP AG. All rights reserved. Page 1

System Parameters
Business Planning and Consolidation 5.1 / 7.0,
version for Microsoft platform
History
Version Date Status (Comments)
1.0 1/16/08 Create first Draft
2.0 12/19/08 Internal revision
3.0 12/24/08 Update newly added parameters for 70MSP3
4.0 3/13/2009 Editorial modifications
4.1 3/16/2009 Added LimitOfCommit application set
parameter; minor modifications to
USE_VARCHAR_FOR_DIM and
RETRIEVE_ON_OFFLINE
4.1.1 3/18/2009 Corrected the valid values in 4.1.2.4 for
DO_COMPRESS_CLIENT
4.1.2 3/20/2009 Corrected ORG_ACCOUNTOWN application
parameter
4.1.3 3/24/2009 Removed ALLOWEXTENSIONS appset
parameter; modified some descriptions
4.2 4/20/2009 Applied 7.0 M SP04 changes
4.21 4/22/2009 Minor typographical edit
4.22 12/22/2009 Updated information for JRN_MAXCOUNT
and LOCKREPORT parameters.
4.23 5/27/2011 Added COMPANY_FILE,
COMPANY_FILE_VERSION, and
REFRESH_ON_CV_CHN application set
parameters. Changed the description of
COMPANY_LOGO application set parameter.

Business Planning and Consolidation System Parameters
Table of Contents
1 APPLICATION SET PARAMETERS .................................................................... 3
1.1 ALLOW_EXTENSIONS ...............................................................................3

1.2 ALLOW_FILE_SIZE...................................................................................3
1.3 DEFAULT_EXTENSIONS ............................................................................4
1.4 APPROVALSTATUSMAIL ............................................................................4
1.5 APPROVALSTATUSMSG .............................................................................5
1.6 AVAILABLEFLAG ......................................................................................5
1.7 AVAILABLEMSG .......................................................................................6
1.8 COMPANY_FILE .......................................................................................6
1.9 COMPANY_FILE_VERSION.........................................................................7
1.10 FILESFOLDERDELIMITER ..........................................................................7
1.11 JREPORTZOOM ........................................................................................8
1.12 LANDINGPAGEITEM .................................................................................9
1.13 LOPTZ_AVAILABLE...................................................................................9
1.14 MAXLRCOLUMNS .....................................................................................9
1.15 MAXLRROWS ........................................................................................ 10
1.16 MSNIMUser ........................................................................................... 10
1.17 MSNIMPassword .................................................................................... 11
1.18 MULTIBYTE_FORMULA ............................................................................ 11
1.19 REFRESH_ON_CV_CHN .......................................................................... 12
1.20 SESSIONTIME ....................................................................................... 12
1.21 SMTPAUTH ........................................................................................... 12
1.22 SMTPSERVER ........................................................................................ 13
1.23 SMTPPORT ............................................................................................ 13
1.24 SMTPUSER............................................................................................ 14
1.25 SMTPPASSWORD ................................................................................... 14
1.26 TEMPLATEVERSION................................................................................ 15
1.27 UPLOADTEMP ........................................................................................ 15
1.28 USE_VARCHAR_FOR_DIM ....................................................................... 16
1.29 DTSSTATUSCHECK ................................................................................ 16
1.30 LIMITOFDIFFERENCE ............................................................................. 17
1.31 RETRIEVE_ON_OFFLINE ......................................................................... 17
1.32 COMPANY_LOGO ................................................................................... 18
2 SEND GOVERNOR APPLICATION SET PARAMETERS ...................................... 19
2.1 INTERVAL_CHECK_SEND ........................................................................ 19

2.2 THREAD_MAXNUM_SG ........................................................................... 19
2.3 UNITPER_SP ......................................................................................... 20
2.4 MAXCELLS_THREAD_SG ......................................................................... 20
2.5 LimitOfCommit ...................................................................................... 20
3 APPLICATION PARAMETERS ......................................................................... 21
3.1 CUSTOMFACTTBLINDEX ......................................................................... 21

3.2 DIMSFORFACTTBLINDEX ........................................................................ 22

3.3 JRN_ACCDETAIL_DIM ............................................................................ 22

3.4 JRN_BALANCE ....................................................................................... 23
3.5 JRN_CLOSING_CODE ............................................................................. 23
3.6 JRN_DESC_MODE .................................................................................. 23
3.7 JRN_IS_STAT_APP ................................................................................. 24
3.8 JRN_MAXCOUNT .................................................................................... 24
3.9 JRN_OPENING_CODE ............................................................................. 25
3.10 JRN_POST_OVERWRITE.......................................................................... 25
3.11 JRN_REOPEN ........................................................................................ 26
3.12 JRN_REOPEN_PROPERTY ........................................................................ 26
3.13 JRN_REVSIGN_CODE ............................................................................. 26
3.14 JRN_VALIDATION_SP ............................................................................. 27
3.15 LOCKREPORT ........................................................................................ 27
3.16 ORG_ACCOUNTLIST ............................................................................... 28
3.17 ORG_ACCOUNTOWN .............................................................................. 29
3.18 ORG_INTCO .......................................................................................... 29
3.19 ORG_PARENTPROPERTY ......................................................................... 30
3.20 TOPDOWN ............................................................................................ 30
3.21 WORKSTATUSVALIDATE ......................................................................... 31
3.22 YTDINPUT............................................................................................. 31
3.23 SIGNED_DATA_FORMAT ......................................................................... 32
3.24 DTSLOGPAGESIZE ................................................................................. 32
3.25 VALIDATE_MBR_LOGIC .......................................................................... 32
3.26 YTD_NECJ_RETRIEVE ............................................................................. 33
4 APPLICATION SET PARAMETERS SUPPORTED IN 5.1 ONLY .......................... 34
4.1 DO_COMPRESS ..................................................................................... 34

4.2 DO_COMPRESS_CLIENT ......................................................................... 34
4.3 USEADOMD .......................................................................................... 35
5 APPLICATION PARAMETERS SUPPORTED IN 5.1 ONLY ................................. 36
5.1 APPROVALORG ...................................................................................... 36
6 APPLICATION SET PARAMETERS SUPPORTED IN 7.0 M ONLY ....................... 36
6.1 BPFSTEP_COMPLETE_MSG ...................................................................... 36

6.2 CLR_COMMENTS_HISTORY ..................................................................... 37
6.3 COMMENT_MAX_LENGTH........................................................................ 37
7 APPLICATION PARAMETERS SUPPORTED IN 7.0 M ONLY ............................. 38
7.1 YTDINPUTTIMEHIR................................................................................. 38
7.2 SEND_SGTABLE_COUNT ......................................................................... 38
7.3 SEC_CACHE_EXPIRE .............................................................................. 39

Note that the information in this document supersedes the application and application set
parameter information in the online help of Business Planning and Consolidation.
1 APPLICATION SET PARAMETERS

Administrators who have Appset task security rights can view and change application set
parameters.
An application set parameter can be either required or optional. If an application set
parameter is required, you can leave it blank to accept the default. If an application
parameter is optional, you can leave it blank or delete it. Do not delete required
parameters, as the system may not work correctly.
The parameters in this guide apply to both BPC 5.1 and BPC 7.0 M unless otherwise
noted.
1.1 ALLOW_EXTENSIONS
1.1.1 Description
 Defines allowed file extensions for upload. Enter a file extension such as txt, xlxs, etc.,
to allow uploading. You can enter more than one extension with a comma (,) delimiter.
1.1.2 Type
 Optional
1.1.3 Default value
 Blank
1.1.4 Valid value
 User can input any extension, such as TXT or ZIP.

 If you enter [ALL], you can upload all file types.
1.1.5 Where this parameter is used
 BPC Web – When posting documents in the Content library menu

 BPC for Office – Save Dynamic Template , Data Upload, Save as Web-Ready File
1.2 ALLOW_FILE_SIZE
1.2.1 Description
 Enter the maximum file size (MB) allowed for uploading. A warning message appears if
the file size exceeds the parameter value when you upload a file.
1.2.2 Type
 Optional
1.2.3 Default value
 Blank. If this parameter is not set, you can upload a file that is 100 Mbyte or less.

1.2.4 Valid value
 User can change the value.
 BPC Web – When posting documents in Content library menu

 BPC for Office – Send Data, Journal-post, DM–Import
1.3 DEFAULT_EXTENSIONS
1.3.1 Description
 The system allows the default file type even if you do not set this parameter. The
default file extensions are hard-coded internally.
1.3.2 Type
 Optional
1.3.3 Default value
 XLS, XLT, DOC, DOT, PPT, POT, XML, MHT, MHTML, HTM, HTML, XLSX, XLSM, XLSB,
ZIP, PDF, PPTX, PPTM, POTX, POTM, DOCX, DOCM, DOTX, DOTM, TDM, PDM, JPG, PNG,
GIF, CSS, MRC, TXT, CSV, XLTX, XLTM, MDB, ACCDB
1.3.4 Valid value
 User can change the value.
 BPC Web – When posting documents in Content library menu

 BPC for Office – Send Data, Journal-post, DM-Import
1.4 APPROVALSTATUSMAIL
1.4.1 Description
 Defines whether owners and managers receive an email when one or the other changes
a work status
1.4.2 Type
 Optional
1.4.3 Default value
 N/A
1.4.4 Valid value
 Yes – Send email

 No – Do not send email

 Submenu “Set work status” in Content Library menu of Web
1.5 APPROVALSTATUSMSG
1.5.1 Description
 Allows you to define a custom email message that is sent when a work status code is
changed. The message is applicable to all applications in the application set. You can
customize the message using the following variables:
- % USER% - Name of user who changed this status
- %STA% - Work status
- %OWNER% - Entity owner
- %CD% - Category dimension
- %CM% - Category member
- %TD% - Time dimension
- %TM% - Time member
- %STA% - Work status
- %TIME% - Time of change
1.5.2 Type
 Optional
1.5.3 Default value
 Blank
1.5.4 Valid value
 User can input a message such as ”This is to inform you that %USER% has updated
the work status for %EM%, %CM%, %TM% on %TIME%".
There is no need for quotes or brackets around parameters.
 Submenu “Set work status” in Content Library menu of Web
1.6 AVAILABLEFLAG
1.6.1 Description
 Controls whether the system is offline or not
1.6.2 Type
 Required

1.6.3 Default value
 Yes
1.6.4 Valid value
 Yes – The system is online and available for sending data to the database.
 No - This system is offline.
 BPC for Office – Send Data, Journal-post, DM-Import
1.7 AVAILABLEMSG
1.7.1 Description
 The message that is displayed to users who try to access an application that is offline.
(AVAILABLEFLAG = No)
1.7.2 Type
 Required
1.7.3 Default value
 Current Appset status is available.
1.7.4 Valid value
 For example, the message might be “Business Planning and Consolidation is

temporarily unavailable due to scheduled maintenance. Please try again later.”
 BPC for OFFICE – Send Data, Journal-post, DM-Import
1.8 COMPANY_FILE
1.8.1 Description
 This parameter allows you to change the Excel file that is displayed when users log on
to BPC for Excel in a given application set.
You must first save the Excel file to:
\\<server_install>\Data\WebFolders\<application_set>\<excel_file_name>
We recommend that the name of the newly defined Excel file differs from the name of
the existing Excel file; otherwise, you cannot go back to the original file.
You must add both the COMPANY_FILE and COMPANY_FILE_VERSION application set
parameters to change the Excel template that is displayed by default. Therefore, after
you add the COMPANY_FILE parameter, you must add the COMPANY_FILE_VERSION
parameter to deploy the new Excel template to users‟ desktops.

1.8.2 Type
 Optional
1.8.3 Default value
 N/A
1.8.4 Valid value
 A valid Excel template file name. Available file extensions are – XLS, XLSM, XLT, XLTM,
XLSB, XLTX and XLSX file types. For example, MyDefaultPage.xls.
 BPC for Excel
1.9 COMPANY_FILE_VERSION
1.9.1 Description
 After adding the COMPANY_FILE parameter and specifying a value for it, use this
parameter to push the new BPC for Excel default file to users‟ desktops.
1.9.2 Type
 Optional
1.9.3 Default value
 N/A
1.9.4 Valid value
 A number that represents the version of the Excel template pushed to users. For
example, 1.0.
 BPC for Excel
1.10 FILESFOLDERDELIMITER
1.10.1 Description
 When you create Web-ready files in Excel, the system creates subfolders based on the
native Excel Save as HTML function. Since the naming rule of the subfolder is different
for each Microsoft Office language, this parameter allows the system to find the
subfolder having the defined delimiter when selecting Web-ready files in BPC Web.
1.10.2 Type
 Required

1.10.3 Default value
 The default value is _:.:-. You must define a value for this parameter if the value is
empty, or does not contain the required delimiter for your Microsoft Office version.
Separate multiple delimiters with a colon; for example, :,:_.
For example, under a folder named 'Report.htm', the system creates the following
subfolders:
o Chinese: report.files
o English: report_files
o French: report_fichiers
o German: report-Dateien
o Italian: report-file
o Japanese: report.files
o Korean: report.files
1.10.4 Valid value
 User can define this delimiter depending on their country.

 Use “:” to separate multiple values
 BPC for OFFICE – When a book was published
1.11 JREPORTZOOM
1.11.1 Description
 This parameter allows you to set the default zoom magnification value on HTML journal
reports.
1.11.2 Type
 Optional
 Blank
1.11.4 Valid value
 We recommend you set the value to 75%.
 BPC FOR OFFICE - Journal Report

1.12 LANDINGPAGEITEM
1.12.1 Description
 This defines the Getting Started page on BPC Web.
1.12.2 Type
 Optional
 1 (This number indicates the page number.)
1.12.4 Valid value
 User can input a page number that already existed in BPC Web as a Web page.
 BPC Web – User can change or create a page as the starting page in the Content
Library.
 BPC Web – All users can see the page in the Getting Started menu as the start page.
1.13 LOPTZ_AVAILABLE
1.13.1 Description
 This parameter takes the system off-line during a lite optimization of an application.
1.13.2 Type
 Optional
 0
1.13.4 Valid value
 0 – do not change to off-line

 1 – change to off-line
 BPC Admin – Lite optimize
1.14 MAXLRCOLUMNS
1.14.1 Description
 The maximum number of columns to display in a live report in BPC Web. The value
includes header and data columns.

1.14.2 Type
 Optional
 30
1.14.4 Valid value
 User can input any number. If you specify a value of 5, one heading column and four
data columns are displayed.
 BPC Web – Live Reporting
1.15 MAXLRROWS
1.15.1 Description
 The maximum number of rows to display in a live report in BPC Web. The value
includes header and data rows.
1.15.2 Type
 Optional
 50
1.15.4 Valid value
 User can input any number. If you specify a value of 5, one heading row and four data
rows are displayed.
 BPC Web – Live Reporting
1.16 MSNIMUser
1.16.1 Description
 The user name that the system uses to operate IM alerts in Insight.
1.16.2 Type
 Optional
 Blank

1.16.4 Valid value
 User can input the user ID of MSN IM.
 BPC Insight – Alert
1.17 MSNIMPassword
1.17.1 Description
 The password that the system uses to operate IM alerts in Insight.
1.17.2 Type
 Optional
 Blank
1.17.4 Valid value
 User can input the password of MSN IM.
 BPC Insight – Alert
1.18 MULTIBYTE_FORMULA
1.18.1 Description
Use this parameter to support dimension formulas with member IDs that contain double-byte
characters, such as those in Japanese, Chinese, Korean, and Russian. The value defines the
dimension formula column type (Nvarchar or Varchar).
1.18.2 Type
 Optional
 Blank
1.18.4 Valid value
 1 – Dimension formula column is created as nvarchar instead of varchar to support

double-byte characters.
 N/A or blank or 0 - Dimension formula column is created as varchar.
 BPC Admin – Process dimension

1.19 REFRESH_ON_CV_CHN
1.19.1 Description
 This parameter allows you to turn on or off the recalculation of data when the current
view is changed. This applies to all worksheets in the workbook.
1.19.2 Type
 Optional
1.19.3 Default Value
 1
1.19.4 Valid Value
 0 – turn off. Data is not refreshed upon a change in the current view.
 1 – turn on. Data is refreshed upon a change in the current view.
 BPC for Excel
1.20 SESSIONTIME
1.20.1 Description
 Defines the session time for Who‟s Online.
1.20.2 Type
 Optional
 3000 (This number indicates 3000 minutes.)
1.20.4 Valid value
 User can input the minutes.
 BPC Admin – Who‟s Online
1.21 SMTPAUTH
1.21.1 Description
 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 email server.
1.21.2 Type
 Required
 1
1.21.4 Valid value
 0 = Anonymous
 1 = Basic
 2 = NTLM
 BPC Web – When posting documents, Work status, Alert

 BPC for Office - Offline distributor
1.22 SMTPSERVER
1.22.1 Description
 The name or TCP/IP address of the SMTP email server the system uses to send email
1.22.2 Type
 Required
 Blank
1.22.4 Valid value
 User can input the SMTP Server name or TCP/IP address.
 Web – When posting documents, Work status, Alert

1.23 SMTPPORT
1.23.1 Description
 Port number for your SMTP email server
1.23.2 Type
 Required

 25 (This is the default SMTP server port number.)
1.23.4 Valid value
 User can input the port number.

1.24 SMTPUSER
1.24.1 Description
 The user name from which email from the system originates.
1.24.2 Type
 Required
 Blank
1.24.4 Valid value
 User can input the User name.

1.25 SMTPPASSWORD
1.25.1 Description
 The password for sending email user name
1.25.2 Type
 Optional (When SMTPAUTH is “1” (basic), this parameter is required.)
 Blank
1.25.4 Valid value
 User can input the SMTP password.


1.26 TEMPLATEVERSION
1.26.1 Description
 Current version number of the dynamic templates in your application set. Whenever
you add to or change your input schedule or report dynamic templates, you should
increment this version number so users automatically receive the new templates
downloaded when they log on to this application set.
1.26.2 Type
 Required
 Current version number of the dynamic templates in your application set
1.26.4 Valid value
 User can input the version or it will change automatically.
 BPC for Office – Logon, Save dynamic template
1.27 UPLOADTEMP
1.27.1 Description
 Temporary folder used to store Content Library documents
1.27.2 Type
 Required
 C:\BPC\FTPServer\OSoftFTP (This value is hard-coded.)
1.27.4 Valid value
 User can input the path and, if BPC 5.0 was installed in other name‟s folder, the
Administrator must change this path according to the path. For example, D:\[Folder
name which was made in installing time]\OSoftFTP.
 BPC Web – Upload document in Content Library menu

1.28 USE_VARCHAR_FOR_DIM
1.28.1 Description
 Defines the type (Nvarchar or Varchar) of all columns in the dimension table, such as
dim<DimensionName>.
 If you have a space restriction problem from SQL and OLAP, you can use this
parameter to determine whether the columns in the Dimension table are Varchar or
Nvarchar (one of the data types from the SQL table column).
 If you use a double-byte character language such as Korean, Japanese, Chinese, or
Russian, we do not recommend using the Varchar data type.
1.28.2 Type
 Optional
 Blank(0)
1.28.4 Valid value
 0 - If this parameter does not exist or value is blank (or 0), all columns are created as
nvarchar.
 1 - If this parameter‟s value is 1, all columns that are nvarchar in the dim table are
created as varchar.
 A specific dimension name or blank can be in the KeyID column of tblDafaults table.
 If the KeyID is a specific dimension name, it is applied to only the specific dimension; if
the KeyID is blank, all dimensions are applied in all dim tables.
 To set this parameter value, you should insert or update the record to tblDefaults table
directly instead of via the Web Administration page.
For example,
This is tblDefaults table that manages all of system parameters.
User ID Type App Key ID Value
_GLOBAL SYSTEM USE_VARCHAR_FOR_DIM ACCOUNT 1
 BPC Admin - Process dimension
1.29 DTSSTATUSCHECK
1.29.1 Description
Use this parameter to hide or show the “Refresh Status Every” check box in the Data Manager
Status View.
If the check box is enabled and large records exist, the performance when refreshing the status
degrades. By hiding the check box, the refresh is performed whenever a user calls the refresh
button manually.

1.29.2 Type
 Optional
 N/A
1.29.4 Valid Value
 0: Hides the checkbox

 1: Show the checkbox
 Data Manager - Status view
1.30 LIMITOFDIFFERENCE
1.30.1 Description
 The least value to process logic is set. If a data is smaller than the value, logic ignores
the data to process.
1.30.2 Type
 Optional
 .00000001 (If the parameter is not set, logic ignores less than 0.00000001.)
1.30.4 Valid Value
 For example, when 0.001 is set, smaller data than the value - such as 0.0009 - is not
processed by logic.
 Script Logic – Processing of script logic
1.31 RETRIEVE_ON_OFFLINE
1.31.1 Description
Use this parameter to restrict data retrieval and export while an application set is unavailable
(system offline). See SAP Note 1260260.
Note: Data manager packages that are set as an Admin package can be retrieved and exported
even when the parameter is set to 0. For example, if „Export from fact table package‟ is set as
an Admin package, a user who has „Manage DM‟ task can retrieve and export the package
while the application set is unavailable. The following tasks can be executed when the value is
0 (IM 3295848):
 Execute logic (script, business rules) from DTS package
 Run Export from fact table package

 Run Append into fact table package
 Add new comments
 Save data through the Dynamic Hierarchy Editor
1.31.2 Type
 Optional
 N/A
1.31.4 Valid Value
 1: Allows retrieving or exporting data while an application set is unavailable (system

offline)
 0: Does not allow retrieving or exporting data while an application set is unavailable
(system offline)
 All functions that retrieve or export data. For example, Refresh data in BPC for Office
and BPC Web, Export DM package, Book Publish, and so on.
1.32 COMPANY_LOGO
1.32.1 Description
 Use this parameter to add your corporate logo to the default templates in BPC
for Excel. Enter the file name for the logo image that you want to display.
You must save the image file to:

\\<server_install>\Data\WebFolders\<application_set>\<image_file_name>
If the COMPANY_LOGO does not exist or the file name is invalid, the default
globe image displays.
1.32.2 Type
 Optional
1.32.3 Default Value
 N/A
1.32.4 Valid Value
 Allows the bmp, gif, and jpg image file types
 Logon to BPC for Excel

2 SEND GOVERNOR APPLICATION SET PARAMETERS
2.1 INTERVAL_CHECK_SEND
2.1.1 Description
 The frequency, in milliseconds, at which the system sends data from the Send
Governor table to the write-back table.
2.1.2 Type
 Optional
2.1.3 Default value
 3000 msec
2.1.4 Valid value
 User can define this interval time.
 BPC for Office – SendGovernor
2.2 THREAD_MAXNUM_SG
2.2.1 Description
 By default, there is one thread that sends records from the Send Governor table to the
write-back table. This parameter sets the maximum number of additional threads that
can be created to run concurrently with the default thread. At increments defined by
the INTERVAL_CHECK_SEND parameter, the Send Governor checks how many
instances of send threads are running. If the number of threads is less than or equal to
THREAD_MAXNUM_SG, Send Governor starts a new send thread.
2.2.2 Type
 Optional
2.2.3 Default value
 3 (thread count)
2.2.4 Valid value
 User can input the thread count.

2.3 UNITPER_SP
2.3.1 Description
 This parameter limits the number of records that are sent (for a given send thread)
from the Send Governor table to the write-back table.
2.3.2 Type
 Optional
2.3.3 Default value
 500 (Record count)
2.3.4 Valid value
 User can input the record count.
 BPC for Office – Send Data, Journal post
2.4 MAXCELLS_THREAD_SG
2.4.1 Description
o Defines the maximum record count that is processed by a send thread.
2.4.2 Type
 Optional
2.4.3 Default value
o 1000000
2.4.4 Valid value
 User can input the maximum record count.
2.5 LimitOfCommit
2.5.1 Description
o Defines the maximum record count in a data send. For example, if a user sends
120,000 cells and the LimitofCommit is set to its default of 100,000, the send
engine splits the data into two parts: One part has 100,000 and the other has
20,000.
2.5.2 Type
 Optional

2.5.3 Default value
o 100000
2.5.4 Valid value
 User can input the maximum record count.
 BPC for Office – Data sending, Script Logic
3 APPLICATION PARAMETERS
Application task security rights can set application parameters.
Application parameters control the way certain features behave in an application. The
application parameters can be different for each application within an application set.
If an application 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 application parameter is
optional, you can delete it if desired.
3.1 CUSTOMFACTTBLINDEX
3.1.1 Description
 Use this parameter to define a dimension list to create a custom index in the
appropriate database table and accelerate import processing. Enter a list of dimensions,
separated by commas. For example, 'Account, Time, Entity, and Category‟. When you
use a custom fact table index, we recommend that when you modify the application,
you select the Reassign SQL Index option.
3.1.2 Type
 Optional
3.1.3 Default value
 Blank
3.1.4 Valid value
 User can input values such as Category, Time, Entity, Account, or RptCurrency.
 BPC Admin – Modify application, Add a new application, Copy an application

3.2 DIMSFORFACTTBLINDEX
3.2.1 Description
 The Fact and Fac2 tables use a clustered index, and the write-back table uses a
composite index. The default fields and order of the fields for the index is Category, Time,
Entity, Account, RptCurrency.
 If you need to change the field and order, enter them here.
3.2.2 Type
 Optional
3.2.3 Default value
 Blank
 If blank, the default value is Category, Time, Entity, Account, RptCurrency.
3.2.4 Valid value
 User can input a dimension list into this parameter, such as Category, Time, Entity,
Account, RptCurrency.
 BPC Admin – Modify application, Add a new application, Copy an application
3.3 JRN_ACCDETAIL_DIM
3.3.1 Description
 A special dimension name used to manage the Opening, Closing, and Reverse Sign
codes. This field is used in conjunction with the JRN_CLOSING_CODE,
JRN_OPENING_CODE, and JRN_REVSIGN_CODE fields.
3.3.2 Type
 Optional
3.3.3 Default value
 Blank
3.3.4 Valid value
 User can input the dimension name.
 BPC for Office – Journal

3.4 JRN_BALANCE
3.4.1 Description
 Controls whether Journals are required to be balanced.
3.4.2 Type
 Optional
3.4.3 Default value
 Blank
3.4.4 Valid value
 1=Yes, 0= No.
3.5 JRN_CLOSING_CODE
3.5.1 Description
 The member name for the 'closing' code. This member is part of the dimension defined
in the JRN_ACCDETAIL_DIM field.
3.5.2 Type
 Optional
3.5.3 Default value
 Blank
3.5.4 Valid value
 User can input the member name.
3.6 JRN_DESC_MODE
3.6.1 Description
 Allow to display the description in the journal template.

 Accept the default N when you want member IDs to be displayed in the application's
journal template. The default also provides optimal readability.
 Use the value Y to display the description in the journal template.

3.6.2 Type
 Optional
3.6.3 Default value
 0
3.6.4 Valid value
 N - Display the member ID

 Y - Display the description of member.
3.7 JRN_IS_STAT_APP
3.7.1 Description
 If the application is used for statutory consolidation, set this field to Y to enable the
subsequent journal fields. Set to N to disable the subsequent fields.
3.7.2 Type
 Optional
3.7.3 Default value
 Blank
3.7.4 Valid value
 Y - Enables the subsequent journal fields.

 N - Disables the subsequent fields.
3.8 JRN_MAXCOUNT
3.8.1 Description
 Maximum number of journal entries returned from a query in the Journal Manager. This
parameter is useful if you have a large number of Journal Entries and want to protect a
user from launching a very long query.
3.8.2 Type
 Optional
3.8.3 Default value
 Blank

3.8.4 Valid value
 A positive integer greater than 0
3.9 JRN_OPENING_CODE
3.9.1 Description
 The member name for the 'opening' code. This member is part of the dimension
defined in the JRN_ACCDETAIL_DIM field.
3.9.2 Type
 Optional
3.9.3 Default value
 Blank
3.9.4 Valid value
 User can define the member name for the Opening code.
3.10 JRN_POST_OVERWRITE
3.10.1 Description
 Controls whether the system keeps the same Journal ID when saving journals that
were previously set to Posted status, but changed to Unposted status.
3.10.2 Type
 Optional
 Blank
3.10.4 Valid value
 Y – Preserves the Journal ID when the unposted journal is saved

 N – Creates a new ID when the unposted journal is saved

3.11 JRN_REOPEN
3.11.1 Description
 Allows you to define the default for reopening journals.
3.11.2 Type
 Optional
 Blank
 If blank, this default value is N.
3.11.4 Valid value
 N – Does not allow reopening of journals

 Y – Allows the reopening of journals
3.12 JRN_REOPEN_PROPERTY
3.12.1 Description
 A custom Journal module assumes that property named UB must be present in account
dimension to further filter the Journals to Re-Open.
3.12.2 Type
 Optional
 Group
3.12.4 Valid value
 If Group, there is no need to modify the account dimension.

 This parameter is used in Application\JournalSvr\clsQuery.vb
3.13 JRN_REVSIGN_CODE
3.13.1 Description
 The member property name that is used to reverse the sign during posting and
unposting.

 This property is defined for the members defined in the JRN_ACCDETAIL_DIM field.
3.13.2 Type
 Optional
 Blank
3.13.4 Valid value
 Y
 The property value must be set to Y to use this feature.
3.14 JRN_VALIDATION_SP
3.14.1 Description
 Allows you to specify the SQL stored procedure name to be executed before
posting/unposting data. This stored procedure performs custom validation on the entire
RecordSet to be posted/unposted and gives back go/no-go to the posting engine.
3.14.2 Type
 Optional
 Blank
3.14.4 Valid value
 User can input the SQL stored procedure name.
3.15 LOCKREPORT
3.15.1 Description
 The report launches when submission validation for a data region is not „0‟ in BPC
Excel. The template must be located in the following folder:
<WebfolderLocation>\<AppSet>\<Application>\eExcel\Input Schedules\Wizard
 A sample template is provided in the following location:
<WebfolderLocation>\Apshell\Finance\eExcel\Input Schedules\Wizard\Validate.xlt
3.15.2 Type
 Optional

 Blank
3.15.4 Valid value
 User can input the template file name.
 BPC for Office - Validate submission
3.16 ORG_ACCOUNTLIST
3.16.1 Description
 Distinguishes from the dynamic hierarchy what account dimension members of the
ownership application represent the legal consolidation method and the ownership
percentage for the subsidiary company.
 The account dimension members should exist in the ownership type application.
 The METHOD member for the consolidation method should be defined in the
parameter. If you define 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 define one or one more account dimension
members according to your business needs. At least one member should be defined for
the ownership percentage.
3.16.2 Type
 Required, if the application is an ownership-type and if performing legal consolidation

that refers to the ownership application.
3.16.4 Valid value
 User defines this value. You can input account dimension members of ownership type
application with comma (,) delimiter.
 BPC Admin - Dynamic Hierarchy Editor

3.17 ORG_ACCOUNTOWN
3.17.1 Description
 The default value is PGROUP. It shows the relationship of the parent and subsidiary
companies in the dynamic hierarchy. If the parameter is not defined, DHE 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 defined, the rule finds the account
dimension member named GROUP or PGROUP during processing.
3.17.2 Type
 Required, if the application is an ownership type and legal consolidation is performed

referring to the ownership application.
3.17.4 Valid value
 You can input account dimension members of ownership type application.
 BPC Admin - Dynamic Hierarchy Editor, BusinessRules
3.18 ORG_INTCO
3.18.1 Description
 This parameter should be a member ID in the INTCO dimension in the ownership

application if using dynamic hierarchies.
3.18.2 Type
 Required, if application is ownership type and legal consolidation is performed.
 I_NONE
3.18.4 Valid value
 User can input the member ID in the INTCO dimension in Ownership application.
 BPC Admin - Dynamic Hierarchy Editor

3.19 ORG_PARENTPROPERTY
3.19.1 Description
 This parameter is used with dynamic hierarchy statutory applications when defining
fixed hierarchies. The value must match the value in the ParentProperty property name
of entities (entities -> group dimension member) in the statutory application's
supporting ownership application.
3.19.2 Type
 Required, if application is ownership type and legal consolidation is performed.
 PARENT_GROUP
3.19.4 Valid value
 User can input the property name of the group dimension.
 BPC Admin - Dynamic Hierarchy Editor, BusinessRules
3.20 TOPDOWN
3.20.1 Description
 Defines how to handle approval of work status.

 If TopDown, work status is approved no matter if sub-work status is approved or not.
 If BottomUp, work status can be approved only if all sub-work statuses are approved.
 When you change the value of this parameter, existing work status information is
removed.
3.20.2 Type
 Required, if work status setting is enabled in the BPC Administration console
 N/A
 If blank, the default value is .
3.20.4 Valid value
 Yes - top down approval of work status

 No - bottom up approval of work status
 BPC Web – Set work status in the Content Library menu.

3.21 WORKSTATUSVALIDATE
3.21.1 Description
 After checking the value of the cell for which a user tries to change the work status.
 If “0”, it passes the validation; if not, it is rejected.
3.21.2 Type
 Optional
 N/A
 If N/A, the default value is no.
3.21.4 Valid value
 Yes - need to check validate

 No - don‟t need to check
 BPC Web – “Set work status” in Content Library menu.
3.22 YTDINPUT
3.22.1 Description
 This parameter controls whether data is input in year-to-date format.
3.22.2 Type
 Optional
 N/A
 If N/A, the default value is no.
3.22.4 Valid value
 Yes - YTD format

 No - Periodic format
 BPC Admin - Application process

3.23 SIGNED_DATA_FORMAT
3.23.1 Description
 Value is used for precision and scale of the signeddata column of tblFact, tblFac2 and
tblFactWB table in an application. If this parameter does not exist, set the default value
that is 25,10 to signeddata column.
3.23.2 Type
 Optional
 If blank, the default value is “25,10”.
3.23.4 Valid value
 User can input the length.

 User must do it before Modify application task runs.
 BPC Admin – Add a new application, Modify application, Copy an application
3.24 DTSLOGPAGESIZE
3.24.1 Description
 Sets the number of records that display in the Data Manager Status View.
3.24.2 Type
 Optional
 300
3.24.4 Valid value
 User can input the number of records to display.
 Data Manager – Status View
3.25 VALIDATE_MBR_LOGIC
3.25.1 Description
 Validates members when processing logic. The performance of processing logic is

decreased due to this validation.

3.25.2 Type
 Optional
 N/A
3.25.4 Valid Value
 1: The system filters 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.
 Script Logic – posting data during running script logic
3.26 YTD_NECJ_RETRIEVE
3.26.1 Description
 To choose the query type to improve the performance of data retrieval when retrieving
YTD measures on Periodic applications or vice-versa.
 This parameter is useful when the below condition are satisfied.
- YTD / QTD measures data is retrieved on periodic application or Periodic / QTD
measures data is retrieved on YTD application.
- The retrieval range is huge, but the portion of the data existing cells is small.
- ColKeyRange or RowKeyRange has over 2 dimensions.
- The retrieval range has no members having dimension formula.
3.26.2 Type
 Optional
 0
3.26.4 Valid Value
 1: To use NonEmptyCrossJoin query

 0: Not to use NonEmptyCrossJoin query
 Retrieve data – EVDRE, EVGET, EVGTS, EVSND, EVINP functions

4 Application Set Parameters Supported in 5.1 only
4.1 DO_COMPRESS
4.1.1 Description
 To allow compressing or uncompressing the web service respond against the

retrieval data request.
 If uncompressing the web service respond, network traffic can be reduced.
 How to set the parameter:
- Run the script below in SQL Server management studio. This parameter is
used internally, so to not expose it through the Web Administration page,
it is set as an internal parameter and it is only modified directly to the
„tblDefaults‟ table.
INSERT INTO [dbo].[tbldefaults] (Userid, Type, App, KeyID, Value)
VALUES(N'_INTERNAL', N'SYSTEM', '', N'DO_COMPRESS',N'0')
4.1.2 Type
 Optional
4.1.3 Default Value
 N/A
4.1.4 Valid Value
 1: To use compress
 0: To use uncompress
 Retrieval data
4.2 DO_COMPRESS_CLIENT
4.2.1 Description
 Allows the compression or decompression of the request query for sending and
retrieving data from BPC client.
 The request queries are always compressed. This cannot be used with
LoadRunner to run reliability or scalability testing.
 How to set the parameter:
- Run the script below in SQL Server Management studio. This parameter is
used internally to not expose it through the Web Administration page. I is

set as an internal parameter and it is only modified directly to the

tblDefaults table.
INSERT INTO dbo.tblDefaults (Userid, [Type], App, KeyID, [Value])

VALUES(N'_INTERNAL',N'SYSTEM',N'',N'DO_COMPRESS_CLIENT',N'0')
4.2.2 Type
 Optional
4.2.3 Default Value
 N/A
4.2.4 Valid Value
 If the parameter is not set or the parameter value is set to 1, the query from
client side is compressed.
 If the parameter value is set to 0, the query is uncompressed.
 Stress test for sending and retrieving data using LoadRunner
4.3 USEADOMD
4.3.1 Description
 If BPC runs in a SQL 2000 environment and data is retrieved with the
condition noted below, data may not be retrieved even though transactional
data exists in the Fact tables. Data can be retrieved without this problem if
ADOMD.NET instead of ADOMD is used from the query engine.
- The calculated member exists in the PageKeyRange.
- Each Row count and Column count are at least more than 2.
- One of the columns has more than 2 values and some columns have just
one value. The columns that have just one value have wrong values
despite the fact that they do not have any values.
 Allows using ADOMD.NET or ADOMD when retrieving data
4.3.2 Type
 Optional
4.3.3 Default Value
 N/A
4.3.4 Valid Value
 If the parameter value is 0 (zero), the query engine will use „ADOMD.NET‟.

 If the parameter value is 1, the query engine will use „ADOMD‟.
 Query engine when retrieving data
5 Application Parameters Supported in 5.1 only
5.1 APPROVALORG
5.1.1 Description
 If you want to use the work status feature, you must use this field to identify
the hierarchy level (H1, H2, H3,.. Hn) for which you want to track the work
status of deliverables.
 You can define only one hierarchy for each application within an application set.
For alternate organizations, "No Status" is displayed when viewing those
members in the work status screen.
 If this field is left blank, work status tracking is not enabled or used to store
Content Library documents.
5.1.2 Type
 Required
5.1.3 Default value
 H1
5.1.4 Valid value
 User can input the hierarchy level.
 BPC Web – Set Work status in Content Library menu
6 Application Set Parameters Supported in 7.0 M Only
6.1 BPFSTEP_COMPLETE_MSG
6.1.1 Description
 BPF has e-mail notification functionality when a step of a BPF instance is

completed and it needs reviewing by reviewer. Regarding the e-mail, the
message can be modified via the parameter.

6.1.2 Type
 Optional
6.1.3 Default Value
 [%BPF_STEP_NAME%] step of [%BPF_NAME%] has been completed by

[%USER_NAME%]
6.1.4 Valid Value
 You can use specific variables to get BPF name, BPF step name, and user
name.
- [%BPF_NAME%]: BPF name
- [%BPF_STEP_NAME%]: BPF step name
- [%USER_NAME%]: user name
 BPF
6.2 CLR_COMMENTS_HISTORY
6.2.1 Description
 Deletes all comment history and retains only the latest comment. Historical comments
are removed after applying the parameter on the AppSet Parameters page of Web
Administration.
6.2.2 Type
 Optional
6.2.3 Default value
 0
6.2.4 Valid Value
 0: Saves the historical comments.

 1: Deletes the historical comments and retains the latest comment only.
 Add comments, View comments
6.3 COMMENT_MAX_LENGTH
6.3.1 Description
 Supports the customized length of 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 AppSet Parameters page. Therefore, the new setting should be larger than the
previous value.
6.3.2 Type
 Optional
6.3.3 Default value
 256
6.3.4 Valid Value
 User can input integers between 256 and 4,000 for the length.
 Add comments, View comments
7 Application Parameters Supported in 7.0 M Only
7.1 YTDINPUTTIMEHIR
7.1.1 Description
 This parameter designates the time dimension hierarchy that is used by a YTD
storage application.
7.1.2 Type
 Required, if application type is YTD input type
7.1.3 Default Value
 H1
7.1.4 Valid Value
 The desired hierarchy of time dimension to send data available; H1 or H2 or

H3
 Sending data
7.2 SEND_SGTABLE_COUNT
7.2.1 Description
 This parameter designates the count of sgData[Application] table that is used

by the data sending process.

 It is to be scalable for sending data and it will process sending date parallel as
the number of the table.
 The “Modify Application” should be performed after change this parameter.
7.2.2 Type
 Optional
7.2.3 Default Value
 2
7.2.4 Valid Value
 Sending data
7.3 SEC_CACHE_EXPIRE
7.3.1 Description
 It is set the expired time (hours) for cache of member access security profile.
 It is to restrict increasing memory size for the cache without any limitation.
During the expired time, if a user does not retrieve data, the cache for the
user is released on the Application server.
 If change this parameter, you must reset IIS on the Application server.
7.3.2 Type
 Optional
7.3.3 Default Value
 24 (hours)
7.3.4 Valid Value
 Reading the cache of member access security profile when retrieving data

BPC System Parameters

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

BPC System Parameters

Загружено:

Авторское право:

Доступные форматы

Business Planning and Consolidation

Last Revision Date 5/27/11

File Name BPC_System_Parameters.pdf

Author Soon Kim

Created Date 1/16/2008

© Copyright 2009 SAP AG. All rights reserved. Page 1

© Copyright 2009 SAP AG. All rights reserved. Page 2

1.1 ALLOW_EXTENSIONS ...............................................................................3

2 SEND GOVERNOR APPLICATION SET PARAMETERS ...................................... 19

2.1 INTERVAL_CHECK_SEND ........................................................................ 19

3 APPLICATION PARAMETERS ......................................................................... 21

3.1 CUSTOMFACTTBLINDEX ......................................................................... 21

© Copyright 2009 SAP AG. All rights reserved. Page 1

3.3 JRN_ACCDETAIL_DIM ............................................................................ 22

4 APPLICATION SET PARAMETERS SUPPORTED IN 5.1 ONLY .......................... 34

4.1 DO_COMPRESS ..................................................................................... 34

5 APPLICATION PARAMETERS SUPPORTED IN 5.1 ONLY ................................. 36

5.1 APPROVALORG ...................................................................................... 36

6 APPLICATION SET PARAMETERS SUPPORTED IN 7.0 M ONLY ....................... 36

6.1 BPFSTEP_COMPLETE_MSG ...................................................................... 36

7 APPLICATION PARAMETERS SUPPORTED IN 7.0 M ONLY ............................. 38

© Copyright 2009 SAP AG. All rights reserved. Page 2

1 APPLICATION SET PARAMETERS

1.1.3 Default value

1.1.4 Valid value

 User can input any extension, such as TXT or ZIP.

1.1.5 Where this parameter is used

 BPC Web – When posting documents in the Content library menu

1.2.3 Default value

© Copyright 2009 SAP AG. All rights reserved. Page 3

1.2.4 Valid value

 User can change the value.

1.2.5 Where this parameter is used

 BPC Web – When posting documents in Content library menu

1.3.3 Default value

1.3.4 Valid value

 User can change the value.

1.3.5 Where this parameter is used

 BPC Web – When posting documents in Content library menu

1.4.3 Default value

1.4.4 Valid value

 Yes – Send email

© Copyright 2009 SAP AG. All rights reserved. Page 4

1.4.5 Where this parameter is used

 Submenu “Set work status” in Content Library menu of Web

1.5.3 Default value

1.5.4 Valid value

1.5.5 Where this parameter is used

 Submenu “Set work status” in Content Library menu of Web

 Controls whether the system is offline or not

© Copyright 2009 SAP AG. All rights reserved. Page 5

1.6.3 Default value

1.6.4 Valid value

1.6.5 Where this parameter is used

 BPC for Office – Send Data, Journal-post, DM-Import

1.7.3 Default value

 Current Appset status is available.

1.7.4 Valid value

 For example, the message might be “Business Planning and Consolidation is

1.7.5 Where this parameter is used

 BPC for OFFICE – Send Data, Journal-post, DM-Import

© Copyright 2009 SAP AG. All rights reserved. Page 6

1.8.3 Default value