I've gotten questions from people over the years about long account numbers/lots of segments, so I thought I would put together a short list of the pitfalls of very large account numbers.

The longest GL account number I've worked with in GP is 27 digits, 8 segments. This is different from the account framework which may be large to accomodate changes but most companies have a much smaller…

I saw a problem recently when a user had trouble while trying to load up entry list in the Correct Journal Entry Window. I gave up after about 10 minutes. I then…

Back to basics. This is something most of the GP newbies ask us. While we have Posting Journals reprint functionality available for all other…

Some features exist in Microsoft Dynamics GP that have been there ‘forever’, but are not given much attention. This post explores the ‘Include in Lookup’ option on the Account Maintenance window.

What’s the big deal?

The big deal is that when new accounts are created the default selections are most likely not the appropriate settings for your accounts, yet these selections are often left ‘as is’. Take a look at the familiar Account Maintenance…

We all know that we can increase the number of characters in an account segment up to the maximum number allowed in the Account Framework. However, if we need to REDUCE the number of characters, all of the documentation tells us we cannot.

Once upon a time there was not an option to display an expanded account width. Therefore, if you wanted to use an alphabetical character instead of a number, the alphabetical character would not be displayed if it was wider than a number. The only way around this limitation was to make the segment an extra character long.

After the ‘display width’ option was introduced,…

Note:

 Like all scripts, this one is provided *as is*, without any warrantee for its suitability for your purpose. There is no substitute for due diligence

-- =============================================
-- Written by Steve Gray
-- 941-747-3669
-- =============================================


-- Drop stored procedure if it already exists
IF EXISTS (
  SELECT * 
    FROM INFORMATION_SCHEMA.ROUTINES 
   WHERE SPECIFIC_SCHEMA = N'dbo'
     AND SPECIFIC_NAME = N'FP_TrialBalanceSummary' 
)
   DROP PROCEDURE FP_TrialBalanceSummary
GO
CREATE PROCEDURE FP_TrialBalanceSummary
-- FP_TrialBalanceSummary '1/1/2009','10/31/2009','4010-01','no','2009','yes','yes','yes','yes','Segment1'


@StartDate datetime,
@EndDate datetime,
@GLAccountNumber varchar(17), 
@HistoryYear varchar(3), /* yes/no*/
@Year int,
@IncludeInactiveAccounts varchar(3), /* yes/no */
@IncludePostingAccounts varchar(3), /* yes/no */
@IncludeUnitAccounts  varchar(3), /* yes/no */
@IncludeZeroBalanceAccounts   varchar(3), /* yes/no */
@SortBy varchar(10) /* the account segment to sort by*/


AS


-- validate
if YEAR(@startdate) <> @Year or YEAR(@EndDate) <> @Year begin
    select @StartDate = '1/1/1900', @EndDate = '1/1/1900'
end


--============================================================================
-- handle account type
--============================================================================
declare @accountTypes table (accountType int)
insert into @accounttypes (accountType) values (3)
insert into @accounttypes (accountType) values (4)
if @IncludeUnitAccounts = 'yes' begin
    insert into @accounttypes (accountType) values (2)
end
if @IncludePostingAccounts = 'yes' begin
    insert into @accounttypes (accountType) values (1)
end


--============================================================================
-- main query
--================================…