MDGP 2013 R2 Feature of the Day: Reverse Year End Close

The Inside Microsoft Dynamics GP blog started a series of Microsoft Dynamics GP 2013 R2 Feature of the day posts the other day. As they did with the Microsoft Dynamics GP 2013 Feature of the Day posts they are doing them as short posts containing a PowerPoint slide show. I am translating these from the PowerPoints into posts; you can find my series index here.

The twenty-sixth Feature of the Day covered is Reverse Year End Close. This feature adds the ability to reverse the GL Year End Close Process in order to open the previous fiscal year.

Before the reversal is performed then users are warned to create a backup and also verifies that all users are logged out of GP prior to starting.

The Reverse Historical Year button will be disabled if the end-user is not maintaining history in the GL Setup form.

The reverse is done by opening the Year-End Closing window (Financial >> Routines >> Year-End Closing) and clicking the Reverse Historical Year button.

The most recently closed year can then be reopened:

Reverse Historical Year

Click to show/hide the Microsoft Dynamics GP 2013 R2 Feature of the Day Series Index

Microsoft Dynamics GP 2013 R2 Feature of the Day
MDGP 2013 R2 Feature of the Day: SmartList Designer Go To's
MDGP 2013 R2 Feature of the Day: Identity Management - Login
MDGP 2013 R2 Feature of the Day: Purchase Requisitions
MDGP 2013 R2 Feature of the Day: Copy And Paste To General Ledger Transaction Entry
MDGP 2013 R2 Feature of the Day: Workflow
MDGP 2013 R2 Feature of the Day: Workflow Types
MDGP 2013 R2 Feature of the Day: Workflow User Delegation
MDGP 2013 R2 Feature of the Day: Default Fixed Asset ID From The Asset Class
MDGP 2013 R2 Feature of the Day: Identity Management - Scalability Groups
MDGP 2013 R2 Feature of the Day: Workflow Calendar
MDGP 2013 R2 Feature of the Day: Reprint Outstanding Transaction in Bank Reconciliation
MDGP 2013 R2 Feature of the Day: Requisition Management Integration Points
MDGP 2013 R2 Feature of the Day: Default Sort Order for Checks
MDGP 2013 R2 Feature of the Day: Document Attach - Scan
MDGP 2013 R2 Feature of the Day: Workflow History
MDGP 2013 R2 Feature of the Day: Workflow Email Notifications
MDGP 2013 R2 Feature of the Day: Azure Backups
MDGP 2013 R2 Feature of the Day: Suggested Item Enhancements - Analysis and Assignment
MDGP 2013 R2 Feature of the Day: Suggested Item Enhancements - Sales Script and Additional Information
MDGP 2013 R2 Feature of the Day: Dashboards
MDGP 2013 R2 Feature of the Day: Management Reporter Web Viewer
MDGP 2013 R2 Feature of the Day: Take Company Offline
MDGP 2013 R2 Feature of the Day: Encumbrance SQL Reporting Services Reports
MDGP 2013 R2 Feature of the Day: Email Or Print Any Report In Word Format
MDGP 2013 R2 Feature of the Day: Reverse Year End Close
MDGP 2013 R2 Feature of the Day: Document Attachment On Payables Transactions
MDGP 2013 R2 Feature of the Day: Roll Down Segment Changes
MDGP 2013 R2 Feature of the Day: Assign An Item To Multiple Sites
MDGP 2013 R2 Feature of the Day: Replace OLE Note With Document Attachment
MDGP 2013 R2 Feature of the Day: OLE Notes Migration Utility
MDGP 2013 R2 Feature of the Day: Purchase Order Prepayment Additions
MDGP 2013 R2 Feature of the Day: Print Remaining Documents
MDGP 2013 R2 Feature of the Day: Email By Document Type

Cashbook Bank Management – Value Exists In The PM_Key_MSTR Table

A client had an odd error with the Cashbook Bank Management module the other day when trying to enter a deposit; the following was printed on the exception report when trying to post the transaction:

Value exists in the PM_Key_MSTR table

I did some digging around and found that the Next Voucher Number field in Payables Management Setup – Options (Microsoft Dynamics GP menu >> Tools >> Setup >> Purchasing >> Payables Setup) was blank.

I set a new value in the Next Voucher Number field and the deposit could be posted without problem.

EFT File Format Import/Export Error

I’ve recently been creating an HSBC Standard 18 BACs file format for a client in Microsoft Dynamics GP 2010 R2.

Unfortunately, once I released it to their system, they reported an error with the import where the Creditor’s Cheque Name wasn’t being output on the resulting file.

I did some testing and it turns out to be a bug in the export function of the EFT File Format (Cards >> Financial >> EFT File Format) window in Microsoft Dynamics GP 2010 R2; I have subsequently tested on GP 2010 SP3 and GP 2013 and the import/export works fine. I realised something odd was going on when I looked at the template in the EFT File Format window (Cards >> Financial >> EFT File Format) and saw that while the Series was defined as Purchasing in the header, the scrolling window for the Data Field only had Receivables Management tables and fields available to it and not the Payables Management tables and fields I would expect;

EFT File Format

Continue reading

MDGP 2013 Feature of the Day: Copy AA Trx Dimensions For POP, SOP And GL

Microsoft are posting the Microsoft Dynamics GP 2013 Feature of the Day series on the Inside Microsoft Dynamics GP Blog.

The sixty second feature they’ve announced is Copy AA Trx Dimensions for POP, SOP And GL.

In Microsoft Dynamics GP 2013 when you copy a Sales Transaction (SOP) or Purchase Order (POP), you can now include the Analytical Accounting Transaction Dimension information;

Copy a Sales Order

Continue reading

MDGP 2013 Feature of the Day: Journal Entry History Inquiry

Microsoft are posting the Microsoft Dynamics GP 2013 Feature of the Day series on the Inside Microsoft Dynamics GP Blog.

The forty first feature they’ve announced is Journal Entry History Inquiry.

In versions prior to Microsoft Dynamics GP 2013, the only Journal Entry Inquiry was on open year journals. Microsoft Dynamics GP 2013 introduces the ability to perform an inquiry on historical years.

This feature modifies the Journal Entry Inquiry window to display information for both open and historical year journal entries;

Journal Entry History Inquiry

In the past I’ve directed users to the SmartList for doing a lookup on historical year journals, but this amended inquiry provides a quick, and much simpler, way for users to do this lookup.

This new feature is targeted at the following roles:

  • CFO
  • Accounting Manager
  • Controller
  • Accountant

MDGP 2013 Feature of the Day: Saved GL Batch Approval

Microsoft have started the Microsoft Dynamics GP 2013 Feature of the Day series on the Inside Microsoft Dynamics GP Blog.

The thirty seventh feature they’ve announced is Saved GL Batch Approval.

The Year-To_Date Transaction Open (GL20000) and Account Transaction History (GL30000) tables have been updated with new columns to store the approval user (APRVLUSERID) and date (APPRVLDT) in order to enhance tracking; this information will be passed from Posting Definitions Master (SY00500) when the batch is posted.

These two new columns can be used on reports;

SQL Server Management Studio

This new feature is targeted at the following roles:

  • Accounting Manager
  • Accountant
  • Controller & CFO

MDGP 2013 Feature of the Day: Reconcile IV To GL

Microsoft have started the Microsoft Dynamics GP 2013 Feature of the Day series on the Inside Microsoft Dynamics GP Blog.

The fifteenth feature they’ve announced is Reconcile IV To GL.

Microsoft Dynamics GP 10 saw the introduction of the Reconcile to GL report which allowed the automation of the reconciliation of differences in Receivables Management and Payables Management to the General Ledger. In Microsoft Dynamics GP 2013 the Inventory Control module will be added to the Reconcile to GL to help users identify the differences between the Historical Inventory Trial Balance and the GL inventory accounts;

Continue reading

Financial Year End Closing – Only Open Year Error Message

I was recently doing some training for a new client and, when showing them how to do period and year end processing encountered an error message when trying to do the Financial Year End Closing (Microsoft Dynamics GP menu >> Tools >> Routines >> Financial >> Year End Closing);

Financial Year End Closing - You must set up a new financial year before you can close the only open year.

This had me stumped for a few minutes as there were Open Year calendars (Microsoft Dynamics GP menu >> Tools >> Setup >> Company >> Financial Periods) on the system for 2011, 2012 and 2013. Typically in the UK a financial year runs from 1st April to 31st March; but this isn’t a hard and fast rule. This particular client has a different financial year and the error message was being produced as there was a gap of one day between the end of 2011 and the start of 2012. Once the calendar was fixed, the Year End Closing could be run without issue.