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
Make it a checkbox in the UI - IsPrivate - as a TinyInt (1).
Replace all CRLF with LF in js/kanban.js and css/kanban.css files.
Try to replace the PHPMailer with the standard email class in FA which itself is based on it. The tests, examples and docs folder in it are not necessary.
Read the Wiki.
he global settings are in the config.php, the company preferences are in the sys_prefs table managed from the Preferences and Company Setup forms. The currency defaults and all others can be set in the chart of accounts and then the company can be created.
If you upgraded your FA 2.3.x to FA 2.4.x, the you may be using the old document numbering system.
@joe/@itronics: Is this how it is coded?
Where is the Project Type entered?
@joe/@itronics: Yes, this needs to be corrected and the empty.po updated.
Adding entries in the database manually is not advisable.
There are other table fields that affect next reference number for new transactions and the audit_trail table. If, however, you still need to do it, then in another dummy company, add a bank account and compare the before and after sql backups to identify what changed and do likewise appropriately in your actual company.
Only one GL Account can be mapped as one Bank Account. Create the GL Account first and then assign the Bank Account.
This way there will be no errors like "GL Accounts already in use".
Adjustment entries (Journal Entries) to match the Opening Balance can be done at the close of the previous fiscal so that all carried over Balance Sheet entries in the new fiscal will be correct. Such entries however will not have the tracking capability for allocations in AR and AP and their reports on ageing.
Make sure you have all the GL entries and the Bank Accounts setup and only then import your transactions.
Have all the fiscal years too available and make sure you have the option to enter transactions in earlier fiscal years enabled in the role permissions.
You will need to pull in the data from FA into your application from within your application or program a trigger in the FA DB to populate your application DB.
To pull in FA data from within your application, use the FA SlimAPI to create a script that can be run on demand or in a cron job.
@joe: Thanks.
Connecting to other applications is best done using the REST API (See SlimAPI in the wiki).
How did you import the banking transactions into FA without having the relevant bank account(s) in place?
If you have a backup prior to importing the transactions, then restore it and logout and login again and then create the bank accounts and then import the transactions afresh.
Which version of FA are you using?
What does "21 year" mean, assuming "14000" is the number of transactions imported you refer to?
@joe: Which setting closes a date (not fiscal year) for further transactions / edits?
Remove Edit permissions in a role for such a restricted user.
@joe / @itronics: any progress on @braathwaate's commit and way forward here?
Prepare the BoM and make sure it also has the necessary labour / equipment charges as cost items. How do you wish to apportion the fixed overheads?
Short of creating your own custom module / hard code changes, you can prefix all items in each location with the appropriate Loc ID prefix. Also to produce Item A from each location prefix it with the appropriate Loc ID. Now the BoM for ItemA_Loc1 will be present n Loc1 only and hence can be used for manufacturing in Work Centre 1.
Native FA allows any location to supply any item to any work centre.
Elaborate on what you mean by close and open accounting periods for each module.
The P&L should be prepared for the fiscal year and hence the close and open for it.
Do you mean to restrict entry to a certain accounting period (what least count?) for each module?
If so, what about reporting across multiple periods, year, years?
For now, focus on the field order in the tables where memo_ is present in your output above, especially in the first one below:
ALTER TABLE `0_budget_trans` MODIFY `memo_` tinytext NOT NULL;
ALTER TABLE `0_comments` MODIFY `memo_` tinytext;
ALTER TABLE `0_gl_trans` MODIFY `memo_` tinytext NOT NULL;
ALTER TABLE `0_supp_invoice_items` MODIFY `memo_` tinytext;
ALTER TABLE `0_voided` MODIFY `memo_` tinytext NOT NULL;Do not make any change to your current schema unless you are sure of the direction of change (from which schema to which) for now.
Which Chart of Accounts are you using and where and when did you get it from?
Was it upgraded from an earlier FA v2.3.x?
A few sql upgrade scripts merely add an new field instead of positioning them to be in synch with the field order in the latest sql/en_US-new.sql file. Even some charts in the official pkg repo too need to have their fields and tables synched likewise. A more uptodate set of charts are in my FA24extensions repo.
There are 5 tables that have the memo_ field and their order can be checked from the attachment herein with that in your backup.
Online MySQL Schema Compare
DBDiff @ Github
Discussion @ StackOverflow
FA now natively supports upto PHP 7.1.x only. PHP 7.2.x is not yet supported.
PHP 5.3.x is still the most widely used and texted version for FA so far for long time users though later versions happen to be discussed in the forum as newbies try to grapple with their maiden installs.
Most script based installs (Scriptaculous, cPanel, SimpleScripts, Fantastico, public OpenVZ templates, etc) rely on outdated versions of FA where the hosting providers make several versions of PHP available on a per application basis possibly in CGI mode.
PHP 7.1 to 7.2 Migration Notes.
The code changes stated in my post above are not required.
The show_codes field in the preferences form is meant to display item_codes in the drop down select boxes for items in the Web UI.
The show_po_item_codes entry in the sys-prefs table controlled by the Setup => Banking and GL Setup form is to direct the display of the item codes in the PO Report (rep209.php).
The show_codes checkbox "name" is available in the preferences menu and gets stored in the users table.
The show_po_item_codes is present as an entry in the sys_prefs table. Under Setup => Banking and GL Setup => Show PO item codes can be checked, and we can then see the item_code printed out in the PO report (rep209.php).
In fixing this, we need to suppress the display of the Item Code heading if not chosen.
The class sys_prefs contains the method show_po_item_codes() which promptly returns the value from the sys_prefs table.
Hence, for now, change line 142 of reporting/rep209.php:
if ($SysPrefs->show_po_item_codes()) {to be:
if ($SysPrefs->show_po_item_codes() || user_show_codes()) {What is the logic behind this redundancy.....
Not yet.
Which version of FA are you using?
Did you modify the PO report file - rep209.php?
Did you recently change your PHP / MySQL versions?
https://frontaccounting.com/fawiki/uploads/Help/Rep209_PurchaseOrders.png
Looks like this is an old CSRF vulnerability for FA v2.3.4 as of 2011-03-05 wrongly posted here as for v2.4.3.
https://0day.today/exploit/16029
Then when the manufacturing charges invoice is raised, put in the cost of goods sold and price of goods received instead so that the net result is what you need to book as manufacturing charges after allowing for tax credits.
Alternatively:
Treat the Company B as a regular Customer and another account for Company B as a Supplier. Keep the Sales and Purchases separate and provide for tax credits on purchase back of manufactured items.
If your tax accountant agrees, make a delivery on consignment for manufacture to Company B so that no billing needs to be done except in escrow and contra-ed when the purchase is made.
FrontAccounting forum → Posts by apmuthu
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 4 official extensions. Copyright © 2003–2009 PunBB.