Using the GTEST command Note: Use caution when working with with GTEST. Always make a backup first. If necessary, seek the assistance of a certified Sage Business Partner, Sage Professional Professional Services Group, , or Sage Customer Support.
The GTEST command can be used to help identify Unbalanced Journals such as indicated in the error displayed below. GTEST does not correct the out of balance but instead displays the Journal Entry that Sage ERP X3 is attempting to create during the posting process. For example, if you are trying to diagnose an out of balance situation while posting a transaction in AR, AP, Inventory Accounting Accounting Interface or WIP accounting interface, interface, you can view the debits and credits to see where the out of balance is occurring.
Note: To ensure the only thing you are dealing with is the out of balance situation, run the
Accounting or WIP Interface prior to setting the GTEST parameter, otherwise, you will see debits/credits debits/credits for every transaction that has yet to post.
Setting the GTEST Command 1. Open the transact transaction ion you you are are attempt attempting ing to to post post 2. From From the tool toolbar bar,, select select que questi stion on mark mark (?) (?) / Diagn Diagnost ostic ic help help / Calcul Calculato atorr
Sage ERP X3- GTEST Command Revised 11/07/2012
Page 1
3. At the Calculator prompt, type sigma(GTEST=0,1,0 ) and press enter. A zero (0) will be returned. Note: This parameter is specific to the user logged in and will not affect other users.
The Parameter Value for DBG must be set to “Yes” to use the sigma function. This parameter value can be set at a folder level or at the user level.
4. Click the X to close the Calculator
Sage ERP X3- GTEST Command Revised 11/07/2012
Page 2
5. After activating this parameter, you will get a message for all the labels called by Functions following the “Object management”, “Processing ” or “Inquiry” template. This message will tell you what process and what label is called. PROCESS.$LABEL Example:
This feature will tell you the last label called before some misbehavior. It will allow you to focus on the part of a process which seems to be problematic, to call the debugging tool just before the problem, to open some information box showing data values, etc.
6. Click Ok through all the prompts and then click the Post button (this does not actually post anything) 7. Click Yes to Validate the Invoice
Sage ERP X3- GTEST Command Revised 11/07/2012
Page 3
8. The Journal Posting window will then launch displaying the entry that would be created when posted. Note in the Journal Posting below, only the Debit amount is generated. This would indicate that the cause of the unbalanced journal is in relation to the Credit amount of the posting.
Sage ERP X3- GTEST Command Revised 11/07/2012
Page 4
Finding the cause of the Unbalanced Journal Now that the GTEST command has displayed the unbalanced journal, you will need to research the cause of the out of balance. Some common occurrences are: Missing Lines on the Automatic Journal Custom Automatic Journals Rounding in the Amount lines of Automatic Journal Missing Accounts in Account Codes
Deactivating the GTEST Command To deactivate the GTEST, type sigma(GTEST=0,-1,0 ) at the Calculator prompt and press enter or exit X3 to turn off the parameter.
Sage ERP X3- GTEST Command Revised 11/07/2012
Page 5
