Openbravo Issue Tracking System - Openbravo ERP | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0005731 | Openbravo ERP | 07. Sales management | public | 2008-10-29 15:27 | 2011-02-04 09:11 |
Reporter | RenateNieuwkoop | ||||
Assigned To | rmorley | ||||
Priority | normal | Severity | major | Reproducibility | N/A |
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 | 0005731: RFE: ATP report | ||||
Description | Right now to determine whether a Sales Order can be shipped, there is only the stock report. When you do have stock there is no indication whether there is already sales order for which the stock is required. What is missing is a Available to Promise report (ATP). It has the following information (example): Product: Boots on hand: 49 Date Qty ATP 29/10/2008 Sales Order 10 39 1/11/2008 Purchase Order 3 42 3/11/2008 Sales Order 2 40 5/11/2008 Sales Forecast 5 35 10/11/2008 Purchase Order 10 45 So for example if you have a new Sales Order today for quantity 45, you can see that you ship all on 10/11/2008 (or 39 today). Even though you have 49 in stock, you can not ship these today because 10 of those are for Sales Orders. What I'm used to is to see the above screen (inquiry ATP) and then have another screen (inquiry plan) where you would see the actual Sales Order and Purchase Order number. Above example has Sales Order 10x on 29/10/2008, but then in the plan screen you would be able to see what the Sales Orders are and what the quantities per Sales Order would be. You could include that info in the above overview, but it would mean that the above screen is less easy to read. | ||||
Steps To Reproduce | |||||
Proposed Solution | |||||
Additional Information | |||||
Tags | ReleaseCandidate, Usability | ||||
Relationships | |||||
Attached Files | |||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2008-10-29 15:27 | RenateNieuwkoop | New Issue | |||
2008-10-29 15:27 | RenateNieuwkoop | Assigned To | => cromero | ||
2008-10-29 15:27 | RenateNieuwkoop | sf_bug_id | 0 => 2207447 | ||
2008-10-29 15:30 | RenateNieuwkoop | Note Added: 0009828 | |||
2008-11-10 13:09 | cromero | Assigned To | cromero => pjuvara | ||
2008-11-17 08:17 | pjuvara | Tag Attached: ReleaseCandidate | |||
2008-11-17 08:18 | pjuvara | Status | new => acknowledged | ||
2008-12-16 11:12 | rgoris | Tag Attached: Usability | |||
2009-10-07 11:08 | johnfandl | Note Added: 0020822 | |||
2009-10-07 11:25 | johnfandl | Note Added: 0020826 | |||
2011-02-04 09:11 | jpabloae | Assigned To | pjuvara => rmorley |
Notes | |||||
|
|||||
|
|
||||
|
|||||
|
|
||||
|
|||||
|
|