Openbravo Issue Tracking System - Openbravo ERP | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0009031 | Openbravo ERP | 02. Master data management | public | 2009-05-14 11:38 | 2011-02-04 09:14 |
| Reporter | MbX7174 | ||||
| Assigned To | rmorley | ||||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | OS | 5 | OS Version | ||
| Product Version | |||||
| 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 | 0009031: Organization-specific BP and Product data | ||||
| Description | Generally OB admin user would like to keep things like BPs and Products common to the whole client. On the other hand the application forces us to do the opposite for a couple of reasons (illustrated with a subset): - The customer-tab of the BP is not a separate record (and table), hence we cannot discriminate the credit limit of the BP, depending on the organization were currently operating under. - The BP tax category is related directly to the Business Partner, this means that multi-national clients cannot select a set of tax rates, applicable to the currently relevant organization (e.g. shipping from Belgium in org1 (source) to France (destination) is a completely different tax-set then from France in org2 to France). - A tax category is linked directly to a product, which means that we basically have the same issue as the previous point: when we want to apply different tax rates, depending on the location of the organization we're currently working for we have a problem (e.g. Bottled water in Belgium is taxed with a rate of 12% VAT, while in France it is 6%; clients, both serving Belgium and France with different organizations to do so have a problem). | ||||
| Steps To Reproduce | |||||
| Proposed Solution | Certain properties of BP and Product must be isolated in a separate child table of the main table. The child table is then used to allow polic variations, depending on the applicable organization. | ||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2009-05-14 11:38 | MbX7174 | New Issue | |||
| 2009-05-14 11:38 | MbX7174 | Assigned To | => rafaroda | ||
| 2009-05-14 13:40 | rafaroda | Assigned To | rafaroda => pjuvara | ||
| 2011-02-04 09:14 | jpabloae | Assigned To | pjuvara => rmorley | ||
| There are no notes attached to this issue. |