Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0002315Openbravo ERP01. General setuppublic2007-11-27 11:052008-06-12 09:43
user71 
cromero 
normalminoralways
closedno change required 
5
 
2.35 
Core
No
0002315: Initial Client Setup
Hi Openbravo Team,


I am Gaylord L. Navarrete, a software engineer who is under research and investigation of OpenbravoERP and its functionality. I am presently connected in a software development company here in the Philippines.

For 3 months now, I am studying Openbravo from 2.32 & 2.33 versions. I found out that there's a lot of bugs and problems related to the functionalities. I've encountered the same problems as others did in there research. Among I've encountered were referenced to you released list of bugs ( 196 bugs ).

From your list of bugs released to open the door for new version OpenbravoERP2.35, you said that it is intended for production usage.

I am looking forward to upgrade my environment from OpenbravoERP2.33 to 2.35.
But my problem on your latest version is :

My environment:

1. OpenbravoERP2.35
2. PostgreSQL Database Server 8.2.0
3. JDK 5 ( Java-1.5.0 )
4. Apache-Tomcat-5.5.25
5. Windows XP
6. Apache-Ant-1.7

When I tried to upgrade OpenbravoERP2.33 - 2.35, I found out that when :

1. Creating an Entity ( Initial Client Setup ) ?????????????????
    - Accounting File upload is obligatory or a required field before you can
      create a client or setup you client.

2. Accounting File Upload ?????????????????
    - Accounting File upload in client setup is not stated on what format were
      suppose to follow.

3. I been using since then our customized ( Company's Chart of Accounts ).
    And I was able to perform the following modules in OpenbravoERP2.33

     a. Procurement Management:
          - Purchased Order
          - Purchased Invoices
          - Purchased Reports

          - Some transactions & reports did not comply because of bugs.

     b. Sales Management:
          - Sales Order
          - Sales Invoices
          - Tax Reports

          - Some transactions & reports did not comply because of bugs.

     c. Financial Management:
          - Receivables & Payables
                - Some transactions & reports did not comply because of bugs.

4. As far as I understand and from previous experienced in ERP modules,
    Receivables & Payables should be separated. It should not be grouped
    into one module management generally.
No tags attached.
Issue History

Notes
(0005904)
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=1839324 [^]
(0002722)
cromero   
2007-11-29 16:13   
(edited on: 2008-06-12 09:23)
Logged In: YES
user_id=1500614
Originator: NO

We would appreciate if you could create a different bug for any of them that you find and include a description of the bug and how to reproduce it in order to being able to solve them.

Thank you for four feedback.

Carlos Romero
Openbravo Team