Revised Models in Content Library

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

Accounts Payable Models

Two accounts payable models using user-defined objects (UDOs) require a new filter. The new filter uses an equals condition on Supplier ID between Payables Invoice and Supplier business objects in two UDOs. Final models 30004 and 30006 that use them do not have any filter or logic changes, but they may generate false-positives results without the updated UDOs.

30004: Payables Invoice Amount Exceeds Average Variance for Supplier

  • In the Average Invoice Payments UDO, the new filter where Supplier ID is equal between objects was inserted in the fourth position.

30006: Unpaid Payables Invoices for New Suppliers

  • In the Supplier Invoice Counts UDO, the new filter where Supplier ID is equal between objects was inserted in the second position.

Human Capital Management Models

The following three models in the content library have been revised, due to the underlying business object relationship changes in this release. All three models now share a single UDO called Completed Payroll Transactions. The UDO collects data for payroll actions run across the last year of transactions, where the status is complete. It uses business objects Payroll Transactions, Payroll Definition, Payroll Relationships, and Person.

50001: Payroll Transactions and Personal Payment Method Managed by Same User

  • The revised model is using Payroll Flows, Personal Payment Method, and Employee Job Assignment business objects, and the new Completed Payroll Transactions UDO. In general, the model design is the same with a few changes.
  • One new date filter was added to the second position to identify personal payment methods updated within the last three months.
  • Filters were both added and updated to use "related to" condition between the new UDO and other related business objects.
  • A few Result Display attribute additions were made to include Date Earned, Relationship Number, and Pay Request ID for uniqueness. The Assignment Type attribute was removed.

50002: Payroll Transactions and Time Cards Managed by Same User

  • This model is significantly revised and should be considered a new replacement model. Previously, the Time Card object was used in its definition, which identified time entry records that were staged for payroll. It was replaced with a new business object called Time Card Information that represents time entry creation.
  • In addition to Time Card Information objects, the revised model also includes Payroll Flows, Employee Job Assignment, and new Completed Payroll Transactions UDO.
  • Two date filters are included to return only completed payroll transactions and time card transactions last updated within the last three months.
  • A filter on time cards will only consider those with a submitted or approved status.
  • A filter on valid person job assignment types was added.
  • Filters were added and updated to use "related to" condition between the UDO and other related business objects.
  • The four filters organized at the end in an "or" condition use the new Time Card Information object to identify time cards entered and updated by the same user managing payroll transactions.
  • The selected Result Display attributes are all modified with this new design, providing contextual information about the control. Additionally, the Payroll Flow business object provides the Instance Name attribute on payroll transactions.

50006: Employees on the Payroll a Short Time

  • The revised model no longer uses Employee Payroll Transaction UDO. It now uses the new Completed Payroll Transactions UDO, along with Payroll Flows, Payroll Time Definition, Employee Job Assignment, and Legislative Data Groups. A few filters remained the same, but several were added.
  • A new filter on valid person job assignment types was added.
  • Two filters were added to identify persons that have not been terminated, or were terminated within the last year.
  • Filters were both added and updated to use "related to" condition between the new UDO and other related business objects.
  • Several changes were made to selected Result Display attributes to provide better contextual information about the control, including Instance Name.

NOTE. If you currently use controls deployed from the earlier versions of models 50001 and 50002, you will see control incidents closed due to false positive results. Additionally, the valid incidents will also be closed but reopened because there may be some missing attribute values due to business object relationship changes. This is a result of relationship changes noted in the Changes Are Made to Business Objects feature. If you currently use controls deployed from the earlier versions of model 50006, only control incidents that are false positives will be closed. Keep in mind this control uses Time Card object for users managing payroll instead of Time Card Information that represents users who enter their time. For our current controls, false positive incidents should no longer exist in your results, but it's recommended you replace them with these 24C revised ones at your convenience. Treat the revised model 50006 as a replacement because the transaction object is different than the previous version.

Business Benefit

Model-content updates are made periodically, based on changes to related objects, 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 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.

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.