GL Journals

[anhhn]

1. Some accounts can be used in GL_Journal (like Advance, Other Receivables, Other Payable, etc) but I need to ensure that BPartner is entered on the Journal Lines. Currently I write a script callout for each account, but it takes too much work (image 100+ accounts). Is it possible to do like this:
- Create custom fields in Account Element: BP Mandatory (Y,N);
- Create script callout (or validator) in GL_JournalLine to check, if BP Mandatory of the Account is 'Y', raise error alert if user ignore to enter BPartner.

2. In Vietnam, we need to declare "against" or "counter" account, i.e.
DR 1111 $10
DR 1381 $5
CR 3381 $15

When you run report for account 1111, for amount $10, counter account is 3381, report for 3381 need to split $15 into ($10 counter account = 1111 and $5 counter account=$5)
Things are complicated in ADempiere since we can enter like this:
DR 1111 $10
DR 1381 $5
CR 3381 $7
CR 334 $8
I heard that Oracle EBS faces the same dilemma and there is proposal of a custom forms in this case, which require user to enter "counter account" manually for each lines. Our intention is "user cannot save journal line in this case". Again, can it be done in script callout?

3. At the start of 2010, we propose new way to enter GL_Journal:
http://sourceforge.net/projects/adempie ... ic/3510011
We like to have this features in the iDempiere version, is it possible (our developer can do all necessary things for the change).

Thanks
Anh Han

[jdcs]

Hi

I looked into your proposed GL/Line entry, it looks good but I am afraid that accountants will be comfortable with it, rather it is better for them to use account combination with ability to make the combination online - when required.

Regarding the case of making Business Partner "Mandatory" in such entry, to my knowledge you can make this:
1. On the Accounting Schema Window, Accounting Schema Element tab - Set the BPartner as Mandatory
2. Restart Adempiere
3. Go to the Journal Line and try to create any combination -
... know the Business Partner is REQUIRED.

I think this may solve your need except the more organized form.

[globalqss]

Hi Anh, about 3 -> I repeat my positive vote on such thread.

That would solve easily your number 1 - I would suggest making the BP mandatory always and use your own company as BP when cannot be defined.

About the 2. I didn't understand the case.

Regards,

Carlos Ruiz

[anhhn]

Thank jdcs and Carlos, I totally forget Mandatory option in Schema

As for 2, all I need is that: If there is many-to-many DR and CR lines in one Journal, raise error and don't let it completed.

Regards,
Anh Han

[edwinang]

I am not very sure bout this. But will ticking Mandatory at BP caused problem with posting of document like Physical Inventory? As i recall, we don't have business partner in M_Inventory. Can we still post in document when the mandatory element is not available?
Just a thought.

Regards,
Edwin

[globalqss]

Good point Edwin, I think it deserves a test to check if that works.

Anh, about 2 sounds like implementable via a ModelValidator BEFORE_POST on GL_Journal.

Regards,

Carlos Ruiz