copy of live while users working?

I don't know how to do it, but I have worked at places that do it that way. Warning: if you take you data without kicking out users, you will be unable to exactly tie test to production.

WE ARE ONLY DOING THIS TO RUN A PARRELLEL PAYROLL SO ONLY THE HR/PR TABLES WILL NEED TO BE IN SYNCH WITH LIVE TO DO THIS AND THE HR/PR FOLKS WILL BE KICKED OUT...JUST THE AP/GL FOLKS ARE ALLOWED TO CONTINUE WORKING...

DOES THAT SOUND BETTER? DO YOU SEE ANY ISSUES WITH THIS FOR A PARRELLEL PAYROLL?

BASICALL WE ARE TAKING A COPY RIGHT BEFORE PR140 IS RUN IN LIVE AND PUTTING THAT IN TEST. WE WILL THEN CONTINUE THE PAYROLL IN LIVE..BUT NEXT WEEK IN TEST WE WILL USE THAT DATA TO RUN A PAYROLL WITH OUR NEW BSI 8 TO SEE IF THE TOTALS MATCH TO WHAT OUR LIVE PUT OUT.

HOPING THIS WILL WORK..

I would prefer a total stoplaw, do a backup then startlaw. Concerns are not with users only but also you have to
consider hr/pr jobs on schedule and of course how about process flow??

consider us fortunate at this point we do not use process flow and we do not have any hr/pr jobs that run via a schedule. We are new to lawson and still getting our wings. thanks very much for the input and advice, I appreciate it more than you know.

Several of the Lawson utilities (i.e. dbcopy, sqldbcopy) allow you to copy across product lines by system code (PR, HR, PA, etc.) or even specific tables. However, you do run some risk in that you wouldn't be copying some base tables, particularly those in IF, like GLNAMES, GLMASTER, and OBJID--which are referenced by HR/PR, etc. Specifically, once you do the copy, you would want to use IFOB form to bump up the OBJ-ID values--otherwise you will likely run into issues with duplicate OBJIDs on personnel actions, deductions, etc.