Hello,
Use your petty cash account. This should be established as a bank account. Then you can use this at both selling and purchasing.
Even if it is called a bank account, it is your own cash register account.
Joe
It's much more fun, when you can discuss your problems with others...
You are not logged in. Please login or register.
FrontAccounting forum → Posts by joe
Hello,
Use your petty cash account. This should be established as a bank account. Then you can use this at both selling and purchasing.
Even if it is called a bank account, it is your own cash register account.
Joe
We are removing ourselves from the original topic.
What we could discuss in another topic is if we shouldd prevent entering non digits in the so called Numeric accounts.
F.i. Only digits 0-9.
Let us close this topic now.
Joe
Please, think about this as an accountant. The COA is presented as
0200
02001
1000
1001
10010
1002
2000
200011
3000
This is a normal presentation, where 5 or more digits are treated as subaccounts.
Can you see the disaster if we would sort these as integers?
This is the way COAs are setup, despite using digits or a combination of digits and characters.
No accountants are confused about this!
Joe
In FA there are no cast to integer for accounts. So you can safely use the default account setting
It would be rather inconvenient to treat an account number as an integer.
You are right. The account settings are either Numeric (which mean that only numeric characters are allowed to enter) =0, alphanumeric, where you can enter alpha characters also (Aa to Zz) =1 and last the alpha characters can only be uppercase = 2.
Sorry, I meant this url.
Joe
Yes, but they are alphanumeric (varchar in database) only allowing 0-9 numeric character values. It will also allow a point sign.
So therefore they can start with a zero character.
Look at the demo.frontaccounting.com, Banking and General Ledger. There are several accounts starting with zero, and the are presented in the Balance Sheet.
Joe
The account are per default set to be alphanumeric. So there are absolutely no problem using accounts with leading zeroes.
Certain EU countries uses leading zeroes for alternative reporting. I guess some French COA are using this.
Never mind it is probably not that necessary to use leading zero accounts.
Joe
@apmuthu
Just curious. Why can't the accounts start with zero, if they are alphanumeric? I see no problems in that.
Joe
Ok, I will ask Janusz again to update the repo.
Joe
Please have a look in Company Setup, Search Customer List. Unmark this if it is marked.
Joe
Today we passed 200 000 downloads on Sourceforge. These are the most popular countries:
1. United States 21,616
2. Indonesia 18,699
3. India 15,366
4. Netherlands 7,521
5. Pakistan 5,115
6. United Kingdom 4,272
7. Bangladesh 3,811
8. Canada 3,724
9. Malaysia 3,490
10. Philippines 3,466
11. Germany 3,312
12. Australia 3,150
13. China 3,030
14. Kenya 2,899
15. South Africa 2,896
16. Egypt 2,467
17. Nigeria 2,208
18. United Arab Emirates 1,964
19. Brazil 1,958
20. Saudi Arabia 1,915
21. France 1,905
22. Singapore 1,876
23. Spain 1,790
24. Mexico 1,594
25. Hong Kong 1,544
Thank you guys for detecting this presentation bug. The file has been fixed and sent to Janusz, that will update the package.
/Joe
@Petros
Thank you for your persistent testing . Please download and replace from the above links again (they have been updated):
/manufacturing/includes/db/work_order_produce_items_db.inc
/manufacturing/includes/db/work_orders_db.inc.
I guess this is as long as I can go with the fixing. It is very complex routines. It also handles ev. negative stock if set etc. Many things to take care of. Digging deaper will require assistance from a skilled programmer that are also familiar with the Advanced Assembly.
/Joe
Hello,
Here are the new files. They have been committed to repo. replace on your server.
/manufacturing/work_order_costs.php
/manufacturing/includes/db/work_order_produce_items_db.inc
/manufacturing/includes/db/work_orders_db.inc
/manufacturing/includes/db/work_orders_quick_db.inc
@Petros
Remarks to your readme.txt file:
2.a. The issue of 10 'input 1' should NOT be devided by any factor to add the material cost per item price. This is the issue for 1 'Output 1' item.
The Worth of the 10 'input 1' was $41.40 (not $44.10).
/Joe
@Petros,
Thanks for the test material. It was nice to make the tests from here.
I have fixed the issues, but want to do some further tests Before releasing the files.
I will be back later.
/Joe
@Petros.
I cannot reproduce your assembly errors.
Will you please give me a detailled example with amounts etc. If there still are errors, I will be extremely glad to fix these,
Joe
@Petros,
It can be a Little tricky to test this on an existing assembled item.
When Selling the item (delivery) it takes the Average Standard Cost to credit the Stock of Finished Goods (FG). Material, Labour and Overhead COSTs.This is done correctly.
The Item Valuation Reports can be a Little tricky also to follow.
There is a flag in config.php, called $use_costed_values, that usually is set to 0. Check that this is so. Then the reports are based on the overall average standard cost values. IF set to 1 it will use the average material COSTs over time. Maybe more correct related to the GL reports.
When testing, please start on a fresh Advanced Assembly Product, because we will get false tests otherwise.
Thanks for participating is this valuable test.
/Joe
Hello again,
The Standard Costs are now updated correctly when producing an Advanced Assembly.
You should now be able to run the valuation reports correctly.
Please download the following files and replace.
/manufacturing/includes/db/work_order_produce_items_db.inc
/manufacturing/includes/db/work_orders_quick_db.inc
Unfortunately I am not able to fix the stand alone button for 'Close' at the moment. The algorithms are now dependent of the production.
Your stock will not get updated only with adding Costs and issues. Only during the production the standard Costs are updated.
This is the reason why it is difficult to just enter additional Costs after all the production is done.
I am sorry for that, but maybe something shows up during the 2.4 release. Then of course we will fix this.
/Joe
Yes, I know where the problem is. I need some additional time to correct this.
Joe
Hello again,
@Petros
The number 1. issue has now been fixed. The following files can be downloaded from the Git repository and replaced on your server:
/manufacturing/includes/db(work_order_issues_db.inc
/manufacturing/includes/db/work_order_produce_items_db.inc
/manufacturing/includes/db/work_orders_db.inc
/manufacturing/includes/db/work_orders_quick_db.inc
I will continue to look into item number 2.
/Joe
1. Ok, I will see what I can do. Should be pretty easy.
2. This is a little more tricky. Maybe we could replace the buttons to only say 'process' and 'close'. Then you will always need to press the 'close' button to close the advanced assembly. I am not sure what is best here. Maybe a third option called 'close' and don't close the 'process' even if it is finished.
Joe
@petros
If you will be so kind to Point me out the two lines (file and position), I will be delighted to change this in the stable release.
/Joe
I guess that if the number of ordered items have been produced, the Wo is automatically closed.
If you produce and close the Wo it is closed even if the manufacturing is not finished.
Joe
Okay, I will look into it.
Joe
Release 2.3.24 stable has been fixed and the file is commited.
You can download the file /manufacturing/includes/db/work_orders_db.inc here.
You should replace the file on your server setup.
/Joe
FrontAccounting forum → Posts by joe
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 4 official extensions. Copyright © 2003–2009 PunBB.