Background
We are implementing Purchase Order and Purchase Order Requisition for a client that has been on GP since 1994. Their business has grown in a direction that was unaccepted and so we now need to implement PO for the entire office.
Since the update to GP2013 Perpetual and all the 'extra' modules that comes with that update - the client is now very interested in using the tools that they 'own' rather than tracking externally.
While we are planning the GP2015 update and looking over what we will need to do to get there, later this fall, we are pushing forward with the GP2013 R2 rollout of Purchase Orders and Requisitions. So for the sake of this post, we are only looking for support responses that address 'how this works in GP2013' we know that there are likely to be changes in GP2015 and the new Workflow, however, we are not in a position to move into GP2015 discussions until this is running in the current UAT and then PRODUCTION systems.
Environment
Running GP2013 R2 on SQL 2012
Modules - GL, PM, BR, IM - client is going to rollout into the UAT full PO and full RM
All items on PO's and Invoice will be NON INVENTORY
INVENTORY is not installed or is not accessible at this time.
We have all the modules installed on a UAT Environment and 2 UAT Only workstations - so there is no fear or concern about contaminating the Production system. The only real rule here is no new 3rd party applications allowed.
We are at the point of creating Purchase Order Requisitions and here is a short list of the questions so far:
ISSUE 1: Tax on the line item does not seem to be calculating. The request is for NON-Inventory item, that has the VENTAX schedule attached, shipping method is PICKUP, the COMPANY uses the VENTAX as the default Purchase Tax Schedule and the VENDOR has a defaulting Shipping Method of PICKUP and has VENTAX attached. Summary - there is no tax is calculating
ISSUE 2: When we create the Requistion there is no option to PRINT on the screen
ISSUE 3: Once the Request is SUBMITTED we find no where to APPROVE.
ISSUE 4: Where does the user go to 'take the APPROVED request and create the PURCHASE ORDER
I am sure that as we move forward with this we will find a number of other matters, but for now this will get us to the testing stage we need to reach by the 1st of July.
*This post is locked for comments
Update to the case notes.
We have decided that due to all the configuration of the Sharepoint system to accommodate the Workflow, we have decided to push all the Requisition training and testing onto the GP2015 system.
Issues 2, 3, 4 are all related to handling of the Purchase Request after it has been submitted and they are all NOT working at this time due to the WORKFLOW. So please do not "at this time" comment or spend time on these matters as we expect that upon the completed installation and configuration of GP2015 Workflow, these will resolve for us.
Issue 1 - Taxes in the Requisition - now that is still an issue.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,253 Super User 2024 Season 2
Martin Dráb 230,188 Most Valuable Professional
nmaenpaa 101,156