ISTech Support Forum - Labor Information and locations....

Welcome, Guest. Please Login.

	05/03/24 at 23:59:48 News: \| IS Tech Support \| Evo~ERP \| Evo Wiki \| Forum \|

ISTech Support Forum › Evo-ERP and DBA Classic › Source Code and Programming in TAS

‹ Previous topic | Next topic ›

Pages: 1

Labor Information and locations.... (Read 1567 times)

ITman

Member

Hello!

Posts: 76
Gender: female

Labor Information and locations....
02/03/04 at 09:13:08

Hi all,

I'm wondering where labor information is stored? I found files...

BKDCLAB
WOLABOR

Were looking to create a listing a past labor. (After it's posted with WO-N).. I see that BKCDLAB, AND WOLABOR has this information. What is the difference between the two exactly? Are these files ever flushed and labor information removed? I was also wondering if I should maybe use another file all together?

Anyone know?

IP Logged

ITman Member Hello! Posts: 76 Gender:	Re: Labor Information and locations.... Reply #1 - 02/03/04 at 11:06:58 I'm also wondering why the labor is recorded in two steps? First the setup time is stored and saved, then a new record is made and stores the run time. Can't it all just be stored into one record? Or does DBA need the setup and the runtime in two different records?
Back to top	IP Logged

Karen Mason

Active Member

Ain't life grand!?!

Posts: 728
Gender: female

Re: Labor Information and locations....
Reply #2 - 02/03/04 at 11:19:19

We use JC-C to print labor transactions. Payroll people use it by employee with a date range to verify P/R entries. I use it in Sequence order to determine how many hours a sequence has run and if all pieces have been recorded. There are many uses for JC-C and many filters.

I do not know why 2 records have to be entered.

Karen Mason, Vice President
Bula Forge & Machine, Inc.
1-60# forgings, machining, & assembly
Cleveland, OH
Tel:216-252-7600 Fax:216-252-7601 www.bulaforge.com
EVO-ERP 09/16/09 SP2

IP Logged

Lynn_Pantic

Administrator

evolution (n) -
gradual change to a
different form

Posts: 5681

Re: Labor Information and locations....
Reply #3 - 02/03/04 at 11:50:48

The BKDCLAB file was developed for the Data Collection module and is also used when entering and posting labor via WO-M and WO-N. Entering labor at WO-F only updates the WOLABOR file. Most of the reports use the WOLABOR file since it always has the labor records regardless how they were originally entered.

This data exists until work orders are purged or archived. Once archived, the data moves to WOHLABOR and BKDCHLAB

Lynn Pantic
IS Tech Support
lynn@istechsupport.com

IP Logged

ITman Member Hello! Posts: 76 Gender:	Re: Labor Information and locations.... Reply #4 - 02/11/04 at 06:12:19 Thanks! The report has to be retroactive so I'll use WOLABOR and WOHLABOR. Thanks again
Back to top	IP Logged

ITman Member Hello! Posts: 76 Gender:	Re: Labor Information and locations.... Reply #5 - 03/29/04 at 08:30:01 Still have one question on this... why is labor recorded in two steps for the setup and then for the run time? Can't it be entered in just one? Should the program I wrote be saving it two seperate steps?
Back to top	IP Logged

Lynn_Pantic Administrator evolution (n) - gradual change to a different form Posts: 5681	Re: Labor Information and locations.... Reply #6 - 03/29/04 at 08:34:59 Yes, it should be saved in 2 separate steps as all the standard DBA reports and posting programs expect a record to be either Setup or Run Time, not both in the same record. It was designed that way because in many cases the setup is performed by a different person.
Back to top	Lynn Pantic IS Tech Support lynn@istechsupport.com IP Logged

Pages: 1

ISTech Support Forum › Evo-ERP and DBA Classic › Source Code and Programming in TAS

‹ Previous topic | Next topic ›