This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Module | Feature | Notes |
|---|---|---|---|
| 29 NOV 2023 | Created initial document. |
HAVE AN IDEA?
We’re here and we’re listening. If you have a suggestion on how to make our cloud services even better then go ahead and tell us. There are several ways to submit your ideas, for example, through the Ideas Lab on Oracle Customer Connect. Wherever you see this icon after the feature name it means we delivered one of your ideas.
GIVE US FEEDBACK
We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com.
DISCLAIMER
The information contained in this document may include statements about Oracle’s product development plans. Many factors can materially affect Oracle’s product development plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.
This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.
Column Definitions:
Report = New or modified, Oracle-delivered, ready to run reports.
UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.
| Ready for Use by End Users Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features. |
Customer Must Take Action before Use by End Users Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing. |
|||||
|---|---|---|---|---|---|---|
| Feature |
Report |
UI or |
UI or |
|
||
Financial Crime and Compliance Management
This document provides the high-level enhancements for Release 23.11.1 of Oracle FCCM Cloud Service. For more information about this product, see product Documentation. Known Issues and Maintenance Pack information can be found at MOS.
The data-loading service supports multiple data origin files to load data into the stage tables with different batches having different Data Origins.There are no changes for existing or single data origin customers.
Supporting multiple data origins allows batches with different data origins to run, reducing run time and increasing performance.
Steps to Enable
To execute batches using multiple data origin, you must update the Schedule Batch parameters.
Key Resources
Multiple Data Origin Support Pipeline Updates
The following data pipelines have been updated in this release to support multiple data origin and parallel runs:
- Load Intermediate Account and Transaction Data
- Load And Prepare Watchlist
- Load Customer Data
- Load Customer Add On Data
- Load Customer Anticipatory Profile Data
- Load Account Data
- Load Account Group Data
- Load Additional Account Data
- Load Account Anticipatory Profile Data
- Load Customer Mapping Data
- Derive Risk and Load Supplementary Information
- Load Transaction Data and Derive External Entities and Risk
- Load Trusted Pair
- Load Loan Data
- Load Insurance Data
Updated pipelines provide better performance and increased functionality
Steps to Enable
- Copy the new version of the pipeline and create a new Job using similar naming conventions.
- Attach the newly created job to the existing Ingestion batch for the changes to be reflected.
Key Resources
The following new data pipeline has been added in this release to support table partitions creation and maintenance:
- Partition_Maintenance
The following data pipelines have been updated in this release:
- Load and Prepare Watchlist: Updated to support correctly populating watchlist members who are present in more than one watchlist.
- Load Account Data: Updated to enable a data quality (DQ) check. Do not disable the DQ during copy or customization of pipelines.
- Load Customer Data:Updated to enable a data quality (DQ) check. Do not disable the DQ during copy or customization of pipelines.
- Load Transaction Data and Derive External Entities and Risk:Updated to enable a data quality (DQ) check. Do not disable the DQ during copy or customization of pipelines.
Updated pipelines provide better performance and increased functionality
Steps to Enable
- Copy the new version of the pipeline and create a new Job using similar naming conventions.
- Attach the newly created job to the existing Ingestion batch for the changes to be reflected.
Key Resources
A new Maintenance Batch has been added in this release to support for table partitions creation and maintenance.
In addition, the Ingestion batch has been updated to replace the DropTempTables task with CleanAMTempData. You must copy the new Ingestion batch for the changes to be reflected.
Updated batches provide better performance and increased functionality
Steps to Enable
Copy the new Ingestion batch for the changes to be reflected.
Key Resources
The Oracle FCCM Transaction Monitoring Cloud Service Data Model has been updated in this release in the following ways:
- In the STG_PARTY_PRODUCT table, the V_PROD_CATG column has been updated to accept the 'LOAN' and 'INS' values.
These updates help ensure that staging data is provided in the format expected by the user interface.
Steps to Enable
Provide these values in the V_PROD_CATG column as needed.
Key Resources
The following data pipelines have been updated in this release to improve performance:
- Load Customer Business Data to Case Management: Updated the removal of CM Customer Business Tables to reduce the overall time taken by CM Ingestion Batch.
- Load Account Business Data to Case Management : Updated the removal of CM Account Business Tables to reduce the overall time taken by CM Ingestion Batch.
- Load External Entity Business Data to Case Management: Updated the removal of CM External Entity Business Tables to reduce the overall time taken by CM Ingestion Batch.
- Load Transaction Business Data to Case Management: Updated the removal of CM Transaction Tables to reduce the overall time taken by CM Ingestion Batch.
Updated pipelines provide better performance and reduce time taken by the CM Ingestion batch.
Steps to Enable
If the out of the box Pipeline and Batches are used, then no changes are required. However, if you have copied the pipeline, batch, or created Customized batches and provided new names for these pipelines and batches, you must follow the steps below:
- Copy the new version of the pipeline and create a new Job using similar naming conventions.
- Attach the newly created job to the existing CM Ingestion batch for the changes to be reflected.
Key Resources
KYC Integration with Third Party Case Management System
KYC now supports integration with a third-party case management system for both Onboarding and Continuous Monitoring.
For Onboarding, a third-party case management system can integrate with the existing KYC Feedback API to fetch risk assessments of all applicants for a given KYC application.
For Continuous Monitoring, a new pipeline KYC Customer RA Export has been added to export the risk assessments. This will generate a .CSV file containing the required risk assessments, which will be available in the object store. This can be fed into an External Case Management system for further investigation.
A new, pre-configured batch, KYCCustomerRAExport, also contains the KYC Customer RA Export pipeline. You can run this batch independently or create an additional task in the KYCDaily or KYCDeploymentInitiation batch and map it to the KYC Customer RA Export pipeline.
The investigation feedback for each risk assessment can be pushed to KYC from the external case management system as a CSV file available in the object store. This feedback intelligence is updated in KYC as part of the KYCDaily batch run using the pre-configured Load CRM Feedback to KYC pipeline.
Supporting third-party case management systems allows clients to integrate Oracle KYC with their existing case management systems.
Steps to Enable
Follow the steps found in “Integrating KYC with External Case Management System” in the KYC CS Administration Guide.
Key Resources
Increased Coverage for Customer Risk Scoring
The following new out of the box risk parameters are included for KYC Continuous monitoring:
- Customer Segment - Refers to the customer segment for the applicant (for example. Retail Banking - Individual, Priority Banking, SME, Corporate Banking, Wealth Management and so on.)
- Length of Banking Relationship – Indicates customer relationship with client in Years
- Expected to Transact with High Risk Cntry - Flag to indicate if the customer is expected to transact with a pre-defined high risk country list (Y/N)
- Stated Total Annual Turnover - Total declared turnover amount for a legal entity
- Annual Cash Transaction Threshold Percentage- Percentage Value indicating proportion of annual cash transaction amount compared to overall annual transaction amount (For example, 25%, 40%)
- Related Party is National of Sanctioned Country Flag- Flag indicating if primary customer or any of the related party is national of a Sanctioned country (Y/N)
- Region Company Is Licensed To Operate In - Value indicating where the company is licensed to operate in a jurisdiction (like Special Economic Zone, Main land)
- Stated Total Annual Income Base - Total declared turnover amount for an individual
- PEP Flag - Flag indicating if the customer is a PEP (Y/N)
- Related Party is PEP Flag - Flag indicating if any of the related party is a PEP (Y/N)
- SAR or STR Filed Flag - Flag indicating if SAR or STR is filed for the customer (Y/N)
Increased coverage allows organizations to better detect behaviors of interest.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
Increased Coverage for Change Log Attributes
The following new out-of-the-box risk factors are included for Accelerated Re-review (ARR) - based Customer Risk Assessment:
- Country of Residence
- Primary Source of Income
- Industry Code
- Ownership Structure – Ownership structure of a legal entity
- Customer Segment
- Expected to Transact with High Risk Cntry
- Stated Total Annual Turnover
- Annual Cash Transaction Threshold Percentage
- Related Party is National of Sanctioned Country Flag
- Region Company Is Licensed To Operate In
- Stated Total Annual Income Base
- PEP Flag
- Related Party is PEP Flag
- SAR or STR Filed Flag
Increased coverage allows organizations to better detect behaviors of interest.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
Bulk Export of KYC Risk Assessment Records
KYC now supports the bulk export of KYC Customer Risk Assessment records that may be required for one-off audit or investigation purpose. Similar to the export risk assessments functionality in the KYC Customer Risk Assessment screen, the customer risk assessments can be exported using this batch in the form of a CSV file.
A new pipeline and job, Customer Risk Assessment Export, have been introduced in this release to support this function. By default, this pipeline exports Customer Risk Assessments generated in the last 7 days.
Bulk export of KYC Customer Risk Assessment records allows clients to easily export these records as needed for audit or investigation purposes.
Steps to Enable
Follow the steps given in “Exporting KYC Risk Assessments” in the Using Pipeline Designer Guide for more details.
Key Resources
The following new staging tables have been added to the Know Your Customer Cloud Service Data Model in this release:
- STG_FCC_CRM_FEEDBACK
- STG_PARTY_OP_ECONOMIC_ZONE
These updates help ensure that staging data is provided in the format expected by the user interface.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
Support for Customer Screening Batch Cases
Investigation Hub Cloud service now supports the Customer Screening case type, which allows for disposition of potential customer screening matches.
Supporting Customer Screening cases allows users to investigate cases which correspond to the source of the data and the categorization of the watchlist record.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
Role-Based Functional Permissions
Security layers control how users interact with the application. User access is subject to functional permissions, which dictate the actions available to the users.In order to allow users to access functions in the application, Administrators must classify users and the functions they are permitted to access. Users can perform only those activities associated with their user group throughout the functional areas in the application.
User-role based access allows administrators to provide access only to the functions and cases which are most pertinent to each user group.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
Users can now take action on multiple cases using Bulk Action from the Case List view instead of taking individual case for action.
By taking action on multiple cases at once, investigators can quickly disposition cases, saving time to focus on investigating the most pertinent cases.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
'Year of Birth' is available as a screening parameter for creating match rules and displayed in case details.
This new parameter will help obtain more accurate matches.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
For the Day 0 screening (initial screening of customer data), clients must screen their entire customer base against all watchlists. This process can be time-consuming and resource-demanding. Any failure during this batch forces us to repeat the entire batch. To address this challenge, we have introduced the Data Slicing feature. This functionality empowers users to partition their data on the Day 0 screening, facilitating the screening of smaller, more manageable chunks or slices of customer data.
Consequently, this reduces resource requirements and the time needed for the screening process.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
Additional fields are added in the private watchlist to record the reason for adding an individual/entity in the private watchlist.
Added watchlist hyperlinks to Case details to help in better analysis of matches.
Additional information about the reason an individual or entity was added to a watchlist provides investigators with greater insight.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
The following batches have been added in this release:
- IndividualDIScreening
- EntityDIScreening
- Individual314aDIScreening
- Entity314aDIScreening
Updated batches provide better performance and increased functionality
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
The following bugs were updated in this release:
- Corrected HMT watchlist Data loss bug: Group Type "Vessel" and records having 4000+ Characters were not being loaded.
- Corrected OFAC Data Duplication Bug: A few records (with the same unique key) were duplicated, which caused problems while generating alerts.
Fixing bugs enhances the user experience by ensuring that the application performs as expected, free of interruptions and errors.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
Analysts can now send an Exemption from the Case Details/Events table a name or narrative-related events.
Supervisor users now have access to a standalone Exemption Management tool. The following functionalities are available:
- You can view all the exemption records
- You can manually add a new record
- You can filter the exemption records
- You can perform the following actions:
- Column selection
- Download the exemption list
- Set Records per page
- You can also the perform the following actions on the detailed exemption record:
- View change history
- Add comments
- Change record parameters
- View watchlist history
- Delete a record
- Accept or reject the exemption
This new Exemption Management tool simplifies taking actions on exemptions, increasing efficiency and accuracy.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
The following bugs were updated in this release:
- Corrected HMT watchlist Data loss bug: Group Type "Vessel" and records having 4000+ Characters were not being loaded.
- Corrected OFAC Data Duplication Bug: A few records (with the same unique key) were duplicated, which caused problems while generating alerts.
Fixing bugs enhances the user experience by ensuring that the application performs as expected, free of interruptions and errors.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
This release introduces two new fields (Place of Birth City Name and Place of Birth Municipality Name) in the Staging Layer and Business Layer to comply with the Philippines Regulatory requirements for CTR and STR reporting.
NOTE: The place of Birth column accommodates only 90 characters, which is a combination of City, Municipality, and Country.
The following scenarios are applicable to populate the Place of Birth column in the CTR and STR E-File:
Scenario 1: If you receive 100 characters in the place of City, and the Place of Birth length is 90 characters, then you must concatenate from backward and capture the first 90 characters of City in the Place of Birth field. Here, the other two fields Municipality and Country code will not be considered because the length of Place of Birth is already used.
Scenario 2: If you receive 80 characters in City, 10 characters in Municipality, and 3 characters in Country code, then concatenation logic must capture the entire 80 characters of City and 10 characters of Municipality. The concatenation logic must not consider the Country code as both the City field (80) and the Municipality field (10) have been utilized for Place Of Birth 90 character requirements.
Scenario 3: If you receive 70 characters in City, 5 characters in Municipality, and 3 characters for Country Code, then you must capture all three fields because the total number of characters of these fields is 78, and the length requirement for Place Of Birth is 90.
Increased coverage of customer details allows more complete and accurate reporting.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
The following data pipeline has been updated in this release:
- Load Customer Data: Updated pipeline provides Place of Birth functionality.
Updated pipelines provide better performance and increased functionality
Steps to Enable
- Copy the new version of the pipeline and create a new Job using similar naming conventions.
- Attach the newly created job to the existing Ingestion batch for the changes to be reflected.
Key Resources