Convert Requisitions to Purchase Order

(0) Share

Report

Posted on by Bill Campbell

This is getting to be a theme with me - but I am sure I am missing a very simple step and I can not find it.

I have in a separate TEST environment, rolled out GP2015 with Web Client and have implemented Workflow for Purchase Requistions. We have made the Workflow work, we get external emails and have them Approve without going into the GP Application.

I have reviewed a number of You-Tube videos on the process, but something is missing. After we do the final approval for a Requisition and I am logged in as the user that created the Requistion, when we attempt to 'convert the requisition to a Purchase Order' the option ( under the action button )

The following are screen shots of the Workflow History.

Note that even after the document has been approved - both as Task and as Final Approval, the status on the Requisition - as shown in above - remains STATUS - Submitted

If anyone has any suggestion as to what I have missed, please comment as soon as possible.

*This post is locked for comments

I have the same question (0)

All responses (41)

Answers (0)

Bill Campbell 12 on at

Like (0)

Report

RE: Convert Requisitions to Purchase Order

To make this work, do I need to turn on the core Purchase Order Enhancements ? Or is that only used if you are not using Workflow?

Was this reply helpful? Yes No
Beat Bucher GP Gee... 28,058 Moderator on at

Like (0)

Report

RE: Convert Requisitions to Purchase Order

Bill,

The core POE (or Purchase Order Enhancement) is part of GP and was there way before WF 2.0... I don't think it's needed, though I didn't saw any special recommendation about that. We used to enable the POE commitment in the past with BP Requisition Management to keep track of the budgets, but after having replaced BP RM by a 3rd party solution for procurement, we had to disable it because the other product was not using it and it caused more issues than anything else.

I'm not there yet with the WF 2.0 approval process, but it's definitely something I want to look at in my 2015 testing

Was this reply helpful? Yes No
Bill Campbell 12 on at

Like (0)

Report

RE: Convert Requisitions to Purchase Order

Thanks Beat, I did not think I needed to have it running - but I was not sure.

It is very strange that the Purchase button is missing from the drop down for all users. Currently all users are configured as Power Users as we do not want for TEST to run into 'permission' issues.

Was this reply helpful? Yes No
Beat Bucher GP Gee... 28,058 Moderator on at

Like (0)

Report

RE: Convert Requisitions to Purchase Order

Yes Bill.. .the security concern during testing phase are usually lower priority and only need to be looked at once everything else works as expected..

Especially now with the all new GP PowerTools, it's so easy to track down the required security :-)..

Let me know if you find what prevents the PO button to get activated.. sounds very strange to me too... unless it needs to be someone else in the WF process that can't be the originator of the requisition... In our 3rd party procurement system, the purchasing dept is usually the final 'pusher' for the PO's into GP... but I can also 'grant' that permission to a regular user and drive the process based on the various rules (something I don't think WF could do).

Was this reply helpful? Yes No
Beat Bucher GP Gee... 28,058 Moderator on at

Like (1)

Report

RE: Convert Requisitions to Purchase Order

Bill,

Don't know if this would help in any ways.. but I found this on some WF document from MS :

Extended Condition Functionality

It is possible to extend the functionality of the Workflow Condition Editor by adding the following line to the DEX.INI file within the local Dynamics GP code folder:

QueryDesignerAllFunctionality=TRUE

Once this line has been added to the DEX.INI file and Dynamics GP has been restarted, the Workflow Condition Editor window will now provide additional options and functionality.

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

Like (0)

Report

RE: Convert Requisitions to Purchase Order

Hello Bill

The originating user must have a limited user type, which actually cannot purchase requisitions. I have once written an article on Limited Users in Dynamics GP 2013 R2 – Security Insight

In order to purchase a requisition, the user type should be "Full" not "Limited"

Let us know if you need any further assistance,

Was this reply helpful? Yes No
Bill Campbell 12 on at

Like (0)

Report

RE: Convert Requisitions to Purchase Order

Mahmoud, thanks for the idea, however, the users I am currently working with are SA and my user - both of which are set as Powerusers and both have System Admin rights in the SQL Server.

Was this reply helpful? Yes No
Bill Campbell 12 on at

Like (0)

Report

RE: Convert Requisitions to Purchase Order

Mahmoud, wondering if you might know why the Drop Down Menu, as shown in the screen shots above does not show the PURCHASE option ?

As well, why after running through the Workflow which shows Final Approval, the Requisition is still showing a status of 'Submitted'

Any thoughts?

Was this reply helpful? Yes No
Jothi Krishnan N 1,891 on at

Like (0)

Report

RE: Convert Requisitions to Purchase Order

Bill....I believe the Actions menus are controlled by the Workflow. So once the Workflow shows the completed status and Purchase option should become available. So, you might want to focus on fixing the status issue.

Was this reply helpful? Yes No
Bill Campbell 12 on at

Like (0)

Report

RE: Convert Requisitions to Purchase Order

That is exactly what I am working on right now.

What I can not figure out is when the Workflow show 'Final Approval' what status should be displayed for the Requisition?

Was this reply helpful? Yes No