[6-stab] journal seqence not respected

Bug #726092 reported by Grzegorz Grzelak (OpenGLOBE.pl)
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Odoo Addons (MOVED TO GITHUB)
Fix Released
Low
OpenERP R&D Addons Team 3

Bug Description

I tried to use bank statement and cash registers functionality. It looks that journal entries created by bank statement or cash registers (using Confirm or Close CashBox respectively) doesn't take numbers from journal sequence but instead of numbers system enters a reference information as concatenation of Bank statement name (or cash register name) and line number.
See the screen. Only item with reference "tttt" is correct as it is created by "Pay invoice" button in invoice.

Related branches

Revision history for this message
Grzegorz Grzelak (OpenGLOBE.pl) (grzegorz-og.pl) wrote :
Revision history for this message
Grzegorz Grzelak (OpenGLOBE.pl) (grzegorz-og.pl) wrote :

I am sorry, it concerns cash registers functionality only. The problem is that when you leave "/" in field name you should get statement name from journal. It works in Bank statement when "confirm" button finishes statement and creates account entries. But in Cash Register you have to click "Open CashBox" first, and this action sets the cash registers name (from other sequence settings) and change the name to readonly. So you are not able to leave name "/" to get entries numbers from Journal sequence. Anyway wrong behaviour.

Revision history for this message
Grzegorz Grzelak (OpenGLOBE.pl) (grzegorz-og.pl) wrote :

I have to elaborate more on this.
Now I see that when you leave "/" as name for bank statement the bank statement takes number of account move. But then when bank statement positions are posted they are numbered very strange (to me) way. They get concatenation of account move number and number of bank statement position. In Poland Journal entries have to have subsequent numbers (with or without prefixes and suffixes). It worked this way in version 5. For me it is regression from version 5.0 I will not able to introduce this functionality to any company.

During discussion in october last year you told that invoices will get number from account move. It was quite ok to me as one invoice has one account move. Some my accountant will be confused but it was clear to explain.

I think sequence for journal means subsequent numbers with no gaps for whole fiscal year. It seems fundamental. And in case of bank statement or cash box you shouldn't mix bank statement or cash register names with account moves numbers.

So I can agree we can have document numbers taken from account move number but never other way. I think account moves created from bank statement and from cash register should have sequences as in version 5.0.

I don't know what it can mean for bank statement or cash register. Maybe

Amit Parik (amit-parik)
Changed in openobject-addons:
assignee: nobody → OpenERP R&D Addons Team 3 (openerp-dev-addons3)
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Mustufa Rangwala (Open ERP) (mra-tinyerp) wrote :

I agree with you for the bank statement is takes sequence from journal and for the cash register case it directly takes sequence from other sequence defined for cash.statements not from journal on cash register (comment #2).

For comment #3 i am not getting you can you please explain the problem in detail ?

thanks,
mra

Changed in openobject-addons:
status: Confirmed → In Progress
Revision history for this message
Ashvin Rathod (OpenERP) (ara-tinyerp) wrote :

Hello Grzegorz Grzelak,

Its fix in lp:~openerp-dev/openobject-addons/trunk-bug-726090-ara branch. It will be merge soon with trunk addons.

Revision ID: <email address hidden>
Revision No: 4548

Thanks,
ara

Changed in openobject-addons:
status: In Progress → Fix Committed
Changed in openobject-addons:
milestone: none → 6.1
qdp (OpenERP) (qdp)
Changed in openobject-addons:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.