Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
| ID | ||||||||||||
| 0011375 | ||||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| design defect | [Openbravo ERP] 05. Production management | major | always | 2009-11-16 14:29 | 2012-05-10 12:12 | |||||||
| Reporter | mensenjh | View Status | public | |||||||||
| Assigned To | mirurita | |||||||||||
| Priority | normal | Resolution | open | Fixed in Version | ||||||||
| Status | new | Fix in branch | Fixed in SCM revision | |||||||||
| Projection | none | ETA | none | Target Version | ||||||||
| OS | Linux 32 bit | Database | PostgreSQL | Java version | 1.6.0_16 | |||||||
| OS Version | Community Appliance | Database version | 8.3.8 | Ant version | 1.7.1 | |||||||
| 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 | 0011375: Internal consumption not integrated in total ERP functionality | |||||||||||
| Description | When posting internal consumption the qty for the product entered in the line is consumed. Even when the material is a valuated stock, no posting is made to an account. The transaction itself is not presented in any report: e.g. Product Movement Report It should not be possible to take valuated stock without financial consequences! This is related to discussion: http://forge.openbravo.com/plugins/espforum/view.php?group_id=100&forumid=615117&topicid=7005586 [^] | |||||||||||
| Steps To Reproduce | 1. Put a valuated material on stock. 2. Enter an internal consumption for the material and process it. 3. The material is gone from stock, but without a financial posting or as a recorded material movement in Product Movement Report | |||||||||||
| Proposed Solution | Possible solutions: + Take the transaction from standard Openbravo ERP. + Issue a warning message stating the limited consequences of the transaction. + Add financial posting functionality to the transaction (preferred solution) | |||||||||||
| Tags | OB3-Reviewed | |||||||||||
| Attached Files | ||||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
| There are no notes attached to this issue. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2009-11-16 14:29 | mensenjh | New Issue | |
| 2009-11-16 14:29 | mensenjh | Assigned To | => rafaroda |
| 2009-11-16 14:29 | mensenjh | Issue Monitored: mensenjh | |
| 2010-02-11 18:16 | rafaroda | Assigned To | rafaroda => adrianromero |
| 2011-06-03 11:00 | dalsasua | Assigned To | adrianromero => dalsasua |
| 2011-07-20 18:11 | dalsasua | Assigned To | dalsasua => jonalegriaesarte |
| 2011-11-25 17:43 | jonalegriaesarte | Tag Attached: OB3-Reviewed | |
| 2012-04-03 12:20 | jonalegriaesarte | Assigned To | jonalegriaesarte => vmromanos |
| 2012-04-10 17:20 | vmromanos | Type | defect => design defect |
| 2012-05-10 12:12 | gorka_gil | Assigned To | vmromanos => mirurita |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |