Please remember that the suppliers descriptions are only put on the documents to him.

All other forms internally will use our own description.

Joe

2

(9 replies, posted in Report Bugs here)

Some of the compatibility problems have now been fixed and committed to 2.4.8 stable repo.

The following compatibility bugs still remains for fixing:

Function get_magic_quotes_gpc() is deprecated in file: C:\wamp3\www\account24\includes\session.inc at line 315

implode(): Passing glue string after array is deprecated. Swap the parameters in file: C:\wamp3\www\account24\includes\ui\ui_lists.inc at line 161

Trying to access array offset on value of type null in file: C:\wamp3\www\account24\reporting\includes\tcpdf.php at line 1127

chr() expects parameter 1 to be int, string given in file: C:\wamp3\www\account24\reporting\includes\tcpdf.php at line 3525

Joe

3

(9 replies, posted in Report Bugs here)

This is good reporting. Let us continue to use this thread for new php version problems.

I will occasionally try to fix the problems with backward compatibility.

Joe

Hello,

The Salesmen implementation is very basic with percent and a breakpoint for another percent.
Please tell me if you need more fields for calculations.
That could be implemented in 2.5.
Otherwise use the dimension for better reports per artisan/salesman.

Joe

5

(5 replies, posted in Announcements)

I was awaiting some item stock improvements from Janusz before moving forwards. But he seems very overloaded with daily work.

I guess we should also consider FIFO option in stock handling. So we need a field for this in the stock moves table. And of course a flag in the company setup for using this.

In my opinion we should try to assemble what we have decided so far. I will make a list and try to put developers on the various tasks.

Joe

This has now been fixed with an extra checkbox, 'Group totals only'.

Committed to 2.4.8 stable. The fixed file can be downloaded here.

/joe

Hello again,

I have been thinking a bit more about this. Even if I don't like it, I will try to implement it with a checkbox. So stay tuned.

/Joe

Hello Guys,

Is this really needed? I think the main reason for a Trial Balance is for investigating all the accounts (not the totals).
You get the totals summarized as a feature already now.

If you need the Group Totals only, you could as well use the Balance Sheet and Profit and Loss Drill Downs.

Are there any interest in this change by the Senior Members?

/Joe

@apmuthu,

All done. Committed to repo, 2.4.8.

The fixed Invoice Document, rep107.php, can be downloaded here.

/Joe

Hello Guys,

This has now been committed to stable 2.4.8 repo. A new Company flag, Use Long Description on Invoices, has been created in the left pane at the bottom.
If this checkbox is set, the Long Item Description lines will be printed as well on Sales Invoices.

The following 3 files were changed and can be downloaded here:

https://sourceforge.net/p/frontaccounti … rences.php
https://sourceforge.net/p/frontaccounti … ils_db.inc
https://sourceforge.net/p/frontaccounti … rep107.php.

@apmuthu

Please update the Wiki with these important features. Thanks in advance.

/Joe

/apmuthu: Done.

This has now been fixed. Committed to Stable repo 2.4.8.

The fixed file can be downloaded here. Please replace.

Thanks for reporting this.

/Joe

Will have a look at this.

Joe

I will have a look at this.

Joe

Yes, really nice indeed. Maybe a good idea to put this link on the Dimensions Wiki page, if it is ok with you, @flpages?
If so, will you, @apmuthu, put the link on the Dimensions Wiki page?

Joe

15

(3 replies, posted in Setup)

Hello,

This issue has now been fixed. Thanks @kvvaradha for reporting this. Committed to stable Repo.

The fixed file can be downloaded here.

Joe

Hello,

This topic has now been fixed and committed to stable repo. To get it working you must download these two files from the repo:

company_preferences.php and create_recurrent_invoices.php.

In 'Company Setup' there is a new check box on the left hand side. Default value unchecked. To use dimensions on recurrent invoices just check the box and update.

@kvvaradha
Let us first test this so we are sure it works. I have already tested, but it need test from others too.

Joe

@kvvaradha.
I found the solution myself. It was quite simple. I will implement it as a company setup checkbox, with the existing behaviour as default.

Just stay put an hour or two.

/Joe

@kvvaradha.
No, No dimensions are created for the Sales Order. And no dimensions on the item lines for Sales Order either. These things make the complexity.
Let us wait for Janusz's comments.

Joe

Hello,

I have been looking at this and is not that easy to implement. Janusz has done some modifications here and I will ask him to look into the topic.

/Joe

20

(21 replies, posted in Setup)

The allocations has been revised and should now work. Committed to stable repo. The fixed file can be downloaded here.

Joe

21

(21 replies, posted in Setup)

Oh yes, I see. The alloc field got stamped in the next year and when the invoice was not allocated by end of last year.
I will have to look at the allocation routines instead. Thanks.

Joe

22

(21 replies, posted in Setup)

Hello again.

I have now went through the deleting fiscal year procedure. I have found no problems here.
Here is a list over what happens when processing deleting of a fiscal year:

Delete Fiscalyear

1. Backup is done
2. All sales orders and details, up to last date, that are fully delivered are removed. Attachments are removed.
3. All purchase orders and details, up to last date, that are fully received are removed. Attachments are removed.
4. All GRN receivals, up to last date, are removed.
5. All debtor trans and details, up to last date, that are fully allocated are removed. Attachments are removed.
6. All cust allocations, up to last date, are removed.
7. All supp trans and details, up to last date, that are fully allocated are removed. Attachments are removed.
8. All supp allocations, up to last date, are removed.
9. All workorders, up to last date, and closed.
   a. All workorder issues are removed. Attachments are removed.
   b. All workorder manufacture are removed. 
   c. All workorder requirements are removed.
   d. Workorders removed. Attachments are removed.
10. All stock moves, up to last date, are removed and converted to a closing stock move.
11. All voided items, up to last date, are removed.
12. All trans tax details, up to last date, are removed.
13. All exchange rater, up to last date, are removed.
14. All cust and supp sub gl transactions are retrieved by account, removed and an end transaction are inserted. 
15. All bank trans, up to last date, are removed and converted to a closing balance trans.
16. All ausit trail, up to last date, are removed.
17. All comments, up to last date, are removed.
18. Finally the fiscalyear is removed.

Joe

I understand this discussion.
The reason for implementing the routines with recursivity is that the assembled items can have a BOM with another assembled item and so on.

Joe

You can also use the account types to decide which accounts shall be summarized in a special way.
I guess that there are some info in the Wiki about this.

Joe

25

(21 replies, posted in Setup)

This is a difficult task. I remember writing these routines years back and we really tried to get it all at that time.
I will try to look into it asap.

Joe