Source Type / Source No. in G/L Entry table.

MarkKeener
MarkKeener Member Posts: 17
edited 2010-03-23 in NAV/Navision Classic Client
I have a client that has a report that they run against table 17 that shows what they've spent for each G/L account with each of their vendors. They do this using the Source Type and Source No. fields that are populated automatically when using either the purchase journal or a purchase invoice.

However, sometimes the wrong G/L account is entered and they want to reclassify the expense to another G/L account. This is done using a regular G/L Journal Entry. But, when doing that, the source type and source number fields are not populated in the journal and so the report is no longer accurate.

I already know that I can expose the Source Type and Source No. fields on the G/L Journal Entry form and they will populate. Is there any reason that I SHOULDN'T do this? Are these fields used for any other reason than to provide a reference back to the vendor (or customer, bank acct, etc.) when entries are made from subsidiary ledgers?

I know this sounds like a dumb question. I can't think of any reason why I shouldn't use these fields in a journal entry, I just want to make sure I'm not overlooking something.

THANKS!!

Comments

  • David_Singleton
    David_Singleton Member Posts: 5,479
    The idea is that if a user should not be able to edit a field, then the table will be non editable (Through license) or the field will be non editable (through properties) or there will be code to give an error message (on validate), always at the table level.

    So if you can with an end user license, go to table designer an modify a field then you have to assume that the developer that created that field wants to allow you to change it.

    So yes you should be able to expose these fields without problems.
    David Singleton

Categories