Changing the posting type on an account after you close the year in General Ledger for Microsoft Dynamics GP

Microsoft Dynamics GP 2013 R2 (12.00.1745) and higher versions:

New functionality was added that will allow you to reopen a year yourself that was already closed successfully. With this new functionality, you can reopen the GL year, change the posting type on the GL Account setup, and simply reclose the GL Year again so the account closes properly. To do this, follow these steps:

1. Have all users exit all companies, and make a current backup of the company database.

Note: If any other users are logged into any company in this Microsoft Dynamics GP installation, you will get a message "You cannot reverse the historical year because other users are logged in to the system." All users need to be logged out of all companies. 

2. Click on Microsoft Dynamics GP, point to Tools, point to Routines, point to Financial and click Year-End Closing.

3. In the Year-End Closing window, click on the Reverse Historical Year button at the bottom.

4. Click Process to reopen the last closed historical year as shown in the Year to Open field.  

5. Click Continue to verify that you have made a backup of the company database. If not, click Cancel and make a backup of the company database before proceeding.

Note: This process will physically move all the historical data from the GL history table to the GL Open Transaction table, and reverse all the Beginning Balance Entries that we brought forward. This process will reopen the GL year as if it was never closed in the first place.

6. Once the year is reopened, the next historical year will populate the window so you can repeat for as many years as you need to be reopened. The historical years can only be reopened in consecutive order starting with the most previously closed year. Just exit out of these windows once you have the year(s) you want to be reopened.

7. Next click on Cards, point to Financial and click Account. Select the GL account you need and change the Posting Type field to Balance Sheet or Profit and Loss as needed and click Save.

8. When you have finished editing the GL account type, click on Microsoft Dynamics GP, point to Tools, point to Routines, point to Financial and click Year-End Closing and reclose the GL year again. Print/review the Year End Closing report as desired.

Note: When you reopen and reclose a GL year, make sure that the Retained Earnings account being used has not changed, and that no historical data has been purged from that year. 

9. Verify the GL account has or doesn't have a beginning balance as needed. 


Q: Why are some Beginning balances different for GL accounts in which I did not change the posting type? 

A: The system allows you to post one historical year back and it creates separate BBF entries for those transactions. However, now if you reopen and reclose the year, those transactions will now be included in the new BBF entry as if it was actually keyed during the open year. It is now considered a current year transaction for that year rather than a historical year posting and will be included in the BBF entry that is recalculated. 

Microsoft Dynamics GP 2013 SP2, Microsoft Dynamics GP 2010, Microsoft Dynamics GP 10.0 and all prior versions:

Use one of the following methods to correct the posting type for the next year.

• If the account is supposed to be a profit-and-loss account, use Method 1 below.

• If the account is supposed to be a balance sheet account, use Method 2 below.

Note Before you follow the instructions in this article, make sure that you have a complete backup copy of the database that you can restore if a problem occurs.

Method 1: The account is supposed to be a 'profit-and-loss' account

As a balance-sheet account, this account will have a beginning balance after the year-end closing process is completed. To change the account to a profit-and-loss account and to reverse the beginning balance, follow these steps:

On the Cards menu, point to Financial, and then click Account. In the Account Maintenance window, type the account number in the Account field. Make sure that the Posting Type area is set to Balance Sheet, and then click Save. The type needs to be Balance Sheet type at this point so we offset the balance that was carried forward and it doesn't affect the RE account now. 

Use one of the following methods, depending on whether you are registered for multicurrency or not registered:

If you are registered for Multicurrency Management in Microsoft Dynamics GP, follow these steps:
In Microsoft Dynamics GP, point to Tools on the Microsoft Dynamics GP menu, point to Setup, point to Financial and then click Multicurrency.

In the Maintain History area, click to clear the General Ledger Account checkbox.
If you are not registered for Multicurrency Management, open SQL Server Management Studio and run the following statement against the company database:
UPDATE MC40000 SET MNSUMHST = 0

Change the Maintain History settings in the General Ledger Setup window so we don't keep the actual journal entry in the prior year, as we only want to offset the BBF that was created. To change the setting, follow these steps: 

In Microsoft Dynamics GP, point to Tools on the Microsoft Dynamics GP menu, point to Setup, point to Financial and then click General Ledger

In the Maintain History area, click to clear the Accounts checkbox and the Transactions check box.
In the Allow area, click to select the Posting to History check box. We want to be able to post an offsetting journal entry using a prior year date. Click OK.
Reopen the period for the prior Fiscal Year. To do this, follow these steps. 
In Microsoft Dynamics GP, point to Tools on the Microsoft Dynamics GP menu, point to Setup, point to Company and then click Fiscal Periods.
In the Fiscal Periods Setup window, make sure that the Financial period for the recently closed year is open.
Enter a journal entry to offset the incorrect beginning balance. To do this, follow these steps:
On the Transactions menu, point to Financial, and then click General.
In the Transaction Entry window, enter a transaction that reverses the incorrect beginning balance of the profit-and-loss account.
In the Transaction Date field, enter a date that is in the closed fiscal year such as 12/31/201x.

For example, if the profit-and-loss account has an incorrect debit beginning balance of $100.00, create a transaction that credits the profit-and-loss account for $100.00, and then debit the retained earnings account for $100.00.

Click Post. (The General Posting Journal should show the entry listed twice.  The first is for the original entry, but due to our settings, we won't be keeping that, and the second set is for the BBF entry that will offset the balance.)

Note The transaction updates only the current year because the Maintain History settings are not enabled.

Change the Maintain History settings in the General Ledger Setup window back to how they originally were. To do this, follow these steps: 
In Microsoft Dynamics GP, point to Tools on the Microsoft Dynamics GP menu, point to Setup, point to Financial and then click General Ledger.
In the Maintain History area, click to select the Accounts checkbox and the Transactions check box.
To post the transactions to the transaction history, click to select the Posting to History check box under Allow. If you do not want to post the transactions to the transaction history, click to clear this check box. Then, click OK.

Use one of the following methods to change the Multicurrency setting back to how it originally was, depending on whether you are using multicurrency or not:
If you are registered for Multicurrency Management, follow these steps:

In Microsoft Dynamics GP, on the Microsoft Dynamics GP menu, point to Tools, point to Setup, point to Financial, and then click Multicurrency.

In the Maintain History area, click to select the General Ledger Account checkbox.
If you are not registered for Multicurrency Management, open SQL Server Management Studio and run the following statement against the company database:
UPDATE MC40000 SET MNSUMHST = 1

Go back to the Fiscal Period setup and mark to close the Fiscal Period for the prior year again.
Now you can verify the balance on the GL account is $0.00 and then you can change the type on the account to Profit and Loss. To do this, on the Cards menu, point to Financial, and then click Account. In the Account Maintenance window, type the account number in the Account field. In the Posting Type area, click Profit and Loss, and then click Save.

Method 2: The account is supposed to be a 'balance-sheet' account 

As a profit-and-loss account, this account will not have a beginning balance after the year-end closing process is completed. To change the account to a balance sheet account and to create the beginning balance, follow these steps:

On the Cards menu, point to Financial, and then click Account. In the Account Maintenance window, type the account number in the Account field. In the Posting Type area, click Balance Sheet, and then click Save. Select Balance Sheet so that the correcting entry that you make in step 6 later in this section will correctly update the beginning balance for the current year.

Use one of the following methods, depending on whether you are using multicurrency or not:
If you are registered for Multicurrency Management in Microsoft Dynamics GP, follow these steps:
In Microsoft Dynamics GP, point to Tools on the Microsoft Dynamics GP menu, point to Setup, point to Financial and then click Multicurrency.

In the Maintain History area, click to clear the General Ledger Account checkbox.
If you are not registered for Multicurrency Management, open SQL Server Management Studio and run the following statement against the company database:
UPDATE MC40000 SET MNSUMHST = 0

Change the Maintain History settings in the General Ledger Setup window using these steps: 
In Microsoft Dynamics GP, point to Tools on the Microsoft Dynamics GP menu, point to Setup, point to Financial and then click General Ledger.

In the Maintain History area, click to clear the Accounts checkbox and the Transactions check box.
In the Allow area, click to select the Posting to History check box, and then click OK.
Verify fiscal period is open so you can post to the prior year. To do this, follow these steps. 
In Microsoft Dynamics GP, point to Tools on the Microsoft Dynamics GP menu, point to Setup, point to Company and then click Fiscal Periods.

In the Fiscal Periods Setup window, make sure that the Financial period for the recently closed year is open.

Enter a journal entry to create a beginning balance for the account. To do this, follow these steps:
On the Transactions menu, point to Financial, and then click General.

In the Transaction Entry window, enter a transaction that creates the correct beginning balance of the balance sheet account.
In the Transaction Date field, enter a date that is in the closed fiscal year.

For example, if the balance sheet account should have a debit beginning balance of $100.00, create a transaction that credits the retained earnings account for $100.00 and that debits the balance sheet account for $100.00.
Click Post.

Note The transaction updates only the current year because the Maintain History settings are not enabled.

Change the Maintain History settings in the General Ledger Setup window back to how they originally were. To do this, follow these steps: 

In Microsoft Dynamics GP, point to Tools on the Microsoft Dynamics GP menu, point to Setup, point to Financial and then click General Ledger.

In the Maintain History area, click to select the Accounts checkbox and the Transactions check box.

To post the transactions to the transaction history, click to select the Posting to History check box under Allow. If you do not want to post the transactions to the transaction history, click to clear this check box. Then, click OK.

Go back to the Fiscal Period setup and mark to close the Fiscal Period for the prior year again
Use one of the following methods to change the Multicurrency setting back to how it originally was, depending on whether you are using multicurrency or you are not:

If you are registered for Multicurrency Management, follow these steps:

In Microsoft Dynamics GP, point to Tools on the Microsoft Dynamics GP menu, point to Setup, point to Financial and then click Multicurrency.
In the Maintain History area, click to select the General Ledger Account checkbox.
If you are not registered for Multicurrency Management, open SQL Server Management Studio and run the following statement against the company database:
UPDATE MC40000 SET MNSUMHST = 1

Microsoft SQL Server VS Oracle

There are many different relational database management systems (RDBMS) out there. You have probably heard about Microsoft Access, Sybase, and MySQL, but the two most popular and widely used is Oracle and MS SQL Server.  Although there are many similarities between the two platforms, there are also a number of key differences. In this blog, I will be taking a look at several in particular, in the areas of their command language, how they handle transaction control and their organization of database objects.

Language

Perhaps the most obvious difference between the two RDBMS is the language they use. Although both systems use a version of Structured Query Language or SQL, MS SQL Server uses Transact SQL, or T-SQL, which is an extension of SQL originally developed by Sybase and used by Microsoft. Oracle, meanwhile, uses PL/SQL, or Procedural Language/SQL. Both are different “flavors” or dialects of SQL and both languages have different syntax and capabilities. The main difference between the two languages is how they handle variables, stored procedures, and built-in functions. PL/SQL in Oracle can also group procedures together into packages, which can’t be done in MS SQL Server. In my humble opinion, PL/SQL is complex and potentially more powerful, while T-SQL is much more simple and easier to use.

Transaction Control

Another one of the biggest differences between Oracle and MS SQL Server is transaction control. For the purposes of this article, a transaction can be defined as a group of operations or tasks that should be treated as a single unit. For instance, a collection of SQL queries modifying records that all must be updated at the same time, where (for instance) a failure to update any single records among the set should result in none of the records being updated. By default, MS SQL Server will execute and commit each command/task individually, and it will be difficult or impossible to roll back changes if any errors are encountered along the way. To properly group statements, the “BEGIN TRANSACTION” command is used to declare the beginning of a transaction, and either a COMMIT statement is used at the end. This COMMIT statement will write the changed data to disk, and end the transaction. Within a transaction, ROLLBACK will discard any changes made within the transaction block. When properly used with error handling, the ROLLBACK allows for some degree of protection against data corruption. After a COMMIT is issued, it is not possible to roll back any further than the COMMIT command.

Within Oracle, on the other hand, each new database connection is treated as a new transaction. As queries are executed and commands are issued, changes are made only in memory and nothing is committed until an explicit COMMIT statement is given (with a few exceptions related to DDL commands, which include “implicit” commits, and are committed immediately). After the COMMIT, the next command issued essentially initiates a new transaction, and the process begins again. This provides greater flexibility and helps for error control as well, as no changes are committed to disk until the DBA explicitly issues the command to do so.

Organization of Database Objects

The last difference I want to discuss is how the RDBMS organizes database objects. MS SQL Server organizes all objects, such as tables, views, and procedures, by database names. Users are assigned to a log in which is granted accesses to the specific database and its objects. Also, in SQL Server each database has a private, unshared disk file on the server. In Oracle, all the database objects are grouped by schemas, which are a subset collection of database objects and all the database objects are shared among all schemas and users. Even though it is all shared, each user can be limited to certain schemas and tables via roles and permissions.

In short, both Oracle and SQL Server are powerful RDBMS options. Although there are a number of differences in how they work “under the hood,” they can both be used in roughly equivalent ways. Neither is objectively better than the other, but some situations may be more favorable to a particular choice. Either way, Segue can support these systems and help to make recommendations on how to improve, upgrade, or maintain your key mission-critical infrastructure to make sure that you can keep your focus on doing business.