Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0019635 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| defect | [Openbravo ERP] 06. Material requirement planning (MRP) | minor | have not tried | 2012-02-02 13:20 | 2012-04-02 06:11 | |||
| Reporter | RenateNieuwkoop | View Status | public | |||||
| Assigned To | umartirena | |||||||
| Priority | normal | Resolution | fixed | Fixed in Version | 3.0MP10 | |||
| Status | closed | Fix in branch | Fixed in SCM revision | ef7286b8b863 | ||||
| Projection | none | ETA | none | Target Version | 3.0MP10 | |||
| OS | Any | Database | Any | Java version | ||||
| OS Version | Database version | Ant version | ||||||
| Product Version | 3.0MP7.1 | 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 | 0019635: MRP: Scheduled delivery date on PO is not in sync with the Planned Order Date in the Purchasing Plan | |||||||
| Description | Please add link to issue 11603 for this. The purchasing plan is reviewing future demand and then suggests a purchase order to be created, offsetting the purchasing lead time. However, instead of the date that the demand is required to be reflected on the scheduled delivery date of the purchase order, the scheduled delivery date is today's date. | |||||||
| Steps To Reproduce | Create a Sales Forecast with a future date. Run the Purchasing Plan for the product (make sure sales forecast is included in planning method). Create a purchase order. The scheduled delivery date is today's date. | |||||||
| Proposed Solution | The scheduled delivery date of the Purchase order should be the Planned Order date of the demand where the order is placed for. See screenshot, the scheduled delivery date should be 13-03-2012 because that is when the demand is due. | |||||||
| Tags | OB3 Documentation | |||||||
| Attached Files |  Issue11603screen1.png [^] (90,801 bytes) 2012-02-02 13:20
| |||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|||||||||||||
|
|||||||||||||
 Relationships |
|
Notes |
|
|
(0044963) dmitry_mezentsev (developer) 2012-02-09 14:55 |
Hello All, We need to browse in details current MRP process before making decisions here. Please Unai verify these things in the code. 1. Planned Order Date in the Purchasing Plan Lines is not the date when we need goods but the date a Purchase Order should be placed for these goods to arrive on time. 2. Date when we need goods is Planned Date of Purchasing Plan Lines. 3. Gorka did brief review of the code and mentioned that currently Planned Order Date is used to populate Order Date field in the Purchase Order Lines and Planned Date is used to populate Schedule Delivery Date at the same level. These fields are hidden now so as for me it makes sense to un-hide them but keeping in More Information section so that Purchase Order Lines layout of those who does not need them is not affected. Then we would need to document these fields after fixing this bug in the new User Manual so it is important to understand the way these fields are used later in the Purchasing flow (might be that they are just informational but if not we would need to explain the way they influence the flow). 4. Purchase Order Header fields. Order Date is filled in with Purchase Plan Document Date. Regarding Schedule Delivery Date in the Header I am not sure, please verify it in the code. |
|
(0044989) umartirena (reporter) 2012-02-10 09:09 |
Hello, I've verified these points: 1. As you've mentioned Dmitry, Planned Order Date in Purchasing Plan Lines is the date a Purchase Order should be done to have the goods when we need. 2. This is what you've said too, date when we need goods is Planned Date of Purchasing Plan Lines. 3. I've verified too that Planned Order Date is used to populate Order Date field in the Purchase Order Lines and Planned Date is used to populate Schedule Delivery Date at the same level. 4. When creating a Purchase Order from the Purchasing Plan, Order Date is filled in with Purchase Plan Document Date, and Scheduled Delivery Date is done in the same way. For me it makes sense to un-hide the fields, I don't know where they can affect in the flow, but usign these fields I think the process would be more efficient, to have the stock in the minimun level as possible. |
|
(0046556) hgbot (developer) 2012-03-20 13:31 |
Repository: erp/devel/pi Changeset: ef7286b8b8631501511d789b178485d02a523650 Author: Unai Martirena <unai.martirena <at> openbravo.com> Date: Tue Mar 13 18:19:02 2012 +0100 URL: http://code.openbravo.com/erp/devel/pi/rev/ef7286b8b8631501511d789b178485d02a523650 [^] Fixes Issue 19635: Sch.del. date PO is not sync with Pl. Order Date in Pur.Plan --- M modules/org.openbravo.v3/src-db/database/configScript.xml M src-db/database/sourcedata/AD_FIELD.xml --- |
|
(0046558) umartirena (reporter) 2012-03-20 13:37 |
After discussing with Dmitry, we took the decision to un-hide upon instance activation Order Date and Scheduled Delivery Date in Purchase Order Lines and put them in the more information section as informative fields. We have not changed Scheduled Delivery Date of the Header because is used in another process later. |
|
(0046916) jonalegriaesarte (reporter) 2012-03-29 17:06 |
Regarding the notes Order Date and Scheduled Delivery Date should appear in Purchase Order Lines. Both fields appear. |
|
(0047172) hudsonbot (developer) 2012-04-02 06:11 |
A changeset related to this issue has been promoted main and to the Central Repository, after passing a series of tests. Promotion changeset: https://code.openbravo.com/erp/devel/main/rev/7814864461ac [^] Maturity status: Test |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2012-02-02 13:20 | RenateNieuwkoop | New Issue | |
| 2012-02-02 13:20 | RenateNieuwkoop | Assigned To | => jonalegriaesarte |
| 2012-02-02 13:20 | RenateNieuwkoop | File Added: Issue11603screen1.png | |
| 2012-02-02 13:20 | RenateNieuwkoop | Modules | => Core |
| 2012-02-02 13:20 | RenateNieuwkoop | Tag Attached: OB3 Documentation | |
| 2012-02-02 18:38 | jonalegriaesarte | Relationship added | depends on 0011603 |
| 2012-02-02 18:39 | jonalegriaesarte | Assigned To | jonalegriaesarte => umartirena |
| 2012-02-09 14:55 | dmitry_mezentsev | Note Added: 0044963 | |
| 2012-02-10 09:09 | umartirena | Note Added: 0044989 | |
| 2012-03-06 13:08 | jonalegriaesarte | Target Version | => 3.0MP10 |
| 2012-03-20 13:31 | hgbot | Checkin | |
| 2012-03-20 13:31 | hgbot | Note Added: 0046556 | |
| 2012-03-20 13:31 | hgbot | Status | new => resolved |
| 2012-03-20 13:31 | hgbot | Resolution | open => fixed |
| 2012-03-20 13:31 | hgbot | Fixed in SCM revision | => http://code.openbravo.com/erp/devel/pi/rev/ef7286b8b8631501511d789b178485d02a523650 [^] |
| 2012-03-20 13:37 | umartirena | Note Added: 0046558 | |
| 2012-03-29 17:06 | jonalegriaesarte | Note Added: 0046916 | |
| 2012-03-29 17:06 | jonalegriaesarte | Status | resolved => closed |
| 2012-03-29 17:06 | jonalegriaesarte | Fixed in Version | => 3.0MP10 |
| 2012-04-02 06:11 | hudsonbot | Checkin | |
| 2012-04-02 06:11 | hudsonbot | Note Added: 0047172 | |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |