Importance of PO Line Item Entry Dates


How many of you, PO users, use the following dates on a PO Line Item Detail Entry window in Dynamics GP?

Snip20130216_1

GP defaults all appropriate fields with User Date, but user can change it with actuals.

These dates are not mere dates. They offer critical means to improve vendor followups. And this could be done per PO line item. For instance, you can create a SmartList custom alert and add it on your GP home page (Reminder Cue) for those PO line items whose Current Promised Date is reached & PO line status is not Closed, Received or Cancelled.

It’s a pain, though, to make this dates entry happen. In my case, users always would say that it’s too much of a data entry and they already have something else as followup mechanism. But trust me, they are fooling themselves (first) and the company overall.

VAIDY

Performance Issue with Received/Not Invoiced Report in POP


Angela Ebensteiner (Technical Lead, Microsoft Dynamics) share a fix on Microsoft Dynamics GP Support blog for the performance issue with Received Not Invoiced report in Purchase Order Processing (POP).

To brief you here on why this performance issue occur, it’s because of huge pile of PO records staying on POP open tables, even after they are closed. When you run the report, it goes through each and every record on POP open table, due to which you got to wait for some time till query processing finishes.

Fix is to remove completed POs from open tables to history, which we have a standard utility available in GP.

VAIDY