Openbravo Issue Tracking System - Openbravo ERP | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0004732 | Openbravo ERP | 03. Procurement management | public | 2008-08-27 18:18 | 2011-02-04 09:16 |
| Reporter | RenateNieuwkoop | ||||
| Assigned To | rmorley | ||||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | acknowledged | Resolution | open | ||
| Platform | OS | 5 | OS Version | ||
| Product Version | 2.40beta | ||||
| Target Version | Fixed in Version | ||||
| Merge Request Status | |||||
| Review Assigned To | |||||
| OBNetwork customer | |||||
| Web browser | |||||
| Modules | Core | ||||
| Support ticket | |||||
| Regression level | |||||
| Regression date | |||||
| Regression introduced in release | |||||
| Regression introduced by commit | |||||
| Triggers an Emergency Pack | No | ||||
| Summary | 0004732: Manage Requisitions doesn't allow update of default field that will be generated on the Purchase Order | ||||
| Description | Procurement Management || Transactions || Manage Requisitions Procurement Management || Transactions || Requisition To Order When the Purchaser is converting the Requisition in either the Manage Requisitions or the Requisition to Order screen, there is no possibility to update any default fields that will be generated on the Purchase Order, such as Payment Terms, Form of Payment, Warehouse. | ||||
| Steps To Reproduce | |||||
| Proposed Solution | There are two solutions: - The Purchase Order gets created in Draft status instead of Completed. The Purchaser can then check the data and complete - In the Manage Requisitions and the Requisition to Order forms, when the Purchaser creates a Purchase Order, before actually creating the Purchase Order, a screen or pop up appears with the values that were not on the requisition and that will be populated on the Purchase Order. The fields would be updateable, the Purchaser would click ok and the PO would be created in completed status Option 2 is obviously more work, but definitely a nicer one. It avoids human error of forgetting to change the PO from 'draft' to 'completed' | ||||
| Additional Information | |||||
| Tags | ReleaseCandidate | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2008-08-27 18:18 | RenateNieuwkoop | New Issue | |||
| 2008-08-27 18:18 | RenateNieuwkoop | Assigned To | => cromero | ||
| 2008-08-27 18:18 | RenateNieuwkoop | sf_bug_id | 0 => 2078643 | ||
| 2008-11-10 13:10 | cromero | Assigned To | cromero => pjuvara | ||
| 2008-11-16 18:56 | pjuvara | Tag Attached: ReleaseCandidate | |||
| 2008-11-16 18:56 | pjuvara | Status | new => acknowledged | ||
| 2011-02-04 09:16 | jpabloae | Assigned To | pjuvara => rmorley | ||
| There are no notes attached to this issue. |