Labor hours showing zero

Yahoo Archive
1
Carl, how are you my friend?

This might be too simple, but we had a similar issue, not finding MES labor entries in Labor Entry or a Custom report we created for daily check-edit.

Our problem was, most of our operators were not Clocking-Out for the day, but only Logging-Out; this makes the individual labor entries accurate (Clock-In Date-wise) but logged into the wrong "Payroll Date"......which in this case was the last time the operator Clocked-Out, 15 days behind.

Just a quick tip on Labor entrty, hoping you all have a good and productive week.

Roel Martinez
ERP Analyst

SABRE TUBULAR STRUCTURES (tm)
www.sabretubularstructures.com<http://www.sabretubularstructures.com/>
8653 E. Hwy 67 | Alvarado, TX 76009
Phone: 817-852-1700 ext. 11858 | Direct Line: 817-852-1858 |Fax: 817-852-1705



[Non-text portions of this message have been removed]
2
Suddenly, all of our MES reporting people are showing zero labor hours even though the Labor Edit report shows clock in and clock out times for the jobs.

We can't figure out what we changed on the fateful day and experiments haven't been able to reverse this.

Any ideas??
3
Are you using AMM & are the reporting more than the job required?
We had a similar issue, we only seen errors in the logs nothing on the screen.
We ended up creating a customization that always checked the request move.

PROBLEM DESCRIPTION: (error)
We get an error message when attempting to report "overproduction" for a job on MES:
'Unexpected error - see appserver logs.'

[09/01/26@12:41:50.100-0600] P-006200 T-006204 1 AS -- (Procedure: 'CreatePartAlloc lib/pwipmtlq.p' Line:1303) ** No JobProd record is available. (91)

RESPONSE FROM DEVELOPMENT:
SCR 59986 will fix the issue in 8.03.409

WORKAROUND:
If you get the error message, either one of the following will solve this problem:
1) Check the Request Move box, and press Save again.
2) Enter less labor quantity than the job operation requires, save, and then start and end an activity for the remaining amount. "


Other possibility to fix this problem is:

"Workaround:
They got around the issue by changing the Output Warehouse on the Resource Group for the last Operation on the Job."

Just make sure one thing, your system is not hanging once you try to report qty agaist jobs, correct?


--- In vantage@yahoogroups.com, "CarlH" <carl.heeder@...> wrote:
>
> Suddenly, all of our MES reporting people are showing zero labor hours even though the Labor Edit report shows clock in and clock out times for the jobs.
>
> We can't figure out what we changed on the fateful day and experiments haven't been able to reverse this.
>
> Any ideas??
>