Information

Title	Punch Processing APE job error: 'RecordCount' is null or not an object

Summary	This article explains why Punch processing job throws the 'Record Count is null' error and how to resolve it.

URL Name	Punch-Processing-APE-job-error-RecordCount-is-null-or-not-an-object

Resolution

For employees that don't punch in but have their punches created from their schedule using the APE job, assign a punch rule with 'Auto-generate job transfers from schedule' option unchecked.
For employees who punch in using clocks, assign a punch rule with 'Auto-generate job transfers from schedule' option checked.

Products	Advanced Scheduling; Time & Attendance

Module	Punch Processing

Version	All

Error Message Code

Script error in 'Applications.WorkforceManagement.APE.TAP.tasks.ProcessPunchGroupForSystem' :
Description= 'RecordCount' is null or not an object:
Line=9
Text= Unknown error 0x800A0BBB

Cause

This error occurs when one or more employees have a punch rule with 'Auto-generate job transfers from schedule' feature checked but are not punching in using clocks instead having their time punches generated by the 'CreateScheduledPunches' APE job.
Because 'Auto job transfer' feature is checked, 'CreateScheduledPunches' job creates 0 length job transfers thus causing Punch Processing job to error.
Both 'Auto-generate job transfers from schedule' and 'CreateSchedulePunches' can't be run on the same employees.

Additional Information

'CreateScehduledPunches' full job moniker: Applications.WorkforceManagement.ape.TAP.jobs.CreateScheduledPunches

Publication Status	Published

Punch Processing APE job error: 'RecordCount' is null or not an object

Information