openerp-india team mailing list archive

["Nhomar Hernandez \(Vauxoo\)" <nhomar@xxxxxxxxx>]

Public bug reported:

Hello.

Try to post a journal entry in a closed period, you will reveive a message:
..... ---- ..... You can not add/modify entries in a closed journal. ..... - ......

Wao, is incredible that a verification than obvious than this:

file: account.py

1211     def _update_journal_check(self, cr, uid, journal_id, period_id, context=None):
1212         journal_obj = self.pool.get('account.journal')
1213         period_obj = self.pool.get('account.period')
1214         jour_period_obj = self.pool.get('account.journal.period')
1215         cr.execute('SELECT state FROM account_journal_period WHERE journal_id = %s AND period_id = %s', (journal_id, period_id))
1216         result = cr.fetchall()
1217         for (state,) in result:
1218             if state == 'done':
1219                 raise osv.except_osv(_('Error !'), _('You can not add/modify entries in a closed journal.'))


Dudes, is a "Closed PERIOD"

It took to me see it something like 20 minutes, with an powerfull rgrep, but: How dou you explain that this is a little stuff to a end user?
How much time will take to an end user see than somebody close PERIOD and will expend hours in look in Journal...

Be carefull please!

Regards.

** Affects: openobject-addons
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Addons.
https://bugs.launchpad.net/bugs/1056479

Title:
  [6.1] Wrong message of verification of period

Status in OpenERP Addons (modules):
  New

Bug description:
  Hello.

  Try to post a journal entry in a closed period, you will reveive a message:
  ..... ---- ..... You can not add/modify entries in a closed journal. ..... - ......

  Wao, is incredible that a verification than obvious than this:

  file: account.py

  1211     def _update_journal_check(self, cr, uid, journal_id, period_id, context=None):
  1212         journal_obj = self.pool.get('account.journal')
  1213         period_obj = self.pool.get('account.period')
  1214         jour_period_obj = self.pool.get('account.journal.period')
  1215         cr.execute('SELECT state FROM account_journal_period WHERE journal_id = %s AND period_id = %s', (journal_id, period_id))
  1216         result = cr.fetchall()
  1217         for (state,) in result:
  1218             if state == 'done':
  1219                 raise osv.except_osv(_('Error !'), _('You can not add/modify entries in a closed journal.'))

  
  Dudes, is a "Closed PERIOD"

  It took to me see it something like 20 minutes, with an powerfull rgrep, but: How dou you explain that this is a little stuff to a end user?
  How much time will take to an end user see than somebody close PERIOD and will expend hours in look in Journal...

  Be carefull please!

  Regards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/1056479/+subscriptions