I think this is a bug, but I wanted some feedback on it before I raised
a JIRA issue...
Any comments anyone?
Chris Snow wrote:
Hi Jacopo,
It seems that you must provide a glAccountTypeId, or a glAccountId for
a transaction entry. If neither are set when you verify a
transaction, the following error message is given (on the demo system):
"Gl account id is not set for [00001] or mapping not found for account
type"
If you don't provide a glAccountId, and only provide a
glAccountTypeId, is there a mapping somewhere to map the two id's? It
appears that AcctgTransService.xml is not doing the mapping, it's only
checking for glAccountId?
<if-empty field="acctgTransEntry.glAccountId">
<add-error><fail-message message="Gl account id is not
set for [${acctgTransEntry.acctgTransEntrySeqId}] or mapping not found
for account type ${acctgTransEntry.glAccountTypeId}"/></add-error>
</if-empty>
Many thanks in advance,
Chris
Jacopo Cappellato wrote:
<div class="moz-text-flowed" style="font-family: -moz-fixed">Hi Chris,
usually the glAccountTypeId is passed to the service in order to
retrieve the proper glAccountId (this is done with a series of lookup
on GL mapping entities)
Regards,
Jacopo
On Sep 21, 2009, at 7:28 AM, snowc wrote:
When adding a transaction entry, there are fields for GlAccountType and
GlAccountId.
Why do we need to enter the GlAccountType when it can be obtained
from the
GlAccount?
Many thanks in advance,
Chris
--
View this message in context:
http://www.nabble.com/Accounting-transaction-%3A-GlAccountType-tp25530186p25530186.html
Sent from the OFBiz - User mailing list archive at Nabble.com.
</div>
