Changes Are Made to Business Objects

This release includes attribute changes, updated business object relationships, and object removals.

New Business Object Attributes

The following business objects have been updated with new attributes.

Business Object New Attributes
Purchasing Line Type
  • Inspection Required
  • Receipt Required

Audit - Common Lookup Types
  • BOSS Application Package Version New
  • BOSS Application Package Version Old

Audit - Common Options for Payables and Procurement
  • Unclaimed Fund New
  • Unclaimed Fund Old

Audit - Item
  • MasterItemVersionId New
  • MasterItemVersionId Old

Audit - Ledger Relationships
  • Replication Enabled New
  • Replication Enabled Old
  • Tree Code New
  • Tree Code Old
  • Tree Version New
  • Tree Version Old

Audit - Person Allocated Checklist Tasks
  • ContentProviderCode New
  • ContentProviderCode Old
  • EmbedTaskActionCode New
  • EmbedTaskActionCode Old

Audit - Standard Lookup Type
  • BOSS Application Package Version New
  • BOSS Application Package Version Old

Audit - Supplier Sites
  • Override B2B communication for special handling orders New
  • Override B2B communication for special handling orders Old

Removed Attributes

Two attributes in the Audit - Contract business object have been removed. They include:

  • OcmFolderId Old
  • OcmFolderId New

Attribute Name Changes

In the Advanced Controls Job History object, attribute Role Count was renamed to User Role Assignments.

Business Object Relationship Changes

There are times when business object relationships are evaluated and could be removed, changed, or added. The following updates in this release apply between HCM-related business objects:

  • The existing relationship direction between Payroll Definitions and Payroll Assignments was reversed. Now the relationship path is Payroll Assignments to Payroll Definitions for data accuracy reasons. As an example, using these two business objects in conjunction with Payroll Transactions may have generated false positive records because analysis incorrectly considered assignments first when a payroll definition must exist first.
  • The relationship between Payroll Transactions and Payroll Relationships was added. This creates a distinct relationship.
  • The relationship between Payroll Definition and Personal Payment Method was removed. This relationship is invalid and could bring back many false positives when the objects are used together.
  • The existing relationship between Person and Employee Job Assignment was reversed. Now the relationship path is Employee Job Assignment to Person for data accuracy reasons. As an example, using these two business objects in conjunction with Payroll Transactions may have generated false positive records because analysis incorrectly considered assignments first when a person must exist first.

NOTE. Changes in business-object relationships impact the following models in the delivered-content library: 50001: Payroll Transactions and Personal Payment Method Managed by Same User, 50002: Payroll Transactions and Time Cards Managed by Same User, and 50006: Employees on the Payroll a Short Time. These impacted models are updated in this release and documented under Revised Models in Content Library.

Removed Business Objects

Nine Product Hub audit objects related to attachment tracking were removed in the list of available objects on the Search Business Object page for Advanced Financial Controls. These objects use different Event Types; when required, you can access event activity via Audit Reports under Tools.

  • Audit - Catalog Attachment
  • Audit - Category Attachment
  • Audit - Competitor Item Attachments
  • Audit - Customer Item Attachments
  • Audit - Item Attachments
  • Audit - Item Revision Attachments
  • Audit - Manufacturer Item Attachments
  • Audit - Structure Attachments
  • Audit - Supplier Item Attachments

Attribute Value Changes

The Match Approval Level attribute in three business objects is a calculated value based on whether an inspection or receipt is required. A couple of combinations were not considered, and therefore updated to do so. The following list of Business Object.Attributes are those using a calculated value for match type.

  • Supplier Site Location.Invoicing: Match Approval Level
  • Purchase Order.Line Locations: Match Approval Level
  • Purchasing Line Type.Match Approval Level

NOTE: If you use this 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 missing. Delivered library content models do not use this attribute.

Business Benefit

Updates to business objects provide additional attribute criteria for your controls and improve accuracy. Those updated for audit maintain alignment to Manage Audit Policies data source.

Steps to Enable

When you use business objects that introduce new attributes, or relationship changes between objects, you must run the Transaction Data Source Synchronization job. Business objects with  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.