Changes Are Made to Business Objects

This release includes changes and attribute additions to business objects, and two new objects.

New Business Objects

Two new business objects are available. They include Time Card Information and Audit - Role Memberships and Access.

  • The first Time Card Information object is used in revised model content in this release. These updated models include 50004: Employee New Hire Created by Same User Managing Time Cards and 50011: Time Reported Fraudulently by Other Employees.
  • The new Audit - Role Memberships and Access object is for security auditing. The object's data comes from audit policy Oracle Platform Security Service (OPSS) when enabled. It supports these Event Types:  RoleCreation, RoleMembershipAdd, RoleMembershipRemove, PermissionSetGrant, and PermissionSetRevocation. This object is used in a new model in this release, called 60024: Application Implementation Consultant Role Events for Users.

New Business Object Attributes

The following business objects have been updated with new attributes.

Business Object New Attribute

Audit - Common Lookup Types

  • BOSS Application Package Name New
  • BOSS Application Package Name Old
  • BOSS Identifier New
  • BOSS Identifier Old
  • BOSS Module Name New
  • BOSS Module Name Old

Audit - General Payables Options

  • Minimum days to initiate escheatment New
  • Minimum days to initiate escheatment Old

Audit - Journal Source Setup

  • Require Subledger Accounting Entry Approval New
  • Require Subledger Accounting Entry Approval Old

Audit - RcvParametersAuditVO

  • Autocreate deliveries for expense destination receipts New
  • Autocreate deliveries for expense destination receipts Old
  • Autocreate deliveries for PAR location receipts New
  • Autocreate deliveries for PAR location receipts Old

Audit - Standard Lookup Type

  • BOSS Application Package Name New
  • BOSS Application Package Name Old
  • BOSS Identifier New
  • BOSS Identifier Old
  • BOSS Module Name New
  • BOSS Module Name Old
Payroll Time Definitions
  • Payroll ID
Payroll Transactions
  • Pay Request ID
  • Time Period Identifier

Attribute Name Changes

Business object attributes correspond to various business areas. In an effort to align the attribute labels shown in the Advanced Financial Controls business objects to labels defined in the corresponding application pages, some are updated.

Business Object Name Old Attribute Name New Attribute Name

Audit - Ledger Relationships

  • First Future Period to Convert Journals Old
  • First Future Period to Convert Journals New
  • Historical Conversion Date Old
  • Historical Conversion Date New
  • Period Old
  • Period New
  • Conversion Date Old
  • Conversion Date New
Payroll Transactions Business Group ID Legislative Data Group Identifier
Receivables Standard Receipt Business Unit Business Unit Identifier

Attributes Removed

The EnterpriseId attribute in Audit - Talent Pool Members business object has been removed.

Attribute Value Changes

The Purchasing: Match Approval Level attribute was updated in Purchasing Setup: General business object. This is a calculated attribute and the format was updated.

NOTE: If you use this Purchasing: Match Approval Level attribute in your control results, your incidents may be impacted. The change may cause some to be closed and recreated where the value has been previously populated. Delivered library content models do not use this Purchasing Setup: General 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. The new objects support new and revised model content included in this release.

Steps to Enable

To use the new Audit - Role Memberships and Access object for security auditing, navigate to the Setup and Maintenance > Manage Audit Policies page. On that page, locate Oracle Platform Security Service (OPSS). If Audit Level is None, select Low instead.

Manage Audit Policies page

Manage Audit Policies Page

When you use business objects that introduce new attributes, you must run the Transaction Data Source Synchronization job. Business objects with attribute changes 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 across models and controls, 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.