Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
| ID | ||||||||||||
| 0024198 | ||||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| design defect | [Openbravo ERP] A. Platform | minor | always | 2013-06-26 16:51 | 2013-07-18 16:42 | |||||||
| Reporter | emartinez | View Status | public | |||||||||
| Assigned To | dmiguelez | |||||||||||
| Priority | normal | 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 | 3.0MP24 | 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 | 0024198: Documentno in Expense Sheet not working well for different Organization sequences | |||||||||||
| Description | When we have two different organizations (and thus different sequences for expense sheet), the documentno does not take the correct sequence according to the organization that has created it. | |||||||||||
| Steps To Reproduce | 1) Go to Document Sequence Window, 2) Search the following standard document sequence: DocumentNo_S_TimeExpense 3) You will see it belongs to organization *, change it to organization A 4) Create the same sequence (with same name), but assign it to organization B 5) Now go to expense sheet window, and try to create one register belonging to organization A, see the sequence automatically chosen. Is it the correct one? 7) Finally, create a new register for organization B, is the sequence correct? | |||||||||||
| Tags | No tags attached. | |||||||||||
| Attached Files |  doc.png [^] (51,082 bytes) 2013-07-09 15:02
| |||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
||||||||
|
||||||||
 Relationships |
|
Notes |
|
|
(0060101) dbaz (developer) 2013-07-18 16:42 |
The "Document Sequence" that actually exists, has a 'Organization' field, but it is not used in the logic but it is there like it is in any other application table. Said that, the issue has changed to 'design defect'. The effort is medium/high and the regression risk is high. An explanation about actually how it is working: When 'NEW' is pressend in a window, to draw the needed document sequence ("Document No") the following code applies: https://code.openbravo.com/erp/devel/pi/file/93daf5858a3b/modules/org.openbravo.client.kernel/src/org/openbravo/client/kernel/reference/UIDefinition.java#l171 [^] There is a call to "getDocumentNo" which at the end in finally calls the data base function AD_Sequence_DocType. The 'organization' is not a parameter. When the field is saved, there is handler in charge of update the documentNo (if it is needed) and save the new sequence value: https://code.openbravo.com/erp/devel/pi/file/93daf5858a3b/modules/org.openbravo.client.application/src/org/openbravo/client/application/event/SetDocumentNoHandler.java#l104 [^] Otherwise (besides the issue, but to take into account during the development) there is the 'Document Type', which also uses the 'Document Sequence', but although it shares some of its functions (like the already mentioned "getDocumentNo"), if there would be the need of a 'Document Type' -> 'Document Sequence' dependency, there is a (manual) callout for each situations. Callout example in charge of update the "Sales Order" > "Document No" based in "Transaction Document" https://code.openbravo.com/erp/devel/pi/file/93daf5858a3b/src/org/openbravo/erpCommon/ad_callouts/SL_Order_DocType.java#l125 [^] |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2013-06-26 16:51 | emartinez | New Issue | |
| 2013-06-26 16:51 | emartinez | Assigned To | => dmiguelez |
| 2013-06-26 16:51 | emartinez | Modules | => Core |
| 2013-06-26 16:51 | emartinez | Triggers an Emergency Pack | => No |
| 2013-06-27 10:20 | emartinez | Type | design defect => defect |
| 2013-06-27 10:20 | emartinez | Summary | Different document types and sequences in Expense Sheet => Documentno in Expense Sheet not working well for different Organization sequences |
| 2013-06-27 10:20 | emartinez | Description Updated | View Revisions |
| 2013-06-27 10:24 | psarobe | Assigned To | dmiguelez => AugustoMauch |
| 2013-06-27 10:24 | psarobe | Category | 08. Project and service management => A. Platform |
| 2013-06-27 14:55 | emartinez | Issue Monitored: emartinez | |
| 2013-06-28 14:58 | emartinez | Steps to Reproduce Updated | View Revisions |
| 2013-06-28 14:58 | emartinez | File Added: TimeExpense.png | |
| 2013-07-05 14:16 | AugustoMauch | Assigned To | AugustoMauch => dbaz |
| 2013-07-09 15:02 | emartinez | Steps to Reproduce Updated | View Revisions |
| 2013-07-09 15:02 | emartinez | File Deleted: TimeExpense.png | |
| 2013-07-09 15:02 | emartinez | File Added: doc.png | |
| 2013-07-18 16:42 | dbaz | Note Added: 0060101 | |
| 2013-07-18 16:42 | dbaz | Assigned To | dbaz => dmiguelez |
| 2013-07-18 16:42 | dbaz | Type | defect => design defect |
| 2014-12-18 18:30 | ngarcia | Relationship added | related to 0018693 |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |