401

(22 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

402

(22 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

403

(22 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

406

(22 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

All money is belonging to a bank account. Even small cash accounts. This is to keep it safe. When operating where money is included, you can better use the deposit or payment form.

Joe

As some of you guys mention, the Gl journal entries are for direct entries without any restrictions. And it should be so in My opinion.
Please use the more easy routines for transactions if you are unsure.

Joe

Hi, it is difficult to satisfy every aspect of tax handling. I think FA has a very good way of handling the taxes.
Maybe someone in the audience has a solution. Otherwise someone may write an extension.

Joe

Hello,

I will ask Janusz to do that.

Joe

Hello @kvvaradha and @poncho1234

I am trying to follow you guys in your wishes.
Let us try to focus on 2.5. Which fields do we need? I will put it on the developer site for 2.5.

Joe

@kvvaradha.
Sure, I also thought about a global config.php flag if the login was from theme, however for safety I think it is better going from existing login.php where all the tests code is executed here and only the layout would be called from theme if a login.inc file exists.

Joe

@kvvaradha
Actually I was doing some trial on login.inc file from the themes. The normal login.php checks if there is a login.inc file in the theme directory and if, this is called instead of the default login. It is prepared, but I thought it could wait to 2.5. To implement it in 2.5, I am waiting for some changing that Janusz want to do before we start implementing the 2.5 things. Unfortunately he is very occupied with his normal work at present.
In the example I did, I changed the login.php, and all the other helpers timeout etc. so it was easier to implement a theme login.
The trials works perfectly and it is safe.
The custom fields is also interesting for at least 2.5. And more.

/Joe

No, I don't have any suggestions at present. Please continue experimenting. Maybe some good ideas will show up.

Joe

@apmuthu, will you update the wiki, I am out of office right now.

/Joe

This seems to be the way to do it. Have just consulted Janusz about it. Awaiting his comment.

Joe

This has been put on the wish list for 2.5 a while ago. We are waiting for a merge of 2.5.

Joe

Yes, I agree with @kvvaradha.

Whenever you like to see a sales order view, the customer id is added to the parameter line. So we really don't need anything changed here.
Tell me if I have misunderstood the question.

/joe

Thanks, I will look into it.

Joe

In 2.4.7 we had to do something against sql injection and therefore we had to reduce the field to only enter 50 characters.
The length is defined as varchar(50) and after implementing the STRICT_ALl_TABLES no longer accepts overwriting of the 50 length.

The field will be changed to 255 chars in 2.5.

Joe

I had the same issue a week ago.

This was a bug in  a release of Chreome. This should be fixed in the latest update of Chrome..

Joe

422

(7 replies, posted in Installation)

Glad you solved it smile

Joe

423

(7 replies, posted in Installation)

You could set the variable $go_debug in config.php to 2 to trap any errors. There might be an explanation. I too remember that I had this problem once, but like you I have forgotten what caused the error.

Joe

424

(7 replies, posted in Installation)

Are you sure you have data for the fiscal year. If you are using the demo material, try to back one fiscal year.

/Joe

Hello again,

This feature is now implemented in Inventory Adjustments. An extra Column is showing Quantity On Hand (QOH) after the description.

The fix has been committed to 2.4.8 repo. The fixed file can be downloaded here.

@detkenn
If you want to add more, change something, please tell me. I appreciate it a lot.

/Joe