AUTHID_CURRENT_USER Inserted Into Package Code After Patch Application or Running ADADMIN
(Doc ID 975506.1)
Last updated on AUGUST 08, 2018
Applies to:Oracle Advanced Pricing - Version 11.5.10 to 184.108.40.206 [Release 11.5]
Oracle Order Management - Version 220.127.116.11 to 18.104.22.168 [Release 11.5.10]
Oracle Shipping Execution - Version 22.214.171.124 to 11.5.10.CU2 [Release 11.5.10]
Information in this document applies to any platform.
Find after application of patch,
modifiers were no longer being applied. We are concerned
that the patch install process (not the patch itself) affected more
than this custom package with AUTHID CURRENT_USER.
Custom code integrates orders and call Pricing Engine via API.
QP: Maintains the Denormalized Data in QP Qualifiers has been run.
Build Attribute Mapping Rules has been run.
Issue is present on production and the test instance.
Issue was not found until it was moved to production.
Expect no issues in pricing when a costing patch is applied
since these are separate modules.
The issue can be reproduced at will with the following steps:
1. Apply Oracle Process Manufacturing patch 8617201,
2. Enter order and modifiers are not applied.
### Workaround ###
Removed inserted line AUTHID CURRENT_USER
from custom code and reintegrated order.
All necessary modifiers applied
The issue has the following business impact:
Due to this issue, concern is raised on the patching process and what it impacts
on custom code.
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|