3,226 Reply by apmuthu

(25 replies, posted in Reporting)

In the file includes/ui/ui_lists.inc, the function sales_areas_list():

function sales_areas_list($name, $selected_id=null)
{
    $sql = "SELECT area_code, description, inactive FROM ".TB_PREF."areas";
    return combo_input($name, $selected_id, $sql, 'area_code', 'description', array());
}

should be made to match it's peers (function sales_persons_list) as:

function sales_areas_list($name, $selected_id=null, $spec_opt=false)
{
    $opt = array();
    if ($spec_opt !== false)
        $opt = array('order'=>array('description'), 'spec_option' => $spec_opt, 'spec_id' => ALL_NUMERIC);
    $sql = "SELECT area_code, description, inactive FROM ".TB_PREF."areas";
    return combo_input($name, $selected_id, $sql, 'area_code', 'description', $opt);
}

and the lines in reporting/includes/reports_classes.inc:

                case 'AREAS':
                    return sales_areas_list($name);

should be changed to:

                case 'AREAS':
                    return sales_areas_list($name, null, _("No Sales Area Filter"));

and the string added to the empty.po for translations.

The "AREAS" is used only in the rep103.php as of now.
The "SALESTYPES" is used only in rep104.php and will need similar changes.

Go to forum: Reporting

3,227 Reply by apmuthu

(4 replies, posted in Setup)

If there is any specific synch needed post requirements here with:
1. FA version, platformand Chart used
2. Target Application and version used
3. Whether DBs are on same server
4. Sample transaction in FA with tables / fields affected (before and after sqls)
5. Same transaction's relevant tables / fields in target DB (before and after sqls)

Go to forum: Setup

3,228 Reply by apmuthu

(3 replies, posted in Accounts Payable)

Service Invoices for appropriate days credit values can be created for the appropriate target dates.
A Quick Entry for corresponding credit as discount for the actual invoice to show the current payment can be passed as well.

Main Order / Invoice Items Portion:
Today:
Sales Cr 1000
Client Dr   300 (30% on order / invoice)
Dummy Discount Dr 700

On first payment:
Client Cr 300
Cash/Bank 300

On Expected Date:
Dummy Discount Cr 300
Client Dr 300 (30% on delivery)

On second payment:
Client Cr 300
Cash/Bank 300

90 days after delivery:
Dummy Discount Cr 400
Client Dr 400 (balance 40% settlement)

On final payment:
Client Cr 400
Cash/Bank 400



This way at anytime, the Dummy Discount Account will always show what needs to be got from the client after a later date.

Go to forum: Accounts Payable

3,229 Reply by apmuthu

(2 replies, posted in Announcements)

Ms Chitra has taken over the task of creating further tutorials in FA for IITB's Spoken-Tutorial.org.

Go to forum: Announcements

3,230 Reply by apmuthu

(3 replies, posted in Accounts Payable)

All the said terms can be placed together as a single term in FA and the actual can be done on local discretion.

Go to forum: Accounts Payable

3,231 Reply by apmuthu

(26 replies, posted in FA Modifications)

Add the necessary fields values into the function add_sales_order() in sales/includes/db/sales_order_db.inc.

Go to forum: FA Modifications

3,232 Reply by apmuthu

(2 replies, posted in Announcements)

Study the Wiki on Taxes setup discussed in the forums several times as well.
The reporting for taxes both summary and detailed are quite generic in nature and covers most aspects generally needed. Both VAT and GSt and Tax exempt are supported.

https://frontaccounting.com/fawiki/index.php?n=Help.TaxTypes
https://frontaccounting.com/fawiki/index.php?n=Help.TaxGroups
https://frontaccounting.com/fawiki/index.php?n=Help.ItemTaxTypes

Go to forum: Announcements

3,233 Reply by apmuthu

(11 replies, posted in Items and Inventory)

@joe: any ideas?

Would entering the fuel bills by "journal voucher / quick entry" to the appropriate state (or state group) fuel expense account solve your issue?

Go to forum: Items and Inventory

3,234 Reply by apmuthu

(1 replies, posted in Banking and General Ledger)

Please make sure that you are using the latest stable FA version as your issues may have been resolved since the official release.

Line 218 of admin/void_transaction.php throws up this error when the exist_transaction() function (also in the same file) tested in the immediate if above it returns false.

This happens when the function get_voided_entry() (defined in admin/db/voiding_db.inc) returns a valid result (1 or more rows).

This latter function extracts:

SELECT * FROM voided WHERE type=$type AND id=$type_no;

This ensures that the said entry was not voided earlier.

Therefore make sure that you have not attempted to void the same entry more than once.

Additionally, for the said error to crop up, as you are voiding a Bank Deposit entry, the function exists_bank_trans() (defined in gl/includes/db/gl_db_bank_trans.inc) must return false, that is that if there was no such entry available.

The sql executed here is:

SELECT trans_no FROM bank_trans WHERE type=$type AND trans_no=$type_no;

There will be such errors if there is a primary key violation in uniquely identifying such transactions....
Also note that the table bank_trans has NULL-able fields type and trans_no and if they have null values in some of their records, it may cause issues.
@joe: please check - should those fields be NOT NULL for best practices or are NULL values possible in FA for these fields?

Go to forum: Banking and General Ledger

3,235 Reply by apmuthu

(25 replies, posted in Reporting)

The logs are available as "history" in the appropriate files' github file page. You can "pull" the project into your local Git Repo and track changes (TortoiseGIT for windows, etc).

Go to forum: Reporting

3,236 Reply by apmuthu

(25 replies, posted in Reporting)

In @dz's post no. 6 in this thread, please correct the function invocation "zone_cells" to be "zone_list_cells" to match the "function zone_row" definition above it.

Alternatively, an extra parameter with a default null value could have been placed in the existing areas functions itself to avoid another set of functions just for the default "No Sales Area Filter" option.

Also, compare your "rep102.php" with the current master file as it has been corrected in 4 places that does not reflect in your post - you may be using a dated version. See lines 44 and 49 to 51 in the said file for changes.

Go to forum: Reporting

3,237 Topic by apmuthu

(0 replies, posted in Report Bugs here)

The FrontAccounting v2.3.25's webroot folder's files were passed through the RIPS Scanner and the attached results were obtained on it's vulnerability. Most if not all are false positives. The $_POST and $_GET variables are washed before usage though they remain in the same variable name causing such scanners to spout such results.

vulnerable example code:

1: print ("Hello "  .  $_GET["name"]); 

proof of concept for execution:

/index.php?name=<script>alert(1)</script>

patch:

Encode all user tainted data with PHP buildin functions before embedding the data into the output. Make sure to set the parameter ENT_QUOTES to avoid an eventhandler injections to existing HTML attributes and specify the correct charset.

1: print ("Hello "  .  htmlentities($_GET["name"],  ENT_QUOTES,  "utf-8");

Go to forum: Report Bugs here

3,238 Reply by apmuthu

(12 replies, posted in Report Bugs here)

Thanks @joe: Stands committed in FA 2.3 and FA 2.4.

Go to forum: Report Bugs here

3,239 Reply by apmuthu

(25 replies, posted in Reporting)

There is no zone code in entire FA even in way back beyond 2014. There is also no file called includes/ui/ui_list.inc but there is a file called includes/ui/ui_lists.inc. It was some custom code implemented / suggested by @dz.

Go to forum: Reporting

3,240 Reply by apmuthu

(1 replies, posted in Manufactoring)

There should be a relationship between input items and output items like:
2 Ltrs of Item 1 is mixed with 3 Kgs of Item 2 to get output of 4 Meters of Item 3 (Item Type: Manufactured Item) packed in 1 Meter packs of Item 4. Make sure a Work Centre exists for Manufacturing. Add Components to the Bill of Materials.

Go to forum: Manufactoring

3,241 Reply by apmuthu

(12 replies, posted in Report Bugs here)

Try to replace line 41 (in both FA 2.3 and 2.4):

SUM(line.quantity) as quantity

with

SUM(IF(line.debtor_trans_type = ".ST_CUSTCREDIT.", -line.quantity, line.quantity)) as quantity

Go to forum: Report Bugs here

3,242 Topic by apmuthu

(2 replies, posted in Announcements)

IIT Bombay with funding from the Govt of India has prepared a few tutorials for FrontAccounting and they are being used to teach B.Com students in Indian Universities. The links are in the wiki. It will take a while for more tutes from them as the lead tutorial contributor (Sheetal Prabhu) for their FA project has sadly left in Sep 2016.

Each Tutorial is around 10 minutes long.

Professor Kannan Moudgalya of IITB heads the Spoken-Tutorial.org team and is ably assisted by Nancy Varkey, the Senior Project Manager there.

Go to forum: Announcements

3,243 Reply by apmuthu

(5 replies, posted in Accounts Receivable)

Normal usage:
Create separate roles for branch users and assign the branch users accordingly.
Assume that only sales returns and sales are allowed in each branch user role.
Sales invoices will all be sequential.
Restriction of invoicing of goods to just the specific branch location not possible.

Disjoint operation:
Headquarters FA has only branches as customers.
Each branch has their own FA instance with the Headquarters as the sole vendor.
Each branch will have their set of customers.
Each customer will have a different Customer ID in each branch it buys from.
No consolidation of Customer Credit across branches will devolve.
Multi branch customers can be placed in the Headquarters FA and billed from there and replenished for deliveries from the HQ to the branches.

Go to forum: Accounts Receivable

3,244 Reply by apmuthu

(2 replies, posted in Items and Inventory)

Wait till April 1st, 2017. Excise will be merged into GST (if the parliament is allowed to function)....

In the meanwhile, Arrange for an invoice type that bills a dummy client.... and gets return of goods when transferred to another client / location. Sometimes, Excise can be treated as a commission agent (Sales Person) as well.....

Alternatively treat it as warehouse transfers and keep the excise offline.

Treating the goods as a manufactured item and the final destination as the real client, Excise can become a Manufacturing service cost with reversibility on manufacture and return to warehouse.

Go to forum: Items and Inventory

3,245 Reply by apmuthu

(11 replies, posted in Items and Inventory)

Treat Fuel as an Inventory Item. Enter a large stock quantity as Opening Balance. Reset to large stock quantity when it nears exhaustion.

Alternatively, use Tags / Dimensions for Fuel purchases.

Go to forum: Items and Inventory

3,246 Reply by apmuthu

(1 replies, posted in Report Bugs here)

@joe: Thanks for the commit.

Go to forum: Report Bugs here

3,247 Reply by apmuthu

(12 replies, posted in Report Bugs here)

Quickfix @joe. Thanks.

Line 53 in the new file:

        AND (line.debtor_trans_type = ".ST_SALESINVOICE." OR line.debtor_trans_type = ".ST_CUSTCREDIT.")";

may also be

        AND (line.debtor_trans_type IN (".ST_SALESINVOICE.", ".ST_CUSTCREDIT."))";

This way, when more transaction types needs to be added, it would be easily readable.

Please commit it.

Go to forum: Report Bugs here

3,248 Topic by apmuthu

(1 replies, posted in Report Bugs here)

FA 2.4RC1 bug 3667 has been fixed here.
It has been backported to FA 2.3.25+ in my repo's FAMods.

@joe: Kindly backport this to the official stable repo as well.

Go to forum: Report Bugs here

3,249 Reply by apmuthu

(4 replies, posted in Modules Add-on's)

SMS gateways are commercial devices and / or service URLs from your mobile service provider or bulk SMS provider. Most such services 'have' / 'allow to format' a mobile number like an email address for sending SMS. Use such email ids in FrontAccounting for the customer / supplier.

No change is needed to FrontAccounting.

Go to forum: Modules Add-on's

3,250 Reply by apmuthu

(12 replies, posted in Report Bugs here)

@joe: Boxygen's claim needs to be checked for reporting consistency.

Go to forum: Report Bugs here