Oracle Financial Services Financial Crimes and Compliance Management - Behavior Detection Application Pack v8.0.0.0.0 Minor Release #8 (8.0.8.0.0)

Description

OFS BD Application Pack v8.0.0.0.0 Minor Release #7 8.0.8.0.0 (ID 30422977)

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.8.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.8.0.0 version and cannot choose to upgrade only selective application packs to v8.0.8.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.8.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 Deprecated in This Release

       Known Issues in This Release

New Features 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.          Oracle Financial Services Know Your Customer has been upgraded in the following ways:

       Data structures created to capture internal and external regulatory reports being filed for KYC review as a part of EOD process.

       Adhoc adverse media request from UI - Arachnys Integration

       Display of questionnaire responses for onboarding assessment and cases

       Extension of KYC and CS real time integration

       Extended the pre-filtering rule for KYC

       Option for recalculation from the user interface

2.          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.8 to resolve issues or implement enhancements:

       Rapid Movements of Funds All Activity

       High Risk Transactions: High Risk Counter Party

       Anticipatory Profile: Expected Activity

       Escalation in Inactive Account

       Transactions in Round Amounts

       Large Reportable Transactions

       Single or Multiple Cash Transactions: Large Significant Transactions

       Change in Behavior: Previous Average Activity

       Patterns of Funds Transfers Between Internal Accounts and Customers

       Hub and Spoke

       Early Payoff or Paydown of a Credit Product

       Anomalies in ATM, Bank Card: Excessive Withdrawals

       High Risk Transactions: Focal High Risk Entity

3.       Oracle Financial Services Trade-Based Anti Money Laundering has been updated in the following ways:

       A new scenario, Anticipatory Profile Expected Goods/Services, has been added.

       The following existing scenarios have been modified in 8.0.8 to resolve issues or implement enhancements:

       Customer Involved with Parties in High Risk Geography

       Significant Number of Amendments

       Deviation From Peer Group � Commodity Price Change

       Inconsistent Shipping

       Change in Behavior: Significant Change in Commodity Price

       Change in Behavior: Commodity Shift

       Change in Behavior: High Risk Country Shift

       Change in Behavior: Region Shift

       TBAML integration with Oracle Enterprise Case Management has been updated to implement the following enhancements:

       Third-party lending area for external events

       Custom goods screening for dual use goods, prohibited, restricted

       Updated the ECM user interface to include:

       Transactions grid

       Screening events- match highlight feature

       Show multiple SWIFT messages

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.

Bugs Fixed in This Release

The following issues have been resolved in OFS BD Release 8.0.8.0.0.

Component

Bug ID

Description

CTR

29113013

Value for the Prior Case in the KYC Customer Dashboard displays incorrect count of open cases.

Features De-supported/Deprecated in This Release   

With the release of Behavior Detection Framework (BDF) 8.0.5, dispositioning alerts through Alert Management (AM) is no longer supported. �AM is only applicable to Trading Compliance and Broker Compliance. For AML and Fraud alerts, the Event Correlation module in Enterprise Case Management (ECM) should be used to correlate events from the FCCM Behavior Detection engine or those ingested from external applications. AM can be used as read-only for viewing historical alerts but it is not to be used for investigating alerts, taking action on alerts, editing alerts and/or promoting alerts to a case.�� The manual Promote to Case functionality is no longer supported.� Customers are to use ECM for reviewing and investigating alerts.�� A restricted use license of ECM is provided with the BDF license which replicates the functionality available in AM to the best that is currently available within ECM.� Implementations should use event correlation to move Alerts from BDF into ECM and then use alert correlation/promote to a case where all levels of investigation can occur.� If this updated process is not clear to your implementation team it is advised that you contact Oracle Partner Network or Oracle Consulting to be trained.

Known Issues/Limitations in This Release

The known issues / limitations in OFS BD Release 8.0.8.0.0 are as follows.

Component

Bug ID

Description

CTR

27979365

Home page does not display correctly. It is not utilizing all available space.

Common Processing

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.

FATCA

28967708

FATCA Report Context is not getting refreshed when an action is taken on 
a report.

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.

29113013

Value for the Prior Case in the KYC Customer Dashboard displays incorrect count of open cases.

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.

29114115

27557961

When monthly scenarios are executed on non-business days, they consider the previous month rather than the expected month.� For example, if November 1 is a non-business day, the scenario generates alerts based on trades occurring in September, rather than October.

User Interface

 

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.