Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
ID | ||||||||||||
0011602 | ||||||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
feature request | [Openbravo ERP] 03. Procurement management | major | always | 2009-12-02 12:43 | 2011-02-04 09:11 | |||||||
Reporter | RenateNieuwkoop | View Status | public | |||||||||
Assigned To | rmorley | |||||||||||
Priority | normal | Resolution | open | Fixed in Version | ||||||||
Status | new | Fix in branch | Fixed in SCM revision | |||||||||
Projection | none | ETA | none | Target Version | ||||||||
OS | Any | Database | PostgreSQL | Java version | ||||||||
OS Version | Database version | Ant version | ||||||||||
Product Version | 2.50MP8 | SCM revision | ||||||||||
Review Assigned To | ||||||||||||
Web browser | ||||||||||||
Modules | Core | |||||||||||
Regression level | ||||||||||||
Regression date | ||||||||||||
Regression introduced in release | ||||||||||||
Regression introduced by commit | ||||||||||||
Triggers an Emergency Pack | No | |||||||||||
Summary | 0011602: Purchase Order: Add a 'Need by date' and possibly a 'confirmed date' | |||||||||||
Description | Procurement Management || Transactions || Purchase Order || Header >> Lines In Purchase Orders created by MRP, the Scheduled Delivery Date is in fact the 'Need by Date', however we do not have a field for that. The Scheduled Delivery Date should be based on the leadtime of the Product or the confirmation date from the Vendor. Alternatively we could have the Scheduled Delivery Date reflecting the offset with the leadtime of the product and a 'confirmed date' with the date communicated by the Vendor. So the dates on the Purchase Order would be: Order Date (existing) = the date the order was entered Need By Date (New)= The date we need the product (could be coming from MRP) Scheduled Delivery Date = offset of the purchasing leadtime (but not before the need by date) Confirmed date (new) = Committed date by the Vendor (not before the need by date) If the confirmed date is not added, then the Scheduled Delivery Date should be populated with the offset of the purchasing leadtime and should be overwritten with a committed date by the vendor | |||||||||||
Steps To Reproduce | Add a product with a purchasing leadtime of 14 days (in our case 'hammer') and safety stock of 1000. Min order qty is 500, quantity type mulitple of 500. Enter a Sales Order for 5 weeks from now for qty 350. Enter a Planning method for inclusion of the Purchase Order and Sales Order. Set up a Purchasing Plan for a horizon of 60 days for hammer. Process the Purchase Plan and create the PO. | |||||||||||
Proposed Solution | In the current scenario the Scheduled Delivery Date is sometime a pastdue date. That is not realistic and not a correct use of the Scheduled Delivery Date field. | |||||||||||
Tags | No tags attached. | |||||||||||
Attached Files | 021209DatesPO1.jpg [^] (232,410 bytes) 2009-12-02 12:43
021209DatesPO2.jpg [^] (218,766 bytes) 2009-12-02 12:44 021209LTHammer.jpg [^] (198,705 bytes) 2009-12-02 12:44 | |||||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | |
Issue History | |||
Date Modified | Username | Field | Change |
2009-12-02 12:43 | RenateNieuwkoop | New Issue | |
2009-12-02 12:43 | RenateNieuwkoop | Assigned To | => rafaroda |
2009-12-02 12:43 | RenateNieuwkoop | File Added: 021209DatesPO1.jpg | |
2009-12-02 12:44 | RenateNieuwkoop | File Added: 021209DatesPO2.jpg | |
2009-12-02 12:44 | RenateNieuwkoop | File Added: 021209LTHammer.jpg | |
2009-12-11 15:27 | rafaroda | Assigned To | rafaroda => pjuvara |
2011-02-04 09:11 | jpabloae | Assigned To | pjuvara => rmorley |
Copyright © 2000 - 2009 MantisBT Group |