Change Management Of The Item Behaves Differently Between API And UI (Doc ID 2884452.1)

Last updated on JULY 20, 2022

Applies to:

Symptoms

 ACTUAL BEHAVIOR  
---------------
Change management of the item performing different validations when executed from API (ego_item_pub.process_user_attrs_for_item) and the application UI.
While creating an Item Change from application the system does not validate 'Item Author' role for the user where as when the same change is done by using API, the code validates if the user performing the item change via API is having "Item Author" role or not.

This is contrasting behavior of same process between UI and API.

EXPECTED BEHAVIOR
-----------------------
Expect the API ego_item_pub.process_user_attrs_for_item to not validate "Item Author" role for a user who is changing item attributes and only validate if the user has "Edit Item" privilege. 

The API also should work as it functions from the application.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Execute below code
 

 2) API fails with error "The Current User 'XXX' does not have sufficient privileges to edit the Attribute Group 'XX_ITEMMGMT_GROUP'

Changes

Cause

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