[
https://issues.apache.org/jira/browse/OFBIZ-13248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17983656#comment-17983656
]
Pierre Smits commented on OFBIZ-13248:
--------------------------------------
I have a few questions regarding:
* Calculate labor costs by multiplying the worker’s hourly rate by their
logged hours.
How will hours be logged?
There a multiple scenarios possible, e.g. a) each MFG worker has access to a PC
(and - OFBiz - permissions) to register completion of assigned task, b) only
Production Manager and/or Assistant have access to a PC (and - OFBiz -
permissions) to register completion of tasks of a Production Run.
* Record these costs as a labor cost entry in the production run’s cost
records.
At what stage of the Production Run will 'these costs' be calculated/recorded?
* Include labor costs in the total production run cost displayed in the
Manufacturing module
At what stage of the Production Run will these cost be displayed in the
Manufacturing application?
This improvement/ticket ties in with entities defined in the accounting
component namely:
* RateType
* RateAmount
The RateAmount defines records that can be used for correct cost calculation
for a given MFG operator and lifespan applicable to the executed task in a
production run.
I suggest to use a new RateType record as seed data, which is subsequently used
for new RateAmount records:
{code:java}
<RateType rateTypeId="FLC" description="Fully Loaded Cost (price for
WorkEffort)"/> {code}
leading to following example RateAmount record
{code:java}
<RateAmount rateTypeId="FLC" rateCurrencyUomId="USD" periodTypeId="RATE_HOUR"
workEffortId="_NA_" partyId="_NA_" emplPositionTypeId="_NA_"
fromDate="2000-01-01 00:00:00.000" rateAmount="95.0"/>{code}
Given that in a company with multiple workers the RateAmount can vary from
worker to worker (based on parameters for each, like contractual salary per
period and factoring in numerous conditions/exceptions). RateAmounts are often
calculated in the budget period before a new accounting year starts , and
mostly after the negotiations have been concluded between Employer and
(potential) employee.
Also, a (scheduled) production run is dependent on actual availability of
workers, and which employee executes a scheduled task is only kno
The Manufacturing Manager (and/or assistant) should be able to implement these
allocation changes in the Manufacturing application, before the last stage
(currentStatusId="PRUN_CLOSED") of a production run is reached.
> Labor costs are missing from cost calculations in the Manufacturing module,
> leading to incomplete production run accounting.
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: OFBIZ-13248
> URL: https://issues.apache.org/jira/browse/OFBIZ-13248
> Project: OFBiz
> Issue Type: Improvement
> Components: manufacturing
> Affects Versions: Upcoming Branch
> Reporter: Yashwant Dhakad
> Priority: Minor
>
> In the Manufacturing module, during cost calculation, labor costs are not
> included or recorded for respective production runs, even though features to
> record the workers’ hourly rates and logged hours are available. This
> omission of labourer’s wages from the final cost calculation, results in
> incomplete cost reporting, as labor expenses are missing from the “Actual
> Costs” section of production run’s respective routing tasks. To address this,
> the system should:
> * Calculate labor costs by multiplying the worker’s hourly rate by their
> logged hours.
> * Record these costs as a labor cost entry in the production run’s cost
> records.
> * Include labor costs in the total production run cost displayed in the
> Manufacturing module.
> These changes will ensure accurate cost reporting, improve financial
> analysis, and eliminate manual calculations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
