51 Reply by joe

(6 replies, posted in Announcements)

Your suggestion has now been implemented and committed to stable repo.

We use the bank_name field for the 'XUMM XRP' name. It is importand that this field contains XUMM as the first name and XRP (currency) name as the last 3 characters.
The name in the Payment Link has changed to XUMM XRP.
This is now prepared for future extension, f.i. XUMM USD.
Internally we do not use the Bank Account currency name. The XRP can cause abnormal exchange traffic.
Instead we rely of the last 3 characters in the name.

will you, @lp, edit the Instructions accordingly.
The changed file, /include/ui/ui_view.inc, can be downloade here and replaced..

Joe

Go to forum: Announcements

52 Reply by joe

(6 replies, posted in Announcements)

Sure, I will fix that.
Should we use the same name, or only XUMM?

Joe

Go to forum: Announcements

53 Reply by joe

(6 replies, posted in Announcements)

Thanks for these instructions.
This is going to be implemented in the next minor release. But if you want to try this already now you can download the file /includes/ui/ui_view.inc here and replace on your server.

Joe

Go to forum: Announcements

54 Reply by joe

(7 replies, posted in FA Modifications)

This has been committed to stable repo and instructions will be put in the Announcement Forum by @lp.

Joe

Go to forum: FA Modifications

55 Reply by joe

(1 replies, posted in Reporting)

hello,

I understand your concern, but when printing all the suppliers, we have to include the inactive suppliers, otherwise we have differences from the GL reports.

Maybe we should mark them as (inactive), right?

Go to forum: Reporting

56 Topic by joe

(3 replies, posted in Announcements)

Announcement

This is a 2.4.16 release, which is a new feature release as well as a bugfix release.

A couple of php 8 problems has been fixed. This release should now be PHP 8 compatible. The following versions has been tested: 8.0.0, 8.0.7, 8.0.12 and 8.1.6.

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

Download instructions

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

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

Purchase documents

We have changed the purchase order detail line description to be updated with the entered
value from editable description or from the Supplier Description field from Purchase price table.

There are so many options for the description field, so we have to get the po line description
held together with the Purchase Order.

Otherwise all other stuff is handled as before.

FA is backward Compatible with this, so there should not be any problems with printing older
Purchase Orders.

At the same time, we have re-established the option to enter fractions of the purchase price.
Up to 6 decimals can be entered, if needed. But only use this option if needed.

Items and Fixed Assets Attachments

The Items and Fixed Assets can now have Attachments if you need this, and when entering new items,
there is an extra tab for entering Attachments. The operation is the same as for Customers and
Suppliers. You can also use the Setup - Attach Documents for this new option.

Security

FrontAccounting should NOT be used via unsecure http protocol. If you really need this - change SECURE_ONLY constant in /includes/session.inc to false (comment in the file added). Unfortunately this option cannot be added in sysprefs/config.php because the settings are not available before session is started.

Common

  • Bug. add_domain function generates a big list of not found domain file errors. Fixed.

  • Bug 5676: Currency stored in MySQL DOUBLE Type causes strange error. Fixed by explicitly SQL ROUND to price dec in
    updating allocations.

  • Bug 5684 Attach documents: error message when attaching document on some php8 versions fixed.

  • Annoyance 5683: Allow attachments from most needed post-creation option screens.

Sales

  • Bug 5678: Customer/Supplier Transactions Ageing Display Calculates Incorrectly (including full allocs) in Customer/Supplier Inquiries. Fixed.

  • Bug 5687: Unable to dispatch SO for service items with u/m decimal places set as "user defined" when SO item qty is less than 5. Fixed.

  • Changed get_unic_dec to get_qty_dec in customer documents for eliminating return -1.

Purchasing

  • Bug. Supplier Payment db calls void_cust_allocations. Fixed to void_supp_allocations.

  • Bug 5678: Customer/Supplier Transactions Ageing Display Calculates Incorrectly (including full allocs) in Customer/Supplier Inquiries. Fixed.

  • Bug5679. Supplier Invoices: error when second invoice to GRN was entered, fixed.

  • Supplier description is overwritten when receiving items. Fixed.

  • Bug 5695: Purchase Order Item Description should be saved on the PO line description directly. Fixed.

  • Allow fractional entry of Purchase Order Line Price. Up to 6 decimals.

  • Bug 5682: Voided PO Deliveries showing up in inquiries. Fixed by changing to Voided icon instead of GL icon.

  • Bug 5697: In Supplier Transaction Inquiry, Aging balances are Incorrect. Fixed.

Item and Inventory

  • Bug 5692: Translatable Strings in locations.php were not translatable. Fixed.

  • The average material cost test for either qoh > 0 and qoh + qty > 0 has changed to 0.0000000001 to avoid strange php results for very small values.

  • Implemented an Items tab for attachments and modified the existing setup attachments.

Fixed Assets

  • Implemented a Fixed Assets tab for attachments and modified the existing setup attachments.

Bank and General Ledger

  • Bug 5685: Bank Statement w/Reconcile report includes gl_trans values that are "0.00". Fixed.

Go to forum: Announcements

57 Reply by joe

(3 replies, posted in Accounts Payable)

Sure, I will take them too begore a release.

Go to forum: Accounts Payable

58 Reply by joe

(14 replies, posted in Report Bugs here)

These items has now been fixed and committed to stable repo.

See forum topic https://frontaccounting.com/punbb/viewt … p?id=10276

Joe

Go to forum: Report Bugs here

59 Topic by joe

(3 replies, posted in Accounts Payable)

We have changed the purchase order detail line description to be updated with the entered
value from editable description or from the Supplier Description from Purchase price table.

There are so many options for the description field, so we have to get the po line description
held together with the Purchase Order.

Otherwise all other stuff is handled as before.

FA is backward Compatible with this, so there should not be any problems with printing older
Purchase Orders.

At the same time, we have re-established the option to enter fractions of the purchase price.
Up to 6 decimals can be entered, if needed. But only use this if needed.

@apmuthu.
Will you check the Wiki and try to update this.

Due to this and other bug fixes we will soon make a minor upgrade.

Joe

Go to forum: Accounts Payable

60 Reply by joe

(14 replies, posted in Report Bugs here)

Hello again,

@ckrosco
I understand your problem with the price decimals. We could simply remove the rounding and only calculate the $price = $price * $data['conversion_factor']. This lets you decide how many decimals the $price should be in. Or as you showed, 6 decimals. What do you think?

Joe

Go to forum: Report Bugs here

61 Reply by joe

(14 replies, posted in Report Bugs here)

@ckrosco
The supplier_code should only be updateded if there is no data for supplier price record. So this has been changed and committed.
Please replace the file on your server.

Regarding the price truncation, I will have a closer look into this.

Joe

Go to forum: Report Bugs here

62 Reply by joe

(14 replies, posted in Report Bugs here)

Hello @ckrosco

The only place the supplier's code or Description is shown is on the written purchase order. On all other places we are using our own name due to internal confusion otherwise.

So this is not a bug. The only person(s) that need to know the suppliers code is the suppler himself. Right?

Joe

Go to forum: Report Bugs here

63 Reply by joe

(13 replies, posted in Items and Inventory)

Thanks @kvvaradha for participating in this discussion.

Joe

Go to forum: Items and Inventory

64 Reply by joe

(13 replies, posted in Items and Inventory)

As you can only have 10 decimals (6 in UOM) in User Preference dialog the test for qoh or qoh+qty > 0.0000000001 will handle all situations now. I have made rigorious tests and it seems to handle all situations now.
All values less than 0.0000000001 will not be possible in the algorithm and no calculation will be executed.

Joe

Go to forum: Items and Inventory

65 Reply by joe

(13 replies, posted in Items and Inventory)

After having tested this weighted average material cost, I have found that the test for qoh > 0 and for qoh+qty > 0 will fail for very small values under 0.0000000001, so the test will be changed to test for this value instead to avoid these fails.

Joe

Go to forum: Items and Inventory

66 Reply by joe

(13 replies, posted in Items and Inventory)

@kvvaradha

To use our weighted average material cost, we must use the same decimals in the items qty. It is this that causes our miss calculation. F.i. if you start with qoh with 0.09 our algorithm is just fine. If we use the qoh of 0.08 we will get a zero value and nothing is calculated. Just fine.

So I see no problems here.

Joe

Go to forum: Items and Inventory

67 Reply by joe

(13 replies, posted in Items and Inventory)

$kvvaradha

yes, if the ($qoh + $qty) is less than 1, there will be strange results. Before calculating this new material_cost, maybe we should first test if the (qoh + qty) >= 1. what do you think?

The routine get_unic_dec() will sometimes return -1. If the return value is -1, then the UOM is using the user defined decimals on the UOM. And should be tested by user_qty_dec(). I will check if all calls to get_unic_dec() is testing for this.
I am aware of the user_price_dec problem with material price. Maybe a standard flag on the home_currency function. to return the value without rounding. I am jsut afraid of ev. side effects. What do you think?

Joe

Go to forum: Items and Inventory

68 Reply by joe

(3 replies, posted in Items and Inventory)

FA is using average material cost on stock items.

The operation can be seen in /purchasing/includes/db/grn_db.inc in the first function update_average_material_cost($supplier, $stock_id, $price, $qty, $date, $adj_only=false).

On line 66 you will see
$material_cost = ($qoh * $material_cost + $qty * $price_in_home_currency) /    ($qoh + $qty);
$material_cost will be currennt material cost multiplied by current qoh + transaction qty multiplied by price in home currency. This will then be divided by qoh + qty.
These operations will be new average matefial cost.
So the calculations are correctly done.

All stock transactions are going through this routine.

Joe

Go to forum: Items and Inventory

69 Reply by joe

(13 replies, posted in Items and Inventory)

FA is using average material cost on stock items.

The operation can be seen in /purchasing/includes/db/grn_db.inc in the first function update_average_material_cost($supplier, $stock_id, $price, $qty, $date, $adj_only=false).

On line 66 you will see

$material_cost = ($qoh * $material_cost + $qty * $price_in_home_currency) /    ($qoh + $qty);

$material_cost will be current material cost multiplied by current qoh + transaction qty multiplied by price in home currency. This will then be divided by qoh + qty.
These operations will be new average material cost.
So the calculations are correctly done.

All stock transactions are going through this routine.

Joe

Go to forum: Items and Inventory

70 Reply by joe

(9 replies, posted in Translations)

Sure, will download and ask Itronics to do that.

Joe

Go to forum: Translations

71 Reply by joe

(3 replies, posted in FA Modifications)

Ok, done. Included in 2.4.15 at Sourceforge.net.

Joe

Go to forum: FA Modifications

72 Topic by joe

(3 replies, posted in Announcements)

Announcement

This is a 2.4.15 release, which is mainly a bugfix release, but also contains an improvement and additional security fixes.

A couple of php 8 problems has been fixed. This release should now be PHP 8 compatible. The following versions has been tested: 8.0.0, 8.0.7, 8.0.12 and 8.1.6.

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

Security

FrontAccounting should NOT be used via unsecure http protocol. If you really need this - change SECURE_ONLY constant in /includes/session.inc to false (comment in the file added). Unfortunately this option cannot be added in sysprefs/config.php because the settings are not available before session is started.

Download instructions

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

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

Common

  • Bug. Not translatable string in Print Statements Report. Fixed.

  • Feature. Added company switch for placing company logo on certain views.

  • Bug. Call to Function add_access_extension was missing in Dropdown theme. Fixed.

  • Feature. Install/Activate Extensions: displays more sensible information for modules available/installed.

  • Feature. Implemented automatic greater fonts in default themes, when higher screen resolutions.

  • Feature. Clean up in function get_attachment_string() in attachments_db.inc

  • Bug. php 8. call to function db_set_charset, maintenance_db.inc can not have second parameter (encoding) to null. Used utf8 instead.

Sales

  • Bug. GL Dimensions should also be included on balance accounts in sales order delivery and Inventory adjustments. Fixed.

  • Bug. Dimensions on credit note should also be set on balance accounts. Fixed.

  • Bug 5660: php8. Unable to create customer credit note. Fixed.

  • Bug. Can't void customer payment if there is an invoice with same number that has been credited. Fixed.

  • Feature. Customer Transactions, Allocations and Supplier Transactions, Allocations has got another selection type, Journal Entries.

  • Feature. Added Customer Payment Attachments menu option after operation.

  • Bug. php 8. nl2br with null parameter in view_sales_order. Fixed.

Purchasing

  • Bug in purchasing/includes/db/invoice_db.inc gives error. Wrong document src. Fixed.

  • Bug. Credit note bug in suppliers. Result in errors. Fixed.

  • Bug. Cannot add received items to invoice if there are empty prev. items. Fixed.

  • Feature. Added Supplier Payment Attachments menu option after operation.

Item and Inventory

  • Bug. Dimensions in cost update should also be set on balance accounts. Fixed.

  • Bug. Cost Update - Second parameter in memo was not showing decimals. Fixed.

  • Bug. Inventory valuation report. Unit decimal -1 issue. Fixed.

Manufacturing

  • Bug. When booking costs on workorders the set dimension on the item wasn't booked on the balance account. Fixed.

Fixed Assets

  • Bug. Presenting a fixed asset attachment (was presenting the Purchase Delivery, should be the Supplier Invoice).

Dimensions

  • Bug. GL Dimensions should also be included on balance accounts in sales order delivery and Inventory adjustments. Fixed.

  • Bug. Dimensions in cost update should also be set on balance accounts. Fixed.

  • Bug. Dimensions on credit note should also be set on balance accounts. Fixed.

  • Bug. When booking costs on workorders the set dimension on the item wasn't booked on the balance account. Fixed.

Bank and General Ledger

  • Bug. Reconcile Bank Account added filter up to reconcile data.

  • Bug. Audit trail is showing double entries for Payment and Deposit. Fixed.

  • Bug. GL Account in Company Defaults missing for test. Fixed

  • Feature. Moved years in default COAs one year forward.

Go to forum: Announcements

73 Reply by joe

(3 replies, posted in FA Modifications)

Thanks @kvvaradha.

We just got this included in the new minor 2.4.15 that is releasing today.

Joe

Go to forum: FA Modifications

74 Reply by joe

(10 replies, posted in FA Modifications)

FYI, itronics has updated the Fiscal Years in the Repo COAs (not included in core). He has found a smart way to automatically always use the current year and previous year for Fiscal Years.

Joe

Go to forum: FA Modifications

75 Reply by joe

(5 replies, posted in Announcements)

The topics are inside the Sections. The archive forum is the parent forum for all the sections. There are no topics here.
The sections are accessible by the links.

Go to forum: Announcements