Hands On With Microsoft Dynamics GP 2018 R2 New Features: Exclude Items on HITB Report With Zero Quantity or Value

Microsoft Dynamics GPThis post is part of the Hands On With Microsoft Dynamics GP 2018 R2 New Features series in which I am going hands on with the new features introduced in Microsoft Dynamics GP 2018 R2 (which was released on the 2nd October). I reblogged the new features as Microsoft announced them along with some commentary of how I thought they would be received by both my clients and I. In this series, I will be hands on with them giving feedback of how well they work in reality.

The tenth new feature is Exclude Items on HITB Report With Zero Quantity or Value. This feature adds two new options to the Historical Inventory Trial Balance (HITB) report. The new options are:

  • Include Items with Zero Quantity
  • Include Items with Zero Value

These items will be excluded on the report if the options are not checked; previously, by default, these items were included. Make sure the checkboxes are unmarked to exclude the items with either zero value or quantity:

Inventory Activity Report Options

When I first read this feature of the day announcement, I thought it would be a good addition. However, now that I’ve been hands on with it, I’m not so sure. Initially, I’d misremembered what the HITB showed; it is basically a report which shows movement of stock. The report I was thinking of, is the Stock Status report and it already allows you to filter out zero quantities or values.

Having played around on Fabrikam, I can’t actually see how excluding items would be useful from the HITB report; when running a Trial Balance, you’d want to see all transactions.

Click to show/hide the Hands On With Microsoft Dynamics GP 2018 R2 New Features Series Index

Hands On With Microsoft Dynamics GP 2018 R2 New Features: Transaction Level Post Through General Ledger

Microsoft Dynamics GPThis post is part of the Hands On With Microsoft Dynamics GP 2018 R2 New Features series in which I am going hands on with the new features introduced in Microsoft Dynamics GP 2018 R2 (which was released on the 2nd October). I reblogged the new features as Microsoft announced them along with some commentary of how I thought they would be received by both my clients and I. In this series, I will be hands on with them giving feedback of how well they work in reality.

The seventh new feature is .When transaction posting is enabled, this feature allows users to perform posting through the General Ledger at a transaction level. The following is a list of supported transactions for this feature:

  • Invoice Entry
  • Receivables Apply Doc.
  • Receivables Cash Receipts
  • Receivables Sales Entry
  • Sales Deposits
  • Sales Trx Entry
  • Voided Trx Maintenance (Sales)
  • Payables Trx Entry
  • Payment Entry
  • Purchasing Invoice Entry
  • Purchasing Prepayments
  • Receivings Trx Entry
  • Returns Trx Entry
  • Assembly Entry
  • Transaction Entry (Inventory)
  • Transfer Entry
  • Manual Checks (Payroll)
  • Project Accounting Transaction windows except Project Closing

To enable post through for transactions, open the Posting Setup window (Administration area page » Setup » Posting » Posting), and mark the Post Through General Ledger checkbox below the Allow Transaction Posting one:

Posting Setup

In theory this is a great addition to Dynamics GP, as many clients want to do transaction level posting, although more these days are wanting to use workflow for approvals which still requires batches.

However, in my testing so far, all Sales transactions which I post using post through work fine, but nothing on Payables posts through at transaction level regardless of the settings.

I need to do additional testing, but so far this feature isn’t looking good.

Click to show/hide the Hands On With Microsoft Dynamics GP 2018 R2 New Features Series Index

Hands On With Microsoft Dynamics GP 2018 R2 New Features: Monthly Recurring Batches

Microsoft Dynamics GPThis post is part of the Hands On With Microsoft Dynamics GP 2018 R2 New Features series in which I am going hands on with the new features introduced in Microsoft Dynamics GP 2018 R2 (which was released on the 2nd October). I reblogged the new features as Microsoft announced them along with some commentary of how I thought they would be received by both my clients and I. In this series, I will be hands on with them giving feedback of how well they work in reality.

The first new feature is Monthly Recurring Batches. This feature allows a recurring batch to be created in Payables Management, Receivables Management and Inventory Control.

When creating the batch, after selecting a Frequency of Monthly, mark the new Use last day of the month; this will change the Posting Date to the last day of the month:

Payables Batch Entry

Continue reading “Hands On With Microsoft Dynamics GP 2018 R2 New Features: Monthly Recurring Batches”

MDGP 2018 R2 Feature of the Day: Exclude Items on HITB Report With Zero Quantity or Value

Microsoft Dynamics GPThe Inside Microsoft Dynamics GP blog has started a series Feature of the Day posts for Microsoft Dynamics GP 2018 R2 on which I am following and adding commentary. The series index for this series of posts is here.

The tenth Feature of the Day is exclude items on HITB report with zero quantity or value

The Historical Inventory Trial Balance (HITB) report has two new options for Dynamics GP 2018 R2; when printing the HITB report you can now decide if you want to include/exclude items with a zero quantity or value. The new options are:

  • Include Items with Zero Quantity
  • Include Items with Zero Value

These items will be excluded on the report if the options are not checked; previously, by default, these items were included. Make sure the checkboxes are unmakred to exclude the items with either zero value or quantity:

Inventory Activity Report Options

This is a good update to the HITB; I have a number of clients with large number of items which will generally have a zero quantity of stock while having other items with stock levels they on which they would want to report. Being able to exclude these will make the report usable.

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

MDGP 2018 R2 Feature of the Day: Transaction Level Post Through General Ledger

Microsoft Dynamics GPThe Inside Microsoft Dynamics GP blog has started a series Feature of the Day posts for Microsoft Dynamics GP 2018 R2 on which I am following and adding commentary. The series index for this series of posts is here.

The seventh Feature of the Day is transaction level post through general ledger. This feature is a new posting option in the Posting Setup window (Administration area page » Setup » Posting » Posting); when Allow Transaction Posting is marked, a new checkbox for Post Through General Ledger Files is now available:

Posting Setup

Continue reading “MDGP 2018 R2 Feature of the Day: Transaction Level Post Through General Ledger”

MDGP 2018 R2 Feature of the Day: Monthly Recurring Batches

Microsoft Dynamics GPThe Inside Microsoft Dynamics GP blog has started a series Feature of the Day posts for Microsoft Dynamics GP 2018 R2 on which I am following and adding commentary. The series index for this series of posts is here.

The first Feature of the Day is monthly recurring batches. This new feature allows ou to, on both Monthly and Bi-monthly batches to mark a Use last day of month checkbox which will update the Posting Date to the last day of the month.

This functionality has been added to Receivables Management, Payables Management and Inventory Control:

Receivables Batch Entry

The example above, shows a receivabled batch dates 30/04/2027 which, with the new checkbox marked, will automatically set the posting date to the last day of the month. So, when the batch is posted the next posting date would be set to May 31.

My initial impression was that this would be a good addition, until I realised that it did not include the General Ledger Financial Batches. I can’t think of a single client who uses recurring batches in any of Receivables, Payables or Inventory.

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

Debugging Integration Manager Crashes

Microsoft Dynamics GPWe’ve had two separate clients recently log calls where Integration Manager was crashing while performing an integration.

The first client was doing an Inventory Items integration on Microsoft Dynamics GP 2015 R2 and the other was doing a Sales Transaction integration on Microsoft Dynamics GP 2016 R2.

Both of the integrations had been running fine for quite a long period of time before starting to crash; no changes had been made to either system and I’ve not been able to determine why Integration Manager (IM) has started crashing.

However, by the use of two ini file switches, we were able to determine what error was being encountered by IM resulted in a crash.

The two switches are already present in the ini file (C:\Program Files (x86)\Microsoft Dynamics\Integration Manager nn/Microsoft.Dynamics.GP.IntegrationManager.ini by default) where the False value needs to be changed to True:

[IMGPPrv]
ShowDynamics=False
DoUIRedraw=False

When these switches are set to True, the Microsoft Dynamics GP windows are not hidden when the integration runs.

We found that for the Inventory Items integration, accounts either didn’t exist, didn’t allow account entry or were inactive; for the Sales Transaction integration, Analytical Accounting (AA) had been enabled for one of the accounts and the integration didn’t handle AA.

I created a VB script for the Inventory Items integration to check the accounts in the Before Document script and cancel the document if the account was going to be a problem.

MS Connect Suggestion: On Purchase Stop Summarising PR Lines

Microsoft Dynamics GPThis suggestion came about from an issue raised by a client while I was working with them to implement Purchase Order Processing with Workflow for approvals of purchase requisitions (PRs).

The issue encountered, is that when multiple lines for the same product at the same cost are added to the PR, approved and converted to PO, these lines are consolidated. This results in loss of information as only one item description or comments are pulled through to the PO.

To illustrate this, I created the following example.

First, create a PR with at least two lines. I have used the 2-A3284A product and changed the description on both rows:

Purchase Requisition Entry

Continue reading “MS Connect Suggestion: On Purchase Stop Summarising PR Lines”

Historical Excel Reporting Price Increase Coming

Microsoft Dynamics GPMark Polino has a set of Historical Excel Reports available for sale. The reports available are as follows:

  • Receivables Management Historical Aged Trial Balance
  • Payables Management Historical Aged Trial Balance
  • Historical Inventory Trial Balance
  • Historic Stock Status Report

Now is the ideal time to buy them, as the price is increasing on 1st April 2017.

SQL Script To Create macro To Activate BOMs

Microsoft Dynamics GPWhile implementing Microsoft Dynamics GP for a new client a while ago, we used Integration Manager to import over 100,000 Inventory items and then a SQL script to insert the 80,000 bill of materials (BOMs).

This worked well, in that it got all of the information loaded, but found that if we inserted the BOMs in this way, they could not be viewed in the BOM Inquiry window.

I used a SQL query to change the status from Active to Pending and then looked at the best way of changing them to Active through the Dynamics GP.

The only way to bulk change the data was by using a GP Macro; the usual way we do this is to do an extract of the data and then mailmerge this into a prerecorded macro in Microsoft Excel.

However, this can be avoided, by using the SQL select to not only get the data, but to output the macro at the same time:

/*
Created by Ian Grieve of azurecurve|Ramblings of a Dynamics GP Consultant (http://www.azurecurve.co.uk)
This code is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 2.0 UK: England & Wales (CC BY-NC-SA 2.0 UK).
*/
SELECT DISTINCT
	'# DEXVERSION=11.00.0364.000 2 2
	CheckActiveWin dictionary ''default''  form bmBillMaintenance window bmBillMaintenance 
	  TypeTo field ''Item Number'' , ''' + RTRIM(BMH.ITEMNMBR) + '''
	  MoveTo field ''Bill Status'' item 0 
	  ClickHit field ''Bill Status'' item 2  # ''Pending'' 
	  MoveTo field ''Expansion Button 1'' 
	  ClickHit field ''Expansion Button 1'' 
	NewActiveWin dictionary ''default''  form bmBillMaintenance window ChangeStatus 
	  ClickHit field ''Bill Status'' item 1  # ''Active'' 
	  MoveTo field ''Process Button P'' 
	  ClickHit field ''Process Button P'' 
	NewActiveWin dictionary ''default''  form bmBillMaintenance window bmBillMaintenance 
	  MoveTo field ''Save Button'' 
	  ClickHit field ''Save Button'' 
	'
FROM
	BM00101 AS BMH
INNER JOIN
	BM00111 AS BMC
		ON BMC.ITEMNMBR = BMH.ITEMNMBR
WHERE
	BMH.Bill_Status = 2

I needed to make sure that SSMS was configured to return the data into text and that the data returned was more than the default 256 characters.

Once you have the returned macros, save the file, open Bill of Materials Maintenance and then run the macro.