Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
| ID | ||||||||||||
| 0031681 | ||||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| feature request | [Openbravo ERP] 06. Material requirement planning (MRP) | minor | always | 2015-12-10 06:20 | 2015-12-14 17:01 | |||||||
| Reporter | yogaskarnik | View Status | public | |||||||||
| Assigned To | Triage Omni OMS | |||||||||||
| Priority | high | Resolution | open | Fixed in Version | ||||||||
| Status | new | Fix in branch | Fixed in SCM revision | |||||||||
| Projection | none | ETA | none | Target Version | ||||||||
| OS | Any | Database | Any | Java version | ||||||||
| OS Version | Database version | Ant version | ||||||||||
| Product Version | 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 | 0031681: User/ Contact field blank when Purchase Order created from Purchasing Plan | |||||||||||
| Description | User/ Contact field blank when Purchase Order created from Purchasing Plan | |||||||||||
| Steps To Reproduce | 1. Login to ERP 2. Go to Purchasing Plan, Create new record with Business Partner=Moon Light Restaurants, Co. 3. Click on Process Purchase Plan 4. Click on Create Purchase Order 5. Go to Purchase Order and observe that the User/Contact field is empty. (video attached) | |||||||||||
| Tags | No tags attached. | |||||||||||
| Attached Files |  purchasing_plan.mp4 [^] (1,748,305 bytes) 2015-12-10 06:20 | |||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
|
(0082732) vmromanos (manager) 2015-12-14 17:01 |
Changed to Feature request minor. The User/Contact field at Purchase Order is hidden by default, which means the field is not used by a standard installation. Besides, the business partner might have more than one contact defined, so the automatic process wouldn't really know which contact to take. That's probably the reason why the process won't populate this field. We should define the rule to know which contact to get for all defined at the Business Partner (for example with a flag or other complex rule). |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2015-12-10 06:20 | yogaskarnik | New Issue | |
| 2015-12-10 06:20 | yogaskarnik | Assigned To | => Triage Finance |
| 2015-12-10 06:20 | yogaskarnik | File Added: purchasing_plan.mp4 | |
| 2015-12-10 06:20 | yogaskarnik | Modules | => Core |
| 2015-12-10 06:20 | yogaskarnik | Resolution time | => 1450047600 |
| 2015-12-10 06:20 | yogaskarnik | Triggers an Emergency Pack | => No |
| 2015-12-14 12:47 | VictorVillar | Priority | normal => high |
| 2015-12-14 12:47 | VictorVillar | Severity | minor => major |
| 2015-12-14 17:01 | vmromanos | Resolution time | 1450047600 => |
| 2015-12-14 17:01 | vmromanos | Note Added: 0082732 | |
| 2015-12-14 17:01 | vmromanos | Severity | major => minor |
| 2015-12-14 17:01 | vmromanos | Type | defect => feature request |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |