May Maintenance Pack for 22B

Revision History

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
29 APR 2022			Created initial document.

Overview

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.

Feature Summary

Risk Management

Advanced Financial Controls

Revised Model in Content Library

In Advanced Financial Controls, the model 50010: Salary Increases Outside Scheduled Range has been revised. You can select the Import action on the Models tab and select it from the content library. The model is found under the Human Capital Management Library, Advanced Transaction Controls. It works in conjunction with an imported business object (IBO) named Schedule of Salary Increases, which is imported automatically with model 50010.

Here's a summary of changes:

• The last two model-logic filters in the OR position were revised to uncheck the Exclude advanced option.
• The first filter in the OR position includes salary start dates that fall before the scheduled increase start date defined in the IBO.
• The second filter in the OR position includes salary start dates that fall after scheduled increase-to date defined in the IBO.

Filters Updated in Model 50010

Model 50010 identifies salary increases that occur outside the budgeted or planned increase schedule of your organization. The model logic was updated to apply analysis that returns correct results.

Steps to Enable

Earlier versions of model 50010 would never have returned any results, but you may have revised the risk logic of an earlier version so that it returns data. If so, you have no need to uptake the 50010 revision. If you have an earlier version of this model and have never revised it, consider the following:

• Delete earlier model or control versions of 50010, and import the revised model.

• The data values in the Schedule of Salary Increases IBO are considered examples. You're expected to update them to values appropriate for your organization. If you've already imported the IBO and updated it with your data values, be sure to export your existing version before importing the revised 50010 model. Otherwise, importing the model would automatically overwrite your existing Schedule of Salary Increases IBO with the sample-value version. After you import the new version of the model, you can then import your version of the IBO to retain your data.

Messaging and Validations Clarify the Use of Journal-Entry Business Objects

In the 22B release, a new business object, Journal Entry, was added. It's a smaller-footprint version of the original Journal Entry object, which has been renamed Journal Entry Expanded. Although the new object is meant to improve performance by containing fewer attributes, both objects represent the same data. So the use of both objects isn't efficient and actually defeats the purpose.

Here are some things we've done to help you manage these objects if you're already performing analysis of journal-entry data.

Warnings: We'll let you know if you already use one of these two business objects and try to use the other. If you decide to use both, you'll at least be forewarned that you may encounter storage and performance issues as a result.

Errors: In some scenarios we won't let you do something that could cause storage or performance issues long-term. Examples include:

• Attempting to use both the Journal Entry and the Journal Entry Expanded objects in the same model.

• Trying to enable a control that uses one of the objects when another control already uses the other. This may occur when you're deploying a new control, importing a control, or activating a previously inactive control.

Enhanced messaging and validations better inform you of potential problems and prevent issues that may arise in the long term.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

If you performed analysis of journal-entry data prior to the 22B release, your models and controls used the business object that's now renamed Journal Entry Expanded. It's highly recommended that you consider replacing these models and controls with versions that use the new Journal Entry business object. If you don't know whether a control uses the Journal Entry Expanded object, don't worry, we'll let you know. At that point you'll want to put together a plan to move to a new control while keeping a record of previously generated incidents and related information.

Advanced Access Controls

Performance Improvements for Asynch SOD API

The asynchronous separation of duties resource simulates how active access controls would identify incidents if individual users were assigned particular job roles. If you've used this REST resource to implement preventive controls within your provisioning workflow, you'll find the perform-analysis call will run 10-20% faster than it did before.

With this improvement, workflow participants such as approvers will be notified in a more timely manner.

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Update 22B

Revision History

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
12 JUL 2022	Advanced Financial Controls	Control Incidents Set to Closed When a Journal Entry Is Deleted	Updated document. Revised feature information.
18 MAR 2022			Created initial document.

Overview

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.

Feature Summary

Risk Common

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.

Common Risk Management

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.

1. The ability to filter for user groups with no eligible members.
2. 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.

Risk Management

Advanced Access Controls

New and Updated Delivered Model Content

Oracle delivers 5 new models to detect separation-of-duties conflicts and sensitive access. In addition, 6 existing entitlements are updated, affecting 17 existing models.

NEW MODELS

• 9341: Manage Bank Accounts and Enter Customer Receipts
• 9342: Set Up Payment and Enter Customer Receipts
• 6681: Set Up Procurement
• 6682: Sensitive Access to Bypass Purchase Order Approvals
• 6371: Create Suppliers and Manage Payables Invoice Tolerance Set

REVISED ENTITLEMENTS

Person Data

The privileges Access Person Extra Information by HR and Manage Person Extra Information by HR have been added to the Person Data entitlement. These privileges allow access to a person's extensible flexfields which may contain sensitive data.  The affected model includes:

• 9700: Person Data

Approve Payables Invoices        

The privilege Manage Financial Applications Workflow Rules allows creation or modification of workflow rules for Financial Applications.  The affected models include:

• 5800: Approve Payables Invoices and Create Payables Invoices
• 5810: Approve Payables Invoices and Create Payments
• 5893: Maintain Supplier Bank Accounts and Approve Payables Invoices
• 6090: Create Purchase Orders and Approve Payables Invoices
• 6370: Create Suppliers and Approve Payables Invoices
• 6750: Enter Journals and Approve Payables Invoices
• 7550: Post Journal Entry and Approve Payables Invoices
• 9373: Enter Budget and Approve Payables Invoices

Sensitive Payment Privileges

The privilege Manage Financial Applications Workflow Rules allows creation or modification of workflow rules for Financial Applications.  The affected model includes:

• 9802: Sensitive Payment Privileges

Sensitive General Ledger Privileges

The privilege Manage Financial Applications Workflow Rules allows creation or modification of workflow rules for Financial Applications.  The affected model includes:

• 9806: Sensitive General Ledger Privileges

Sensitive IT Security Privileges

The privilege View Audit History allows viewing of the audit history of all the business object attributes enabled for auditing.  The affected model includes:

• 9361: Sensitive IT Security Privileges

Manage Worker

The privilege Edit Pending Worker allows users to correct pending-worker records. The affected models include:

• 4056: Manage Worker and Manage Payroll
• 4057: Manage Worker and Manage Payroll Batch Processes
• 4058: Manage Worker and Manage Payroll Costing
• 4070: Manage Worker and Manage Compensation
• 4075: Manage Worker and Manage Time and Labor

The content library is continually reviewed by experts in relevant business areas to provide the most accurate and comprehensive SoD and sensitive access control definitions. Consider uptaking these new models and entitlement changes based on your business requirements.

Steps to Enable

As a rule, when you import a model that uses entitlements, you import the entitlements automatically. But if an earlier version of an entitlement exists in your target environment, the content-import job cannot replace it with a newer version. So:

• If an entitlement has been revised, but you have not yet imported any of the models that use it, you can import one of these models now. The import operation includes the new entitlement along with the model.

• If an entitlement has been revised, and you imported a model that uses it during an earlier update, you also imported the earlier version of that entitlement. To use the new version, your only option is to edit your existing entitlement to incorporate its revisions.

Ability to Deploy Up to 100 Controls At a Time

From the Advanced Controls list of actions, you can deploy either access controls or transaction controls. In either case, a Select Models page displays a list of models you may deploy as controls. You can now select up to 100 models. In the past, the limit was 25. The initial display of models is still limited to 25 but to select more, you can click a Load More Items option or you can click a Select All checkbox.

Control Deployment

This feature will allow for the faster and more efficient deployment of models to controls

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

It is important to note that controls should only be deployed after the underlying model has been run, analyzed and the results determined to be complete and accurate.

Advanced Financial Controls

New and Revised Models in Content Library

Advanced Financial Controls has four new models added to the content library, and two existing models have been revised. When you have access, you will be able to select the Import action on the Models tab and select them from the Content Library.

NEW MODELS

For new models, the following table provides information on the content library, library type, model name and business objects associated to the model.

Content Library	Library Type	Model Name	Business Objects
Enterprise Resource Planning Library	Advanced Transaction Controls	40011: Journals Posted and Specify Ledger Options Managed by the Same User	Journal Entry Expanded Ledger Setup: General Journal Entry Action Log
Enterprise Resource Planning Library	Advanced Transaction Controls	40012: Payable Invoices Approved and Created or Updated by the Same User	Supplier Payables Invoice Payables Invoice Approvals (new)
Enterprise Resource Planning Library	Advanced Transaction Controls	40013: Payable Invoices Approved and Payment Created or Updated by the Same User	Supplier Payment Payables Invoice Payables Invoice Approvals (new)
Common Setup Library	Advanced Audit Controls	60019: Fusion Business Object Attributes Disabled	Audit - Audit Policies (new)

UPDATED MODELS

In the Enterprise Resource Planning Library, modifications were made to two Advanced Transaction Controls.

30002: Duplicate Suppliers and Sites

• Model logic was revised to identify possible duplicate suppliers and sites based on similarity of their supplier name and address. It no longer considers bank-related information when evaluating your supplier master data.

• The model now leverages a user-defined object called Active Suppliers and Sites to perform analysis, only including those data records that are active for duplicate analysis.

• Attribute results returned will include those related to supplier's name, number, site, address, and business unit. With this combination of attributes, it will identify similar supplier name and address records both within the same, or across different, supplier numbers.

NOTE:  If you are using a prior version of model 30002, you should stop using it.  The model design and its filters were updated because changes were previously made to business object relationships and generating inconsistent results.

40004: Payment Process Request Created by Same User Managing Suppliers

• In 22A release, the Payment Process Request business object attributes were updated. This model was revised to uptake changes and modify Result Display attributes selected to include Amount, Currency Code, Payment Status, and Payment File Reference.

NOTE: If you are using a prior version of model 40004, it is optional to uptake the revised model since only Result Display attributes were updated.

Three of the new transaction models - 40011, 40012, and 40013 - were introduced to complement separation-of-duties access models called 7554: Post Journal Entry and Set Up General Ledgers, 5800: Approve Payables Invoices and Create Payables Invoices, and 5810: Approve Payables Invoices and Create Payments, respectively. Additionally, changes to existing content can be periodically updated based on changes, input, or recommendations by experts.

Steps to Enable

No advance setup is required for you to import models in Advanced Controls. However, a Risk Management administrator must set the Transaction and Audit Performance Configuration date options under the Advanced Controls Configurations tab under Risk Management > Setup and Administration. Two created-as-of-date options are required, one for transactions and the other for audit events. These settings improve performance by eliminating older data from data-synchronization jobs. When these created-as-of-date options already exist, you should periodically review and change them to return only current data.

New models delivered in this release use the Payables Invoice Approvals business object. Approval business objects leverage archived and completed approval records created from workflow tasks, in this case for invoices, the FinApInvoiceApproval task.  This information depends on the Extract Workflow Tasks for Archive job, during which the completed approval task flows are archived from SOA BPM tables into archival FND_BPM tables.  This ESS job is automatically scheduled to run once a day, but it is recommend you check the scheduled process status. If you are working with your model in a test environment and creating and approving records, you may need to run this job manually from Scheduled Processes to archive the information right away.

Finally, once you have performed the above and imported the models, you must run data synchronization, which retrieves the source data used during model analysis.

Tips And Considerations

Before using new model content, evaluate available models that match requirements for your organization under the Import action for models. The Import from Content Library page is organized by product area and model types. Once you identify models appropriate for you, import, review, and modify them in your test environment. Importing all available models is not recommended. In some cases, you may have already imported the model in a previous update. Or, some may source data from products or audit configurations you have not enabled. Moreover, models may contain user-defined or imported business objects that create data set controls or objects, respectively.

NOTE:  There is no way to revise an existing control with new business objects, filters, or the attributes displayed.  Uptake of the revisions made to 30002 and 40004 starts by importing and reviewing them as a model.

Key Resources

• For more information about importing models, see a set of five topics beginning with "Import Models, Controls, or Conditions." These topics appear in Using Advanced Controls at Oracle Help Center > Cloud Applications > Risk Management and Compliance > All Books.

Changes Are Made to Business Objects

This release includes new business objects, and additions and changes to attributes in objects.

New Business Objects

The following new business objects were introduced to support new model content:

• Audit - Audit Policies
• Payables Invoice Approvals

Renamed Business Object

The existing business object Journal Entry was renamed to Journal Entry Expanded. This has no impact on your existing models and controls; you will see the new name after upgrade.

New Business Object Attributes

The Purchasing Line Type business object had updates to the following attributes:

• New attribute called Product Type
• Two attributes were mislabeled and their names swapped:  Matching Basis and Purchase Basis

To extend the currency conversion feature introduced in 22A on Payables Invoice, the Purchase Order business object has been updated to include these attributes:

• Purchase Order.Conversion Currency
• Purchase Order.Line: Price Converted
• Purchase Order.Line: Ordered Amount Converted

The following table lists additional audit business objects updated with new attributes.

Audit Business Object	New Attributes
Audit - General Payables Options	Minimum Interest Amount New Minimum Interest Amount Old
Audit - Payment System	Name New Name Old Processing Model New Processing Model Old
Audit - Person Allocated Checklist	Archive After Months New Archive After Months Old Checklist Display Name New Checklist Display Name Old Purge After Months New Purge After Months Old
Audit - Person Allocated Checklist Tasks	ActivityAction1Label New ActivityAction1Label Old ActivityAction2Label New ActivityAction2Label Old ActivityAction3Label New ActivityAction3Label Old ActivityAction4Label New ActivityAction4Label Old ActivityAction5Label New ActivityAction5Label Old CalendarActionLabel New CalendarActionLabel Old CompleteActionLabel New CompleteActionLabel Old RejectActionLabel New RejectActionLabel Old SaveActionLabel New SaveActionLabel Old

Attribute Name Changes

Business objects have attributes that correspond to various business areas such as Human Resources, Procurement, Payables, and so on. In an effort to align the attribute labels shown in the Advanced Financial Controls business objects to labels defined in the corresponding application pages, several are updated.  Access the list of Attribute Name Changes to review the changes.

Attribute Data Type Changes

The following attributes in the Audit - Item business object had their data type change to string:

• Packaging String Old
• Packaging String New

Updates to business objects provide additional attribute criteria for your controls, and those updated for audit maintain alignment to Manage Audit Policies data source.

Steps to Enable

When you use business objects that introduce new attributes, such as Line: Ordered Amount Converted in Purchase Order object, you must run the Transaction Data Source Synchronization job. Business objects using new attributes require that the data synchronization job be run in order to return the related values. Depending upon the number of business objects you are using with new attributes, the data synchronization job may take a little longer than usual.

Tips And Considerations

For renamed attributes and business objects, you don't need to do anything to models or controls that reference these names. Just be aware they have changed.

Key Resources

• For more information about using currency conversion attributes, see Set Up Currency Conversion under Oracle Implementing Risk Management > Configuration and Administration > Configure Advanced Controls.

Control Incidents Set to Closed When a Journal Entry Is Deleted

In the past, when the Transaction Data Source Synchronization job was run, deleted records weren't recognized. In this release, after you configure Manage Audit Policies for journals, any incident corresponding to a journal line transaction that was deleted is closed when control analysis is run.

Additionally, when the transaction data synchronization job has identified deleted journal line transactions via auditing, the job summary for the Journal Entry business object will display a new Deleted Records count.

NOTE: The feature supports the new Journal Entry business object and not Journal Entry Expanded object.  As indicated under the Changes Are Made to Business Objects feature, the existing Journal Entry business object was renamed to Journal Entry Expanded. 

With the audit of journal lines enabled, data synchronization and control analysis jobs recognize deleted journal transactions. This eliminates false positive incident results.

Steps to Enable

When using the Journal Entry business object in your controls, you will want to enable the auditing of this object to minimize false positives when transactions are deleted. The following one-time, prerequisite steps are required.

1. Navigate to My Enterprise > Setup and Maintenance > search for Manage Audit Policies task.
2. At the top of the page, select the Configure Business Object Attributes button for Oracle Fusion Applications.
3. Select General Ledger for the product to configure.
4. For objects, locate and select the parent Journal and child Journal Line under that object.
5. For attributes, select the following:  Header ID, Line, Account, Line Description, and Currency.  Below is an example of this page and the configuration.

Configuration of Journals Audit Object

The above steps will enable the auditing of deleted journal transactions. When a journal line has been deleted, your control will recognize this and close the incident once the Transaction Data Source Synchronization and Control Analysis jobs are run.

Ability to Add More Than Two Group Filters in Model

In previous releases, there was a limitation on the number of group filters you could define in a single Advanced Financial Controls model. Before, you could only apply one similar filter against another that defined an equals grouping filter. Now, you can add a secondary similar filter after another filter using similar.

Model Logic Using Two Similar Filters

Extending the use of grouping filters like similar and function filters within the same model logic eliminates the need to create and maintain related user-defined business objects.

Steps to Enable

You don't need to do anything to enable this feature.

Ability to Deploy Up to 100 Controls At a Time

From the Advanced Controls list of actions, you can deploy either access controls or transaction controls. In either case, a Select Models page displays a list of models you may deploy as controls. You can now select up to 100 models. In the past, the limit was 25. The initial display of models is still limited to 25 but to select more, you can click a Load More Items option or you can click a Select All checkbox.

Control Deployment

This feature will allow for the faster and more efficient deployment of models to controls

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

It is important to note that controls should only be deployed after the underlying model has been run, analyzed and the results determined to be complete and accurate.

IMPORTANT Actions and Considerations

ADVANCED FINANCIAL CONTROLS

Business Object Changes

You will find there are two overlapping business objects for journals: Journal Entry and Journal Entry Expanded. The Journal Entry Expanded is the existing object and was renamed from Journal Entry in this release; it is used in current delivered model content. The new Journal Entry business object will have fewer attributes to improve performance. In the future, existing delivered model content that uses Journal Entry Expanded will be revised to use the newer Journal Entry business object.

Over time, it is recommended you transition to the newer Journal Entry object. In the meantime, if you are attempting to use both the Journal Entry and Journal Entry Expanded business objects, which the system will allow you to do, it will cause delays and the combined data may exceed capacity. Attention should be taken to ensure that only one or the other is used in either active models or controls.

NOTE: To reduce your risk, you can restrict access to either business object on the User Access to Business Objects page under Risk Management Data Security. Also, if you suddenly experience a much longer data synchronization and/or control analysis, it could be that both journal business objects are being used. Check the Job Summary page after the data synchronization job has completed to confirm which business objects were included.

Delivered Content Model Updates

In upcoming releases, there are two planned model updates to Content Library for Advanced Financial Controls. They include:

• 50010: Salary Increases Outside Scheduled Range - is revised to update model logic.
• 40004: Payment Process Request Created by Same User Managing Suppliers - the model is revised to look for invoices within 3 months (as in the description) rather than 24 months.

ADVANCED ACCESS CONTROLS

Access Control Incident Results

During SOD analysis using Risk Management Advanced Access Controls the job roles Employee and Contingent Worker raise incidents related to privileges Manage File Import and Export as well as Import Supplier Bank Accounts. These privileges are granted via the duty: Payee Bank Account Management. This duty is planned for removal from the Employee and Contingent Worker roles. It will be replaced with a comparable duty, minus the two noted privileges.

Due to this role structure change, incidents referencing these roles and privileges may be automatically closed. The incidents will remain available to view, the status will just no longer be in a pending state and so you may notice your incident counts go down. There's no action on your part, we just wanted you to be aware.