Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
ID | ||||||||
0002095 | ||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
defect | [Openbravo ERP] 06. Material requirement planning (MRP) | minor | always | 2007-10-15 14:10 | 2008-06-12 09:43 | |||
Reporter | gorkaion | View Status | public | |||||
Assigned To | gorkaion | |||||||
Priority | normal | Resolution | fixed | Fixed in Version | 2.35 | |||
Status | closed | 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 | |||||||
Merge Request Status | ||||||||
Review Assigned To | ||||||||
OBNetwork customer | No | |||||||
Web browser | ||||||||
Modules | Core | |||||||
Support ticket | ||||||||
Regression level | ||||||||
Regression date | ||||||||
Regression introduced in release | ||||||||
Regression introduced by commit | ||||||||
Triggers an Emergency Pack | No | |||||||
Summary | 0002095: Improve names in transaction type list | |||||||
Description | Openbravo v2.34 The names of the transactions in "In/Out transaction types for planning" list type reference are confusing. Correct naming should be: Material Forecast -> Requisition Material Need proposal -> Requisition proposal Work Requierement proposal -> Work Requirement proposal | |||||||
Tags | No tags attached. | |||||||
Attached Files | ||||||||
![]() |
|
![]() |
|
(0002385) user71 2007-10-16 13:12 edited on: 2008-06-12 09:22 |
Logged In: YES user_id=1639235 Originator: NO "Material Forecast" means a prediction of what materials will be required at some future time. "Requisition" means a document/order that requires the items to be acquired as in "purchase order". "Requisition" is in common usage in the British and American army, but less common in commerce. Again the key is in the emphasis. A "Requisition" is an "Order!", very emphatic, refused on pain of death, almost. A "purchase order" is a request from one business to another, which may be declined or accepted. If I were to receive a document headed "Requisition", I would not take it kindly as it would be deemed aggressive. You may find that American usage is more used to the term "Requisition", I can only offer my opinion on British/European usage. "Material Need proposal" is a poorer way of saying "Material Forecast" "Work Requirement proposal" might be better as "Work Requirement Recommendation" or even just "Work Requirement" as the recommendation is effectively inferred. I have difficulty in differentiating between the first 2 terms as there seems to be little difference in the meaning, which I am sure is not your intention. Perhaps you could let me know what you would use in Spanish and I will try to work out the English terms. Kind regards, Andrew Ballantine. |
(0002386) gorkaion (viewer) 2007-10-16 18:13 edited on: 2008-06-12 09:22 |
Logged In: YES user_id=1500690 Originator: YES Hi Andrew, Thank you for the feedback. I'm going to open a new thread in the Functionality forum to discuss the terminology of the whole list. http://sourceforge.net/forum/message.php?msg_id=4572002 [^] There more people will see this and could make their suggestions so we can reach to a good set of terms. Sorry for moving you around the trackers. Gorka Ion |
(0002387) gorkaion (viewer) 2007-10-21 17:07 edited on: 2008-06-12 09:22 |
Logged In: YES user_id=1500690 Originator: YES Changed the names as suggested in the forum. |
(0002388) rafaroda (viewer) 2007-10-26 09:00 edited on: 2008-06-12 09:22 |
Logged In: YES user_id=1892190 Originator: NO Verification assigned to rafaroda. |
(0005684) user71 2005-06-01 00:00 edited on: 2008-06-12 09:43 |
This bug was originally reported in SourceForge bug tracker and then migrated to Mantis. You can see the original bug report in: https://sourceforge.net/support/tracker.php?aid=1813780 [^] |
Copyright © 2000 - 2009 MantisBT Group |