Description
OFS
BD Application Pack v8.0.0.0.0 Minor Release #6 8.0.6.0.0 (ID 28080815)
This
release of OFS BD Application Pack is cumulative of all enhancements and bug
fixes done since v8.0.0.0.0
release.
Prerequisites
Release 8.0.6.0.0 of the Oracle Financial Services Behavior
Detection Application Pack is not fully backward compatible with earlier
versions of FCCM applications. You must upgrade all of your FCCM applications
from existing 8.0.x versions to 8.0.6.0.0 version and cannot choose to upgrade
only selective application packs to v8.0.6.0.0.
How to Apply This Release?
For
detailed instructions on installing this OFS BD Release, see OFS BD Application Pack
Installation and Configuration Guide 8.0.6.0.0.
Due
to the future deprecation of the CSA field, V_TYPE, in the STG_PARTY_MASTER,
the Customer Type (CUST_TYPE_CD) in the Customer (CUST) table will be derived,
therefore the following CSA fields are required to be populated:
·
Stg_Party_Master.f_financial_entity_ind
·
STG_PARTY_MASTER.v_party_type
In
addition, the CSA table, STG_PARTY_TYPE_MASTER, must be populated.
· STG_PARTY_TYPE_MASTER.v_party_category
Refer
to the BD FSDF Download Specification document for detailed
descriptions of the CSA fields mentioned above.
In
addition, when populating the STG_PARTY_TYPE_MASTER
CSA table, the table may contain the suggested code values as follows:
|
v_party_type_code |
v_party_type_desc |
v_party_category |
|
IND |
Individual |
I |
|
FIN |
Financial |
C |
|
ORG |
Other
Organization |
C |
|
[ANY ADDITIONAL FIRM SPECIFIED CODES] |
|
I or C |
The value in the STG_PARTY_MASTER.v_party_type field must contain a value present in the v_party_type_code field of the Stg_Party_Type_Master table.
Oracle Financial Services Behavior Detection
This section includes the following sub-sections:
· New Features in This Release
· Bugs Fixed in This Release
· Features De-supported/Deprecated in This Release
·
Known Issues/Limitations in This Release
Following is the list of new features incorporated in this release. For detailed information on usage of these features, see the various OFS BD Application Pack User Guides.
1. All Oracle Financial Services Behavior Detection Applications have been enhanced in the following ways:
·
New
OFSAA Landing page showing the available Applications for which a user has
access. Support for Single Page Applications using Oracle JET Forms that makes
use of JET based widgets.
·
New
style sheets have been applied which complement the HTML5 layout approach.
Single point configuration to switch theme and revert to earlier theme.
·
Document
Management using CMIS (Content Management Interoperability Services), an OASIS
standard enabling information sharing between different Content Management
Systems. OFSAA Forms Framework and OJET framework has been enhanced to support
doc upload/search with tie in to CMIS repository.
2. Oracle Financial Services Behavior Detection Alert Management has been enhanced in the following ways.
·
Historical
Data Copy (HDC) now supports archiving of data in CLOB fields.
·
General
Data Protection Regulation (GDPR) Compliance updates include:
·
Data
Redaction – To restrict Personally Identifying Information (PII) access based
on Roles
·
Right
to be forgotten – To randomize the requested customer
·
Encryption
– To restrict access to files
·
Log 4
J version 2– For security reasons
·
Audit
3. Oracle Financial Services FCCM Analytics has been enhanced in the following ways:
·
The
following reports have been introduced:
·
Transaction
Monitoring Report
·
Transaction
Volume Report
·
Pre-Cases,
Correlation, and Event related tables are added to ECM subject area.
·
The
Business Catalog has been enhanced to support Case Audit History, such that
Link & Merge, and Admin Actions are reportable.
·
The
Statement View has been enhanced to work for both standalone ECM and third
party AML.
·
The
product model has been changed from Alert based to Event based to improve
usability.
4. Oracle Financial Services Know Your Customer has been upgraded in the following ways:
·
Manual override of the periodic re-review risk assessment date
·
Manual
override of the risk score expiration date
5. Oracle Financial Services FATCA Management has been upgraded in the following ways:
· FATCA Canada Reporting template updated to latest version.
6. Oracle Financial Services Common Reporting Standard (CRS) application has been upgraded in the following ways:
· New CRS Reporting templates for Canada, United Kingdom,
Singapore, and Hong Kong.
7.
Oracle Financial Services Currency Transaction
Reporting (CTR) application has been upgraded in the following ways:
· Introduction of Person Master and Person Address Master to support retention and use of user updates to frequently appearing Person Involved entities.
· Updates to de-duplication processing to handle CTRs with overlapping transactions that are not true duplicates or superseding CTR.
· The Bank Secrecy Act Currency Transaction Report scenario has been modified to support CTR generation at an ultimate parent level using Party To Party Relationships.
· UI and Functionality Updates:
· Configurable ability to file a Person Involved with multiple addresses.
· Ability to add a new person involved and associate them to a transaction on the current CTR.
· Additional fields added for edit of a transaction (foreign amounts and country).
· Additional search criteria for location; results list updated to display location.
· Ability to configure standard comments; available as part of actions taken.
· Account Trim feature to ensure passing in publicly available, non-modified account identifiers to FinCEN.
· Updates to workflow metadata for better OOB support for rework and correct/amend actions.
· Closed gap for use of Affiliated Bank static data for Exemption filing.
· Added “Jump to Page” functionality on Search results to be consistent with other applications.
· Document upload/download integration with CMIS standard.
8. Oracle Financial Services Anti Money Laundering/ Institutional Anti Money Laundering has been updated in the following ways:
The following existing scenarios have been modified in 8.0.6 to resolve issues or implement enhancements:
· Anomalies in ATM, Bank Card – Excessive Withdrawals
· CIB - Product Utilization Shift
· CIB – High Risk Geography Activity:
· CIB – Significant Change from Previous Peak Activity
· Frequent Changes to Instructions
· High Risk Transactions – High Risk Geography
· Hub and Spoke
· Large Reportable Transactions
· Patterns of Funds Transfers Between Internal Accounts and Customers
· Patterns of Recurring Originators/Beneficiaries in Funds Transfers
· Transactions in Round Amounts
For detailed information on installation, configuration, and usage of features, see Oracle Financial Services Behavior Detection Applications Pack Installation Guide from the OHC Documentation Library.
For more information on the OFS AAI requirements, see OFS Advanced Analytical Applications Infrastructure Application Pack in the OHC Documentation Library.
Enter the resolved issues in a table here.
Features De-supported/Deprecated in This Release
Enter any de-supported features here.
Known Issues/Limitations in This Release
The known issues /
limitations in OFS BD Release 8.0.6.0.0 are as follows.
|
Component |
Bug ID |
Description |
|
Alert Management |
28019750 |
Performance issues
with Alert Management when using Internet Explorer. |
|
CTR |
27010253 |
When Expand All action
is taken in the Transaction tab, the Include Shared Branching checkbox gets
un-checked. |
|
27983892 |
The Export to Excel,
Email, and Download E-File actions are not functioning from the E-File List
Page. |
|
|
27979365 |
Home page does not
display correctly. It is not utilizing all available space. |
|
|
22595644 |
Clients using OFSDF
CSA and implementing the Currency Transaction Reporting (CTR) application may
experience a failure during batch load of the Currency Transaction table if
the data is being sourced from the STG_CARDS_PAYMENT_TXNS table. |
|
|
28040040 |
The copyright footer,
on entry to a page, may appear inappropriately in the middle of the page. On
refresh of page it displays correctly. |
|
|
CRS |
27938246 |
The CRS UK template
revised report is not getting generated with all data. Users will not be able
to submit any amended/void reports using the application. |
|
Data Model |
27992814 |
Hive H2Ts and T2H
files are failing. This will be corrected in a post-8.0.6.0.0 patch. |
|
FATCA |
27129575 26917605 |
Enterprise Case
Management is not integrated with FATCA and no FATCA cases will be available. |
|
KYC |
25482263 |
Customer Submitted
Documents unable to view in the UI due to documents not being moved from file
system to KYC system. The documents can be referred outside KYC system. |
|
28000097 |
The Online Help guide
is not displaying. |
|
|
25563976 |
For KYC Case
Assignment to occur, it is expected to have a Mantas batch to be open,
although KYC is independent of Mantas batch. |
|
|
Scenario |
22545134 |
An error message may
be displayed when a user tries to review and save a scenario created using
the scenario wizard tool. |
|
22586745 |
For some security
focus scenarios, the Focal Entity Display ID may not be populated due to an
incorrect mapping of the underlying scenario data to the resulting alert
review record. This will result in the Focus column on the UI displaying as
null. |
|
|
User Interface |
20194576 |
For clients using the Personal Trading
Approval (PTA) application, new fields and options are visible on the
Questionnaires Administration screens to Admin users. These fields are not
used by PTA and can be ignored. |
|
22231998 |
When searching for a
specific link on the Network Graph using the highlight tool, sometimes
invalid links show up in the list for selection. |
|
|
22267893 |
For clients using KYC
application, after the risk assessments are promoted to case, under Customer
tab in case management only ‘Risk Information’ and ‘Details’ options will
have data and other options will not have data. |
|
|
20668259 |
When Ingestion is run,
the following warning messages related to batch and calendar maintenance may
display in some logs: WARN CALENDAR_MANAGER
- Message 265050: The Calendar name 'SYSCAL' has no Holidays specified. FATAL BATCH_CONTROL -
Message 265032: Some Batch Processes are already running. WARN FDT - Message
30102: Date 20091213 out of bounds for calendar SYSCA These messages can be
ignored as there is no functional impact. |