One of your ideas has been delivered from your suggestion.New and Revised Models in Content Library

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

For the new model, the following criteria provides information on the content library, library type, model name and business object associated to the model. See the Changes Are Made to Business Objects feature that describes the supported Event Types for this model; also review the Steps to Enable section on that feature.

  • Model Name: 60024: Application Implementation Consultant Role Events for Users
  • Business Object: Audit - Role Memberships and Access
  • Content Library: Common Setup Library
  • Library Type: Advanced Audit Controls

UPDATED MODELS

Updates were made to four transaction models. One of these models is found in the Enterprise Resource Planning Library, while the other three are in the Human Capital Management Library.

Accounts Payable Model

30001: Duplicate Payables Invoices

  • One equals filter on Supplier ID between business objects was added in the fourth position of model logic. The previous model may have generated false-positive results without it.

Human Capital Management Models

50004: Employee New Hire Created by Same User Entering Time Cards

  • The model’s name and description are updated to reflect some of the changes.
  • The previous Time Card business object for transactions was replaced with the new Time Card Information object. It represents users who are entering time instead of managing time cards afterwards. This is considered more of a replacement model, since the transactions it analyzes concern time-card entry and not the administration of time cards afterwards.
  • All filters have been revised or added to incorporate the new object in this model and include:
    • Two date filters applied on time cards and employee job assignments updated in the last three months
    • Filters for available job assignment types and action codes that contain the word "hire"
    • Only considers submitted and approved time cards
    • Filters to return the person’s current record and corresponding job assignment
    • Lastly, two filters to identify a user who created the job assignment and the same user who may have created or updated time card
  • Result Display was updated to select attributes from the new object and provide contextual information from the others.

50009: Employees with More than One Annual Salary Change

  • The model’s name and description are updated to reflect some of the changes.
  • A new user-defined object (UDO) was created. It's called Employee Salary Changes, and its description is, "Identify employee salary changes in the last year." It uses Salary, Person, and Employee Job Assignment business objects. It's filters include:
    • Filter on employee and contingent worker person types
    • Only salary changes in the last year, excluding any future dated ones
    • Filters to return the person’s current record and corresponding job assignment
  • The final model was updated to use the UDO, and includes filters that:
    • Include employee and contingent worker person types, and salary changes in the last year
    • A grouping filter on Person ID, in which a count function is applied to identify persons with two or more salary changes
  • Result Display was updated to select attributes from the new UDO.

50011: Time Reported Fraudulently by Other Employees

  • In the existing User Names UDO, the person type filter was removed and a filter to return the person’s current record was added.
  • Like model 50004, the previous Time Card business object for transactions was replaced with the new Time Card Information object in the model. Also consider this more of a replacement model since transactions analyzed are around time card-entry and not those who administer time cards afterwards.
  • Also, in this model using the UDO, filters were added to include those with an available person ID, and only time cards that have been submitted and approved.
  • Result Display was updated to select attributes from the new object and provide contextual information from the others.

The new audit model tracks changes to Application Implementation Consultant job role, a role that grants a large amount of application access, and its access should be closely monitored. Model-content updates are made periodically, based on changes, input, or recommendations by experts.

Steps to Enable

To use the new 60024 model, auditing for security needs to be enabled that corresponds to the Audit - Role Memberships and Access object. Navigate to the Setup and Maintenance > Manage Audit Policies page, set Audit Level to Low for Oracle Platform Security Service (OPSS).

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 Configuration tab under Risk Management > Setup and Administration. The 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.

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 delivered-model revisions starts by importing and reviewing them as a model. If an existing model uses the same name as the model you import, you will need to rename the revised model during import.

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.