1,826

(8 replies, posted in Reporting)

Report 1 GL Transactions balance is correct:
Ending Balance - Opening Balance = 726,990.22 - 715,855.05 = 11,135.17

Report 2 Tax Balance wrong:
(Outputs - Inputs) * 14 / 100 = 11,633.37 = (Output Tax - Input Tax) = (16,642.49 -  5,009.12)

This is clearly a case of rounding off errors. The first report is done line by line computation of tax, whilst the second one computes the tax on the total value at the end.

@joe: Should we not attempt to simulate the first in the code for the second?

1,827

(5 replies, posted in Setup)

When you upload the FA code to your server, there is only a config.default.php file which is a template for your real config.php file which gets created along with the config_db.php file when the install is complete. Some other files too get created on completion of install.

Explain what you did to "clear the existing entries". The default password is "password" and the default user is "admin". Restoring your company file will need to take care of the table prefix to match that which is in the config_db.php for the said company.

1,828

(8 replies, posted in Reporting)

The period in the first report is Period:    01-03-2018 - 31-03-2018.
The period in the second report is Period: 01-02-2018 - 31-03-2018.
Synching them might solve your issue.

1,829

(0 replies, posted in Translations)

The Norwegian (nb_NO) translations for the core has been updated (88% done) and a new Install Wizard has been added (27% done).
The Norwegian language has now been added to Transifex.

This is an old thread and was meant for FA 2.3.x and not for the current version. Kindly revert if you are on the FA v2.4.x branch. If you are on the FA 2.3.x branch, then take it's counterpart folder from the last released version in that series - better still, just upgrade to FA v2.3.26.

Refer this Post for update mechanism and non use of deprecated update_journal function.

The function write_journal_entries() defined in gl/includes/db/gl_journal.inc is now used to edit journal entries by first voiding it and then adding the modified entry it as a new one.

In FA 2.3.x, the said function write_journal_entries() is defined in gl/includes/db/gl_db_trans.inc.

1,833

(26 replies, posted in Report Bugs here)

The outstandings seem to be computed for each line independently without being cumulative. This is wrong.
The allocations get summed up even for previous years as the date in the common WHERE clause is taken instead of being a specific range for allocations alone.

1,834

(5 replies, posted in Reporting)

It might be useful to include in a landscape report in rep101.php itself. Any reason not to include it in the core? The portrait mode does not have enough space in it - maybe just a branch_code number alone may suffice in it.

@kvvaradha: Provide your patch to include in the core. During such editing, does the reference number of the entry change?

1,836

(5 replies, posted in Reporting)

The Customer Balances Report (rep101.php) screenshot is here.

Note that the Customer Ledger Account is just one debtor_no in the debtor_master table. Only the debtor_trans table has the branch_code as well.

The $sql variable will need the trans.branch_code field in it in the function get_transactions() in the rep101.php file for your need to be addressed.

@joe: want to include the Customer Branch filter in the rep101.php?

This is a new file in FA 2.4.x. Looks like it was made to be linked into an Edit Journal button on journal entries listing.

1,838

(4 replies, posted in Announcements)

Post Release Fixes.

@kvvaradha: Good catch.
Wonder how it slipped thru for so long.

@joe: can commit it by removing the last closing bracket in the doc_date line.

1,840

(2 replies, posted in Setup)

Change it in the appropriate stanza in config_db.php file.

When the same company is both a customer and a supplier, allocations can be made separately if monies are available in ban/cash to make payment to supplier side and if receipts are available from the customer side to allocate to customer invoices.
If no such amounts in the bank and from the Customer receipts are available to allocate, a form of adjustment allocation is needed between the Customer side and Supplier Side of the same company.
A credit note equated debit note to sum zero will be needed.

For example, Company A supplies $ 100/- worth of goods and takes delivery of $75 worth of our products. If we pass a Journal Entry to transfer $75 from the supply side to the customer side to pay for the Sales Invoice, the allocations would not appear to have been done on both sides, but mere amounts tallied. Here we pass a Credit Note to the Customer Side and a matching debit note to the Supply side and then allocate the credit and debit notes to the customer and supplier invoices.

Yes.

Is it that you are sending goods to your customer (retailer) on the basis of some invoice raised on them and then if your goods remain unsold you have agreed to take return of it from your retailer and / or agree to pay the retailer for his shelf space rental as your prorata cost sharing agreement as you control the price at which your product must be sold to the end customer which if too high will render most unsold and make of poor returns to your retailer?

If this is the case, make the retailer a supplier of rental services to you and then make a Supplier invoice to the extent of the rental and then pay / adjust / allocate accordingly.

@BraathWaate: The reason this part of your Pull Request was not taken into the core is probably because the browser back button usage is not advised in FA and that is why we have a Back link on practically every key FA page which takes us to a known state each time it is clicked. Browser Cache is another issue that will affect such operations.

1,845

(20 replies, posted in Banking and General Ledger)

First off, I assume that you have no extensions installed that need db modifications.

A similar DB schema check will need to be done for all tables and for all records in lookup tables.
Note that the default document numbering system now has a pattern template in FA 2.4.x.

Some Chart of Accounts in FA 2.3.x and even in FA 2.4.x have field order differences with the standard sql/en_US-new.sql chart.

After synch-ing the chart, then see if an upgrade withing FA is necessary (Setup=>Software Upgrade). In each instance backup before and after such interventions.

1,846

(20 replies, posted in Banking and General Ledger)

Which Chart of Accounts did you start out in FA 2.3?
Do you have a backup before upgrade?
Can you check out the differences between the pre-upgrade sql schema and that of the last FA 2.3.26 version's sql/en_US-new.sql?

You should have done all this and then upgraded to FA v2.3.26 and then if all was well, attempt to do an upgrade to FA 2.4.4 and then verify that the resultant schema is in consonance with the tables and field orders and the new config.php settings and new sys_prefs table records - above all, the schema being in synch with the latest sql/en_US-new.sql.

1,847

(20 replies, posted in Banking and General Ledger)

The table definition of the 0_budget_trans table in FA 2.4.x is:

CREATE TABLE `0_budget_trans` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `tran_date` date NOT NULL DEFAULT '0000-00-00',
  `account` varchar(15) NOT NULL DEFAULT '',
  `memo_` tinytext COLLATE utf8_unicode_ci NOT NULL,
  `amount` double NOT NULL DEFAULT '0',
  `dimension_id` int(11) DEFAULT '0',
  `dimension2_id` int(11) DEFAULT '0',
  PRIMARY KEY (`id`),
  KEY `Account` (`account`,`tran_date`,`dimension_id`,`dimension2_id`)
) ENGINE=InnoDB;

It has just 7 fields and the memo_ field is the 4th one.

Which Chart of Accounts did you start out with?

1,848

(0 replies, posted in FA Modifications)

When any code that has been specifically written for FA 5.4+ needs to be backported / integrated with FA in a backwards compatible manner, refer the GitHub project php-code-downgrade.

1,849

(26 replies, posted in Report Bugs here)

At Line 52 in reporting/rep101.php, the value of the $sql variable for the first available debtor_no in the second Date Range (2018) in the function get_open_balance() is:

SELECT 
    SUM(IF(t.type = 10 OR (t.type IN (0 , 1) AND t.ov_amount>0), -ABS(t.ov_amount + t.ov_gst + t.ov_freight + t.ov_freight_tax + t.ov_discount), 0)) AS charges
   ,SUM(IF(t.type != 10 AND NOT(t.type IN (0 , 1) AND t.ov_amount>0), ABS(t.ov_amount + t.ov_gst + t.ov_freight + t.ov_freight_tax + t.ov_discount) * -1, 0)) AS credits
   ,SUM(IF(t.type != 10 AND NOT(t.type IN (0 , 1)), t.alloc * -1, t.alloc)) AS Allocated
   ,SUM(IF(t.type = 10, 1, -1) * (ABS(t.ov_amount + t.ov_gst + t.ov_freight + t.ov_freight_tax + t.ov_discount) - ABS(t.alloc))) AS OutStanding
FROM 1_debtor_trans t
WHERE t.debtor_no = '1'
  AND t.type <> 13
  AND t.tran_date < '2018-01-01'
GROUP BY debtor_no;

The output corresponding to the statements attached is:

charges    credits    Allocated    OutStanding
-6540        -6540            0            0

Do you want to zero out the Charges and Credits in this instance?

1,850

(9 replies, posted in Setup)

Wiki-ed it.