I remember there being lots of bugs in 404 where resource level set up data failed to do what it was supposed to (in many processes... backflushing & finite scheduling were the ones I can remember but there were others) if the resource group (containing the resource) had null values in the same fields.
Most issues were resolved in 405.
If it DIDN'T work in your test environment (perhaps unkown as no one can check everything truly until being 'real world load live'), consider putting some values at the group level.
It would at least quickly eliminate that (a bug) as the source of the problem and could be set up & checked (via a quick dummy job that you report against, then check costs & finally kill when done) in seconds.
Rob
________________________________
From: saab_barracuda <chris.clunn@...>
To: vantage@yahoogroups.com
Sent: Wednesday, June 10, 2009 4:15:40 PM
Subject: [Vantage] Re: Labor costs not being captured - 803.404B
Manasa: Costing Labor Rates in the resource group setup only affect the standard cost roll and job estimates. That has no effect on applied costs.
Ed: The only other thing I can think of is to check that the "Production Worker" box is checked on the first page of Employee setup.
Did this work for you in your test environment before implementation?
Most issues were resolved in 405.
If it DIDN'T work in your test environment (perhaps unkown as no one can check everything truly until being 'real world load live'), consider putting some values at the group level.
It would at least quickly eliminate that (a bug) as the source of the problem and could be set up & checked (via a quick dummy job that you report against, then check costs & finally kill when done) in seconds.
Rob
________________________________
From: saab_barracuda <chris.clunn@...>
To: vantage@yahoogroups.com
Sent: Wednesday, June 10, 2009 4:15:40 PM
Subject: [Vantage] Re: Labor costs not being captured - 803.404B
Manasa: Costing Labor Rates in the resource group setup only affect the standard cost roll and job estimates. That has no effect on applied costs.
Ed: The only other thing I can think of is to check that the "Production Worker" box is checked on the first page of Employee setup.
Did this work for you in your test environment before implementation?
--- In vantage@yahoogroups .com, Ed Garbowski <egarbowski@ ...> wrote:
>
> - None of the accounts, applied labor, WIP or COS reflect any labor costs.
>
> - Actual labor costs do not show up on the Production Detail, but hours do show.
>
> - We do have Labor Rate populated with the correct figure and Active Shop Employee is checked. There is only $1.00 populated in the Pay Rate since we are not using it.
>
> Thanks,
> Ed
> From: vantage@yahoogroups .com [mailto:vantage@yahoogroups .com] On Behalf Of saab_barracuda
> Sent: Wednesday, June 10, 2009 11:56 AM
> To: vantage@yahoogroups .com
> Subject: [Vantage] Re: Labor costs not being captured - 803.404B
>
>
>
>
>
> Which specific accounts are you not seeing labor costs? Applied Labor, WIP, COS, all of the above?
>
> Are there labor transaction costs showing for your jobs (WIP report and/or Production Detail)? If not, are there at least labor hours showing up on your jobs (Production Detail)?
>
> Do you really have "Labor Rate" populated? I.e. not just "Pay Rate" but the field for "Labor Rate" in Employee setup? The Labor Rate and Pay Rate are two related but separately assigned variables.
>
> Labor cost is a simple calculation of labor hours times labor rate.
>
> --- In vantage@yahoogroups .com<mailto:vantage% 40yahoogroups. com>, "Ed Garbowski" <egarbowski@ > wrote:
> >
> > Since going live 7 weeks ago, we have not shown labor costs to be captured in our WIP/Inventory Reconciliation report. We are using the Payroll module which is selected in the Company setup, the labor rate is set in Payroll, employees are set as Payroll employees, GL accounts are correct, Pay Types and Labor expense code are all pointing to the same GL accounts, and we have checked everything else we know of to verify settings are correct, however cannot figure out why labor is still not showing up. Any ideas of where else to look?
> >
> > Thanks,
> > Ed
> >
>
>
> ____________ _________ _________ __
> The information contained in this message is intended solely for the individual to whom it is specifically and originally addressed. This message and its contents may contain confidential or privileged information. If you are not the intended recipient, you are hereby notified that any disclosure or distribution, or taking any action in reliance on the contents of this information, is strictly prohibited.
> We have taken precautions to minimize the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this message. We cannot accept liability for any loss or damage caused by software viruses.
>
> This message (including any attachments) is intended only for
> the use of the individual or entity to which it is addressed and
> may contain information that is non-public, proprietary,
> privileged, confidential, and exempt from disclosure under
> applicable law or may constitute as attorney work product.
> If you are not the intended recipient, you are hereby notified
> that any use, dissemination, distribution, or copying of this
> communication is strictly prohibited. If you have received this
> communication in error, notify us immediately by telephone and
> (i) destroy this message if a facsimile or (ii) delete this message
> immediately if this is an electronic communication.
>
> Thank you.
>
>
> [Non-text portions of this message have been removed]
>
[Non-text portions of this message have been removed]