Search options (Page 177 of 247)

The code appears incomplete since the "incen_fine" form variable is not defined (did you mean to replace the 'mahamai' with a single +Incentive / -Fine variable).

Any reason why you would want to comment out the $taxes and $tax_total assignments and prevent it forming part of the $display_total?

I would expect the last part of the function display_po_items() to be:

    start_row();
    label_cell(_("Incentive / -Fine"), "colspan=$colspan align=right");
    small_amount_cells(null, 'incen_fine', price_format(get_post('incen_fine',0)));
    label_cell('', 'colspan=2');
    end_row();

//    $display_sub_total = price_format($total + input_num('incen_fine'));

//    label_row(_("Sub-total"), $display_sub_total, "colspan=$colspan align=right","align=right", 2);

    $taxes = $order->get_taxes(input_num('freight_cost'));
    
    $tax_total = display_edit_tax_items($taxes, $colspan, $order->tax_included, 2, $order->trans_type==ST_SUPPINVOICE);

    $display_total = price_format($total + input_num('freight_cost') + $tax_total + input_num('incen_fine'));

    start_row();
    label_cells(_("Amount Total"), $display_total, "colspan=$colspan align='right'","align='right'");
    $order->order_no ? submit_cells('update', _("Update"), "colspan=2 align='center'", _("Refresh"), true)
        : label_cell('', "colspan=2");
    end_row();

    end_table(1);
    div_end();
}

But where does the 'incen_fine' get stored and how?

When done, don't forget to submit it here and to the project to assist others.

Hope this suffices:

https://frontaccounting.com/fawiki/inde … nkAccounts

@ckrosco: In your first post here you stated

Does this mean that you entered the exchange rate manually or got it from the FA exchg rate provider by manually clicking the get rate button?

It would be nice if you provided the changed files (or actual workflow menu click sequence) so that it may be included in the next version natively.

Provide the changed code to test.

If the incentive is calculatable from the quantity, then a enable/disable flag (0/1) is sufficient for it and an amount variable for delays if it is variable with no dependancy will suffice. Better to have a quick entry for those transactions where these issues arise with no fields necessary in the tables. The fields can be avoided altogether if quick entries are used except that manual computation will be necessary.

Try to uncheck the auto-update, save, tick the auto-update, save and see what happens. Actually, there should be only one update each day for each currency.

From the comments on line 297 in includes/ui/ui_view.inc:
"autoupdate means use remote service & store exrate on first transaction."

Hence there is no cron job used here!

Lines 36 to 41 in gl/manage/bank_accounts.php:

    if ($Mode=='ADD_ITEM' && (gl_account_in_bank_accounts(get_post('account_code')) 
            || key_in_foreign_table(get_post('account_code'), 'gl_trans', 'account'))) {
        $input_error = 1;
        display_error(_("The GL account selected is already in use. Select another GL account."));
        set_focus('account_code');
    }

Line 39 above can have the error message modified as @joe stated or the if statement modified to be more tolerant like:

    if ($Mode=='ADD_ITEM' && (gl_account_in_bank_accounts(get_post('account_code')) )) {
        $input_error = 1;
        display_error(_("The GL account selected is already in use. Select another GL account."));
        set_focus('account_code');
    }

Provide an example of the 2 fields envisaged - are they different for each GRN or only their values are different for each GRN or they have some relationship (calculatable formula) with existing constants / field values?

You might want to experiment with manually entered values into the sys_prefs table and / or use special charge / service items in the GRN.

Checkout the screenshot in the wiki and make a mockup of what you want and link it in here.

Where is the Polish version hosted? Any screenshots?