For partners that build or integrate commercially available applications and service solutions with the Oracle Cloud Platform
For partners that provide implementation or managed services around Oracle Cloud Applications
By Implementing Supplier Audit History. How to capture reason code?
Comment
From release 13, if a supplier user is making a profile change through Supplier Portal, he/she can provide the change description/reason which will be available to approvers. We have an ER to implement change control on supplier profile when the change is initiated internally (from Suppliers Workarea). When that ER is delivered, you can track all supplier profile changes.
As of now, Audit is the best way and it communicates the change details along with when and by whom were the changes done. In Audit, you will not get the reason for change, but do you really expect a lot of reasons for profile changes?
Thanks,
Piyush
Be the first to rate this
|
Sign in to rate this