MDGP 2016 R2 Feature of the Day: Project Accounting Line Distributions Edited By Item

Microsoft Dynamics GPThe Inside Microsoft Dynamics GP blog has started a series Feature of the Day posts for Microsoft Dynamics GP 2016 R2; as the most recent versions have been, these posts are in the form of PowerPoint slides; I am reposting them here so they can be read more easily.

The series index for this series of posts is here.

The eighteenth Feature of the Day is Project Accounting Line Distributions Edited By Item.

Distributions can be edited by line item, but Summary cannot be edited.

Timesheet Entry

Continue reading “MDGP 2016 R2 Feature of the Day: Project Accounting Line Distributions Edited By Item”

MDGP 2016 R2 Feature of the Day: New Project Accounting Timesheet Status Report

Microsoft Dynamics GPThe Inside Microsoft Dynamics GP blog has started a series Feature of the Day posts for Microsoft Dynamics GP 2016 R2; as the most recent versions have been, these posts are in the form of PowerPoint slides; I am reposting them here so they can be read more easily.

The series index for this series of posts is here.

The seventeenth Feature of the Day is a new Project Accounting Timesheet Status report.

This feature provides a report for PTE Timesheets which gives visibility into all timesheets including missing timesheets and can be printed by status or approver:

Project Accounting Timesheet Status Report

Click to show/hide the MDGP 2016 R2 Feature of the Day Series Index

Enabling Workflow Approvals For Both Purchase Requisitions & Purchase Orders

Microsoft Dynamics GPWorkflow 2.0 has workflow types for both purchase requisitions (PRs) and purchase orders (POs). When Workflow 2.0 first came out there was a bit of talk about how you could only use one or the other, but not both.

This is not true; you can have approval workflows enabled for both PRs and POs at the same time without having to approve at both stages.

This is done by building up a condition on a workflow step which include the PO line origin. Microsoft have a blog post which covers how to do this step-by-step. There is only one problem; the blog post is incorrect in one critical point:

The problem with the blog, is that Microsoft show the Purchase Order Line field Line Origin being set to Manual. However, Line Origin is a numeric field which does not allow a word like Manual to be entered.

But, all is not lost; you can follow Microsoft’s blog post, but check for the numeric values for Purchase Order Line.Line Origin:

  • 1 = line manually entered on a purchase order
  • 10 = line created from a purchase requisition.

This information has come in very handy recently for two different clients where we assisted them in creating workflows which required approval of purchase requisiitons and purchase orders where lines had not come from a purchase requisition.