In last weeks post, I outlined several tools that were previously freely available from Professional Services but now are bundled under PSTL 2010 as free tools.
There is one more free tool I did purposely omit for a couple reasons:
As planning for GP 2010 was being worked on, a few ideas were floated to perhaps add some more tools to PSTL 2010. One good reason for this was to take a bunch of the simpler separate tools and put them together just for ease of maintenance and discoverability by our users. The other thought was that we could add value to PSTL by adding a new free feature.
The applications outlined previously are examples of the former, the SOP PO Number Check tool is an example of the latter.
Below is a screenshot of the PSTL main window with the new application highlighted.
Activating the item and selecting the feature and pressing Next takes you to the main setup window.
For full details of use and functionality, consult the PSTL documentation. But a quick overview is that this tool will check the Customer PO Number in SOP to see if it has been previously used. However this application is a bit more advanced than the usual fare that the user can set up various means to check the different SOP document types to determine which documents should be checked for duplicate Customer PO Numbers, which tables to check, and if the Customer PO Number field should be required or not for that document type.
Several items are already defaulted in for the user and can be modified as desired (except noted below).
So in the window the columns and descriptions are:
Check DB - When searching the database, should this document type be checked?
Which Tables - Work only, History only, or Both?
Check on UI - When entering in the value (by hand) on the UI should the document type be checked or ignored.
Required - Should the Customer PO Number field be made a required field in SOP Entry
Warning Type - Different settings from Do Nothing, to Warn only, to Reject, to Ask for the Password.
Message - User editable message per SOP Type.
Now I did say that "Message" is user configurable so that you can change the message given to the end user to fit the warning type desired. That is only partially true in the GP 2010 RTM version of PSTL. It is true that it should be editable however the field was accidently made non-editable in the RTM release (will be fixed in GP2010 SP1). So if you desire to change the default messages (or enable messages for Returns and Quotes), you'll have to edit the gpCustomerPOSetup in the DYNAMICS database directly.
Why so many options? Because different customers want different things. I've seen a number of different variations of this customization as well as newsgroup postings asking how to do this type of feature. We have done a few different ones over the years with some giving warnings and some not allowing duplicates at all. So when I wrote this a few years ago, I thought that I would take the opportunity to put in every kind of flexibility feature I could think of so that it could work for most customers. You'll never hit 100% but I tried to make this as flexible as possible to cover most situations.
Once the features are set up, then the Customer PO Number field in Sales Transaction Entry and Sales Customer Detail Entry will be validated against the selected rules.
Looking at the screenshot below, we see that for a SOP Invoice for AARONFIT0001 is being entered and the user enters in Customer PO Number "A". As noted in the setup by default, this field is made required and the entered Customer PO Number was checked and at least one duplicate was found.
The user can select "Yes", "No", or "Display". See why the message is editable? The buttons are hard coded depending on the Warning Type so the message given should make sense given the choices given by the buttons in the dialog. Thinking about that a bit more - it appears I did miss a flexibility option in that the button names should have been configurable too.
As this is a Warn and Ask prompt, the user can choose to say "Yes" to allow, "No" to try again, or "Display" to show you all the documents it was found on. The dialog does tell you the first document found but the Display button should open a window to display the full results.
Note I said should- if you do choose "Display" you'll get an "Access Denied" message. This is a bug added when the app was moved into the PSTL code and will be was fixed in SP1. You can't get around this one and for now you'll have to be happy with just seeing the one duplicate that it shows you in the dialog.
When the bug is fixed, the window that you will see is:
So just thought I'd put a spotlight on this new free utility added to PSTL 2010 that will make life a bit easier for our customers.
Best Regards,Patrick RothDeveloper Support
EDIT: 29-Nov2011 Should have done this when SP1 came out, but wanted to note that the issue I noted was fixed in SP1.
Never knew something like this existed. Awesome article and thanks for sharing..
This is both great news and a nice explanation. Thank you for keeping us informed!
Posting from Mark Polino at DynamicAccounting.net
I find that it has a limitation when two users enter new Sales Orders at the same time, in such case, this tool will not be able to identify the duplicate PO numbers since the Sales Orders are not Saved yet. In such case it allow two new Sales Orders to have same Customer PO Number.
Yes I could see that happening as the check happens right away on entry and not later on (ie after the document is saved).
While I cannot promise this will be changed, it does sound like a reasonable suggestion.
Please log a product suggestion via Microsoft Connect. See the post below for details:
Is this available in pstl for GP 10?
No, this and several other tools were put into PSTL with 2010. It was a pretty big effort and there are no plans to put this into previous versions of PSTL.
Our company is poise to begin using SOP, and have completed setups. The question of customer POs arose, in one of our customers require a PO that represents their annual contract, therefore there would be duplication of the PO. After reading this post, my question is:
Out of the box, SOP will allow the users to enter any Customer PO Number value as many times as you wish. This was the specific reason that I wrote this tool (which got put into PSTL as a free tool) as customers wanted something to not allow this to happen.
I then made the tool to be flexible and allow/not allow/prompt as the user desired to be flexible for each customer.
This is great! Does PSTL need to be installed on every workstation for this to work?
Yes the code must be installed on a workstation for it to work on that workstation.
Best practice is to have all workstations with all the same dictionaries and customisations installed.
PLEASE READ BEFORE POSTING
Please only post comments relating to the topic of this page.
If you wish to ask a technical question, please use the links in the links section (scroll down, on right hand side) to ask on the Newsgroups or Forums. If you ask on the Newsgroups or Forums, others in the community can respond and the answers are available for everyone in the future.