Purchase Requisition Approve always grayed out

(0) Share

Report

Posted on by Community Member

On test server, I've updated my GP 2013 to 2013 R2. Setup a 1 step workflow and entered a purchase requisition with the approve set to my test user who has the role PowerUser. When I look at the requisitions pending approval, I see it. Check the box, but the approve button never becomes available. Same is true for SA user. I'm guessing there is something I did not setup right, but I cannot find it. Direction, guidance, suggestions are all much appreciated.

*This post is locked for comments

I have the same question (0)

All responses (10)

Answers (1)

Jonathan Fear on at

Like (0)

Report

Did you check the box for Allow Originator to be an approver?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Yes. I have even had a different user create the req than the approver, but the result is the same, gray.

Was this reply helpful? Yes No
Suggested answer

Mahmoud Saadi 32,738 on at

Like (0)

Report

Approving a requisition is not related to having a user as a power user or an SA. You need to check the configuration on the workflow setup

Check how the hierarchy levels are setup and which user has the access to approve

Your feedback is highly appreciated,

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

The workflow has 1 step set to Approval assigned to 1 user. Condition is always required. Completion policy is only one response needed. It's as simple as I can make it. Is there something I'm missing?

Was this reply helpful? Yes No
Mahmoud Saadi 32,738 on at

Like (0)

Report

Have you activated the workflow by checking the (active) check box?

Have you tried different user as an approver ? In case the originator is the the same approver, have checked the originator to approve their own acquisitions ?

If it still occurs, just create a different workflow. You may refer to my blog to review the workflow setup steps just for further assurance

Keep us posted,

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Yes, it is marked as active. If I look at the history it shows it's waiting for approval.

Yes, I've tried 2 different users as approvers. I've tried the originator and a different user.

Your blog shows a Final Approval after 2 steps. Since I only have 1 step should there be a final approval? Or just show step 1?

Was this reply helpful? Yes No
Mahmoud Saadi 32,738 on at

Like (0)

Report

The number of steps should not matter. I have just tested one-step workflow and it is just fine.

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (0)

Report

Found the problem. Workflow is using the Windows Login not the GP Login. I was logged in to the machine using a generic admin account I do all my testing with, but logged into GP as my user. When a workflow was submitted, it was logging the originating user as the Windows admin user. Then I would try to approve the requisition, but GP would not enable the approve button since it was picking up permissions for the Windows admin user, not the GP user I was logged in as who has approval permissions.

Once I logged into the machine as my user (and GP as my user), then the approve button was enabled, and the workflow functioned.

This mixed security model is a very bad idea.

Was this reply helpful? Yes No
Jonathan Fear on at

Like (0)

Report

Hi George,

Workflow has always used Windows security even when we were on SharePoint. The reason is because you can pull more information from AD then apposed to information from with GP. It makes more sense to use Windows then it does GP.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

With SharePoint, it would make sense that it would use Windows authentication. However, reading the docs, I did not see that mentioned. Many of us did not use SharePoint workflow. I still contend it's a bad practice to have mixed authentication. GP could use use Windows auth and even map back to a GP log in for legacy sake if necessary.

In practice, we do have instances of 1 Windows log in that might be used by multiple GP users. We won't be able to do that any more.

Was this reply helpful? Yes No