Issue/Symptom/Question

We have a Job that is in a specific OU, yet Purchase Orders were allowed to be set up under a different OU on two occasions. If the Job # is assigned an OU, it should not allow an entry to be made that does not match that OU. Why is this happening and what can be done to fix this issue?

Environment

PENTA for windows

Purchasing > Purchase Orders - Grid Option

Resolution/Fix/Answer

The Purchase Order OU Id that is located in the header record of the Purchase Orders-Grid Options window, does not have any edits in place to match with the Job Id's OU id. The reason for this is the PO OU Id in the header record, does not impact accounting transactions. The OU id exists to facilitate Purchase Order security and Purchase Order auto-numbering. Because Purchase Orders can have multiple job and non-job distributions, having the PO OU Id match the Job OU Id is not always an option. 

In order to prevent incorrect OU's from being entered when creating a purchase order, users can change the User Preferences setting to have Penta automatically use the Job/WO's OU Id or Job/WO's Balance Sheet OU. See the process below to update the information in Penta:

1. While in the Purchase Order - Grid Options window, click on File > User Preferences > Window:

2. Click on Default Rules - choose which OU Default Method to be used. Click on OK to update the preference.

This needs to be updated per User while in the Purchase Orders - Grid Options window. If the setting is set to No Default, users are able to enter any OU when setting up a Purchase Order.