Search options (Page 1 of 2)

GL transactions at this stage are only created if you add additional costs on the work order or there are additional costs in the included item. The items are otherwise 'only' moved.

Admin

Well, this is a common problem working with currencies. The problems arise when multiplying and dividing the rates forth and back and with only 4 decimal places.
Most peiople don't see this as a major problem. The variances would be booked during allocations and payments. If you would like more accuracy, you should increase the decimal places in the exchange rates. Setup tab, Display Setup, Exchange Rates.

Admin

There seems to be a problem with joins in version 5.0.12 of MySQL. Look at this topic, https://frontaccounting.com/punbb/viewtopic.php?id=13
This SQL statement is inside the file
/manufacturing/includes/db/work_order_requirements_db.inc in a function called get_wo_requirements:

function get_wo_requirements($woid)
{
    $sql = "SELECT ".TB_PREF."wo_requirements.*, ".TB_PREF."stock_master.description,
        ".TB_PREF."stock_master.mb_flag, 
        ".TB_PREF."locations.location_name, 
        ".TB_PREF."workcentres.name AS WorkCentreDescription FROM 
        ".TB_PREF."wo_requirements, ".TB_PREF."locations, ".TB_PREF."workcentres INNER JOIN ".TB_PREF."stock_master ON 
        ".TB_PREF."wo_requirements.stock_id = ".TB_PREF."stock_master.stock_id 
        WHERE workorder_id=$woid
        AND ".TB_PREF."locations.loc_code = ".TB_PREF."wo_requirements.loc_code
        AND ".TB_PREF."workcentres.id=CAST(workcentre AS UNSIGNED)";    

    return db_query($sql, "The work order requirements could not be retrieved");    
}

Put parentheses around the FROM tables

....... FROM (".TB_PREF."wo_requirements, ".TB_PREF."locations, ".TB_PREF."workcentres) 
INNER JOIN ".TB_PREF."stock_master ON .......

Please report if this helps!
New edited files with JOIN's from multiple tables will be put on the CVS on Sourceforge.

/includes/db/manufacturing_db.inc
/manufacturing/includes/db/work_order_requirements_db.inc

Admin

thansk dkshukla ,

for your contribution. It is certainly of great help for our future developemnt. We like when peiope are creative and this will, of cource, be in our future plans.

Admin

thanks for pointing that out!

Admin

Hello,

It is in the Supplier and Purchasing Reports (the middle section of the Purchase page). Then it is the last report in this class. Happy reporting

Admin

Hello,
Simply speaking it is just a way of keeping track of various departments, cost centres, projects inside the company.
You can have 2 levels, e.g. level 1, department, level-2, cost-centre.
When you create the dimension you decide if it should be of level 1 or level 2.
You can by this keep track of cost centres inside a department inside a company.

Default the system havs 1 level of dimensions. That is, you can keep a simple track of departments or cost centres or whatever, but just in one level. That is, you can keep track of departments only or cost centres only inside a company.

If you don't need dimensions you can set it to 0 in the company setup.
Here you can choose between level 0, 1 or 2.

I hope this gives meaning to you.

Admin

We have been doing some more research and detected some differences in declaring the work centre id in the database. It might cause problems in newer versions of MySQL. We have solved it by casting the string versions into unsigned. It should fix the problems.
Please check out the following files from the CVS.
/includes/db/manufacturing_db.inc
/manufacturing/work_order_entry.php
/manufacturing/includes/work_order_issue_ui.inc
/manufacturing/includes/db/work_order_requirements_db.inc
/manufacturing/includes/db/work_orders_quick_db.inc
/manufacturing/inquiry/where_used_inquiry.php

We hope that this solves your problems.

Admin

Thanks for the bug report. The last one with the debug boxes has been fixed.
Another bug, according the Issue link in Work Order Inquires, produced an empty screen, has been fixed.
Affected files:
/manufacturing/work_order_entry.php
/manufacturing/includes/work_order_issue_ui.inc
/manufacturing/includes/db/work_orders_quick_db.inc
Please check them out from the CVS repository on Sourceforge.

We couldn't reproduce your first error (viewing the work order). Could you please, after downloading the affected files, tell us if the bug still exists. That is, try to enter a new work-order and view it.
If the bug still exists, please tell us exactly what you entered. That way we should be able to fix it rapidly.

Admin

Hi Sammie,
We understand what you mean and one way to do this is to stamp the memo_ field with the user_id when creating General Ledger transactions. It might be sufficient enough. All transactions from the sub-systems will create General Ledger transactions, at least the critical ones.
A slightly similar method is to add a new field in the GL_trans table called user_id.
What do you think? Will eather approach be ok?

Admin

Hello andres,
Yes we have plans for export/import of various items. See this link.
https://frontaccounting.com/wb2/pages/p … future.php.
We are more looking into xml for doing this, but an API could also be of interest.

Admin