Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0002579Openbravo ERP09. Financial managementpublic2008-01-31 18:512008-12-17 11:09
psarobe 
rmorley 
highminoralways
acknowledgedopen 
5
 
pi 
Core
No
0002579: Properly handling the posting of inactive documents
If a document is not active and try to account, no message is shown but it put it as posted

ENVIRONMENT
==========
R 2.35mp1
Oracle/Postgres
FF
Linux

STEPS:
======
1.Login in English
2.Go to Financial management->Setup-> Fiscal calendar->Year->Period
3. Move to period control and uncheck the flag Active for the document AR Invoice
4. Go to Sales management->Transaction->Sales invoice
5. Create a sales invoice but in that period (date) with lines.
5. Complete and posted.

No message is shown and in the button says POST.

Solution:

When a document is not active for that period, you cannot post anything. Is similar as when the period is closed but for this case:
-The message must be "The document for this period is not active and it cannot be posted"
-In the button must put: Not posted
Messages, ModuleCandidate, ReleaseCandidate
Issue History
2008-06-13 18:28cromeroTag Attached: Messages
2008-06-13 18:28cromeroTarget Version => 2.50
2008-06-13 18:28cromeroDescription Updated
2008-06-13 18:29cromeroStatusnew => scheduled
2008-06-21 19:40pjuvaraTypedefect => feature request
2008-06-21 19:40pjuvaraFixed in Version2.40 =>
2008-06-21 19:40pjuvaraTag Attached: ReleaseCandidate
2008-06-23 13:30pjuvaraSummaryNot active documents, no accounting message => Properly handling the posting of inactive documents
2008-06-24 18:54pjuvaraPrioritynormal => high
2008-11-03 13:43pjuvaraTarget Version2.50 => 2.60
2008-11-10 13:09cromeroAssigned Tocromero => pjuvara
2008-11-21 16:45pjuvaraStatusscheduled => acknowledged
2008-11-21 17:05pjuvaraTarget Version2.60 => trunk
2008-11-22 23:26pjuvaraTag Attached: ModuleCandidate
2008-12-17 11:09pjuvaraAssigned Topjuvara => rmorley

Notes
(0006168)
user71   
2005-06-01 00:00   
(edited on: 2008-06-12 09:43)
This bug was originally reported in SourceForge bug tracker and then migrated to Mantis.

You can see the original bug report in:
https://sourceforge.net/support/tracker.php?aid=1883767 [^]