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
Here is a first draft of rep311.php which should do the job.
@joe: Move the defines to sys_prefs table with appropriate settables in the Company Setup and incorporate it into the core if found useful.
Additional variables could be number of barcodes per sheet (here 1) besides suppressing the header if not necessary.
The first default company must not be removed.
However all is not lost.
Edit your config_db.php and set your default company to the index of the company you now have. It is also possible that your original company 0 database is still there and you can create a stanza for it in the sid file as well.
Start from scratch and install FA 2.4.6+ anew.
Use the en_US-new.sql chart - the one with no demo data for your default install and keep this "0" company as default. Only this company can create other companies.
FA has been in production use around the world for over a decade now.
If rep303.php has the 'EAN' replaced with 'C128B', the attached Stock Check Sheets would ensue.
The EAN8 barcode type is hardcoded in the reporting/rep303.php file in lines 327-329:
$barcode = str_pad($trans['stock_id'], 7, '0', STR_PAD_LEFT);
$barcode = substr($barcode, 0, 8); // EAN 8 Check digit is auto computed and barcode printed
$rep->write1DBarcode($barcode, 'EAN8', $rep->cols[$firstcol++], $bar_y + 22, 22, $SysPrefs->pic_height, 1.2, $style, 'N');The default FA reporting/includes/barcodes.php file is from the TCPDF 's 1dBarcode library when used.
The reporting/rep303.php file however uses another library's extracted barcode functionality which supports only the following subset of formats:
EAN, EAN-8, EAN-13, GTIN-8, GTIN-12, GTIN-14, UPC, UPC-12 coupon code, JANUsing another subset of TCPDF from a GitHub project for barcode generation is also feasible. This library is set to be PHP 5.4+ compatible but for backwards compatibility with PHP 5.3.x, just replace all instances of "= []" with "= Array()" in it's src/BarcodeGenerator.php file.
Sample code for using it in a standalone manner would be:
<?php
include('src/BarcodeGenerator.php');
include('src/BarcodeGeneratorPNG.php');
$generator = new Picqer\Barcode\BarcodeGeneratorPNG();
file_put_contents('src/files/081231723897-code128.png', $generator->getBarcode('081231723897', $generator::TYPE_CODE_128));
echo '<img src="data:image/png;base64,' . base64_encode($generator->getBarcode('081231723897', $generator::TYPE_CODE_128)) . '">';The above will both generate a file and display it inline as well.
Delete branches first and then delete customer with no branch. Transactions may be pertaining to the first branch created when the customer was created.
@kvvaradha: Your Post #3 is the same as your post #7 which has been incorporated in this official commit which is what I would like to revert and make it as per my commit.
Send it to ME :-)
I'll atleast update it in the FA24extensions repo which has some fixes over the years that others have reported or that which I just stumbled upon.
Whilst realising the method I mentioned above is too involved, an alternative way of looking at it would be:
1. Before closing a fiscal, make sure all "deletable customers" have zero balances with adjustment Journal Entries as appropriate.
2. Make a list of all such customers who then have zero balances for the year on closure using the Trial Balance before closing the fiscal.
3. Identify those customers chosen for deletion.
4. In the new year, after closing the previous fiscal, just attempt to delete the customer branches first and then the customer (is there any such option in the FA UI?).
5. Pray for the best!
@joe / @itronics: Making a provision to delete a customer with no transactions anywhere in the current fiscal will render the past records orphan - any good fix..... - maybe a check in all open fiscal years alone?
Setup => Company Setup => tick "Use Barcodes on Stocks" and optionally tick "Company Logo on Reports" if logo is present and desired.
Items and Inventory => Items => Add New Item
You will now see the EAN-8 Barcode which if clicked, will yield a random EAN-8 barcode
Any other barcodes you will need to make changes in the codebase and you can also use third party online tools to generate them like:
https://barcode.tec-it.com/en/EAN8
https://www.free-barcode-generator.net/code-128/
Items and Inventory => Inventory Reports => Stock Check Sheets => Select "Yes" for "Show Pictures" and optionally "Inventory Column" and now all barcodes will be listed.
Since you want code-128 barcode and one barcode per sheet with your fields listed there, just edit the Stock Check Sheets reporting/rep303.php file to suit your need.
If you need technical assistance for it, post your specs and bounty in the Jobs board and hopefully someone will assist you.
I have rolled it back in my FA24mods repo folder which upstream may pull in.
Your definition of "old" customers are those with no transactions for upto 4 years.
Look for persistent opening balances that have not been adjusted too in a long time.
1. check the debtors_master for full list of customers / suppliers.
2. check the debtor_trans for their old transactions to start with
3. then shortlist the ones that do not appear from a date 4 years ago
4. check if they appear in any of the various voucher types and keep only those which do not appear after a certain date four years ago.
5. Now these customers are in the crm_* tables and in the debtor_master and should not be in your recent debtor_trans table.
6. Copy these debtor_master and crm_* entries into an archive first
7. Now go ahead and delete the specific entries in their current db tables.
Many other tables like voided, gl_trans, cust_branch, etc., too can possibly sport remnants of such customers' transactions.
Make sure that the id of the fiscal years are in the same order as the year ranges themselves! Closing FYs will otherwise be a nightmare.
You may want to make a separate comment like entry below the tallied values in a different column so as not to confuse accountants.
Will need to revert this commit - see this post.
What is the purpose of getting the last_sales_order_detail() field (in this case, 'stk_code' which is the stock_id)? Byusing this commit, we are making the default choice of the Item description select box override the actual selection made in it. Should this be restricted to only those with editable description alone if used at all?
New FA 2.4.6+ install on Windows XAMPP 1.7.3, PHP 5.3.1, MySQL 5.0
Browser FireFox 52.9 ESR on WinXP SP3
Using sql/en_US-demo.sql Chart.
Sales => Direct Invoice
Changing the Item Code results in the next Item Description select box being correctly updated by Ajax.
Changing the Item Description select box momentarily changes the Item Code and then the Item Code reverts back to what it was along with the old Item Description appropriate to it.
Tested with and without Barcode enablement in Company Setup page.
Recent commits discussed in this post culminating in this commit may have something to do with it. Rolling back the said commit makes FA happy like before.
That is how it is expected to be.
PL will be clear and detailed only before closure.
BS will become clear by itself only after closure as the Profit/Loss gets transferred to it.
Updated Dutch (nl_NL) translations. See Links above.
180 strings left to translate.
Check on a clean install of FA 2.4.6+
Thanks. Wiki-ed it.
Screenshot upload to wiki - settings awaited.
Alternatively, make a separate table that holds debtor_masters' primary key (debtor_no) matched to an account number in osCommerce in the latter and create a view that provides for direct import into FA from it.
Are you all getting this error in your reports or in the screen display / drilldown view itself?
@joe: Has the BS/PL got their Cr/Dr switched on closure of Fiscal Year?
Instead of changing FA core operations, try to change the Balance Sheet report to suit your needs.
Should we not check if real_name is blank instead of a single space?
FrontAccounting forum → Posts by apmuthu
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 4 official extensions. Copyright © 2003–2009 PunBB.