@boxygen

Hello, I am overloaded with other work this week and next week. If you have a suggestion for changing the sql, then I would be extremely glad smile

/Joe

777

(4 replies, posted in Announcements)

Announcement

This is a 2.4.4 release.

This version fixes a couple of serious bugs as well as some minor bugs.

Please report any bugs/problems found via our Mantis Bugtracker at http://mantis.frontaccounting.com.

Download instructions

In Sourceforge FrontAccounting (https:/sourceforge.net/projects/frontaccounting), select
Files -> FrontAccounting 2.4 ->2.4.4.

For Windows users select the zip file. For all other users select the tar.gz file.

Common

  • Misleading on system diagnostics (MariaDB), fixed.

  • Adapting to google's error when getting exchange rates. Fixed.

  • Backups/Restore: fixed compressed backup view, fixed obsolete ajax indicator during download.

  • Google and Bloomberg Exchange Rate fix.

  • System Diagnostics: fixed set of tested themes directories.

  • Third party extensions installation fixed.

  • Installed Third Party extension version display.

  • Added VARLIB_PATH and VARLOG_PATH defines to simplify packaging.

  • Password field in installer changed to hide text.

  • Company Logo On Reports. Better Logo align.

  • Added deferred income account and prepayment terms in init sql files.

  • Void a Transaction: keeping date unchanged after transaction voiding to allow continuation on date.

  • Reference edit boxes has been extended to show 16 chars instead of 10.

  • New installer translations (Hindi, Tamil, Vietnamese), updated gettext template.

Sales

  • Fixed rounding differences in sales delivery and invoice.

  • Sales Area list, added 'No Area Filter'.

  • Fixed bank account auto-selection on Customer Payments page.

  • Fixed printing sequences of Sales Invoices.

  • Fixed a Shipping bug in Sales Order Report.

  • Fixed redundant $sign in reports Sales Order, Sales Quotation.

  • Added a Total Amount for Sales Orders Report and a Grand Total.

  • Sales Order Entry: initial item selector position points to last ordered item
    (seems to be more useflist than always selecting first item in selector).

  • Added POS name in cash payment memo.

  • Opening Balance bug in rep101.php (Customers Balance).

Purchasing

  • A white screen on Supplier Invoices and Supplier Credit Notes when no supplier defined. Fixed.

  • Fixed redundant $sign in report Purchase Order.

  • Bank Payment: for selected supplier payment set supplier account dimensions.

Items and Inventory

  • New company setting 'Barcodes On Stock' implemented. Rep303 shows barcodes if set.

  • Inventory Valuation Report showing 0 (zero) on Unit Cost and decimal precision fix.

  • New Report: Inventory purchasing transaction based report.

  • Fixed a minor weird bug in QOH in inventory Planning Report.

  • Wrong error message in Save Items.

Manufacturing

  • Stock Status display, Manufacturing Reports: fixed products on WO count.

  • Work Order Entry, Work Order Additional Costs: fixed input data checks.

  • Produce Finished Items: fixed broken document reference (changed input order).

Fixed Assets

  • Better check for fixed assets.

Bank and General Ledger

  • Sort Chart of Accounts by name. Fixed.

  • Account Class/Group drill down added.

  • Subledger list shows inactive records in Journal Entry. Fixed.

  • Fixed get_shipping_tax_as_array() definition (default null as argument).

  • Journal Edition: allow edit reconciliation status for bank related journals.

  • GL Inquiry: search by memo, added journal edition link.

  • Reconcile Bank Account: added memo display, added Reconcile All button.

  • Changed GL Inquiry to also include the Reference Number.

I have never heard of any problems here before. Please be a little more specific. If this is an error the test is very hard to setup, so please be sure that you have observed a problem.

Joe

779

(13 replies, posted in Reporting)

Yes this is right.

/Joe

All Reference Edit Boxes has been extended to show 16 chars instead of 10.

Committed to 2.4 SF Git Repo.

/Joe

Yes we will increase the field a bit.

Joe

782

(7 replies, posted in Report Bugs here)

The former commit of this issue has been rolled back due to the unknown consequences needed by the backwards compatibility to the prior php 5.6 versions.

Janusz will give a short explanation to this.

/Joe.

@apmuthu.

Janusz has explained this in a former post to this topic.

/Joe

784

(7 replies, posted in Report Bugs here)

This has been fixed and committed. Thanks.

/Joe

This has now been fixed and committed to 2.4 Repo.

You can download a copy from here:

Download.

/Joe

Hello,

The Reference number is not the same as the # number. The # number is an internal number. Please use the Reference number as the official number. If you need an ongoing number, use default numbering template (the one with empty prefix) for this purpose.

I will fix the GL Inquiries to also show the Reference number. And I will look if there are more places that this is needed.

/Joe

If you need more than 50 characters, couldn't you just use the Comment field for that?

Joe

An addendum to my former post!

1. Advanced Manufacturing.
If you make several productions or adding extra costs to a Work Order, the work in progress will be visible in the balance sheet.

When the closing productions has been done the work in progress is transferred from works in progress to finished goods.

From the Release status to Production you will see the demand of BoM items in the Item Status together with other demands as sales orders.

Joe

The material is first taken when producing. The simple assembling is taken immediately from raw material. For the advanced manufacturing this happens during producing. As far as I know we don't use the work in progress. It goes from raw material directly to finished goods.

Of course the material is reserved after the release (advanced manuf.).

Joe

@alaa

I cannot reproduce any errors in rep201. Could you be more specific and detailed.

Specific trans types? Or?

Joe

@boxygen
I have just tested to rep201.php and it seems to already work.

I now recall why we got this error in rep101. We had to take care of the new options to add AR/AP lines in Journal Entry.
And we changed the rep101 and rep201 (1, 2) to fix these items, but forgot to fix rep101 regarding the Bank Payment.

I really hope that it is working in rep101 now. Did you try with your data?

/Joe

Committed

@boxygen
I am terrible sorry that I did not accept your change in the SQL sentences in rep110. It turns out that you were right in changing it.
The 3.rd SQL sentence regarding the open balance allocation, it should also be changed accordingly.
The 4.th SQL sentence seems to be ok as is.

I am attaching the corrected file, rep101.php1. Please download and rename it to rep101.php and update your reporting folder.

Please test it and tell me if this is ok. I will then commit it and change rep201.php in the same way.

Joe

You are right Guys. I will look into this.

/Joe

@apmuthu.
As I wrote, if a credit note is made after a payment has been used for allocation the credit note is taken over the allocation, leaving the original Customer Payment open for other allocations.

@boxygen
A Bank Payment will show up in the Customer Balance. No problems with that. If the Bank Payment is not allocated with an existing Customer Payment, you can see that in the rep101.

Joe

Hello again, Guys.

I have now produced the no 1-5 in the above example.
What I needed is to add a
6. Go into Allocations, because the Credit Note has taken over the former allocation and the original Payment is left with no allocation. Use this original Payment for allocating your Bank Payment to the Customer and everything is correct.

Instead of doing the no. 5 Bank Payment to pay the customer as compensation, you can make an agreement with the customer to let the Customer Payment be there waiting for allocation of a future Sales Invoice.

We don't have to change anything in the SQL sentences in rep101. Everything is ok.

@boxygen: You should NOT change anything in the REP101 SQL.

/Joe

Hello Guys.

No we are not combining Customers and Suppliers even if they are the same legal entity.

However I understand @boxygens post. It will arise if the following condition has happened:

1. Sales Invoice is sent for products.
2. Sales Invoice is paid by Customer.
3. Customer is returning Items to us for some reason and the items are ok.
4. Credit Note is sent to Customer.
5. Bank Payment is sent to Customer as Compensation for returned Items.

This no. 5 has to be taken care of in the system.

So we must fix this.
I guess we have a similar condition on the Supplier side.

Joe

Banking and General Ledger,  Closing GL Transactions.

You may need to update the Access Role for doing this.

Joe

You can close a date for further entries.
You are free to define your own periods so to speak. There are no periods in FA but many reports are on a monthly selected base. You can change if desired.

Joe

How you setup your accountancy is all about what you need in accordance with your accountant. Either cash or accrual based.

FA will follow you in these approaches. When using prepayments the accountancy is maybe a little different, but in my opinion there are no further requirements needed in FA to accomplish this.

Joe

Hello,

Oh yes, they are saved. Just press the Get button after you have selected the Fiscal Year and Account / Dimension.

/Joe