Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0008743Openbravo ERP06. Material requirement planning (MRP)public2009-04-23 13:402009-05-05 00:00
jtarbal 
gorkaion 
normalminoralways
closedfixed 
5
2.50 
2.50MP1 
Core
No
0008743: Document number of Purchase Order does not follow doc. sequence format
The purchase order documents that are created from the Purchasing MRP functionality have the document number value with a different format than the defined in the Document Sequence of the Purchase Order document.

In order to reproduce the error, follow the next steps:
1.- Configure a document sequence format for the Purchase Order document that uses a prefix
2.- Use the Purchasing Plan functionality in order to create a Purchase Order proposal.
3.- With the "Create Purchase Orders" button of the "Purchasing Plan" header window, create the purchase orders
4.- Navigate to one of the purchase orders created and realize how the document number format does not follow the document sequence defined before
250MP1
Issue History
2009-04-23 13:40jtarbalNew Issue
2009-04-23 13:40jtarbalAssigned To => rafaroda
2009-04-28 12:36psarobeTag Attached: 250MP1
2009-04-28 12:36psarobeStatusnew => scheduled
2009-04-28 12:36psarobeAssigned Torafaroda => gorkaion
2009-04-28 12:36psarobefix_in_branch => pi
2009-04-30 17:26hgbotCheckin
2009-04-30 17:26hgbotNote Added: 0015967
2009-04-30 17:26hgbotStatusscheduled => resolved
2009-04-30 17:26hgbotResolutionopen => fixed
2009-04-30 17:26hgbotFixed in SCM revision => http://code.openbravo.com/erp/devel/pi/rev/a3de4e2cef41862d293848573f46aeb21122b207 [^]
2009-05-04 20:04psarobeRegression testing => No
2009-05-04 20:04psarobeStatusresolved => closed
2009-05-05 00:00anonymoussf_bug_id0 => 2786920

Notes
(0015967)
hgbot   
2009-04-30 17:26   
Repository: erp/devel/pi
Changeset: a3de4e2cef41862d293848573f46aeb21122b207
Author: Gorka Ion Damián <gorkaion.damian <at> openbravo.com>
Date: Thu Apr 30 17:25:57 2009 +0200
URL: http://code.openbravo.com/erp/devel/pi/rev/a3de4e2cef41862d293848573f46aeb21122b207 [^]

Fixed bug 8743.The DocumentNo is now properly calculated.

---
M src-db/database/model/functions/MRP_PURCHASEORDER.xml
---