Projects:Simple GL Journal

Introduction

In Openbravo there is a window (GL Journal) that allows to manually entry journals in the system. This window has three levels, that it, three tabs (Batch, Header and lines) and in most of the cases this is a pain for the end users since it is enough with just two levels (Header and lines). Another issue that this window has is that you can only selects accounting schemas so when posting the gl journal you only have one entry in the fact_Acct table. Thanks to this project you will be able to select gl items” so when posting the record it will be done in different accounting schemas...as many as the gl item has it defined

Scope ERP

• This is collaborative development to be done in core
• New window named “Simple GL Journal”
• Two tabs, header and lines. Same tables as Header and lines of current GL Journal window
• Add in Header one field in form view:
  • Multi-general ledger: A flag
    • If it is not marked shows General ledger field field as of now
    • If it is marked the system will not show the General ledger field and we won’t take it into account for next operations
    • Show it in grid view as well
• Add in Lines one field in form view:
  • G/L Item: Combo where shows all G/L Items. Will have a display logic and will be shown just when in the header “Multi-general ledger” is flagged
  • The elements showed in this combo will depend on the org defined in the header, that is, on the org tree. Similar as it happens for sales invoice when it is a financial sales invoice:
    • Create a header (sales invoice) and save
    • Move to lines and in the section “More information” mark the check “Financial invoice line”. It will show the combo box “Account” which is really a gl item combo box. Use the same logic to show the elements with the exception that need to be marked the gl items as “Enable in financial invoices”
  • Show it in grid view as well
  • If “Multi-accounting schema” is not flagged then we will show Account field
• When Posting the Header:
  • We must ensure that all lines are created either with account combinations (Account) or gl item. Cannot be mixed lines
  • If there is any error during the process we will do rollback and no journal entries will be created
• Modify the way this table is posted since now we will introduce g/l items
  • Now you can only select accounts that belong to just one accounting schema (defined in the header) so when posting the document there will just one journal entry. This behaviour will not change when the user selects an account. Posting process exactly as it is now
  • But after this development and if the user selects G/L Item since the G/L item can have configured different valid combinations when posting the document it will have as many entries as in different accounts is defined the g/l item and the organization defined in the header.
  • So if the organization is defined for Schema 1, 2 but the gl item has valid combinations in schema 1,2 ,3 the journal entries will be just for schema 1, 2
  • If the organization is defined or can be posted in schemas 1,2 but the gl item is only defined in 1, then it will raise an error and document cannot be posted
  • As explained in above lines, the way we post the document should be similar as Sales Invoice documents

Benefits

• Simpler window since it is not necessary to enter a batch. So you skip one level of data entry
• Simpler to search journal entries. Since you don't have the batch level you can directly search for specific journal entries
• In this window you will also be able to see journal entries that have been done using the other window (Batch), so you can take advantage of searching journal entries as well