Search options (Page 63 of 246)

Reimbursements can be treated as cash advances to original purchasers and then a payment allocation and settlement to them. Otherwise, a normal cash purchase can be entered and cash given as reimbursement and recorded in the memo accordingly. The latter will not track supplier.

When one Vendor's payment needs to go to another vendor upon suitable authorisation, it is best to create a credit/debit note pair for each vendor and then make the allocation as normally done.

This happens when there are no transactions in function get_customer_trans_version() in sales/includes/db/cust_trans_db.inc. The construct at lines 37-43:

    $sql= 'SELECT trans_no, version FROM '.TB_PREF. 'debtor_trans
            WHERE type='.db_escape($type).' AND (';

    foreach ($trans_no as $key=>$trans)
        $trans_no[$key] =     'trans_no='.db_escape($trans_no[$key]);

    $sql .= implode(' OR ', $trans_no) . ')';

can be modified to be

    $sql= 'SELECT trans_no, version FROM '.TB_PREF. 'debtor_trans
            WHERE type='.db_escape($type).' AND trans_no IN ('.implode(',', db_escape($trans_no)).')';

Thanks. Their free plan provides for:

FA is multi tenant. You can choose to hos each company in a separate database or use different table prefixes and place them in the same table. Each "tenant" is then chosen in the login screen. The FA code is just a single instance but each company has it's own folder for it's data files.

If you create User A in both companies with same / different passwords, FA will accept that as well, since the users table is different for each company (with either different table prefixes in the same database oand/or different databases).

@joe: nice fix?

You can use my unofficial version for PHP 5.3.

If you use the sql/en_US-new.sql as your Chart of Accounts it will be without the dummy data.

@joe: should a flag be used or should it simulate the old functionality with the inclusion of the said code?

If you need to implement it this way, then the following should suffice as $qoh=0 for the first computation:

if ($qty > 0 && ($qoh != -$qty)) {
    if($qoh == 0 && $avg_cost != 0)
        $avg_cost = ($avg_cost + ($unit_cost*$qty_new)/$qty)/2;
    else
        $avg_cost = ($avg_cost*($qoh+$qty_delayed)+$unit_cost*$qty_new)/($qoh+$qty);
}

Hope the first computation too will remain a weighted average cost.

@joe: is this the desired design outcome?

The last version of CMS archived home page is of v12.1 / 2009. They still state that they are a Microsoft Silver Partner and the DB may still be MS SQL Server.

You may want to use the SlimAPI as a REST client to push batch info into FA.

The version of the REST API tested for FA 2.4.x is here.

Whilst the Denali version uses the MS SQL server, what database does the legacy version use?
Could not trace the old legacy version to study it.

You can run VMWare Player in your Win7+ workstations and run WinXP in a Virtual Machine in it where your legacy CMS client can run. That way, you will not need to change the software and the way you run your business.

Have you setup your Chart of Accounts in FA and tailored it to suit your existing one in the legacy CMS?
You will need to use the latest FA v2.4.4+ Git Master as it sorts out quite a bit of issues.

Perform one batch of one type of transaction with just one transaction in it and compare the before and after backups of the sql - you can then figure out how to frame the SQL statements to import a full batch.