Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0002437
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] 07. Sales managementminoralways2007-12-29 13:412008-06-20 12:16
Reporteruser71View Statuspublic 
Assigned Toalostale 
PrioritynormalResolutionfixedFixed in Version2.40alpha-r3
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Merge Request Status
Review Assigned To
OBNetwork customerNo
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0002437: Parsing failed on orderby clause

DescriptionWhen I create a new shipment for a completed sales order by copying the lines from the sales order, then save in the header and select lines, then I get the following error:

12:37:15 [http-8180-Processor24] ERROR org.openbravo.erpCommon.utility.TableSQLData - Parsing failed on orderby clause: M_InOutLine.QuantityOrder ASC, M_InOutLine.Line ASC - pos: 29

OB2.35
Postgresql 8.2
Ubuntu 7.10
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0002897)
rafaroda (viewer)
2008-01-09 17:24
edited on: 2008-06-12 09:23

Logged In: YES
user_id=1892190
Originator: NO

Hi,

Can you please specify the exact steps that you follow (including the type of Sale Order)?

Thank you,

Rafa Roda Palacios
Openbravo Team
(0002898)
user71
2008-01-09 21:52
edited on: 2008-06-12 09:23

Logged In: YES
user_id=1770033
Originator: YES

Steps to reproduce the error (Open Bazaar client)
1 create standard sales order with one line and complete it.
2 create shipment heeader, save and then create lines from sales order.
3 go to sales order and save

You now have the error in the log file. No error on the screen.
(0002899)
rafaroda (viewer)
2008-05-29 17:37
edited on: 2008-06-12 09:23

Logged In: YES
user_id=1892190
Originator: NO

Steps to reproduce:

1. In Goods Shipment Lines:
1.1. Go to 'Sales Management || Transactions || Goods Shipment' and select one record with lines.
1.2. Go to 'Lines' tab.
1.3. Enter into Edit mode.
1.4. Go to Relation mode.
1.5. log4j message: ERROR org.openbravo.erpCommon.utility.TableSQLData - Parsing failed on orderby clause: M_InOutLine.QuantityOrder ASC, M_InOutLine.Line ASC - pos: 29

2. In Sales Invoice lines
2.1. Go to 'Sales Management || Transactions || Sales Invoice' and select one record with lines.
2.2. Go to 'Lines' tab.
2.3. Enter into Edit mode.
2.4. Go to Relation mode.
2.5. log4j message: ERROR org.openbravo.erpCommon.utility.TableSQLData - Parsing failed on orderby clause: C_InvoiceLine.M_Product_Uom_Id ASC, C_InvoiceLine.QuantityOrder ASC, C_InvoiceLine.Line ASC - pos: 34

3. In Service project header
3.1. Go to 'Project & Service Management || Transactions || Service Project' and select one.
3.2. Enter into Edit mode.
3.3. Go to Relation mode.
3.4 log4j message: ERROR org.openbravo.erpCommon.utility.TableSQLData - Parsing failed on orderby clause: C_Project.Created ASC, C_Project.Name ASC - pos: 21
(0002900)
rafaroda (viewer)
2008-05-29 17:38
edited on: 2008-06-12 09:23

Logged In: YES
user_id=1892190
Originator: NO

Impact in the application: Grid in Relation mode is not ordered by any field.
(0002901)
rafaroda (viewer)
2008-05-30 09:29
edited on: 2008-06-12 09:23

Logged In: YES
user_id=1892190
Originator: NO

Steps to reproduce:
4. In Work Effort header
4.1. Go to 'Production Management || Transactions || Work Effort' and select one.
4.2. Enter into Edit mode.
4.3. Go to Relation mode.
4.4. log4j message: ERROR org.openbravo.erpCommon.utility.TableSQLData - Parsing failed on orderby clause: M_Production.Movementdate DESC, M_Production.DocumentNo DESC - pos: 30

(0002902)
rafaroda (viewer)
2008-06-03 10:23
edited on: 2008-06-12 09:23

Logged In: YES
user_id=1892190
Originator: NO

Steps to reproduce:

5. In Project Phase:
5.1. Go to 'Project & Service Management || Transactions || Multiphase Project ' and select one record with phases.
5.2. Go to 'Project Phase' tab.
5.3. Enter into Edit mode.
5.4. Go to Relation mode.
5.5. log4j message: ERROR org.openbravo.erpCommon.utility.TableSQLData - Parsing failed on orderby clause: C_ProjectPhase.SeqNo ASC, C_ProjectPhase.SeqNo ASC - pos: 24

6. In Expense Sheet Lines:
6.1. Go to 'Project & Service Management || Transactions || Expense Sheet' and select one record with lines (or create a new one).
6.2. Go to 'Lines' tab.
6.3. Enter into Edit mode.
6.4. Go to Relation mode.
6.5. log4j message: ERROR org.openbravo.erpCommon.utility.TableSQLData - Parsing failed on orderby clause: S_TimeExpenseLine.Line ASC, S_TimeExpenseLine.Line ASC - pos: 26

7. In Sales Order header
7.1. Go to 'Sales Management || Transactions || Sales Order' and select one.
7.2. Enter into Edit mode.
7.3. Go to Relation mode.
7.4. log4j message: ERROR org.openbravo.erpCommon.utility.TableSQLData - Parsing failed on orderby clause: C_Order.DocumentNo DESC, C_Order.DocumentNo DESC - pos: 23

8. In Sales Order Lines:
8.1. Go to 'Sales Management || Transactions || Sales Order' and select one record with lines.
8.2. Go to 'Lines' tab.
8.3. Enter into Edit mode.
8.4. Go to Relation mode.
8.5. log4j message: ERROR org.openbravo.erpCommon.utility.TableSQLData - Parsing failed on orderby clause: C_OrderLine.Line ASC, C_OrderLine.Line ASC - pos: 20

9. In Business Partner header
9.1. Go to 'Master Data Management || Business Partner' and select one.
9.2. Enter into Edit mode.
9.3. Go to Relation mode.
9.4. log4j message: ERROR org.openbravo.erpCommon.utility.TableSQLData - Parsing failed on orderby clause: C_BPartner.Value ASC, C_BPartner.Value ASC - pos: 20
(0002903)
alostale (viewer)
2008-06-04 13:14
edited on: 2008-06-12 09:23

Logged In: YES
user_id=1500722
Originator: NO

r4795.
(0006026)
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=1860374 [^]

- Issue History
Date Modified Username Field Change
2008-06-20 12:16 plujan Status resolved => closed


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker