Search options (Page 20 of 47)

There is a bug in it. These radio buttons has name protect . But in db_import  function it was called check_value('protected');

So it should be changed to work properly.

@mark0300 while importing database it connects to replace the entire database
If you want to retain your current login and security roles these two options will help you to get it.

@joe  update the backups.php file to fix this issue.

Looks like this is a strange issue. I feel the below code is missing the cust allocation.

  while ($row = db_fetch($result))
    {
        if ($row['type'] == ST_SALESINVOICE)
        {
            $deliveries = get_sales_parent_numbers($row['type'], $row['trans_no']);
            foreach ($deliveries as $delivery)
            {
                $sql = "DELETE FROM ".TB_PREF."debtor_trans_details WHERE debtor_trans_no = $delivery AND debtor_trans_type = ".ST_CUSTDELIVERY;
                db_query($sql, "Could not delete debtor trans details");
                $sql = "DELETE FROM ".TB_PREF."debtor_trans WHERE trans_no = $delivery AND type = ".ST_CUSTDELIVERY;
                db_query($sql, "Could not delete debtor trans");
                delete_attachments_and_comments(ST_CUSTDELIVERY, $delivery);
            }        
        }    
        $sql = "DELETE FROM ".TB_PREF."cust_allocations WHERE trans_no_from = {$row['trans_no']} AND trans_type_from = {$row['type']}";
        db_query($sql, "Could not delete cust allocations");
.
.
.
}

And may be it should be like this

while ($row = db_fetch($result))
    {
        if ($row['type'] == ST_SALESINVOICE)
        {
            $deliveries = get_sales_parent_numbers($row['type'], $row['trans_no']);
            foreach ($deliveries as $delivery)
            {
                $sql = "DELETE FROM ".TB_PREF."debtor_trans_details WHERE debtor_trans_no = $delivery AND debtor_trans_type = ".ST_CUSTDELIVERY;
                db_query($sql, "Could not delete debtor trans details");
                $sql = "DELETE FROM ".TB_PREF."debtor_trans WHERE trans_no = $delivery AND type = ".ST_CUSTDELIVERY;
                db_query($sql, "Could not delete debtor trans");
                delete_attachments_and_comments(ST_CUSTDELIVERY, $delivery);
            }        
                      $sql = "DELETE FROM ".TB_PREF."cust_allocations WHERE trans_no_to = {$row['trans_no']} AND trans_type_to = {$row['type']}";  // newly added 
        db_query($sql, "Could not delete cust allocations");  // newly added. 
        }    
        $sql = "DELETE FROM ".TB_PREF."cust_allocations WHERE trans_no_from = {$row['trans_no']} AND trans_type_from = {$row['type']}";
        db_query($sql, "Could not delete cust allocations");
}

I have added two more lines added newly to collect the respective invoice allocation entires delete. Like the same for supplier allocations.

If it helps feedback us to fix it in core.

Dude looks like the issue is not in program. I have tested in both versions. It worked fine for me.  Can you record a video with inspect element and show us the js errors if possible.

Did you install any other modules and themes?.

Is it hosted in remote server or localhost ?

Let's try the issue in next level. In case we can predict the issue.

@kevinleebr  Looks like the fiscal year was set to 2019. If you change the invoice date or delivery date to 2019 it might work.

Still if you have problem you can enable debugging mode and update us the issue screenshot or something with error log. We can help you very well.

@anoopmb, you are right, its useful module here. But where the company has less people and try that. its double work for them to do it. So the first solution, we applied there is for the small companies or those who handles FA functions totally.

@joe , great to hear it.  How about cron job connectivity. ?

Shall we make one to make it automatically on its recurrent day.

It's a tricky feature to add both language for a single item. We must add one more name field to store it in stock master table.

And than you can customize the sales and purchase invoice to show the second name field in it .

But for rtl,  it's a bit complex to make it both in same invoice.

How ever there is a problem with payment of next year for previous year invoice.

Let's take his example. He issued several invoices  at the end of last year and collected the payment in next year.  Which means the system needs to make one journal entry for a customer at least to record the invoice balances as opening balance and that should be allocated in the next year.

That's good idea. But you have to know which invoices are allocated. With that it's good for you to reallocate it.  Hope you got good solution. Once you implement it successfully or issues. Just drop your feedbacks and hints

I am giving the way of my solution. Because I tried one functionality before for the users who are coming to FA from other software's.  Like they wanted to keep the journal of previous customer opening balances as journal entry. And when the customer make payment record the payment against that journal entries.

So the solution is to separate the invoices which are paid on 2015 and invoiced in 2014.  And than we have to summarise the balance of it and make one journal entry.  And change the allocation of invoices to that newly created journal entry to take effect. Let's say if you have 50 invoices in 2014 and paid in 2015. All these invoices needs to be removed and created one journal entry with all its balance.  After that we have to reallocate the payments against that journal entry.  Like this. We can remove all the other entries like stock balance in stock moves,

You have to remove related entries in
audit trail
Bank trans
Comments,
Cust allocations
Debtor trans
Debtor trans details
Gl trans
Journal
Grn_items, batch
Purch_orders
Purch_order_details
Sales orders
Sales orders details
Stock moves
Supp trans
Supp trans details
Trans tax details
Wo orders,

And other tables if anything affecting the yearly data. 
May be If you see tother

@detkenn - not everyone is expert in accounting.  Sometimes a learning accountant,  like new joiny or new person, might make mistake in account selection. And sometimes by mistake. We might choose wrong account and input it by accidently, in this cases the careless mistake can be highlighted. Most of accounting software's  also have this feature to check before make entries.

Hope this feature would be helpful for others.

Your second option is fine I feel. Because sometimes. People may make reverse entries once they made mistake in another form. So I think the warning would be fine. At the same time even if they post it with warning. It should work and submit the journal entry.

Here is a screenshot for reference what i talked. And code i modified in gl_journal.php

// New function to check it 
function check_account_selection($code, $amount){
    $sql = "SELECT ms.*, cl.class_name, cl.ctype FROM ".TB_PREF."chart_master AS ms LEFT JOIN ".TB_PREF."chart_types AS tp ON ms.account_type= tp.id LEFT JOIN ".TB_PREF."chart_class AS cl ON cl.cid = tp.class_id WHERE account_code= ".db_escape($code);
    $res = db_query($sql, "Cant get the chart class selection");
    if(db_num_rows($res) == 1 ){
        if($row = db_fetch($res)){
            if($row['ctype'] == CL_EXPENSE && $amount > 0)
                display_warning(_("You are entered the Expense under the debit side"));
            if($row['ctype'] == CL_ASSETS  && $amount < 0 )
                display_warning(_("You are entered the Asset in credit side"));
        }
    }

}
function handle_new_item()
{
    if (!check_item_data())
        return;


    if (input_num('AmountDebit') > 0)
        $amount = input_num('AmountDebit');
    else
        $amount = -input_num('AmountCredit');
    
    check_account_selection(get_post('code_id'), $amount);  // This is new line in existing code
    

    $_SESSION['journal_items']->add_gl_item($_POST['code_id'], $_POST['dimension_id'],
        $_POST['dimension2_id'], $amount, $_POST['LineMemo'], '', get_post('person_id'));
      unset($_SESSION['journal_items']->tax_info);
    line_start_focus();
}

abd for updating of exiting entry.

 
function handle_update_item()
{
    if($_POST['UpdateItem'] != "" && check_item_data())
    {
        if (input_num('AmountDebit') > 0)
            $amount = input_num('AmountDebit');
        else
            $amount = -input_num('AmountCredit');


        check_account_selection(get_post('code_id'), $amount); // This is new line in existing code


        $_SESSION['journal_items']->update_gl_item($_POST['Index'], $_POST['code_id'], 
            $_POST['dimension_id'], $_POST['dimension2_id'], $amount, $_POST['LineMemo'], '', get_post('person_id'));
        unset($_SESSION['journal_items']->tax_info);
        line_start_focus();
    }
}