Search options (Page 48 of 247)

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.

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.

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.

You may want to make a separate comment like entry below the tallied values in a different column so as not to confuse accountants.

Updated Dutch (nl_NL) translations. See Links above.

180 strings left to translate.

Thanks. Wiki-ed it.
Screenshot upload to wiki - settings awaited.

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?

Should we not check if real_name is blank instead of a single space?

Make a Kit item of your "product and service" sold to your customer.
Since you know all the costs - landed cost - book it all a the price of the product bought from the Supplier.
Do not directly book the Supplier Invoice to the COGS. Do it through the Supplier Account where you can allocate the payments too.

1. Supplier Advance Proforma Invoice.
2. Advance to Supplier: Dr Supplier, Cr Bank
3. Cr - Import, Delivery, Custom Duties, etc,, Cr - Supplier for Direct Goods Cost, Dr. Purchases Expenses for Goods+Costs
4. Take into stock: Cr Supplier, Dr Stocks
5. (Optional) Allocate Payment to Supplier: Dr Supplier, Cr Supplier
6. Make Kit Item of Unit Goods and variable units of Install Service Charges
7. Invoice Kit Item to Customer - Dr Customer, Cr Sales
8. Payment from Customer - Cr Customer, Dr Bank
9. (Optional) Allocate Payment from Customer - Dr Customer, Cr Customer

@joe: anything more standard?

Once the Barcode type and value field are ascertained, you can use TCPDF to generate them as needed.

In the sql/en_US-new.sql standard chart, the fields with the word description in them are defined thus:

# grep description en_US-new.sql | grep -v KEY

  `description` varchar(60) NOT NULL DEFAULT '',
  `description` varchar(60) NOT NULL DEFAULT '',
  `description` varchar(60) DEFAULT NULL,
  `reason_description` char(100) NOT NULL DEFAULT '',
  `description` tinytext NOT NULL COMMENT 'usage description',
  `description` tinytext,
  `description` tinytext,
  `description` varchar(60) NOT NULL DEFAULT '',
  `description` varchar(200) NOT NULL DEFAULT '',
  `description` varchar(60) NOT NULL,
  `supplier_description` char(50) NOT NULL DEFAULT '',
  `description` tinytext,
  `description` varchar(60) NOT NULL,
  `description` varchar(60) NOT NULL DEFAULT '',
  `description` varchar(60) NOT NULL DEFAULT '',
  `description` tinytext,
  `description` varchar(50) DEFAULT NULL,
  `description` varchar(60) NOT NULL DEFAULT '',
  `description` varchar(200) NOT NULL DEFAULT '',
  `long_description` tinytext NOT NULL,
  `description` varchar(200) NOT NULL DEFAULT '',
  `long_description` tinytext NOT NULL,
  `description` tinytext,
  `description` varchar(60) DEFAULT NULL,
  `description` char(50) NOT NULL DEFAULT '',

In FA v2.5 alpha, it may be useful to classify the description field differently and standardize their field length / type uniformly.

In the following files that refer to supplier_description, there is no truncation occurring in the code (except where function text_row() is used):

inventory/purchasing_data.php
inventory/includes/db/items_purchases_db.inc
purchasing/includes/purchasing_db.inc
purchasing/includes/db/po_db.inc
reporting/rep209.php

Hence, a mere increase in field size is sufficient ordinarily.

However, where a form field restricts input size / max width using the function text_row() defined in includes/ui/ui_input.inc, changes in 4th (size) and 5th (max width) arguments will also be needed. This is so only in the first file listed above.