We are using an external requisition system that generates POs in GP for us today. In some cases, we need user to go into GP to edit the PO (fix a promise date for example). However, we want to prevent them from creating a new PO in that window. I can't seem to prevent it using a security role/task and I can't lock it with Field Level security. What's the best method to do that?
This is a tough question as you want them to be able to modify a PO but do not want them to create a new one. If they can save in this window, they can create a new PO in that window.
Looking at the Security Roles and Tasks, I don't believe we can do this. You might be able to restrict access to the Purchase Order items lookup so they can't select any items. However, I believe they would still be able to save it as a new transaction with just no details.
I would look at this differently and instead of trying to not allow the user to create new PO's, look at correcting how the data is coming from the external requisition system and correct the issue that is sending the wrong information to GP. This way the user won't have to edit the PO and you can restrict access for that user to the PO Entry window so they cannot create PO's.
If that is not an option, you are going to likely need a customization to do this as it is double edged. You want them to be able to make changes and save the changes but not be able to enter new information for a PO.
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
789
Share
Report
All responses (
Answers (
