Dynamics GP 2018 R2 – HITB Include and Exclude Zero Quantity or Value

With the release of Dynamics GP 2018 R2, several new features were introduced to the core functionality in the system. In this post, we will shed a light on an interesting feature provided for the inventory module in regards to the Historical Inventory Trial Balance.
In previous posts, it has been thoroughly discussed that HITB usually encounters issues represented with zero quantity and negative/positive cost. The source of the problem is represented with mismatching issues between inventory cost layers ( IV10200, IV10201) from one side and (SEE30303) from the other side.
Here is a brief on the issue:
Inventory Cost Layers versus HITB (SEE30303)

Inventory Cost Layers versus HITB (SEE30303)

I have seen such case with multiple clients, resolving this case requires internal matching or rebuilding of the HITB inventory source in order to recalculate quantity and value records and ensure that historical and current inventory balances are matching.
In the same context, the recent release of Dynamics GP 2018 R2 has introduced an interesting feature for the HITB report represented with the ability to either include or exclude either items with “Zero Quantity” or “Zero Value”, this will ensure that HITB report is being filtered properly for all the zero quantity or value records.
In order to print the Historical Inventory Trial Balance report, follow the path below:
Reports > Inventory > Activity > Historical IV Trial Balance
HITB Report Modification
Best Regards
Mahmoud M. AlSaadi

Dynamics GP – Year End Closing – Query Timeout Expired Error | “The Stored Procedure glYearEndCloseMain”

If you are performing the year end closing procedure and encountering the error ” Query Timeout Expired” specifically at step 3 out 7, then an error message popped up ” The stored procedure glYearEndCloseMain returned the following results DBMS … “, you need to know that the GL year end closing procedure has failed as it partially closed the year.

Year End Closing - Query Timeout Expired Error | "The Stored Procedure glYearEndCloseMain"

Issue Diagnosis:

When closing the year, Dynamics GP goes through seven steps precisely in order to reconcile GL balances, check returned accounts, account types … etc and close the year.

Step 3 calls stored procedure “glYearEndCloseMain” which primarily moves records from GL20000 to GL30000, create BBF records. Here is the SQL statement which is causing the system to hang:

BEGIN
    DECLARE @stored_proc_name CHAR(26);
    DECLARE @retstat INT;
    DECLARE @param23 NUMERIC(19, 5);
    DECLARE @param24 INT;
    DECLARE @param25 INT;
    SET NOCOUNT ON;
    SELECT @stored_proc_name = ‘TWO.dbo.glYearEndCloseMain’;
    EXEC @retstat = @stored_proc_name 2017,
                                      2018,
                                      1,
                                      ‘Z-US$’,
                                      ,
                                      0,
                                      ‘AVERAGE’,
                                      ‘CLOSE’,
                                      639100,
                                      ‘GLTRX00014007’,
                                      ‘DYNSA’,
                                      ‘##0545413’,
                                      ‘##0545449’,
                                      ‘##0705413’,
                                      1460,
                                      0,
                                      0,
                                      639100,
                                      639100,
                                      0,
                                      ‘2017.01.01’,
                                      ‘2017.12.31’,
                                      @param23 OUT,
                                      @param24 OUT,
                                      @param25 OUT;
    SELECT @retstat,
           @param23,
           @param24,
           @param25;
    SET NOCOUNT ON;
END;

Resolution 
The very initial step to ensure that you restore Dynamics GP databases since in such case the GL tables would be partially corrupted due to having “partial year end closing”

The next step is to check the “Auto Growth – Maximum Size ” property on the database server for the GP database. The case occurred due to having insufficient database size restricted by the maximum size.

 

Management Reporter Crashing while Importing / Exporting Building Blocks

When migrating reports from one management reporter server to another, the easiest way is to export the management reporter building blocks from the original management reporter server and import them into the new server.

(more…)