David E Jones wrote:
Should we consider having an error journal in the demo data by default?
I'm guessing you've thought about this Jacopo and maybe you have some
reasons to not do it.
Yes, the error journal is already configured in the demo data for the
Company party.
The problem that Raj was having was probably caused by the fact that he
was not using the demo data; the error reported by Anil is caused by the
fact that the payment "demo10000" is associated to the TESTING
organization party... and we have not still configured the accounting
setup for that party.
It would definitely mask errors that people should be seeing and
resolving, but both short term and long term might smooth things out
with these accounting transitions. If an error journal gets really big
it shouldn't be too hard to fix configuration problems and then post the
entire error journal (and those transactions that succeed will go, and
those that still error out should stay in the journal). I think that
service already exists (it's one of the basic ones I wrote a LONG time
ago), but some UI changes may be needed or something.
Now, I understand the meaning of that service (posting the entire
journal); thanks for the information, we will use this feature.
Jacopo
Anyway, just some thoughts that might make this easier.
-David
On Jan 9, 2008, at 4:55 AM, Jacopo Cappellato wrote:
Anil, Raj,
both the errors are caused by the same auto posting accounting
transaction service related to payment applications; I'm working right
now to fix it (not sure if it is a missing demo setup or an error in
the service).
However, in the meantime, you can 'fix' it by defining an error
journal for your company:
* in Anil's scenario is the TESTING party (the demo payment is
associated to this party)
* in Raj's scenario... I'm not sure (Raj is probably using a
customized party).
By the way, the process to setup an error journal is very simple; I've
recently described this in another email but I'm copying here the same
notes:
============
The quickest way to fix this is to define a error journal for the
company: in this way, all the accounting transactions that cannot be
posted (for example because there isn't a mapping defined) are moved
to the error journal and no error is thrown.
You can create the error journal in this way:
1) go to Accounting-->General Ledger-->Setup-->Journals
and create a new journal:
https://demo.hotwaxmedia.com/accounting/control/SetupGlJournals?organizationPartyId=Company
2) go to Accounting-->General Ledger-->Setup-->Accounting Preferences
and select the journal in the "Error Gl Journal Id":
https://demo.hotwaxmedia.com/accounting/control/PartyAcctgPreference?organizationPartyId=Company
All the "incomplete" transactions will be visible here:
https://demo.hotwaxmedia.com/accounting/control/ListUnpostedAcctgTrans?organizationPartyId=Company
============
Jacopo
Raj Saini wrote:
I am facing the similar problem when I try to do the "Quick Ship
Entire Order" in Order Manager application when not using the demo
data. It works with demo data though.
Error I am getting is:
ERROR: Could not complete the Issue OrderItemShipGrpInvRes to
Shipment
[file:/tmp/ofbiz-trunk/applications/product/script/org/ofbiz/shipment/issuance/IssuanceServices.xml#issueOrderItemShipGrpInvResToShipment]
process [problem removing the orderItemShipGrpInvRes value: The
current transaction is marked for rollback, not beginning a new
transaction and aborting current operation; the rollbackOnly was
caused by: Service [createAcctgTransAndEntries] threw an unexpected
exception/errororg.ofbiz.service.ServiceValidationException: The
following required parameter is missing: [OUT]
[createAcctgTransAndEntries.acctgTransId] (The following required
parameter is missing: [OUT]
[createAcctgTransAndEntries.acctgTransId])] calling service
issueOrderItemShipGrpInvResToShipment in
createShipmentForFacilityAndShipGroup
Could it be due to new demo data in accounting package?
Thanks,
Raj
Anil Patel wrote:
Hi,
I did a clean install of demo data. Open the Payment "demo10000"
When I try to change payment status to Reveived by clicking on
"Status to Received" button following exception is thrown
Error calling event: org.ofbiz.webapp.event.EventHandlerException:
Service invocation error (Could not commit transaction for service
[setPaymentStatus] call: Roll back error, could not commit
transaction, was rolled back instead because of: Service
[createAcctgTransAndEntries] threw an unexpected
exception/errororg.ofbiz.service.ServiceValidationException: The
following required parameter is missing: [OUT]
[createAcctgTransAndEntries.acctgTransId] (The following required
parameter is missing: [OUT] [createAcctgTransAndEntries.acctgTransId]))
I am not sure if this is set up data issue or problem with code,
Ideas on what could be the problem here.
Regards
Anil Patel
