DataBase - PO Approvals

Asked By AndreaSmile

08-Dec-08 08:16 AM

We have a customer who says their PO's keep unapproving randomly - when using
the PO Approval feature of POP.

We have instructed the customer to print the PO's via Print PO Documents and
not go back into the PO after it is approved.

The user has approval authority upto $1,000; and they can approve PO's for
any user up to their authority. All other users seem to have unlimited
approval authority.

Any ideas? They can not recreate at will and can't really outline a pattern
of when the po's unapprove.

08-Dec-08 12:31 PM

using the PO Approval feature of POP [sic].<

This is not standard POP functionality, rather a part of PO Enhancements.


Yes, plenty of ideas:

1) start by downloading and installing the new Support Debugging Tool at
your customer site. You can obtain the tool at
https://mbs.microsoft.com/partnersource/support/selfsupport/productreleases/supportdebuggingtool10.htm?printpage=false.
I have been using it successfully to troubleshoot these so called random acts
of computing gods.

Also, take a look at my "First look" article at
http://dynamicsgpblogster.blogspot.com/2008/08/first-look-at-support-debugging-tool.html to get a general idea about the product.

Support Debugging Tool will also help you with the next 2 steps.

2) Setup a DEXSQL.LOG file that will allow you to identify the database
calls when the approval process is executed. This way you can identify what
stored procedures are being executed and what values are being passed to them
vs. what's get written into the tables.

3) Create a Dexterity script log (SCRIPT.LOG) file that will allow you to
see what GP scripts are being called and what values are being passed to them
when the approval process is being done, or when the window is opened again.

4) Check for VBA customizations that may be working against the behaviour of
the window. I have found improperly implemented VBA code that significantly
changes the behaviour of a particular field and "confuses" GP as to how the
field should be treated and what value should be stored.

5) Checked for table triggers that may be working against data storage
normal behaviour. You should be able to identify these with a DEXSQL.LOG or a
SQL Profiler.

6) Create a SQL Profiler, preferrably a stored proc replay that will allow
you to copy the execution into a Query window and replay the statements
leading up to the problem.

I guess you have plenty to go by, so let's stop here.

Best regards,
--
MG.-
Mariano Gomez, MIS, MCP, PMP
Maximum Global Business, LLC
http://www.maximumglobalbusiness.com
The Dynamics GP Blogster at http://dynamicsgpblogster.blogspot.com

08-Dec-08 12:52 PM

Thanks Mariano - i am familiar with all these tools - however if the customer
cannot recreate at will - the logs and dexsql really will not help too mcuh.

08-Dec-08 10:50 PM

------=_NextPart_0001_A3915E75
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Hi Andrea

Just a little clarification about what the Support Debugging Tool can do for you.

If you turn on Advanced Mode, you can add a Trigger onto the save event of a table and check for when a value (or values) on that
table has changed.  While the trigger is waiting to fire, the system will be logging all the Dexterity and SQL activity.

So once it triggers and the data has changed, you will have the logs leading up to the change and can identify the cause.

I created the Support Debugging Tool after a support case ran for a year on a situation we could see in the data but not replicate.
Once installed and setup, it found the issue in a few days.

Please see this post for more information:

http://blogs.msdn.com/developingfordynamicsgp/archive/2008/07/30/support-debugging-tool-for-microsoft-dynamics-gp.aspx

I believe you could set up the Support Debugging Tools, Automatic Debugger Mode to watch for your PO's unapproving and find
the cause.

David Musgrave [MSFT]
Escalation Engineer - Microsoft Dynamics GP
Microsoft Dynamics Support - Asia Pacific

Microsoft Dynamics (formerly Microsoft Business Solutions)
http://www.microsoft.com/Dynamics

mailto:David.Musgrave@online.microsoft.com
http://blogs.msdn.com/DevelopingForDynamicsGP

Any views contained within are my personal views and not necessarily Microsoft policy.
This posting is provided "AS IS" with no warranties, and confers no rights.

------=_NextPart_0001_A3915E75
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg1252\deff0\deflang3081{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\f0\fs20 Hi Andrea
\par
\par Just a little clarification about what the Support Debugging Tool can do for you.
\par
\par If you turn on Advanced Mode, you can add a Trigger onto the save event of a table and check for when a value (or values) on that table has changed.  While the trigger is waiting to fire, the system will be logging all the Dexterity and SQL activity.
\par
\par So once it triggers and the data has changed, you will have the logs leading up to the change and can identify the cause.
\par
\par I created the Support Debugging Tool after a support case ran for a year on a situation we could see in the data but not replicate.  Once installed and setup, it found the issue in a few days.
\par
\par Please see this post for more information:
\par
\par http://blogs.msdn.com/developingfordynamicsgp/archive/2008/07/30/support-debugging-tool-for-microsoft-dynamics-gp.aspx
\par
\par I believe you could set up the Support Debugging Tools, Automatic Debugger Mode to watch for your PO's unapproving and find the cause.
\par
\par David Musgrave [MSFT]
\par Escalation Engineer - Microsoft Dynamics GP
\par Microsoft Dynamics Support - Asia Pacific
\par
\par Microsoft Dynamics (formerly Microsoft Business Solutions)
\par http://www.microsoft.com/Dynamics
\par
\par mailto:David.Musgrave@online.microsoft.com
\par http://blogs.msdn.com/DevelopingForDynamicsGP
\par
\par Any views contained within are my personal views and not necessarily Microsoft policy.
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par }
------=_NextPart_0001_A3915E75--