Infor LN & BaanFree worksheetPDF, Excel, Word exportInfor LN

Infor LN Batch Job Schedule Register

Most LN problems that appear overnight come from a job nobody remembers. This register documents what runs, when, who owns it and what it needs before it starts.

Download:
Job nameSession or programFrequencyStart timeTypical duration (min)Business ownerDepends onLast run statusLast run date
Total typical minutes
167 min
Jobs
5

Session names in the example rows are descriptive placeholders. Use the exact session codes and job names from your own LN job management setup. Review the register after every upgrade, because sessions and parameters can change.

Get an overnight job summary

Optional help building a read-only daily summary of LN job outcomes.

Optional. The tool and every export work without this. No spam.

How to use the register

List every job that runs on a schedule or is run by hand at fixed times, including period end tasks. For each, record the session, frequency, start time, typical duration and the business owner who cares if it fails. Fill Depends on with the job or file it needs first. Export to Excel and keep it with your runbook, then update the last run status during daily checks.

Why dependencies matter

A planning run that starts before the stock snapshot finishes will plan against stale data. An invoice run that starts before shipments are confirmed will miss them and surprise finance in the morning. Writing the dependency next to each job makes the sequence visible, and the duration column shows where a slow job pushes the next one past its start time. Check that start time plus duration leaves a margin before the next dependent job.

Reading the register

Sort by start time to see the night in order, and by status to find failures. The total typical minutes is a rough load indicator, not a wall clock time, because jobs overlap. Jobs with no owner are the first risk: when they fail nobody feels responsible. Jobs with long durations and failed status deserve a recovery note on what to rerun and in what order.

Common mistakes

Running everything at midnight, leaving period end tasks undocumented, and keeping the schedule only in the head of one administrator are the usual faults. Also avoid recording the schedule once and never revisiting it: new integrations, new sites and upgrades add jobs and shift timings. Review quarterly.

Frequently Asked Questions

Does this replace LN job management?

No. LN job management runs the jobs. This register documents them in a form people can review, share with auditors and use in a runbook, including jobs triggered outside LN.

Which jobs should be included?

Everything scheduled or repeated at fixed times: planning, invoicing, rate imports, interfaces, archiving, reports and period end tasks. Include manual jobs that someone must remember to run.

How often should the register be reviewed?

Quarterly, and after every upgrade, new integration or new site. Update the last run status as part of your daily or weekly operations check.

What should I write in Depends on?

The job, file, or business event that must complete before this one can run correctly, for example shipments confirmed or the rate file received. Use None if there is no dependency.

If you want a morning summary of overnight job outcomes without opening each session, we can build a read-only monitor over your LN job data.