Openbravo Forum End of Life Notice

Dear Openbravo Forum User,

Because of continued very low usage we decided to stop the forums on 31st of August 2017

In case of questions: webmaster "at"

Where to do mapping?


sathiyan sivaprakasam

Posts: 14

Joined: Wed Mar 18, 2009 7:26 pm

Post Thu Nov 05, 2009 11:00 am

Where to do mapping?

Requirement from document for aggregation of ledger entries:

In the process of booking from the sub-ledger (like invoices) to the general ledger, all datasets of one business process which share the same data except the amount, could be summerized (=> the amount is summerized). In this case it must be possible to report the single bookings which belong to one GL booking entry.

 from the example:


The products involved:

  • product1 references account 6130

  • product2 references account 6140

  • product3 references account 6130

The accounts involved:

  • 6130, 6140 - accounts for expenses

My question:

1) How are we distinguish product1 and product3 should go to 6130. But how product2 should go to 6140. Where is this configuration should do?

2) 6130 and 6140 are both accounts for expenses. Why we should have two account for same account for expenses?


Richard Morley

Posts: 52

Joined: Tue Mar 17, 2009 8:48 am

Post Thu Nov 05, 2009 12:11 pm

RE:Where to do mapping?

The mapping is already defined at the product level and you don't need to address that. 

All you need to address is the situation where the existing mapping results in the system presents two lines where the transaction string only differs by the transaction value, then the transactions strings should be aggregatted on posting to the  GL.

Why a user may configure the system to use two different expense accounts is a matter of accounting need.  For example, perhaps the invoice is for Rent and two lines relate to costs associated with an office in Pampona and one line relates to an office in Barcelona.



Return to Discussion

Who is online

Users browsing this forum: No registered users and 2 guests

Website Terms

Designed by ST Software for PTF.