Changing the Table G\L Entries' G\L Account No.

cpina

Navision 4.0
I need changing value of G\L Account no.
On C/AL's side there is no problem since it does not have code in the validation trigger.
Will it change something in the logic?

Phenno

cpina wrote:

Navision 4.0
I need changing value of G\L Account no.
On C/AL's side there is no problem since it does not have code in the validation trigger.
Will it change something in the logic?

Except of the fact that in most countries it's illegal to do that, I think you'll not have a problem with logic, at least in Navision Logic.

You'll have a problem with papers, documents which you made upon posting through journals (if balance of accounts that you're changing is changed through journals) etc...

ssingla

Posted entries should not be modified under any circumstances.

Though it is possible by coding or direct modification the same should not be done as it is not only illegal it is also not ethical. The audit trail is lost and the system is then prone to manipulations and frauds.

Moreover the account numbers in G/L entry has some times reference to other tables like ILE and value entry for actual and expected cost posting.

DenSter

Make sure you have a new pasport and tickets to a place that they can't find you, because that's not considered to be legal any place that I know of. If there is incorrect information in your general ledger, you need to correct it with new journals.

ssingla

Being a solution partner you should always work with integrity and ethics. Solutions which break the law should not be implemented. =;

David_Singleton

Actually its not at all illegal to change account numbers in your accounting system. I would guess that most Navision users have done it at some time. For instance, have you ever converted a client from One ERP system to Navision? Did they keep the EXACT GL structure as they had in their old system, or did they do some "clean up" of accounts to get the posting accounts to better match Navision.

Further to this, even within Navision I have made major changes for clients to restructure their accounts by changing the account numbers. (yes its rare, but I have done it).

The key though, is that the process needs to be audited. The companies auditors need to understand and accept the reasoning behind the change, and need an audit able "before after" so that they can confirm that no funny business happened.

Yes I understand what you are all saying, that basically it should not be possible to just go to GL account and change the number, and I agree, its far too easy. But in terms of Never, Its Illegal, well not always.

I remember one case where I was working with a client that had been upgraded from SAP to Navision. They brought in the entire SAP GL to Navision, and it eventually became a nightmare to manage, so we sat with the auditors, built a plan, and then ran through a process to merge a lot of accounts, and seperate a few others, giving a much more usable system. We had to have a valid audit at the day of the conversion, AND one that could be retrospectively compared with the original SAP Closing Audit.

A second case was a client that had been bought out, and their head office mandated a specific chart of accounts. I fought this because account schedules or consolidation could have given them the data they wanted, but in the end it was either that or dump Navision. Again its very complex, and not cheap, but there just are cases where its possible, and legal.

ssingla

The concept I have understood is that what is proposed to do is to Modify the posted G/L Entrie's G/L Account no. by way of some coding which means alterations and not renumbering.
Further as you have remarked if the scenarion as per you, what needs to be done is that you should have a backup of the old system as in lot of countries like our's (India) you can be asked to produce books of account for the last 8 years which they can match with any printout obtained during the search of the clients premises. Any difference in the printout and the system will create a lot of problems.

Also Auditor needs to physically sign the books of accounts audited by them and if there is some modification exist between that printed books and system as on date it will be looked with a suspicious look.

Subject to this it can be done.

kine

Do not forget the bug, solved in SP3 which is messing up the SIFT tables when record is renamed!!!

ssingla

SIFT table will come into picture if SQL option is used or is it applicable for Native DB also.

kine

Just for SQL option...