Automation of BN101, PA100, BN100, LP100

We schedule the BN101, BN100 and PA100 reports at 5 am before users begin their work day, so no date parameters are needed (it's left blank), and it picks up the prior day's work. We don't use LP at this point. The biggest issue is getting our users to look at the output and make corrections as needed, since we've had questions come in, weeks and even months later, asking about why something wasn't updated.

Stephanie do you run the BN101 after or before the BN100?

Is your BN101 set up to populate the "as of" date? Does it continuously change? What date do you use in there?

Hi Kelly - it's been so long since these were set up I had to recheck - for BN101, we use the first of the month, and we do update that particular date every month.

We have several jobs that we schedule to run once a week. These are financial reports for the current period. On the first day of the month I have a LPA flow that automatically changes the dates for the reports. This keeps the reports correct and we do not have to manually change them.

What is the best practice for these.  Is a daily run considered overkill?  We run our BN100 once every 2 weeks right before the payroll process kicks off.

We run ours 6xs a week. We often have over 100 pages per run and the associated errors. We have 20,000 employees. We basically run it everytime we are scheduled to run a PA100.

Anyone doing with the LP100?

Thanks.

I think "best practice" really depends on your organization and your processing.  We used to run prior to our payroll runs, however, the number of transactions was really too unwieldy, and it works better for us now to run daily.