It's much more fun, when you can discuss your problems with others...
You are not logged in. Please login or register.
FrontAccounting forum → Posts by apmuthu
Logout
Clear browser cache
Close all instances of the browser
Login
List the contents of the users table.
Check if the IP Hijack code is causing issues with your PHP version.
Your diagnostics are for company 0 - list it for the company 1 or whichever failed.
Provide example of GL Entries you wish to achieve - voucher specifics.
Enable the openSSL extension in PHP and restart the webserver.
Folder write permissions issue?
The field ordering for some tables do not match the en_US-new.sql. The table sys_types is no longer used in FA 2.4.x. There are other tables / fields in FA 2.4.6 with some dropped. The official charts have been reasonably updated to comply with table names and field presence and ordering in the FA24extensions repo.
@joe: Any fixes for non calendar year fiscals in dealing with depreciation?
Use an Open Sales Order for each Project till completion. Keep delivering as needed. Then on project completion, create a single sales invoice for all such deliveries. Use dimensions/tags as needed otherwise.
Read the Wiki and search the forum or post your bounty in the Jobs forum for FA assistance.
@joe: any commit needed?
@sledge: The existing CoA you are using must be compared with the one in my repo and suitable changes done to synch it with the latter among possibly others.
Anyone else having this issue?
It is not a solution. It will provide inputs to make an extension to accommodate it as a functionality even possibly in the core, whilst providing you a means of quickly getting the work done in the meanwhile.
1. Take a backup 1.
2. Make one depreciation entry manually.
3. Make a list of all other assets you wish to depreciate in a similar manner.
4. Take backup 2.
5. Compare backup 1 and backup 2 and see what SQLs are needed to arrive at the latter from the former.
6. Make such SQL statements for other similarly depreciable items and execute it enblock
7. If anything breaks, revert to either backup 2 or 1 as appropriate.
Will need to logout and login again after closing all browser instances and clearing the cache.
Looks like we need to make this feature generic to be based on the fiscal year start and end dates.
FA 2.3.26 release version has the same rep709.php as the v2.3.25 has. Ignoring whitespace changes, the effective diff between the FA 2.3.26 version and FA 2.4.6+ version is attached to experiment with.
The Wiki lists all resources needed and searching the forums would be a start.
FA24extensions Repo
GL Account Groups Post
GL Sub Ledger Post | Alternative Post
Use Sub-Ledger for properties and brokerage main accounts. The Wiki has only skeletal info on this as of now but some Charts in the official pkg repos and in the FA24extensions repo have examples of such usage.
The official Dutch (nl_NL) Chart has been updated to match the fields and field orders in the FA24extensions repo.
In the 2.5 alpha, make provisions in the db for the bin concept in the warehousing for inventory - long overdue.
Official Dutch CoA has some infirmities is excess/missing fields as also some other CoAs. In my unofficial FA24extensions repo, I have corrected all of them thus far:
There was no difference between the official nl_NL-default.sql and the one in my unofficial FA24extensions repo except that the lone fiscal year start date has been advanced from 2017 to 2018 and the presence of a missing sys_prefs flag:
('ref_no_auto_increase','setup.company', 'tinyint', 1, '0'),It has since been updated in my repo to have the corrections for missing fields, not needed fields as well.
Furthermore, there are some differences between the official chart and the one auto-generated from my script.
Official:
INSERT INTO `0_bank_accounts` VALUES
('1010', '2', 'XYZ Bank betaalrekening', '12345678', 'XYZ Bank', 'Adres bank 1\n1234 AB PLAATS BANK', 'EUR', '1', '1', '9040', '0000-00-00 00:00:00', '0', '0'),
('1000', '3', 'Kas', 'N/A', 'N/A', 'N/A', 'EUR', '0', '2', '9040', '0000-00-00 00:00:00', '0', '0'),
('1020', '0', 'XYZ Bank spaarrekening', '12345678', 'XYZ Bank', 'Adres bank 1 \n1234 AB PLAATS BANK', 'EUR', '0', '4', '9040', '0000-00-00 00:00:00', '0', '0');
Generated:
INSERT INTO `0_bank_accounts` (`account_code`,`account_type`,`bank_account_name`,`bank_account_number`,`bank_name`,`bank_address`,`bank_curr_code`,`dflt_curr_act`,`id`,`bank_charge_act`,`last_reconciled_date`,`ending_reconcile_balance`,`inactive`) VALUES
('1060', '0', 'Current account', 'N/A', 'N/A', NULL, 'EUR', '1', '1', '5690', '0000-00-00 00:00:00', '0', '0')
,('1065', '3', 'Petty Cash account', 'N/A', 'N/A', NULL, 'EUR', '0', '2', '5690', '0000-00-00 00:00:00', '0', '0');
Similar data changes in chart class, chart_master, etc.
Official audit_trail: `stamp` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
Generated audit_trail: `stamp` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
Official bank_trans: `bank_trans_type_id` int(10) unsigned DEFAULT NULL,
Generated bank_trans: No such field in FA 2.4
Official bom: fields parent, component, loc_code are all CHAR fields.
Redundant: KEY `parent` (`parent`,`loc_code`),
PRIMARY KEY (`parent`,`component`,`workcentre_added`,`loc_code`),
Generated bom: The above fields are all VARCHAR
No KEY: `parent`
PRIMARY KEY (`parent`,`loc_code`,`component`,`workcentre_added`),
Official budget_trans: No memo_ field after `account` field
Generated budget_trans: `memo_` tinytext NOT NULL,Both links in your post above are the same. Try to inspect the code behind the browser display of the link - you might find another link is some js.
It is possible that the email was being spooled if there are many in the range or that the range is not properly made to be ascending (from/to).
Anyone else getting this issue?
@joe: In the light of discussions here and in the other thread, please set this issue to rest.
Applying CoA differences between the official one and mine is trivial as it mostly just has schema changes in field ordering. The real issue comes when using the new pattern of document numbering from FA 2.3.x to FA 2.4.x. If your FA 2.4.x has errors on using my CoA but no errors on using the official CoA, then your official CoA schema will need to be compared with mine in a diff tool like WinMerge or directly in a MySQL client like SQLyog.
The FA userbase would be sad to see a longtime user like you go if you do! We are here to do any hand holding as required.
@anoopmb: good catch. Needs to be corrected in FA 2.3 as well. Where did you have to use this function?
Whether a new field is necessary and whether the function name should be changed accordingly needs to be ascertained.
Note that this function is not used in FA 2.3.26 and in FA 2.4.6 as well and see if it needs to be removed. Neither is it used in any official theme / extension and those in my FA24extensions repo.
@joe: can commit it.
The menus appear very cluttered (when expanded out) for accounting usage. A nice attempt though and maybe the finished version will be better.
FrontAccounting forum → Posts by apmuthu
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 4 official extensions. Copyright © 2003–2009 PunBB.