Application Parameters for Consolidation

As a prerequisite to using consolidations, you must update some settings via the ’set application parameters’ option from the web client. The parameters reference how organizational information from the ownership application is used for example. You did this back on day one and now you’ll see how they (the ones that start with ’ORG’ )are used in the Dynamic Hierarchy Editor (DHE).

• Opening Balance: Enables the business rule table for balance carry forward.
• Org_Accountlist: Member id’s of the ownership account dimension that store methods, % consolidation and , % ownership.
• Org_Accountdown: member id of the ownership account that specifies the Position of a consolidation entity within the group.
• Org_intco: the 3rd party member in the Intercompany dimension.
• Org_ownershipcube: name of the linked Ownership application.
• Org_parentproperty: property name in the Groups dimension to define the hierarchy used in the dynamic hierarchy editor.
• Ownership_App: the consolidation logic requires the Ownership application .

Set AppSet Parameters

Following Parameters must be set during setting up the Application Set. (Most of them are not necessarily consolidation required, but the generic system requirement for AppSet. )
 

http://servername/OSoft/Admin/SetParameters.aspx


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. Y=Yes; N=No


AVAILABLEMSG:  The message that is displayed to users who try to access an application that is offline (AVAILABLEFLAG = No). For example, the message might be Business Planning and Consolidation is temporarily unavailable due to scheduled maintenance.



AVAILABLEURL: The name of the Web page to display to users who try to access an application that is offline. (AVAILABLEFLAG = No). For example, the url might be: /BPC/NotAvailable.asp


ALLOW_EXTENSIONS: If [ALL], It was allowed all extension in BPC.


DEFAULT_EXTENSIONS: XLS, XLT, DOC, DOT, PPT, POT, XML, MHT, MHTML, HTM, HTML, XLSX, XLSM, XLSB, ZIP, PDF, PPTX, PPTM, POTX, POTM, DOCX, DOCM, DOTX, DOTM, CDM, TDM, PNG, GIF, JPG, CSS, MRC

ALLOW_FILE_SIZE: Maximum Files Size allowed for uploading is 100M, which should be written as “104857600”.


UPLOADTEMP Temporary folder used to store Content Library documents. (Required)
Directory for web server to put uploaded file before it was transferred into file share.


TEMPLATEVERSION: 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 that users will automatically get the new templates downloaded when they log on to this application set. For example: 01 (Version01). User can also reset the template version from the Admin Console.

JREPORTZOOM: This parameter allows user to set the default zoom magnification value on HTML journal reports. The recommended value = 75%

LOGLEVEL: 0= No log, 1 = Error Log only, 2 = Error and Success Logs, 3 = All Logs ( Error, Warning, Success)

SYSTEM: BPC 7 Internal system Parameter, default value = 1

MESSAGE BPC 7 Internal system Parameter, default value = Blank

STATUS BPC 7 Internal system Parameter, default value = 1


Technical Aid: At back end, all parameters are stored in ABAP DDIC table:
UJA_USER_DEF.