This week on the Dynamics GP blog roundup:

  • When is it okay to close purchase orders via a SQL scripting solution and what are the possible ramifications?
  • Payables management history missing after processing a payment in Dynamics GP
  • GP Dex.ini settings not working
  • Issues receiving against unauthorized purchase orders

When is it okay to close purchase orders via a SQL scripting solution and what are the possible ramifications?

On the Dynamics GP Support and Services Blog, Angela Eckman Ebensteiner stated that there are times when you have to manually close lines on a purchase order or the entire purchase order itself within the purchase order processing module.

Ebensteiner stated that she has a number of questions about closing purchase orders that are old (or stuck) via a SQL scripting solution rather than manually doing it through the front end.

In her blog post, Ebensteiner pointed out that the Dynamics GP support team recommends closing the purchase order or order line manually. The team doesn't  recommend using a SQL scripting solution to update the purchase order statuses.

You can find out why here.

Payables management history missing after processing a payment in Dynamics GP

Also on the Dynamics GP Support and Services Blog, Jeff Grant stated that recently he had  several support cases where the payables management history was missing after a payment was processed.

So he decided to write about the possible reason this was happening to help others who might run into the same situation.

In my casework the end users had been processing payments in the Select Checks/Build Checks windows in default Dynamics GP and the resulting historical records were no longer in the system for review after the posting had completed as they were completely missing from the Historical PM SQL tables.

You can find out the reason for this issue here.

GP Dex.ini settings not working

....Read More