This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Product | Feature | Notes |
|---|---|---|---|
| 18 MAR 2022 | Created initial document. |
IMPORTANT NOTE: If you are being updated directly from 21D to 22B you should review the content of both 22A and 22B sections to ensure you see all the changes included in the update.
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 |
|
||
Reports Now Cover Approval History Attributes for Remediation Plan |
||||||
Improvement in Mass Edit Security Assignment for Advanced Control Incidents |
||||||
Improvement in Mass Edit Security Assignment for User Group Membership |
||||||
Transactional Business Intelligence for Risk Management
Reports Now Cover Control Stratification
A new Control Stratification dimension has been added to the Risk Detail dimension located in the Risk Management Cloud - Assessment Real Time subject area. The Control Stratification dimension supports the attributes shown in the following illustration.
Example of the Control Stratification Dimension
The introduction of the control stratification dimension within the risk details enables you to include the control stratification within the relation to a risk records.
Steps to Enable
Leverage new subject area(s) by adding to existing reports or using in new reports. For details about creating and editing reports, see the Creating and Administering Analytics and Reports book (available from the Oracle Help Center > your apps service area of interest > Books > Administration).
Reports Now Cover Approval History Attributes for Remediation Plan
The Remediation Plan approval history attributes have been added to the Remediation Plan Details dimension located in the Risk Management Cloud - Assessment Results Real Time and Risk Management Cloud - Compliance Real Time subject areas.
New Approval Attributes Added to Risk Management Cloud - Assessment Results Real Time > Remediation > Remediation Plan Details
The addition of the approval history attributes enables the user to report on approval workflow for any given remediation plan.
Steps to Enable
Leverage new subject area(s) by adding to existing reports or using in new reports. For details about creating and editing reports, see the Creating and Administering Analytics and Reports book (available from the Oracle Help Center > your apps service area of interest > Books > Administration).
New Subject Area for Transaction Model Results
A new subject area for Advanced Financial models provides the ability to report on transaction model results. Results can be synchronized to OTBI for one or more specific models at a time so that model results can be analyzed before a model is deployed as a control.
Report Synchronization by Model
From the Monitor Jobs page, you can view the report synchronization job to see how many records were synchronized and are now available in OTBI.
Report Synchronization Job Summary
In OTBI, a new subject area for Risk Management Cloud - Advanced Financial Models Real Time is available to build reports based on the model result data. Similar to reporting on Advanced Financial Control Results, since each model definition can be different, the result values available to select have a generic label such as Result Value 1, Result Value 2 and so on. These correspond to the Result Display values selected in the model definition, in the same order. These columns can be renamed in the OTBI report.
Risk Management Cloud - Advanced Financial Models Real Time Subject Area
You can use OTBI to slice and dice data returned by transaction models to quickly identify false positives or extraneous data. You can then tweak model logic to provide only records that fit the exception criteria of the transaction model, before deploying it as a control.
Steps to Enable
Leverage new subject area(s) by adding to existing reports or using in new reports. For details about creating and editing reports, see the Creating and Administering Analytics and Reports book (available from the Oracle Help Center > your apps service area of interest > Books > Administration).
Tips And Considerations
Results for a transaction model may include the values of attributes you select, values returned by function filters, and values returned by filters that use the Equals condition on the same attribute or the Similar condition. Because these attributes and filters differ from one model to another, the OTBI subject area uses generic labels that indicate the relative position of result values. For example, Result Value 1 is the first attribute or filter value among a model's results. If you add or remove result attributes or these types of filters, you change the positions of the remaining result values. If you add a result attribute at position 4, for example, what had been Result Value 4 becomes Result Value 5, 5 becomes 6, and so on. Keep this in mind as you modify your model and synchronize its results with OTBI.
Role Information
The new Advanced Financial Control Models Transaction Analysis Duty role for this subject area (FBI_ADVANCED_FINANCIAL_CONTROL_MODELS_TRANSACTION_ANALYSIS_DUTY) has been predefined to the Advanced Transaction Controls Analyst job role. If you've customized that role, you need to add the new privilege to it. If you use predefined job roles, you don't need to make any changes.
Improvement in Mass Edit Security Assignment for Advanced Control Incidents
In the Mass Edit Security Assignment page, you can select either the Access Incident or Transaction Incident object. The first thing that's new is there is now an additional attribute specific to these objects called Advanced Control Name. For performance purposes, you must specify which control's incidents you want to work with.
Mass Edit Incidents - Control Selection
Once you've selected a control, the incidents related to that control may exceed the standard 500 record limitation. While we'll still limit the display to 500 records, we now let you know how many records there are in total and that you can perform an update to all of them by selecting the Select All checkbox. You can also perform selective edits in the following manner:
- Edit a specific set of records by selecting a few from the initial list or a filtered list.
Incident Selection for Editing
Because the volume of incidents requiring security updates may be great, these new capabilities for searching, selecting, and updating will make this process much more efficient.
Steps to Enable
You don't need to do anything to enable this feature.
Improvement in Mass Edit Security Assignment for User Group Membership
There are two updates related to user group membership in the Mass Edit Security Assignment functionality.
- The ability to filter for user groups with no eligible members.
- The ability to see all the existing members within a user group.
Mass Edit Security for User Group Membership
The ability to search through user groups to find those with ineligible members, or with no eligible members at all, will help those managing the group membership maintain them more efficiently and effectively.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
On a regular basis, those charged with managing the membership of user groups (owners and editors) should check to see if those groups contain ineligible members or no eligible members at all. These managers should remove ineligible members and possibly replace them with new eligible members. When user groups have no eligible members, managers should consider whether they are still valid groups and if so, who should be added to them.
Financial Reporting Compliance
Financial Reporting Compliance
Changes to Managing Survey Responses
The management of survey responses includes additional states and actions that can be taken by the survey owner.
New Survey States:
- Open to Responses: This state allows participants to submit responses.
- Closed to Responses: This state prevents participants from submitting responses, unless an owner reopens the survey.
New Survey Actions:
- Open for Responses: This action is available if the survey is in the Closed to Responses state. By selecting it, an owner reopens the survey (changes its state to Open to Responses).
- Close for Responses: This action is available if the survey is in the Open to Responses state. By selecting it, an owner closes the survey (changes its state to Close to Responses). However the survey can be reopened.
- Close Survey: This action is available if the survey is in either the Open to Responses or Closed to Responses state. By selecting it, a survey owner permanently closes the survey. It can't be reopened, and no additional responses can be submitted.
Example of Available Actions for a Survey that Is Open to Responses
A survey can be standalone or associated with an assessment batch. These new actions and states apply only to standalone surveys. Users can't change the state of a survey associated with an assessment batch.
Authorized users can view surveys in the Surveys work area. The table on the Surveys page has been updated with the addition of an Assessment Batch Name column and a single Due Date column. So users can view the survey name, state, responses, due date, and when applicable, the associated assessment batch name.
The due date is either the date when a standalone survey is set to close or the due date of the assessment batch. The End Date attribute has been migrated to the Due Date attribute.
Example View of the Surveys Page Tab
A background job updates an open survey's state to Closed to Responses based on the due date. The survey owner can update the due date and open the survey to responses, or the owner can permanently close the survey to any additional responses.
The enhancement allows the survey owner to manage when a survey is closed to responses, other than the due date. If the due date has passed, the survey owner can update the due date and state to Open to Responses, allowing participants to submit their answers. In addition, in the event an active survey needs to be closed to responses for any purpose, the survey owner can update the survey's state to Closed to Responses and then open at a later date.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
Existing reports may use the Survey Details > End Date attribute of the Risk Management Cloud - Assessment Results Real Time subject area. No changes are needed to these reports, however, because all survey end-date data has been migrated to due date.
New Quick Actions for Financial Reporting Compliance
To enhance the ease of navigation, 19 new quick actions were added to support the creation of Financial Reporting Compliance records. These are now included along with previously existing Risk Management quick actions
Quick Actions
The benefit of quick actions is that by selecting them, users reduce the number of navigation steps they would otherwise have to perform to get to the actionable page that a quick action takes them directly to.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
If you know you need to create something new, most likely there is a quick action for it. If you don't immediately see it in the list presented, select the Show More to see a more structured presentation.