• Introducing Dark Mode! Switch by clicking on the lightbulb icon next to Search or by clicking on Default style at the bottom left of the page!

Object acct setup

Bgetty

Active Member
Hi all,
We are in the process of revising our Chart of Accounts and am looking for some opinions from others.
In particular, I am wondering what others think about building some logic (for on-line inquiries or reporting) into object accounts. Presently, we do not use category codes on object accounts (used extensively on BU though). When I took the General Accounting I course the instructor recommended staying away from category codes on object accounts. For the life of me, I do not remember why though, but I did write it the GA I course manual.

Brian Getty, CGA
Kinross Gold-Timmins Operation
CANADA
WorldSoftware A7.3 Cum 11 V4R5
 

Graham_Aberdein1

Active Member
Hi Brian,

We don't use account category codes extensively either. We use them for
selective reporting using a relatively small portion of our
chart-of-accounts.

The main reason for us is the maintenance can be significantly greater than
for BU category codes, given that account category codes have to be set up
at the BU.Object.Sub level. Mind you if you have your chart-of-accounts set
up in a logical fashion (something to strive for), then you could use
Worldwriter to update your account category codes.

There may also be performance issues on reporting/inquiries if you use
account category codes extensively - but I'm not sure since, as mentioned,
we don't use them much. Perhaps others on the list can comment?

Hope this helps.

Graham G. Aberdein
Clarica
World A7.3 cum 11 (G/L, A/P, F/A)







Bgetty <bgetty@kinross.com>@jdelist.com on 13/03/2001 11:33:12 AM

Please respond to jdeworld@jdelist.com

Sent by: owner-jdeworldml@jdelist.com


To: jdeworldml@jdelist.com
cc:
Subject: Object acct setup


Hi all,
We are in the process of revising our Chart of Accounts and am looking for
some opinions from others.
In particular, I am wondering what others think about building some logic
(for on-line inquiries or reporting) into object accounts. Presently, we do
not use category codes on object accounts (used extensively on BU though).
When I took the General Accounting I course the instructor recommended
staying away from category codes on object accounts. For the life of me, I
do not remember why though, but I did write it the GA I course manual.

Brian Getty, CGA
Kinross Gold-Timmins Operation
CANADA
WorldSoftware A7.3 Cum 11 V4R5
--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat
=&Board=W&Number=7219
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +
This is the JDEList World Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +
 
I would recommend that you not build logic into the object account. Instead,
use the 3rd account number field if you want to put meaning into your
account. For example, I have used the letter B in the 3rd account number
field that had 1110.1 as the obj, sub, which was a bank account, with a large
volume of inquires and entries. Depending on your General Ledger constants it
could be entered as a B or *B, etc, and the system will recognize the
relationship to 1110.1. The 3rd account number field is alpha/numeric, but
must be unique across all companies.
Without knowing more about your organizational structure I can say from my
experience as a user and a consultant on many implementations I have found
the use of category codes at the account level to be helpful. It allows you
to group like accounts across entities.

Sandra Scribner
SCB Enterprise Solutions
401-421-9910 ext 16
 

Colin_Hugill

Reputable Poster
Brian,

Cat Codes at the account level work well, but the gothcha factor relates to
maintaining them. Hence the instructor would have tried to steer you away
from them unless there was no other way for you to derive the information
that you want.

You need a very good "MASTER" (ie model) business unit with all unique
obj.sub's contained within it. You should make sure the cat codes are
correct in this model. Every time the cat codes become 'out of whack' you
can use the advanced technical functions to do a global update of cat codes
based on the "MASTER" (option 5 on G09316 - pgm P09813)

Regards...... Colin HUGILL
 

Colin_Hugill

Reputable Poster
Brian,

One thing I forgot to mention was the possibility of using the ALTERNATE
OBJ.SUB fields on the account master. Like cat codes, these also require
careful maintenance. The advantage that ALT obj.sub has over use of the 3rd
account number field is that the ALT obj.sub does not have to be unique.

Mostly though, both Cat Codes and ALT obj.sub give the best benefits in
FASTR reporting. I can't remember how much you can use them for on screen
inquiry etc.

Cat codes 21 22 & 23 may very useful. The "Statutory Account Inquiry" (menu
G0912 opt 23) is based around these codes. The inquiry uses the same front
end program as the low volume consolidator but the second program behind it
is different.

It's a case of horses for courses really.

Regards...... Colin HUGILL
 
Top