G/L Entry No. vs Vendor/Customer/Bank Entry No.

Phenno

You, probably, already found out that Entry No. in G/L Entry is same as Entry No. tha receives applicable "ledger entry" such are vendor, customer, bank...

Is there a special reason for this?

Marije_Brummel

The reasons can be

A.) It is handy

B.) It saves the trouble of finding a unique number

C.) Tablelocking?

D.) ?? Anyone

kine

It is the only connection between GL Entry and Cust/Vend/Bank entry...

Phenno

Mark Brummel wrote:

The reasons can be

A.) It is handy

B.) It saves the trouble of finding a unique number

C.) Tablelocking?

D.) ?? Anyone

Handy for what?
Is it used in Navigate function? (I never deeply investigated how navigate works, must say)

The only reason could be cause of Document No. is not a real unique type of key, it can be duplicated sometimes... but master/detail (or master/master) structure is kind of weird. To primary keys are forces to be same.

Are there any other tables that has this feature?

Marije_Brummel

It is used in the G/L register form.

We use it in our add-on for additional entries also available from this form and created when posting g/l journals.

Phenno

Mark Brummel wrote:

It is used in the G/L register form.

We use it in our add-on for additional entries also available from this form and created when posting g/l journals.

well, it's clear that it has to be used in g/l register...

Ok, thx ppl. I haven't found documentation for this feature so I was little bit confused.. I thought there was a "deeper" reason for this.

Alex_Chow

Phenno wrote:

You, probably, already found out that Entry No. in G/L Entry is same as Entry No. tha receives applicable "ledger entry" such are vendor, customer, bank...

Is there a special reason for this?

This is just for audit trail purpose. In case a very paranoid person want to challenge the system.