Remerciez-le!

Remerciez @Admin pour avoir partagé cet document gratuitement, de la manière la plus simple, en partageant sur les réseaux sociaux.

Oracle Financial Services Analytical Applications Infrastructure Administration

Oracle Financial Services Analytical Applications Infrastructure Administration Guide Oracle Financial Services Software Confidential - Restricted ii D DO OC CU UM ME EN NT T C CO ON NT TR RO OL L Version Number Revision Date Changes Done Draft Created: July 2012 Captured the administration configurations for 7.3.2.0.0 Interim Release enhancements. 1.0 Updated: September 2012 Updated the suggested reviewed changes. 1.1 Updated February 2013 Removed the Filter Servlet section from this document and the same can be obtained by contacting support team. 1.2 Updated: June 2013 Included Forms Framework enhancement configuration details. 1.3 Updated: June 2013 Included the following sections:  MLS Utility 1.4 Updated: August 2013 Included the following sections:  Config Schema Upload/ Download Settings  Database Password Reset/ Change 1.5 Updated: September 2013 Removed some sections and added those as FAQs in Installation Guide. 1.6 Updated November 2013 Updated MLS Utility section. 1.7 Updated December 2013 Added Configure SSO Authentication section. Created by: Anand / Gitcy Reviewed by: Bharath / Lokesh/ Sue Approved by: Jeevraj / Surag Ramachandran / Subhashini Executive Summary This document includes the necessary instructions for module specific configurations. We recommend you to download the latest copy of this document from OTN library which includes all the recent revisions (if any) done till date. Table of Contents Oracle Financial Services Software Confidential - Restricted iii T TA AB BL LE E O OF F C CO ON NT TE EN NT TS S 1 OFSAAI ADMINISTRATION ...................................................................................................................... 4 1.1 Dimension Configuration: Alphanumeric and Numeric Codes ................................................................... 5 1.1.1 Configure Alphanumeric Dimensions ............................................................................................................. 5 1.1.2 Configure Numeric Dimensions ...................................................................................................................... 7 1.1.3 Configure Alphanumeric Code in Simple Dimension Tables ........................................................................... 9 1.1.4 Create Index on Code Column ....................................................................................................................... 9 1.2 Hierarchy Node Internationalization ......................................................................................................... 10 1.2.1 Scope .......................................................................................................................................................... 10 1.2.2 Prerequisites ................................................................................................................................................ 10 1.2.3 Multi Language Support (MLS) Table ........................................................................................................... 10 1.2.4 Node Generation Process ............................................................................................................................ 13 1.2.5 Configure Mapper for Multiple Locales ......................................................................................................... 14 1.2.6 Update Nodes in Existing Regular BI and PC Hierarchies ............................................................................ 14 1.2.7 Limitations .................................................................................................................................................... 15 1.3 T2T and PR2 Query Performance Optimization ....................................................................................... 15 1.4 Configure Data Quality Rule Approval Parameters .................................................................................. 16 1.5 Run Rule Framework Configuration ......................................................................................................... 16 1.5.1 Enable RRF/PR2 Links in OFSAAI ............................................................................................................... 16 1.5.2 Command Line Utilities ................................................................................................................................ 18 1.5.3 Component Registration ............................................................................................................................... 18 1.6 Configure Forms xml to execute Server Side Rule .................................................................................. 24 1.7 Data Element Filters Classification ........................................................................................................... 25 1.7.1 Limitations .................................................................................................................................................... 26 1.8 Configure Forms Framework Enhancements ........................................................................................... 26 1.8.1 Performance Optimization in Forms Framework ........................................................................................... 34 1.9 Multiple Language Support (MLS) Utility .................................................................................................. 34 1.10 Config Schema Upload/ Download Settings ............................................................................................ 37 1.11 Database Password Reset/ Change ........................................................................................................ 37 1.12 Configure SSO Authentication ................................................................................................................. 38 Administration Guide Oracle Financial Services Software Confidential - Restricted 4 1 1 O OF FS SA AA AI I A Ad dm mi in ni is st tr ra at ti io on n This section consists of information related to module specific configurations. You can refer to the required sections appropriately. • Dimension Configuration: Alphanumeric and Numeric Codes • Hierarchy Node Internationalization • T2T and PR2 Query Performance Optimization • Configure Data Quality Rule Approval Parameters • Run Rule Framework Configuration • Configure Forms xml to execute Server Side Rule • Data Element Filters Classification • Configure Forms Framework Enhancements • Multiple Language Support (MLS) Utility • Config Schema Upload/ Download Settings • Database Password Reset/ Change • Configure SSO Authentication Conventions and Acronyms Conventions Description Actions are indicated in Bold AIX Advanced Interactive eXecutive EPM Enterprise Performance Management KBD Key Business Dimensions OEL Oracle Enterprise Linux OFSAAI Oracle Financial Services Analytical Applications Infrastructure RHEL Red Hat Enterprise Linux SQL Structured Query Language UDP User Defined Properties UMM Unified Metadata Manager T2T Table to Table Administration Guide Oracle Financial Services Software Confidential - Restricted 5 Conventions Description RRF Run Rule Framework 1 1. .1 1 D Di im me en ns si io on n C Co on nf fi ig gu ur ra at ti io on n: : A Al lp ph ha an nu um me er ri ic c a an nd d N Nu um me er ri ic c C Co od de es s This section explains the configuration changes for Alphanumeric Code enhancements introduced as part of 7.3.1.0.0 IR. OFSAAI supports both numeric and alphanumeric dimensions. Both dimension types require a numeric member code. An alphanumeric dimension will additionally store an alphanumeric member code. A numeric dimension can optionally store an alphanumeric code as well, but it will be equivalent to the numeric code value. After the successful installation of this IR, you may need to run SQL updates on the REV_DIMENSIONS_B table. This table stores the required dimension metadata including dimension member data type and the member column names for dimension member tables where the numeric and alphanumeric codes are stored. In the REV_DIMENSIONS_B table:  The column MEMBER_DATA_TYPE_CODE with value ’NUMBER’ identifies a dimension as numeric and value ‘VARCHAR2’ identifies a dimension as alphanumeric.  MEMBER_CODE_COLUMN specifies the member table column which holds the alphanumeric member code. This is optional for numeric dimensions, where alphanumeric and numeric member codes would be equivalent.  MEMBER_COL specifies the numeric member code column. NOTE: Any change done in REV_DIMENSIONS_B table requires web server restart since, the dimension definitions data in cache memory has to be refreshed. A new installation by default will have the seeded key dimensions configured as numeric, although those dimension member tables include a column for alphanumeric member codes. You can configure any of these dimensions as alphanumeric. For more information refer to Configure Alphanumeric Dimensions. You might also need to run some SQL updates for numeric dimensions. For more information refer to Configure Numeric Dimensions. 1 1. .1 1. .1 1 C Co on nf fi ig gu ur re e A Al lp ph ha an nu um me er ri ic c D Di im me en ns si io on ns s To configure an editable (numeric) dimension as alphanumeric and to remove the optional code attribute from prior releases you have to back up the affected dimension tables (like REV_DIMENSIONS_B, REV_DIM_ATTRIBUTES_B, REV_DIM_ATTRIBUTES_TL, and DIM_<DIMENSION>_ATTR) and perform the following steps on each applicable dimension. Administration Guide Oracle Financial Services Software Confidential - Restricted 6 1. Set the member type as alphanumeric (VARCHAR2) in REV_DIMENSIONS_B, and identify the member table’s alphanumeric code column name if it is not populated already. Update REV_DIMENSIONS_B SET Member_Data_Type_Code = ’VARCHAR2’ [, Member_Code_Column = ‘{Alphanumeric Column Name}’] Where Dimension_ID = {Dimension ID} Example: Update REV_DIMENSIONS_B SET Member_Data_Type_Code = 'VARCHAR2', Member_Code_Column = 'TP_PRODUCT_CODE' Where Dimension_ID = 5; NOTE: In OFSAAI 7.3, the seeded key dimensions have already populated MEMBER_CODE_COLUMN. 2. If there is an associated code attribute which is present from OFSAAI release 7.3 for capturing the alphanumeric member code, remove it manually as follows: If the attribute currently contains values:  Update the alphanumeric codes from the attribute table to the Member Code Column of the member table. I.e. Execute the Update_Dimension_Code procedure using steps detailed in the Data Model Utilities Guide. For example: Either run fn_updateDimensionCode from SQL Plus or use a Batch to run TRANSFORM DATA with the Update_Dimension_Code procedure for your Dimension ID.  Remove the attribute values from the dimension attribute table (DIM_<DIMENSION>_ATTR). For example, if you are updating the Common Chart of Accounts Dimension, where Attribute Name is ‘COMMON COA CODE’, Member_B_Table_Name is ‘DIM_COMMON_COA_B’, and Attribute Table Name is ‘DIM_COMMON_COA_ATTR’, execute the following statement: Delete from DIM_COMMON_COA_ATTR where Attribute_ID = (Select Attribute_ID from REV_DIM_ATTRIBUTES_TL where Attribute_Name = 'COMMON COA CODE' and dimension_id = (select dimension_id from REV_DIMENSIONS_B where member_b_table_name = 'DIM_COMMON_COA_B'));  Remove the attribute definition from REV_DIM_ATTRIBUTES_B & REV_DIM_ATTRIBUTES_TL tables. This is necessary to prevent the Dimension Administration Guide Oracle Financial Services Software Confidential - Restricted 7 Member UI from showing the code as an optional attribute, since it already displays the alphanumeric and numeric codes based on the member table.  Delete alphanumeric attribute metadata from ATTRIBUTE_B table. Example: Delete from REV_DIM_ATTRIBUTES_B where Attribute_ID = (Select Attribute_ID from REV_DIM_ATTRIBUTES_TL where Attribute_Name = 'COMMON COA CODE' and dimension_id = (select dimension_id from REV_DIMENSIONS_B where member_b_table_name = 'DIM_COMMON_COA_B'));  Delete alphanumeric attribute metadata from ATTRIBUTE_TL table. Example: Delete from REV_DIM_ATTRIBUTES_TL where Attribute_ID = (Select Attribute_ID from REV_DIM_ATTRIBUTES_TL where Attribute_Name = 'COMMON COA CODE' and dimension_id = (select dimension_id from REV_DIMENSIONS_B where member_b_table_name = 'DIM_COMMON_COA_B')); 3. In case any rows in the Dimension member table contain a null alphanumeric code even after running the fn_updateDimensionCode procedure, you need to manually run an SQL update as illustrated in the example below: Update DIM_GENERAL_LEDGER_B set GL_Account_Code = GL_Account_ID Where GL_Account_Code is null; Commit; 4. Save your changes using Commit; 1 1. .1 1. .2 2 C Co on nf fi ig gu ur re e N Nu um me er ri ic c D Di im me en ns si io on ns s If REV_DIMENSIONS_B.Member_Code_Column is populated for a dimension, any UI which displays an alphanumeric code will look in the specified uploads/Geographie/ ofsaai-administration-guide.pdf