August Maintenance Pack for 22C

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 JUL 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

Changes Are Made to a Business Object

This release includes a change to the Audit - Profile Option business object. Previously, the audit object was not returning changes related to deletion events. The Audit - Profile Option object has been updated so it returns deletion events, just as the Audit Report does.

Updates to audit business objects maintain alignment to Manage Audit Policies data source.

Steps to Enable

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

Update 22C

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
17 JUN 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 Common

Transactional Business Intelligence for Risk Management

Streamlined Deep Links

If you've created action links for any of the following object types, they'll no longer work: Create Risk, Create Control, Create Process, Create Issue, Create Remediation Plan.

Future references to these deep links will require fewer parameters to be passed.

Steps to Enable

If you've created action links for any of the following object types, replace them with these streamlined links:

Object Type	Deep-Link URL
Create Risk	https://<server_url>/fscmUI/faces/deeplink?objType=CREATE_RISK_OBJECT
Create Control	https://<server_url>/fscmUI/faces/deeplink?objType=CREATE_CONTROL_OBJECT
Create Process	https://<server_url>/fscmUI/faces/deeplink?objType=CREATE_PROCESS_OBJECT
Create Issue	https://<server_url>/fscmUI/faces/deeplink?objType=CREATE_ISSUE_OBJECT
Create Remediation Plan	https://<server_url>/fscmUI/faces/deeplink?objType=CREATE_REMED_PLAN

Key Resources

• See Creating Analytics for Risk Management, Link Analyses to Applications section for more information on setting up deep-link URLs.

Reports Now Cover Additional Deep Drills

The Risk Management Cloud - Compliance Real Time and Risk Management Cloud - Assessment Results Real Time subject areas offer deep link URLs to the following: Issue, Remediation Plan, Risk Analysis, and Risk Evaluation. These deep links allow you to view or edit specific records by passing parameters.

The following Financial Reporting Compliance OTBI deep links are now supported:

• Edit Issue
• Edit Remediation Plan
• View Risk Analysis
• Edit Risk Analysis
• View Risk Evaluation
• Edit Risk Evaluation

The following are the new action links:

Object Type	Deep-Link URL
Edit Issue	https://<server_url>/fscmUI/faces/deeplink?objType=EDIT_ISSUE_OBJECT&objKey=ObjectKey=@{1}
Edit Remediation Plan	https://<server_url>/fscmUI/faces/deeplink?objType=EDIT_REMED_PLAN&objKey=ObjectKey=@{1}
View Risk Analysis	https://<server_url>/fscmUI/faces/deeplink?objType=VIEW_RISKANALYSIS_OBJECT&objKey=ObjectKey=@{1};RiskAnalysisId=@{2}
Edit Risk Analysis	https://<server_url>/fscmUI/faces/deeplink?objType=EDIT_RISKANALYSIS_OBJECT&objKey=ObjectKey=@{1};RiskAnalysisId=@{2}
View Risk Evaluation	https://<server_url>/fscmUI/faces/deeplink?objType=VIEW_RISKEVALUATION_OBJECT&RiskId=@{1};RiskEvaluationId=@{2}
Edit Risk Evaluation	https://<server_url>/fscmUI/faces/deeplink?objType=EDIT_RISKEVALUATION_OBJECT&RiskId=@{1};RiskEvaluationId=@{2}

For example, the first URL in the table navigates to the Edit Issue page. (Note, the user must have the corresponding authorization.)

Example of an Edit Issue Record UI Page

A user reviewing an OTBI analysis may decide to update an issue, remediation plan, risk analysis, or risk evaluation. When deep links are implemented, this becomes a quick process: The user can simply drill to results and edit with a couple of clicks.

Steps to Enable

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

Key Resources

• See Creating Analytics for Risk Management, Link Analyses to Applications section for more information on setting up deep-link URLs.

Subject Areas Now Cover Attachments

For the Risk Management Cloud - Compliance Real Time and Risk Management Cloud - Assessment Results Real Time subject areas, new dimensions are added so that you can include URL and attachment names in the reports you create. These new dimensions are related to controls, control test plans, risks, assessment details, and assessment result details.

Also for the Risk Management Cloud - Advanced Access Controls Real Time and Risk Management Cloud - Advanced Financial Controls Real Time subject areas, new dimensions are added so that you can include URL and attachment names in the reports you create. These new dimensions are related to controls.

The following are the new dimensions, metrics, and attributes that have been added for each specific object:

Risk Management Cloud - Compliance Real Time

• Assessment Details > Assessment Attachments
• Control Details > Control Attachments
• Control Details > Control Test Plans > Control Test Plan Attachments
• Risk Details > Risk Attachments

Risk Management Cloud - Assessment Results Real Time

• Assessment Details > Assessment Attachments
• Assessment Results > Assessment Result Details  > Assessment Result Attachments
• Control Details > Control Attachments
• Assessment Results > Control Test Plan Results > Control Test Plan Result Attachments
• Risk Details > Risk Attachments

Risk Management Cloud - Advanced Access Controls Real Time

• Advanced Control Details > Advanced Control Attachments

Risk Management Cloud - Advanced Financial Controls Real Time

• Advanced Control Details > Advanced Control Attachments

Each dimension contains the following attributes:

• Attached By
• Attached Date
• File Name or URL
• Type

New Metrics - Count of Attachments

• Assessment Details > Attachments > Facts - Assessments
• Assessment Results > Attachments > Facts - Assessment Results
• Control Details > Attachments > Facts - Controls
• Risks > Attachments > Facts - Risks
• Advanced Control Details > Attachments > Facts - Advanced Control Results

Example of an Attachment Dimension

Often attachments are associated to records. Now the user can view the who, when, and type for attachments in an OTBI report. If the attachment is a URL, the user can quickly drill in, rather than navigate back to the application.

Steps to Enable

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

Tips And Considerations

Attachments that are URLs can be formatted such that they are hyperlinks. Attachments that are files can have deep links to the objects where the actual attachments can be opened.

Common Risk Management

Improved Progress Tracking for Advanced Control Model and Control Analysis

When you monitor the progress of a model- or control-analysis job, the percentage complete is more accurate and is updated every minute.

Monitor Jobs Control/Model Analysis Progress

Especially with longer running jobs, seeing the percentage complete is a good way to track where the job is. Having more accuracy will help prevent confusion over whether a job is stuck and not progressing.

Steps to Enable

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

Security Updates to External Auditor Job Role

The External Auditor predefined job role was updated to include two existing roles. These roles were introduced in earlier releases to support subject areas for models in Advanced Controls.  The added roles include Advanced Financial Control Models Transaction Analysis and Advanced Access Control Model Transaction Analysis.

The External Auditor job is responsible for auditing advanced access and transaction controls. The additional security for reporting against models aligns with this responsibility.

Steps to Enable

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

Role Information

Two duty roles for reporting on models in OTBI have been added to the predefined External Auditor job role. If you've customized that job role, you need to add the duties to it. If you use predefined job roles, you don't need to make any changes.

Duty Role Name	Technical Duty Role Name	Corresponding Subject Area
Advanced Access Control Model Transaction Analysis Duty	FBI_ADVANCED_ACCESS_CONTROL_MODEL_ TRANSACTION_ANALYSIS_DUTY	Risk Management Cloud - Advanced Access Models Real Time
Advanced Financial Control Models Transaction Analysis Duty	FBI_ADVANCED_FINANCIAL_CONTROL_ MODELS_TRANSACTION_ANALYSIS_DUTY	Risk Management Cloud - Advanced Financial Models Real Time

New Notification Options

A new Settings for Email Alerts and Notifications tab, located in Setup and Administration, enables you to exercise granular control over the objects for which email alerts and notifications are, or are not, system-generated. This new tab replaces the Email Alerts feature in the Configuration Options tab, which has been deprecated.

The new feature also permits global suppression of all emails and notifications. It's a quick way to put a temporary hold on these notices without impacting the object-level settings. Users with the appropriate privilege can update these settings to Suppress emails, Suppress notifications, or both. When both attributes are selected, all emails and notifications are suppressed across all Risk Management applications.

The default configuration is to allow all email alerts and notifications to be sent. You can modify the default settings as needed across business areas and objects.

Business Areas:

• Access Certifications
• Advanced Controls
• Financial Reporting Compliance
• Risk Management (Common)

New Notification Configuration Page

 In addition, the feature set includes the following updates:

• Track who has changed the settings, as defined in Manage Audit Policies.
• Enable the customer to export all notification event triggers.
• Removal of existing email configurations from the Configuration Options page.
• The configuration settings don't impact reminder notifications in Financial Reporting Compliance.

The new Settings for Email Alerts and Notifications feature enables organizations to manage which email and notifications are sent and their delivery format (notification or email alert). The configuration options enable the organization to manage email and notifications holistically or at the level of specific application objects.

Steps to Enable

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

Tips And Considerations

The global suppression of emails and notifications is intended primarily for use in development and test environments, where typically application communications aren't desired. In very infrequent cases, when a large update is made to the production environment, a temporary shut-off of all communications may be desirable.

Financial Reporting Compliance email reminders are not impacted due to the implementation of this feature. If a user takes the explicit action to send an email reminder to a group of users, the email will be sent regardless of the configuration setting.

Role Information

The feature is enabled by two new privileges inherited by the Risk Management Administrator duty role, which is part of the Risk Administrator job role. If you've customized your roles, you need to add the privileges to the duty role. If you use predefined roles, you don't need to make any changes.

Privilege Name	Technical Privilege Name	Description
View Email Alert and Notification Settings	GTG_VIEW_EMAIL_ALERT_AND_ NOTIFICATION_SETTINGS	Allows for viewing configurations for email alerts, notifications, and global settings.
Edit Email Alert and Notification Settings	GTG_EDIT_EMAIL_ALERT_AND_ NOTIFICATION_SETTINGS	Allows for editing configurations for email alerts, notifications, and global settings.

Financial Reporting Compliance

Financial Reporting Compliance

Survey Questions Support Carriage Returns

When you create survey questions, you may need to include carriage returns to better communicate the thought and intent of the question. Now the carriage returns included in a question definition are maintained when the question appears in a survey.

Question Definition With Carriage Returns

Question with Carriage Returns in Preview Mode

The question text can be very long or have a list of details as part of the question. Carriage returns allow for enhanced formatting when the question is rendered for the end user.

Steps to Enable

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

Tips And Considerations

During the process of creating the survey questions, leverage the Preview action to view how the question will appear within a survey. This will allow you to make additional changes when needed.

Ability to Import Issue Records

You can now migrate legacy issue records during the initial implementation of Financial Reporting Compliance. In addition, you can incrementally import issue records to existing object records.

The import template has a new issue-specific worksheet, called "Issue," to enable the entry of issue-record details. The Issue worksheet remains blank as you generate the import template, no matter whether you select the With Data or Without Data option. This means the template doesn't export documented issue records.

As part of the record for each issue you import, you must identify a single origin record, so that the issue record is mapped to the appropriate object record. The import template supports the ability to import new origin records and related issue records at the same time. For this scenario the user who initiates the import becomes the default issue record owner. This business rule is consistent with all new records being imported into the application.

When new issue records are incrementally imported, the data-migration process validates whether an issue validator or issue owner has been assigned to the object record the issue is being associated to. The following are the ORIGIN_OBJECT_TYPE_CODE values:

• GRC_PROCESS
• GRC_RISK
• GRC_CONTROL

Prior to implementation of Financial Reporting and Compliance, there are documented issue records that need to be imported as part of you legacy data, along with their relationships to other records. Support for the import of issue records streamlines data migration into the application.

Steps to Enable

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

Tips And Considerations

Financial Reporting and Compliance data migration order of execution for the sheets are the following:

1. Perspectives
2. Control
3. Risk
4. Process
5. Issues

Monitor Jobs UX  has been updated to include the count of imported issues.

The user who is importing the data doesn't have to have the privilege as an issue owner nor issue validator.

A Copy of an Assessment Batch Now Includes Attachments

In the past, a copy of an assessment batch didn't include attachments to the original batch. Now, attachments associated with the original batch are included with its copy as well.

To streamline assessment administration, you may copy an assessment batch when its scoping criteria are the same as those of a batch you want to create. Attachments associated with the original batch often include information pertaining to the batch you're initiating. These attachments are now included, ensuring that all aspects of the original batch definition are copied.

Steps to Enable

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

Update to Assessment Batch User Groups

The owner of an assessment user group can now add assessors to the group, which will have the ability to complete an associated survey. In addition the newly added assessors receive the standard assessment batch notifications.

While an assessment batch is active it's not uncommon for the need to modify the assessor assignment. Newly added assessors that are either part of a user group or individually associated will be notified of the new task assignment and be able to complete assessment in its entirety.

Steps to Enable

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

Risk Management

Advanced Access Controls

New Delivered Model Content

Oracle delivers two new models to detect separation-of-duties conflicts.

• 6871: Enter Journals and Manage Financial Applications Workflow Rules
• 7557: Post Journal Entry and Manage Financial Applications Workflow Rules

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 based on your business requirements.

Steps to Enable

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

Business Objects Defaulted

Only three business objects are appropriate for access models. When you create an access model, all three are now selected by default. You don't have to select them manually. Even if a filter doesn't reference one of the business objects, there's no harm in it being in the model definition.

Business Objects Defaulted

Creating an access model is even quicker since there will be fewer clicks.

Steps to Enable

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

View and Search on User Attributes

In the Results by Control and User page, you can now view and search on user-related information. These attributes include:

• Manager Name
• Location
• Department
• Country
• Job
• Email
• Business Unit

Below is an example of these attributes related to a user, and a search. The user's job is UX Designer, and that's surely not what you'd expect among the results of a control called Enter Journals and Create Payments.

Additional User Attributes

Pending incidents related to the selected user can be mass edited:

All records, or those returned based on the user attribute search, can be exported for reference.

Export Filtered Records and Parameters

With this additional information, business process owners, compliance managers, and auditors can more efficiently investigate and take remediation actions on access incidents. For example, a compliance manager might search for all the users with conflicts in the Europe business unit and mass edit to assign them to the business process owner (result investigator) researching Europe employees. A business process owner might search for all users in the IT department, accept them, and assign a mitigating control because it is expected these users will have excessive access. An auditor might search for a manager's name to see if any users are returned who are not in the department related to that manager.

Steps to Enable

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

Advanced Financial Controls

Revised Models in Content Library

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

30001: Duplicate Payables Invoices

• Two filters were removed because they may cause false negatives. They no longer consider different data values for Invoice Payment Status Indicator and Supplier Type.

• One filter was added to identify duplicate invoices, where the Invoice Currency is also the same.

• Attributes such as Supplier Number and Invoice ID were added to the results, providing additional details to support deep links from OTBI.

30008: Contract Payment Terms Different than Invoices

• The user-defined object supporting model 30008, called Contract Purchase Agreements, was updated to include attributes for Payment Terms Identifier and its corresponding Name.

• The Invoice ID was added to the results in the final model, providing additional details to support deep links from OTBI.

NOTE:  If you are using a prior version of model 30008, and import the revised model, you will be required to rename the user-defined object.  See the related feature in this document called Revised User-Defined Objects Require Rename During Import.

40004: Payment Process Request Created by Same User Managing Suppliers

• The first filter in the model indicates the date range to be analyzed.  The number of months to analyze was corrected to use 3, as indicated by the filter description.

40005: Suppliers and Purchase Orders Managed by the Same User

• One new filter was added to only analyze standard purchase order types. The model description was also updated to reflect this change.

• A second filter only includes amounts where Line Locations: Assessable Value are greater than zero from the Purchase Order object.

• The attribute Purchase Order ID was added to the results, providing additional details to support deep links from OTBI. 

• Additionally, amount related attributes added to results include Line Locations: Assessable Value, Line Locations: Schedule Number, Line Locations: Product Type, and Currency.

40008: External Bank Accounts and Payments Managed by the Same User

• The attribute Payment ID was added to the results, providing additional details to support deep links from OTBI. 
• Additionally, attributes added to results include Payment Amount, Currency, Type, and the Payment File Reference.

40009: Purchase Orders and Procurement Approval Routing Rules Managed by the Same User

• This model 40009 utilizes a UDO, called Purchase Orders Recently Updated.  One new filter was added to only analyze standard purchase order types, and the model description was also updated to reflect this change.

• A second filter added to the UDO that only includes amounts where Line Locations: Assessable Value are greater than zero from the Purchase Order object.

• A third filter added to the UDO aggregates (sum function) the assessable line values by purchase order to calculate a total by number.

• In the final model attribute Purchase Order ID was added to the results, providing additional details to support deep links from OTBI. 

• Additionally, amount related attributes added to results include the calculated Sum Value and Currency from the UDO.

40012: Payable Invoices Approved and Created or Updated by the Same User

• Amount related attributes were added to results that include Amount and Currency.

40013: Payable Invoices Approved and Payment Created or Updated by the Same User

• Amount related attributes were added to results that include Amount and Currency.

Updates to existing model content can be made periodically, 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.

Finally, once you have performed the above and imported the models, you must synchronize business objects, 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 any model revisions delivered 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 Oracle Fusion Cloud Risk Management: 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 Attributes

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

• Line Locations: Match Approval Level
• Line Locations: Receipt Required
• Line Locations: Inspection Required

The Supplier Site Location business object was updated to add the following attributes:

• Invoicing: Match Approval Level
• Invoicing: Receipt Required
• Invoicing: Inspection Required

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

• Conversion Currency
• Line: Entered Credit Converted
• Line: Entered Debit Converted
• Journal Batch: Control Total Entered Credit Converted
• Journal Batch: Control Total Entered Debit Converted

Note that these attribute additions to Journal Entry are not included in Journal Entry Expanded business object.

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

Audit Business Object	New Attributes
Audit - Contract	Base Contract New Base Contract Old
Audit - Document Records	Creation Source New Creation Source Old
Audit - Job Evaluation Criteria	Working Conditions New Working Conditions Old
Audit - Person Allocated Checklist	BackgroundImage New BackgroundImage Old Context New Context Old ContextualAction New ContextualAction Old CroppedBackgroundImage New CroppedBackgroundImage Old
Audit - Person Allocated Checklist Tasks	ActivationEligyPrflId New ActivationEligyPrflId Old AnalyticsPath New AnalyticsPath Old DisplayOptions New DisplayOptions Old EnableTaskExpiry New EnableTaskExpiry Old ExpiryDate New ExpiryDate Old ExpiryRelativeTo New ExpiryRelativeTo Old LearningItemId New LearningItemId Old ReportParameters New ReportParameters Old VideoType New VideoType Old VideoUrl New VideoUrl Old
Audit - Sales Lead	Don't Contact Preference New Don't Contact Preference Old Email Preference New Email Preference Old Mail Preference New Mail Preference Old Phone Preference New Phone Preference Old Primary Campaign ID New Primary Campaign ID 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.

Business Object Name	Old Attribute Name	New Attribute Name
Salary	Date Salary Approved	Salary Approved
Audit - Contract	Supplier Site Id New	Supplier Address New
	Supplier Site Id Old	Supplier Address Old
Audit - Participant Header	ParticipantId2 New	Participant Identifier New
	ParticipantId2 Old	Participant Identifier Old
Audit - Supplier Addresses	PartySiteId	Address Name

Attributes Removed

The following table lists audit business objects where attributes have been removed.

Business Object Name	Attributes Removed
Audit - Customer Account Site	Account Site Set
Audit - Item	EnabledFlag New EnabledFlag Old InventoryOrganizationId SummaryFlag New SummaryFlag Old
Audit - Item Category Association	Catalog
Audit - Item Extensible Flexfield	InventoryOrganizationId1
Audit - MDF Budget Team	CurrencyCode
Audit - MDF Claim	Approved by ID Rejected by ID
Audit - MDF Claim Team	CurrencyCode
Audit - MDF Request Team	CurrencyCode
Audit - Profile Keywords	BusinessGroupId
Audit - Sales Lead	Event Code Primary Contact Relationship ID
Audit - Sales Lead Contacts	Relationship ID
Audit - Supplier Contacts	RelationshipId1 RelationshipId2 RelationshipId3 RelationshipId4
Audit - Supplier Payment Attributes	PartySiteId

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 Locations: Match Approval Level 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, 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 Fusion Cloud Risk Management: Implementing Risk Management > Configuration and Administration > Configure Advanced Controls.

Comma or Semicolon Serves as Delimiter in Model Filters

A transaction-model filter may use a Matches any of or Matches none of condition. It lists a set of values, then looks for matches (or the absence of matches) between those values and values of a specified attribute in transaction records. As you construct the filter, you can now use either a comma or a semicolon as the delimiter for the values it lists. You use these conditions and list of values in a standard filter in conjunction with number, ID, and string type attributes. 

Example of Matches None of Condition

Support for the use of semicolon or comma as delimiter for your values avoids confusion about which to use based on attribute type.

Steps to Enable

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

Revised User-Defined Objects Require Rename During Import

Models available for import from the delivered-content library may cite user-defined objects. If you import one of these models, the object is selected automatically for import with the model. If an object with the same name already exists in your environment, the import process offers two options to avoid conflict: Rename (the newer object is imported under a new name) or Use Existing (the newer object is not imported). In this release, the import process will recognize whether a model and its corresponding object are revised. If so, the Rename option is required; you can’t select the Use Existing option. The first person to import a revised model and user-defined object after a release update provides the new version of the object with a new name.

In this release, model 30008 references a user-defined object, Contract Purchase Agreements. It's been updated in the delivered-content library. Any prior version of this model using the original user-defined object are not impacted.  If you have never imported this model, you will never see the previous version. 

Rename User-Defined Object From Content Library

NOTE:  See the related feature in this document, Revised Models in Content Library, to review changes made to model 30008.

The feature enables you to retain the original user-defined object associated to a delivered model, while allowing you to import and uptake revised versions.

Steps to Enable

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

Existing Imported Business Objects Are Not Overwritten

Models available for import from the delivered-content library may use imported business objects. If you import one of these models, and its object doesn't exist in your environment, the object is imported automatically with the model. These objects contain sample values, which you're expected to update with your organization's own values. So if you import a model associated with an imported object that already exists in your environment, the sample-value version of the object is not imported and your data is not overwritten. In prior releases this was not the case, and you needed to export the imported object as a backup before importing subsequent copies of the related model from content library.

This change is related only to objects imported with models through the content-library option.

The change maintains data integrity of any imported business object containing your organization's values. Those values are not overwritten if you import additional copies of a model through the content library.

Steps to Enable

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

New Warning Against Simultaneous Use of Journal Entry and Journal Entry Expanded Business Objects

In the 22B release, a new Journal Entry business object was added. An existing business object with the same name was renamed Journal Entry Expanded. The introduction of the new, more streamlined business object opened the door to customers using the two similar objects in transaction models and controls. But their simultaneous use duplicates data and has the potential to cause issues with storage and performance.

The 22C release adds a new warning, triggered when the data synchronization job runs. If both objects are in use, the record of the job in the Monitor Jobs page reports its status as Completed with Warnings. In the details of the job record, the new warning message defines the situation and related impact, and recommends using only one of the business objects.

Model and control security prevents many users from accessing all transaction models and controls. So it may not be obvious if both the Journal Entry and Journal Entry Expanded business objects are being used. The new warning clarifies the situation and its impact.

Steps to Enable

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

Tips And Considerations

If both journal-entry business objects are in use, you should plan to migrate away from using the Journal Entry Expanded business object. This will improve application performance and will prepare you for this business object being deprecated in a future release.

IMPORTANT Actions and Considerations

ADVANCED FINANCIAL CONTROLS

Business Object Changes

In a future release, an optimization update will be made to the Journal Entry and Journal Entry Expanded business objects: they will retrieve data related only to the primary ledger. Another business object will be added to support journals from secondary ledgers. If your organization analyzes both ledger categories, you'll need to create a new control specific to journals for secondary ledgers.

Attribute Data Type Changes

In an upcoming release, date attributes in two business objects will undergo data-type changes.

• The Approved Date attribute in the Purchase Order business object will change from date type to timestamp type. If you use this attribute in your control results, your incidents may be impacted. The change may cause some to be closed and recreated.

• For some dates in the Payables Invoice business object, timestamp is not consistently available from the source. For consistency, these date attributes will no longer return the time portion of a date value. The attributes include Accounting Date, Exchange Date, and Cancellation Date.