My Oracle Support Banner

Last Updated By and Date Fields To Reflect Only The Changes Made By Human And Not System (Doc ID 2303426.1)

Last updated on JULY 12, 2023

Applies to:

Oracle Fusion Sales Cloud Service - Version and later
Information in this document applies to any platform.


On : version, Opportunities

Last Updated By field in report should reflect only the changes made by human and not system

We have a custom built Opportunity detail report where we have a field called LAST UPDATED BY exposed in the report. For many of the records in the report the value for the last updated by is "FUSION_APPS_CRM_ESS_APPID" and last updated date is also captured based on the system updated time.

We understand that When scheduled processes are run, those are ESS jobs within the Fusion Application Sales Cloud (CRM) application and they have an ID associated to them.

So basically, when the "Last Updated by" field is set to "FUSION_APPS_CRM_ESS_APPID", it means a scheduled process updated the record. So in our case when the record is updated by the Territory assignment job then in that case the last updated by will be set as "FUSION_APPS_CRM_ESS_APPID".

But we do not want the LAST UPDATED BY field to reflect the system made changes, we want the field to hold the values or changes made by humans.

How to capture only the updates made by users and not the system?


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.