Update 22A

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
23 DEC 2021			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 Common

Common Risk Management

Updated "Run By" Search Attribute in Monitor Jobs

In Monitor Jobs, you can search for jobs run by a specific person. It used to be that you could select from a list of 500 users. But any users in excess of 500 would not show in the list. So now, rather than selecting from a limited list, you search for any part of a user name in a free-form text box. If you have saved searches that use the Run By field, you can continue to use the limited list of 500 users for those saved searches. Any new search you create will allow you to search using free-form text instead.

Search Run By

You can now search for any user who may have run a job.

Steps to Enable

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

Ability to Mass Edit Security User Group Membership

Security administrators and user group owners can now use the security mass edit functionality to update the members within a security user group.

Just like with any other security mass edit, this includes the ability to append, remove, or replace users as members within the selected groups

As employees come and go and change positions within an organization, being able to mass edit user group membership is very helpful when a user needs to quickly be added to or removed from more than one user group. 

Steps to Enable

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

Tips And Considerations

User groups are a great way to manage security access to records.  Continual maintenance of user group membership is necessary to ensure proper access is granted.

Ability to Migrate User Groups

To help in the implementation of new user groups, users can now migrate user groups from one environment to another. This is enabled with a new Actions button.

When you perform the migration, validations ensure that only user groups with eligible members can be imported into the destination environment.

The main benefit is that user groups, especially large ones can be implemented in development and test environments, verified and then migrated intact into the production environment.  This is especially beneficial during implementations to ensure that only validated user groups are properly set up in production.

Steps to Enable

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

Tips And Considerations

To migrate a user group, you must be able to see the group so that you can select it. You must also have the Create and Edit User Group privilege, which is what enables the import and export actions.

Updated Email Templates

The emails for the entire Risk Management application have been updated with a new look and feel. The new layout provides more specific information about the required action. The location of the Action button is consistent, and the button takes you directly to the page where you can perform the necessary activity.

Also, when more than four emails would have been previously generated, they are now consolidated into a single email for less notification noise.

There are several key benefits to this enhancement:

• Refreshed and consistent layout
• More pertinent information
• A direct link to the page where the action can be performed
• Consolidation of emails when applicable to reduce email volume noise

Steps to Enable

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

Transactional Business Intelligence for Risk Management

Reports Now Cover Control Stratification and Additional Survey Attributes

A new Control Stratification attribute has been added to the Risk Detail dimension located in the Risk Management Cloud - Compliance Real Time subject area.

Set as In Review

Example of the New Control Stratification Dimension Within the Risk Details Dimension

 New survey attributes have been added to the Survey Details dimension located in the Risk Management Cloud - Assessment Results Real Time.

• Survey Template Name
• Respondent Email Address
• Respondent Completion Date

Risk Management Cloud - Assessment Results Real Time > Survey > Survey Details

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. The new survey attributes provide additional information pertaining to the survey respondent, which may be required by external auditors. These include a unique respondent ID, which can be the respondent's first name, last name, and email address, as well as the date the respondent submitted responses.

Steps to Enable

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

New Attributes Available for Access Certification

The Risk Management Cloud - Access Certification Real Time subject area has been enhanced to allow you to create a report that includes additional user-role and who attributes.

• Certifier Last Updated By
• Certifier Last Updated Date
• Creation Date (Timestamp has been included)
• Role Code
• User-Role Asset Book
• User-Role Business Unit
• User-Role Data Access Set
• User-Role Ledger

New Attributes Added to the Access Certification Details

Additional New Attributes Added to the Access Certification Details

These new attributes enable additional insight regarding the user-role assignments being certified. In addition, the information the user who completed the certification and when it was submitted.

Steps to Enable

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

IMPORTANT Actions and Considerations

FINANCIAL REPORTING COMPLIANCE

Obsolete Security Artifacts

The Delete Survey privilege (GTG_DELETE_SURVEY) has been removed. Now, only users authorized as owners of a survey are able to delete it.

ADVANCED FINANCIAL CONTROLS

Transaction Data Synchronization Job Must Be Run Following Quarterly Update to 22A

After you upgrade to release 22A, you must run Transaction Data Synchronization. This job takes longer than incremental synchronization of data because it must rebuild previously synchronized data, due to updates for performance improvements. This will not affect existing incident results if you simply rerun the synchronization job. However, you may want to review the existing Created as Of dates for Transactions and Audit Events for a possible update to optimize subsequent data synchronizations and analysis.

Financial Reporting Compliance

Financial Reporting Compliance

Changes to Remediation Plans and Tasks

The record of an issue includes a Remediation tab, which opens a page displaying information about remediation plans associated with the issue. This region now displays each plan's status.

Example of the Remediation Plan tab displaying the status

Within the Remediation tab, the Tasks region has been updated to allow the user to drill on each specific task to view the details.

Example view of the itemized list of Tasks.

A Tasks region of this page used to display detailed information about the tasks to be completed for a selected remediation plan. Now this region displays summary information about those tasks. In the row for a task, you can click its name to open a page that displays detailed information about the task.

Users authorized to view the issue record can easily view the status of the associated remediation plan. In addition, these users can view each defined remediation task with the ability to drill to view the details.

Steps to Enable

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

Change to Managing Control Relationships to Risks

As you define a risk, you can relate control records to it, either as primary or as subordinate to another control. You can now remove a primary control only if you first remove any controls that are subordinate to it. If appropriate, you can then select the removed subordinate controls to relate them to the risk once again.

Example of the Related Control Activities: For the 07.07 Control record to be removed, the subordinate controls need to be removed first

This enhancement ensures that when you remove related controls from a risk, the remaining controls have your intended primary and subordinate relationships.

Steps to Enable

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

Changes to the Creation of Issues

Issues can't be created for an object record in the New state.

An issue documents a deficiency in associated object record. While the object record is in a New state, the creation of the record is considered a draft and has not been initially submitted. Therefore the appropriate security may not have been applied, or the complete documentation of the record may not have been defined.

An issue is to documents a deficiency in for an associated object record

Steps to Enable

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

Changed Encrypted IDs in the Import Template

In the import template generated by the Data Migration utility, SYSTEM_ID values are no longer encrypted. Rather, the template includes the numeric system ID, which is the same as the ID available in OTBI.

Because the numeric system ID is the same as the ID available in OTBI, the use of system IDs in the applications is streamlined. You can identify records by the same numeric value.

Steps to Enable

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

Tips And Considerations

This change requires you to generate a new data export, so that records with numeric system IDs can be used to import data.

Changes to Assessment Action Buttons

The actions a user can take on an assessment record depend on its state. Action buttons and menus now include only the actions permitted by the current state of an assessment, as shown in the following table.

State	Action
New	Perform Assessment
In Review	Review Assessment
Awaiting Approval	Approve Assessment
Request for Information In Review	Respond to RFI
Request Information In Approve	Respond to RFI

The View Assessment action enables authorized users to view the assessment record. 

These actions are located on the following UI pages:

• Assessment Batches > Assessment Records
• Control Record > Assessment tab
• Risk Record > Assessment tab
• Process Record > Assessment tab
• My Assessments tab

The updates to the action button clarify the actual task being performed by the end user.

Steps to Enable

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

Configuration Option to Make Survey Mandatory in Assessments

While initiating an assessment batch or an impromptu assessment, its owner may associate it with a survey template. Now, the owner may also require that assessors complete the survey before submitting assessment results. If an assessment record is rejected, the assessor can update and resubmit the survey responses.

Example of the Configuration Option to Require Assessors to Complete Survey

An assessment may need to include a survey for many reasons. Under specific circumstances, the assessment owner may need to ensure all assessors register their survey responses prior to submitting their assessment records. This enhancement enables the owner to determine the assessments for which survey responses are required.

Steps to Enable

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

Enhancements to Assessment Survey UI Flow

Multiple enhancements improve the overall management to complete an assessment record. To use them, an assessment actor would navigate to an object record, click its Assessment tab, and select an assessment record. The available actions depend on the state of the assessment and the user's authorization.

Often there is the need to include a survey as part of the assessment record. Updates to the survey configuration and Complete Survey assessment train stop streamline this process.

• The survey instructions have been moved to appear above the first survey question.
• The additional click to complete the survey is removed.
• Additional buttons have been applied to navigate through a survey with multiple pages.
• The user must click Register Your Survey Responses on the final page of the survey.

The Perform Assessment Button is an Example of How Assessment Record Action Buttons Have Been Updated

The Complete Survey assessment train stop has been updated to streamline the user's overall UI experience.

Example of the Complete Survey Train Stop

Assessment actors can still navigate through the train stops by clicking Back, Next, or Cancel, in addition to clicking the train stops themselves. If the survey takes up multiple pages, buttons labeled Go to Previous Survey Page and Go to Next Survey Page enable navigation within the survey.

Example of the Register Your Survey Responses, Which Captures the Responses But Does Not Submit the Assessment Result

The assessor must submit survey responses by clicking the Register Your Survey Responses button on the final page of the survey. After registering initial responses, the assessor can update the responses prior to submitting the assessment record by clicking Update Your Survey Responses.

Example Once the Survey Responses Are Registered the Assessor Will Be Able to Update Their Response

The assessor need only provide responses to questions flagged as mandatory. The assessor can skip questions that are not mandatory and proceed to the next page, or register the survey. Once the assessment record has been submitted, the assessor can update the survey responses only if the assessment record was rejected during the assessment workflow process.

The Complete Survey train stop UI enhancements streamline the user experience of registering survey responses. It enables the assessor to complete the survey within the assessment record and improves the corresponding navigation through the assessment flow.

Steps to Enable

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

Risk Management

Access Certification

Role Code Information Is Added

Each security role has a code to assist in its identification. The role-code information has been added to the following areas within the application: My Team, Certifier Worksheet, Mass Assignment, and Finalize Roles.

Example of the Role Code Attribute

Role code provides additional information regarding the role being certified. You can now leverage name and the technical name for each role.

Steps to Enable

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

Advanced Financial Controls

New and Revised Models in Content Library

Advanced Financial Controls has one new model added to the content library, and an existing model has 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.

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

Content Library	Library Type	Model Name	Business Objects
Enterprise Resource Planning Library	Advanced Transaction Controls	40010: Journals Created and Approved or Posted by the Same User	Journal Entry Ledger Setup: General Journal Entry Action Log (new)

Also in the Enterprise Resource Planning Library, modifications were made to the model 40004: Payment Process Request Created by Same User Managing Suppliers. Changes include:

• Payment business object and a filter using it were added to eliminate false positives.
• Two additional filters were added to identify both supplier or supplier party updated or created by the same user who created the payment process.
• Additional Result Display attributes were selected. Some include Supplier Name, Supplier:Created By, Supplier:Last Updated By, and Payment ID.

The model name and description remain the same.

Introduced for transaction analysis, the new model complements a separation-of-duties access model called 6870: Enter Journal and Post Journal Entry. That's because the new transaction model identifies users who have actually posted or approved records between the different entitlements. Additionally, changes to existing content can be periodically updated based on 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.

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 revisions made to 40004 starts by importing and reviewing it 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 additions, changes, and removal of attributes in business objects.

New Business Object

A new business object called Journal Entry Action Log was introduced to support new model content.

New Business Object Attributes

The Purchase Order business object was updated to add the following attributes:

• Line: Ordered Amount
• Line Locations: Assessable Value
• Line Locations: Schedule Number
• Line Locations: Ordered Amount

The following attribute additions and label changes were made to the Payment Process Request business object:

• The existing Amount attribute was renamed to Amount Rounded because it does not include decimal places. If you are using the original attribute in your model or control, the label is updated.

• A new Amount attribute was added that includes the decimal places. To include amounts that might include decimal places, you need to revise your model or control to use this new attribute.

• Other attributes added to this business object are Currency Code, Payment Status, and Payment File Reference.

To support the New Currency Conversion Available in Payables Invoice Object, that business object has been updated to include these attributes:

• Amount Converted
• Invoice Amount Paid Converted
• Conversion Currency

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

Audit Business Object	New Attributes
Audit - Item	Create Supply After New Create Supply After Old
Audit - Person Allocated Checklist	ForceCompletedTemplateId New ForceCompletedTemplateId Old InitiatorPersonId New InitiatorPersonId Old InitiatorUser New InitiatorUser Old ObjectId New ObjectId Old SelfAssignedFlag New SelfAssignedFlag Old
Audit - Related Item Relationship	Controlled At New Controlled At Old Rank New Rank Old
Audit - Sales Lead	Email Verification Date New Email Verification Date Old Email Verification Status New Email Verification Status Old Last Sync to Marketing Date New Last Sync to Marketing Date Old Opt-out Comment New Opt-out Comment Old Opt-out Reason New Opt-out Reason Old Primary Phone Verification Date New Primary Phone Verification Date Old Primary Phone Verification Status New Primary Phone Verification Status Old SalesTargetLeadDaysToVerify New SalesTargetLeadDaysToVerify Old Stage New Stage Old Validation Due Date New Validation Due Date Old
Audit - Sales Territory	Latest Version

Attribute Name Changes

Business objects have attributes that correspond to various business areas such as Expenses, 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.

Business Object	Old Attribute Name	New Attribute Name
Payables Setup Invoice	Matching: Amount Tolerances	Matching: Amount Tolerances ID
Payables Setup Invoice	Matching: Quantity Tolerances	Matching: Quantity Tolerances ID
Audit - Supplier Sites	B2B Communication Method New	Enable B2B Messaging New
Audit - Supplier Sites	B2B Communication Method Old	Enable B2B Messaging Old

New Business Object Relationship

In this release, a new relationship was created between Receivables Adjustments and Receivable Invoice business object.  Previously, Receivables Adjustments was a stand-alone object.

Attributes Removed

The following attributes are no longer available in the Audit - Payroll Calculation Range Value business object, and have been removed:

• Effective End Date
• Effective Start Date

The Effective End Date attribute has been removed and is no longer available in the Audit - Sales Territory business object.

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 introduced new attributes, such those in Purchase Order, any audit object, or Payment Process Request's new Amount attribute, you must run the Transaction Data Source Synchronization job. Business objects using the new attributes require that data synchronization job to run in order to return the related values. Depending upon the number of business objects you are using with the new attributes, the data synchronization job may take a little longer than usual.

Next, with regard to the new Amount attribute in Payment Process Request, you will want to evaluate the following additional steps. These include:

• If you were previously using this attribute, you will find it was renamed to Amount Rounded. Identify the models or controls that use it.
• In the event you want to uptake the new Amount, first export your control xml file and import it as a model.
• As a model, you can revise it to apply the new attribute.
• Redeploy the revised model as a new control.

NOTE:  There is no way to revise an existing control with the new attribute.

New Currency Conversion Available in Payables Invoice Object

If your organization transacts in multiple currencies, you can now use converted currency amounts as you define controls and work with incident results. This release introduces a new currency-conversion feature that you can enable and configure. When you enable it, two new amount attributes in the Payables Invoice business object provide converted values based on a default currency you define. You can use these two attributes, Amount Converted and Amount Paid Converted, as you would any other attribute in your models, controls, and their results.

As an example, use the Amount Converted attribute to identify invoice amounts greater than 5,000. In this case, the default To Currency was set to USD, and the calculated values are expressed in that currency.

Example of Using New Amount Converted Attribute in Filter

When selecting the results to display in your model or control results, you can include the Amount Converted, Amount Paid Converted, and Conversion Currency.  The Conversion Currency value is the same for all invoice results since it reflects the configuration default for To Currency.  When the Invoice Currency (From Currency) is the same as the Conversion Currency (To Currency), the Amount and new Amount Converted attribute values are the same. 

The following model result example shows two new conversion attributes, along with the current available attributes of Amount and Invoice Currency.

Exported Model Result Example with Converted Attributes

When you operate your business in more than one country, converting invoice transactions to a single currency normalizes amounts that help identify those that cross defined thresholds or represent material amounts.

Steps to Enable

To use and populate currency conversion attribute values in the Payables Invoice business object, you must first perform some setup, since the feature is disabled by default. On the Advanced Controls Configuration page, you will find a new region called Currency Conversion Configuration. 

Advanced Controls Configuration Page

In this new region, select Edit to define your defaults.

• Select the Enable box to enable currency conversion.

• The To Currency field defaults to USD. This represents the currency the amount will be converted to. You can select any currency you have enabled for the Manage Currencies task.

• The Rate Type field defaults to the one designated as the default for Manage Conversion Rate Types task. You can select a different rate type, but be sure to use one that is regularly maintained.

• The Business Objects Supporting Currency Conversion field identifies the business objects that support converted amount attributes. For this initial release, the Payables Invoice is supported with three new attributes: Amount Converted, Invoice Amount Paid Converted, and Conversion Currency.

• A user and time stamp at the bottom of this region indicates the last person who updated the defaults.

Edit Currency Conversion Configuration Region

Important: Evaluate carefully the defaults you select. The conversion process expects the necessary rate and currency data sources; anything missing would result in converted amounts that are blank.

When you use business objects that introduce new attributes, such as these new conversion attributes, you must run the Transaction Data Source Synchronization job. After finalizing your configurations, the first data synchronization job may take a little longer since it is calculating the new Payables Invoice converted amount values. 

If you later make any changes to these defaults, running the data synchronization would update all the converted amount values. Doing so may impact your control incidents using any of the three new conversion attributes, especially if used in a filter of the logic.

Important: If you ever want to disable the feature after it's been in use, you must delete any model or control using the conversion attributes in their definition.

Tips And Considerations

The new converted amount attributes depend upon source financial information that is necessary to produce a converted value. Without the information, these amounts will be blank. The following summarizes the financial information expected as part of the calculation. Most likely, users with this access will be financial or general ledger administrators.

1. The currency you want to use as default To Currency for Advanced Controls must be an enabled currency on the Manage Currencies task, under My Enterprise > Setup and Maintenance.
2. Consider using the Rate Type for Advanced Controls designated as the default for Manage Conversion Rate Types task, under My Enterprise > Setup and Maintenance. For example, rate types are associated with daily exchange rates to perform foreign currency journal conversions. It's important to select a rate type that's regularly updated and maintained.
3. Daily Rates correspond to Rate Type and provide key details to perform currency conversions.  A daily rate includes criteria for the From Currency, To Currency, Rate Date, and Rate on that date for the defined Rate Type. Any daily rate missing would not provide a converted amount.

Once you've confirmed the above financial criteria is available, and you've set up the currency conversion configuration, converted amounts can be calculated when you use the Payables Invoice business object. As an example, this is how the Amount Converted attribute value is calculated:

• The Invoice Currency attribute is used to identify the From Currency.

• Advanced Controls Configurations defines the To Currency and Rate Type.

• Next, the Date attribute in Payables Invoice is used to find the Rate Date and its corresponding rate for From/To Currency combination.

• Finally, during the transaction data synchronization job, this rate is multiplied against the Amount attribute in Payables Invoice to calculate the new Amount Converted value.

Key Resources

For more information on currencies, rate types, and daily rates, see the "Implementing Enterprise Structures and General Ledger" book at Oracle Help Center > Cloud Applications > Financials > Books.

Role Information

The new currency conversion feature requires one new privilege for configuration, and one one privilege to be renamed. The new privilege is added to one predefined duty role. If you've customized that role, you need to add the new privilege to it. If you use predefined duty roles, you don't need to make any changes. 

New Privilege

Job Roles Inheriting Duty	Updated Duty Role	Added Privilege
Risk Administrator Advanced Access Controls Analyst Advanced Transaction Controls Analyst	Advanced Controls Administrator Duty ORA_GTG_ADVANCED_CONTROLS_ADMINISTRATOR_DUTY	Edit Currency Conversion Configuration GTG_EDIT_CURRENCY_CONVERSION_CONFIGURATION

Renamed Privilege

The renamed privilege is the one establishing the rights to configure the Access Performance Configuration region. Its new display name in security console is Edit Access Performance Configurations. (Formerly it was called Edit Advanced Controls Configuration.) Its technical name — GTG_EDIT_APPLICATION_CONFIGURATION — has not changed. The display name is updated automatically, and no change is required on your part.

Display of Integer Attribute Types No Longer Shows Commas

In Advanced Financial Controls, results from models and controls can include attributes that are an integer (or identifier) type. In previous releases, you may have seen some of these identifier values included commas. Now the commas have been removed, such as for the Invoice ID attribute.

Example of Integer Attribute Types

Display of identifier values without commas more accurately represents the data, and distinguishes it from amount values that do have commas.

Steps to Enable

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

Data Security Invoked Automatically for Secured Audit Business Objects

In release 21C, the Transaction Data Source Synchronization job was changed to return data for secured audit business objects. However, you were required to run a few one-time steps to initiate this.  These steps are no longer required and are now invoked automatically.  If needed, you can refer to the 21C feature, Data Available for Secured Audit Business Objects, to reference secured audit objects previously impacted.

Automatically invoking security when the data synchronization job is run reduces the number of steps required to return data for any model or control using the secured audit business objects.

Steps to Enable

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

Control Incidents Set to Closed When a Payables Invoice Is Deleted

When the Transaction Data Source Synchronization job runs, deleted records aren't recognized. In this release, after you configure Manage Audit Policies for payables invoices, any incident corresponding to an invoice transaction that was deleted is closed when control analysis is run.

Additionally, when the transaction data synchronization job has identified deleted invoice transactions via auditing, the job summary for Payables Invoice business object will display a new Deleted Records count.

With the audit of payables invoices enabled, data synchronization and control analysis jobs recognize deleted invoice transactions and eliminate false positive incident results.

Steps to Enable

When using the Payables Invoice 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 Payables for the product to configure.
4. For objects, locate and select the parent Invoices object and the underlying Invoice object.
5. For attributes, select the following:  Invoice ID, Business Unit, Description, Number, Supplier, and Supplier Site.  Below is an example of this page and the configuration.

Configuration of Invoice Audit Object

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

Result Investigator Is Added to Extract

As you view the results for a control, there is an Extract to Excel option. For transaction controls, the result investigator was not extracted. Now it is.

Excel Extract

Some people prefer to analyze data in Excel, and now they'll have the result investigator assigned to an incident available in the extracted data.

Steps to Enable

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