PO Email Notification View Document Detail Issue 'You have insufficient privileges for the current operation. Please contact your system administrator'
Hi friends, we are going to discuss about the PO approval notification issue when user click on the 'view Document Detail' link it gives error 'You have insufficient privileges for the current operation. Please contact your system administrator'.In PO email approval notification , there is an link provided 'View Document Detail' to view the PO in read only form but when user is clicking on this link it went to Oracle EBS Login page and when user login the application it gives the error message 'PO Email Notification View Document Detail Issue You have insufficient privileges for the current operation. Please contact your system administrator'. In this post , We will share the action steps and solution for this issue.
Cause of this Issue 'You have insufficient privileges for the current operation Please contact your system administrator' in PO email Approval Notification
It comes because user don't have the right oracle application menu access to view the PO details. User should have the access for some other Application menu which this link 'View Document Detail' refers.
Action Step/Solution of the Issue 'You have insufficient privileges for the current operation. Please contact your system administrator' in PO email Approval Notification
Step 1:- Here below is the user responsibility using this users is trying to approve the PO through email approval notifications.
Step 2:- In above responsibility , We are using the Menu 'Purchasing Buyer GUI'. We need to assign these below 2 new sub-menus under this main menu 'Purchasing Buyer GUI'.
PO Order Tab
PO Agreement Tab
Step 3:- Goto Application==> Menu navigation as below.
Step 4:-
Here below we are assigning the 2 new sub-menus under this main menu 'Purchasing Buyer GUI'.
PO Order Tab
PO Agreement Tab.
Step 5:- After this , We need to clear the cache using the 'Functional Administrator' responsibility and then we can re-verify this issue. This issue should be resolved after these action steps.
0 comments:
Post a Comment