OFS
CAP Application Pack v8.0.0.0.0 Minor Release #2 - 8.0.2.0.0 (23731217)
This
release of OFS CAP Application Pack is cumulative of all enhancements and bug
fixes done since v8.0.0.0.0 release.
The
minimum patch set level should be OFS
CAP Application Pack v8.0.0.0.0.
For detailed instructions on
installing this OFS CAP Release, refer to OFS CAP
Installation and Configuration Guide 8.0.2.0.0 in OTN
Documentation Library.
Note: Starting 8.0.0.0.0 release, OFSAA applications are packaged and
released as Application Packs.
Oracle
Financial Services Capital Adequacy Pack Applications
This
section includes the following sub-sections:
· New Features in this Release
· List of Bugs Fixed in This Release
· Known Issues/Limitations in This Release
Following
is the list of features incorporated in this release. For detailed information
on usage of these features, refer to the 8.0.2.0.0
User Guides of OFS CAP applications from OTN
Documentation Library.
Enhancements in Basel Applications
CBRC –
Standardized Approach: This feature caters to the
standardized approach as per the regulations issued by China (CBRC). It
includes the various reclassifications and treatment of exposures as per the
RWA treatment and the capital treatment prescribed by the Chinese regulator.
CBRC – Internal
ratings-based Approach: This feature caters to the internal
ratings-based approach as per the regulations issued by China (CBRC). It
includes the various reclassifications and treatment of exposures as per the
RWA treatment and the capital treatment prescribed by the Chinese regulator for
the advanced approach banks.
RWA Forecasting: RWA Forecasting is mandatory for the banks as a result of the
Comprehensive Capital Analysis Review (CCAR) regulations, which are specific to
US. These regulations mandate the reporting of the forecasted capital and RWA
figures for nine quarters and five years in total.
Attribution
Analysis: This analytical feature aims at helping the
banks to attribute the risk-weighted assets and capital changes to various
factors across two comparable executions for Basel. This feature is supported
for the factors under Credit Risk, Market Risk, Operational Risk, and Capital
Structure. The supporting reports are also available in the Basel Dashboard for
the same.
Enhancements
in Operational Risk Economic Capital Application
The
objective of Oracle Financial Services Operational Risk Economic Capital
application is to calculate risk measures such as Operational Risk Value at
Risk (VaR), Conditional VaR,
Expected, and Unexpected Loss arising due to Operational Risk by executing loss
distribution modeling on the historical data of the financial institution. Data
can include internal loss data and scenario estimates of the financial
institution, and external loss data. Insurance benefit adjustments are also
supported. OREC product supports these functionalities through following
product features:
OREC Production
·
Units of
Measure:
An Operational Risk Category (ORC) or Unit of Measure (UOM) is the level (for
example, organizational unit, operational loss event type, risk category, and
so on) at which the financial institution's quantification model generates a
separate distribution for estimating potential operational losses. This term
identifies a category of operational risk that is homogeneous in terms of the
risks covered and the data available to analyze those risks. OREC application
allows defining of mappings between various common dimensions forming Units of
Measure.
·
Calculation
Dataset: This
is the main assumption set for OREC modelling. This helps you to define
features such as minimum time window to be used for modelling, dates to be
considered for various types of losses, loss amount type to be considered for
modelling, outlier handling methods, various data inclusion / exclusion
filters, insurance benefit cap, and so on. Calculation dataset can be modelled
to arrive at proper granularity (UOM mappings), De Minimis threshold, EVT
threshold, shift amount, and so on. This definition has an approval workflow.
This acts as a onetime definition which can be re-used across models and
ensures uniformity and consistency.
·
Data
Preparation:
Data Preparation feature aids in moving Internal Losses, External Losses,
Scenarios and Insurance Policies from staging area to the processing area. Data
Preparation allows setting up various rules for moving data from stage area to
processing area. This data can further be used for Sandbox modelling and
Capital Calculation. Data Preparation supports Internal and External loss data
Scaling, Currency Conversion, Reclassification and UOM mapping.
OREC Sandbox Model
·
External Loss
Data Scaling:
This Sandbox model supports factor based power law scaling. This method assumes
existence of a universal power-law relationship between the operational loss
amount within a certain time period and the size and exposure towards
operational risk within a certain time period of different financial
institutions. Various scaling factors such as Gross Income, Asset Size, Profit,
Volume of Transaction, and so on, representing size and exposure can be used.
Linear Regression is used to establish a relationship between loss and scaling
factor.
· Calculation Dataset Modelling: The
Calculation Dataset which is defined in Production Infodom can be modelled in
Sandbox Infodom. Assumptions defined can be modelled to check their behavior.
The Dataset Modelling facilitates the following:
•
Different UOM combinations can be tried out to decide which UOMs
to merge, based on their data nature.
•
The time window for each UOM can be decided. This can be over and
above the minimum time window specified by Dataset in Production. This
flexibility overcomes the data scarcity problem in some UOMs.
•
Decide the De-Minimis threshold for different UOMs. This is required
for severity modelling.
•
Decide whether to include the near miss, gains, pending losses,
and so on at each UOM.
·
Loss Frequency
Modelling:
Frequency modelling allows modelers to finalize the frequency distribution for
an UOM after checking EDA, fitting various distributions, checking the
parameters, and Goodness of Fit output and other indicators such as PDF, CDF,
PP plot, and QQ plot.
·
Loss Severity
Modelling:
Severity modelling allows modelers to finalize the severity distribution for an
UOM after checking EDA, fitting various distributions, checking the parameters,
GOF output and other indicators such as PDF, CDF, PP plot, QQ plot. Shifted,
truncated, and non-truncated distributions can be fitted. They are mutually
exclusive. Single Severity Distribution or EVT covering body distribution and
tail distributions is also supported.
·
Scenario
Modelling:
The OREC application facilitates the modelling of scenarios and finalize the
frequency and severity distribution and their parameters for different scenario
assessment approaches. Scenario modelling is enhanced to support modelling of
additional assessment approaches such as percentile method. A joint
distribution using loss and scenario can be modelled. This is in addition to
the existing methods where loss and scenario can be modelled separately and
combined using weights.
·
Correlation: The
Correlation model is used to define Correlation and Copula for Loss Data and
Scenario. In case of loss data, correlation and copula matrix is generated
between UOMs. This reflects the dependency structure between UOMs. In case of
Scenario Correlation, correlation and copula matrix is generated between
Scenarios. This reflects the dependency between Scenarios, that is, chance of
multiple scenarios happening together.
OREC Capital Calculation and Allocation
·
Capital
Calculation Model: Capital Calculation Model is defined in OREC Production to
capture the inputs for estimating Operational Risk Capital. After definition,
execution of this model results in calculation of all the required risk
measures such as Operational Risk VaR, Conditional VaR, Expected Loss, and Unexpected Loss for various UOMs
and firm level followed by allocation of capital to various Legal Entities and
Lines of Businesses.
·
Capital
Allocation Model: Capital Allocation is required to allocate the capital numbers
calculated by executing a Capital Calculation Run. Capital numbers calculated
can be allocated back to Units of Measure, Lines of Business, and Legal
Entities.
R Integration
and Extensibility: All the sandbox and production models are integrated with R
software. Various statistical techniques are registered using OFSAA Modelling
Framework and integrated with OREC application. New R techniques can be
registered and integrated with OREC application at client site.
List
of Bugs Fixed in This Release
|
Component |
Sub Component |
Bug No |
Subject/Description |
|
Engines/Backend
Components |
OPTIMIZER |
23549146 |
POST
MITIGATION RWA IS GREATER THAN PRE MITIGATION RWA IN BASEL BATCH |
|
23564997 |
OPTIMIZER CRE ENGINE
BUILD ISSUE ON SOLARIS |
Known Issues/Limitations in This Release
|
Component |
Sub
Component |
Bug No |
Subject/Description |
|
Install and
Upgrade Issues |
|
23581627 |
CAP 8.0.2 ON 8.0.1 - SOLARIS AND WEBLOGIC : ERRORS IN 8.0.2
INSTALLATION LOG |
Oracle Financial Services Analytical Applications Infrastructure
This
section includes the following sub-sections:
· New Features in This Release
· List of Bugs Fixed in This Release
· Known Issues/Limitations in This Release
New Features in This Release for OFSAAI
Following
is the list of new features incorporated in this release. For detailed
information on usage of these features, refer to OFSAAI
8.0.2.0.0 User Guide in OTN
Documentation Library.
The
following features are introduced in this release:
Data Management Tools
· Table creation
on the fly from Data File Mapping and Data Mapping screens is introduced. This
allows you to add dynamic tables into the data model within OFSAA ecosystem.
· Query validation
is made optional while saving Data Mapping definition through the introduction
of a new configuration parameter.
· To limit the
number of records that needs to be loaded, a new target property (RecordLoadLimit) is introduced in Data Mapping definition.
Data Quality Framework
· Dynamic Degree
of parallelism for RDBMS is supported.
· Referential
Integrity checks can be defined using composite key columns.
System Configuration & Identity
Management
· Users can be
optionally created or modified to get authenticated using OFSAA Security
Management System in case LDAP authentication is configured.
· Audit Trail
report has been enhanced to show detailed information for various operations
such as User -User Group map, User Group-Domain map, User Group- Role map, User
Group –Folder-Role map, Role-Function map and Profile Holiday Map.
Business Metadata Management
· Derived Entity
definition supports creating materialized views with option to refresh
fast/force/complete on demand/commit and query rewrite.
Forms Framework
· Forms Framework
has been enhanced to render Forms with CSS3 and HTML 5 constructs in addition
to support of HTML 3. This is to enable support of Standards Mode and rendering
of HTML pages in Internet Explorer and Google Chrome.
· Migration of
Tabs and Layout details is supported for Object Migration Command line utility.
· The behavior of
the type 102 control can be changed to either single select or multi-select
based on a particular column value of the grid.
List of Bugs Addressed in this Release
|
Component |
Sub component |
Bug ID |
Description |
|
Administration |
Utilities |
21328053 |
INFODOM DROPDOWN IN "USER GROUP-BATCH EXECUTION MAP"
SCREEN SHOWS FULL LIST |
|
Object Migration |
22446723 |
OBJECT MIGRATION SHOULD PERSIST SOURCE AND TARGET OBJECT IDS
INTO DATABASE |
|
|
Data Entry Forms and Queries |
Data Entry |
21339271 |
NUMBER FORMAT CAUSES EDIT TO FAIL WITH SPECIAL CHARACTER NOT
ALLOWED ALERT |
|
Data Loading |
- |
21173111 |
'ORA-12899: VALUE TOO LARGE FOR COLUMN' IN MESSAGESERVER LOG
RUNNING F2T |
|
Forms Framework |
- |
20598965 |
MENU AND DROP DOWN OVERLAP |
|
GRC Infrastructure |
- |
22459967 |
SEARCH FUNCTIONALITY NOT WORKING IN KBD PREFERENCE SUMMARY PAGE
FOR OTHER LOCALE |
|
|
- |
22459895 |
KBD MAPPER AND CHECKER SCREEN NOT GETTING TRANSLATED IN OTHER
LOCALES |
|
|
Business Restructure |
21625588 |
MULTI LOCALE SUPPORT IN BUSINESS RESTRUCTURE |
|
Install and Upgrade Issues |
Service Packs |
21915445 |
PATCH INSTALLER DOES NOT VALIDATE FOR SESSION LEVEL SHELL AND
PROCEEDS WITH BASH |
|
Base Installer |
21810719 |
ENVCHECK.SH CHECKS NLS_LENGTH_SEMANTICS DATABASE SETTING AT
SESSION LEVEL |
|
|
20727720 |
EDITABLE INFORMATION DOMAIN NAME FIELD IS NOT USER FRIENDLY |
||
|
Metadata such as T2T, F2T, etc |
T2T Issues |
21812780 |
T2T FINISHES SUCCESSFULLY WHEN REJECTION THRESHOLD EXCEEDED |
|
- |
22539004 |
T2F TASKS ARE FAILING |
|
|
Operations |
Batch Monitor |
21949567 |
API'S REQUIRED TO TRACK THE BATCH STATUS |
|
Rules Framework |
|
22486848 |
WSMREREQUEST.SH FAILED WITH ORA-12899 |
|
System Configuration |
Configuration |
22453450 |
APPLICATION ID IS NOT DISPLAYING CORRECT FOR OTHER LOCALES IN
MODIFY/VIEW SCREEN |
|
Information Domain |
21484146 |
ADD PERSISTENCE UNIT ENTRY IN GRCPERSISTENCE&PERSISTENCE
DURING INFODOM CREATION |
|
|
Security Management System |
- |
21697204 |
UCP CONNECTION POOL FAILING IN ALL THE LAYERS |
|
Unified Metadata Manager |
Business Metadata Management |
21367887 |
$MISDATE,$RUNSK DOES NOT WORK
IN DATA SET ANSI JOIN SUBQUERIES |
|
20760616 |
NEED SPECIAL CHARACTERS IN
HIERARCHY SHORT DESCRIPTION |
||
|
Data Quality Definition |
20511796 |
CHANGE IN ALERT MESSAGE IN DQ
LIST OF VALUES CHECK RULE WHEN FILTER TYPE IS CODE |
|
|
- |
21464164 |
MAPPER SCREEN PAGE IS TAKING
TOO MUCH TIME TO LOAD AND SAVE |
|
|
Metadata Browser |
22455350 |
MDB>DATA SOURCES MENU IS NOT
TRANSLATED TO OTHER LOCALES |
|
|
Workflow Framework |
- |
21610478 |
UNABLE TO ADD MORE THAN ONE
DATA FIELD |
Known Issues/Limitations in this Release
· Model upload option (Erwin or DB
Catalog) mode for the subsequent uploads is not same as the initial upload
mode.
· Exporting object type with code
2000 (User) fails if FAILONERROR is set to N.
· Dynamic table created during Data
File Mapping has incorrect column data types.
· Data Mapping
screen alignment changes if tables selected are with big names.
· Description is not getting updated in Excel Upload edit mode.
· Export with Include Search Info option for Type =1 container is
not showing search information when exported to Excel Sheet.