Configuring Labor Reporting Parameters in Infor Factory Track: A Complete Guide

Why Labor Reporting Configuration Matters

Labor costs are one of the biggest line items in manufacturing operations. According to the U.S. Bureau of Labor Statistics, manufacturing unit labor costs rose 4.7% in 2024, putting pressure on manufacturers to track every labor hour with precision. Inaccurate labor data doesn’t just affect payroll; it skews job costing, distorts production scheduling, and undermines the entire ERP feedback loop that management depends on.

With more than 200 configurable parameters, Infor Factory Track modules can help companies understand their labor costs. But that flexibility comes with a responsibility: those parameters must be set correctly from the start, or they can generate bad data silently for months before anyone notices.

This guide is built from Infor’s official documentation, hands-on implementation experience, and real-world configuration patterns across discrete and process manufacturing environments. Whether you’re doing a fresh implementation or auditing an existing setup, you’ll find actionable guidance here that goes beyond the basics.

If you’re working with a consulting partner on your Factory Track deployment, the team at Sama Consulting specializes in Infor ERP implementations and can help you align your labor reporting configuration with your operational requirements.

Understanding the Infor Factory Track Architecture

Before touching any parameter, you need to understand what Factory Track is and how its modules relate to labor reporting.

Factory Track comprises three modules: The Shop Floor module is a work center automation solution that provides paperless manufacturing capabilities. Shop Floor delivers a kiosk-based solution that can be accessed by multiple production floor operators to track labor, report job operations, and track work-in-progress and finished goods. The Time Track module is a comprehensive time and attendance application. Because nearly every manufacturer has specific attendance and labor rules, Time Track provides a configurable solution that allows organizations to set up their own rules concerning attendance and labor, such as shift duration, labor management, absence management, and timesheet tracking.

The Warehouse Mobility module rounds out the platform by handling receiving, material movement, and inventory operations  and also surfaces labor-related transactions for workers on mobile devices.

Labor reporting lives primarily in the Shop Floor module and the Time Track module. The parameters you configure determine:

• How labor time is captured (automatically vs. manually)
• What data fields operators are required to fill in
• How machine time relates to labor time
• Whether users can close jobs, complete operations, or specify quantities
• How transactions post to the connected ERP (SyteLine/CloudSuite Industrial or LN)

Understanding this structure means you’ll always know which form to go to when a labor reporting behavior needs to change.

The Three Layers of Labor Reporting Parameters

Factory Track uses a layered parameter architecture. Think of it as a hierarchy where each level can override or refine the one above:

Layer 1: Global Parameters

Settings that apply to all Factory Track transactions and forms across the entire installation. These are the foundation.

Layer 2: Site Parameters

Settings that apply to a specific site, particularly the ERP connection, shift codes, and posting behavior.

Layer 3: Transaction-Level Parameters (Transaction Set Maintenance)

The most granular level. Each individual transaction  End Run, Job Move, Job Booking, etc.  has its own configurable parameter set. These control exactly what operators see and what they’re allowed to do during a specific transaction.

The Transactions Setup form is used to determine what transactions are available in the application and to define the parameters used by each transaction. The User Parameters form is used to define parameters at the user level. Transaction Set Maintenance is used to configure parameters for individual transactions. Warehouse Parameters configure transaction parameters specific to a warehouse.

This layered approach is powerful. A warehouse in one facility can have different quantity-reporting rules than another without touching the global configuration.

Configuring Global Parameters for Labor Reporting

The Global Parameters form is your starting point. Navigate to Configuration > Parameters > Global Parameters.

⚠️ Caution: Only programmers who are authorized to customize your Infor Factory Track application should use the Global Parameters Setup form. Changes here affect every transaction system-wide.

Key Global Parameters That Directly Affect Labor Reporting

Time Track Implemented

Select this check box to enable the Time Track module. Caution: The Time Track Implemented parameter significantly changes the way your application operates. You should only select this parameter when you are implementing the Time Track module. Selecting or clearing this parameter under other circumstances may cause your application to behave unpredictably or incorrectly.

This is probably the single most impactful parameter in the entire system. Getting it wrong creates cascading issues across every labor transaction.

Process Labor Transactions

Select this check box to process labor transactions for the selected ERP. If this is not enabled, labor records will be captured in Factory Track but will not post to your ERP  meaning job costing and work order actuals will be wrong.

Display Resource ID

Select this check box to display the resource ID field on Shop Floor transaction forms. Time Track transaction forms use this parameter as well. When Display Resource ID is set to Yes, select this check box to display the list of job resources defined for the job. When this is cleared, all valid resources are displayed.

This matters for operations where specific machines or resources need to be tracked against labor time.

Maximum Job Run Hours

Specify the number of hours a job can be running before it is marked as an error record. You can use this parameter to prevent excessive hours from being clocked to a job in the event that an employee forgets to stop it.

Setting a sensible threshold here (typically 10–12 hours for a single shift) acts as a safety net. Without it, a forgotten clock-out can post 60+ hours to a single job.

Active Job Behavior on Login

Select this check box to enable the user to view the active job on the Work Center form as soon as the user logs on to the application. Enabling this reduces the steps an operator needs to take when resuming work, which improves data accuracy  operators are less likely to skip logging back onto a job.

Defer Processing of Unposted Transactions

Select this check box to defer the processing of unposted shop floor transactions. This enables the shop floor operator to continue with the next shop floor task without waiting for the completion of task in CSI. In high-volume environments, this prevents the kiosk from blocking the next operator while a prior transaction is posting to the ERP.

Avoid Posting Labor Backflush Transactions

Select this check box to avoid posting of labor backflush transactions. Use this if your ERP handles labor backflushing at a different level, to prevent double-posting.

Using the Transaction Set Maintenance Form

Once your global settings are dialed in, most of your labor reporting configuration happens in the Transaction Set Maintenance form. This is where you control the behavior of each individual labor transaction.

Navigate to Configuration > Transaction Set Maintenance.

Use the Transaction Set Maintenance form to configure parameters for transactions. You can configure parameters for these transactions: End Run, End Run Only, End Machine, End Project Labor, End Service Labor, End Team Run, Job Booking, Job Material Issue, Job Move, and more.

The form has a grid of transaction names. Select one to view its available parameters. Every transaction has:

• General settings (visible in the header area): warehouse pre-fill, success message display
• Transaction Parameters tab: the detailed, transaction-specific checkboxes and fields
• Label Print Parameters (optional): if you need labels printed on transaction completion

Configuring Key Labor Transaction Parameters

End Run / End Run Only

The End Run transaction is used to stop a job operation and record the labor time. It’s one of the most frequently used transactions on the shop floor.

Navigate to Transaction Set Maintenance and select SF_JobMove from the grid.

Use the Transaction Set Maintenance form to configure parameters for the End Run, End Run Only, End Machine, End Team Run, Job Move, Join/Leave Team, and Team Member Reporting transactions. Select SF_JobMove from the grid.

Key parameters to configure:

Allow Quantity Reporting Select this check box to allow users to specify the quantity completed when stopping job operations. This is critical for manufacturers tracking WIP. If disabled, operators can stop a job without reporting quantities  which means your ERP won’t know how much was produced.

Allow Receiving Location Select this check box to allow users to specify a receiving location. Clear this check box to always use the default receiving location. Specify a default location where completed items will be received.

Require Re-authentication Select this check box to require generic users to sign in again using the Employee Authentication form after performing this transaction. Clear this check box to allow users to perform additional transactions, after performing this transaction, without signing in again. This matters in shared kiosk environments where a single login is used by multiple operators.

Quantity Validation Select this check box to warn users if they are attempting to report a quantity of good and scrapped items that exceeds the quantity received. This prevents over-reporting completions relative to the job order quantity.

Close Job Prevention Without Full Material Issue Select this check box to prevent users from closing a job if all material has not been issued. Useful in environments where material completeness is a quality gate before a job can be marked done.

Issue to Parent Job Select this check box to issue completed items from a sub-assembly job to its parent job. Items will only be issued to a parent job if: A parent job is defined for the sub-assembly job in SyteLine, and the last operation of the sub-assembly job is being performed. Select this check box to ask users whether to issue completed items to a parent job.

Enable End Run Only Select this check box to enable the End Run Only transaction. End Run Only stops labor without recording a quantity  useful when an operator needs to leave mid-job and another operator will take over.

End Machine

The End Machine transaction records machine time as separate from labor time. This is relevant when you want to track machine utilization independently.

The machine ratio determines what portion of the reported labor time will be reported for the machine. For example, a ratio of .5 will report half the reported labor time for the machine.

When configuring End Machine parameters:

• If Combine Labor and Machine Time is selected at the employee type or team level, the machine ratio field becomes available during the transaction.
• If Time Track is not implemented, machine time is managed differently  the End Machine transaction handles it directly rather than through a ratio field.

The key decision here is whether you want machine time to be automatically derived from labor time (using a ratio), or whether operators will report machine time in a separate, dedicated step. In most discrete manufacturing environments, the ratio approach reduces operator burden while still giving you machine utilization data.

End Team Run & Team Member Reporting

Team-based labor reporting is one of Factory Track’s most powerful features for high-volume assembly lines or shift-based environments.

When a labor transaction is performed using the team number, that transaction is replicated for all members of the team. A supervisor can also perform transactions on behalf of their entire team.

In Transaction Set Maintenance, there are additional parameters you can configure for the End Team Run and Team Member Reporting transactions by selecting MES_TeamsTransaction from the grid.

Critical considerations for team labor reporting:

• The team leader must be configured in the correct security group (FT-TeamLeader).
• Attendance transactions work differently from labor transactions in team mode: Attendance transactions cannot be performed for a team. Employees must clock in and out individually.
• Work set proration settings also apply here. This enhancement adds the ability to configure work sets to prorate time on the weighted average of run times or planned quantities of the jobs in the work set. You can also configure labor and machine time to use separate proration methods. An additional enhancement for work set machine time is that proration will only occur on jobs using the same machine.

Job Move

The Job Move transaction is used to record the physical movement of a job between operations or work centers. It’s grouped with End Run parameters in the SF_JobMove transaction set because the two often occur together.

Key parameters to set:

• Pre-fill Warehouse: Select this check box to pre-fill the warehouse on the transaction with the warehouse assigned to the user. The user can change this warehouse for a specific transaction if needed.
• Show Success Message: Select this check box to show a success message when the transaction is successfully completed. On busy shop floors, this visual confirmation matters  operators frequently move to the next task without confirming the transaction went through.

Job Booking (Time Track Mode)

If you have Time Track implemented, Job Booking replaces the Labor Reporting transaction for starting and stopping jobs.

If the Time Track functionality is implemented, you must use the Job Booking transaction instead of Labor Reporting transaction to start or stop these jobs.

The Job Booking transaction ties labor time directly into the Time Track attendance and payroll framework, meaning hours are reconciled against clock-in/clock-out records, shift rules, and overtime policies  not just raw timestamps.

The Display Resource ID parameter is specifically relevant here: The Resource ID field is displayed only for Job start/stop and Job Setup start/stop transactions. This field is displayed only when the Display Resource ID parameter is set to True.

Configuring Site Parameters That Affect Labor Reporting

Site Parameters govern how Factory Track connects to your ERP and how specific posting behaviors work. Several of these directly impact labor reporting.

Navigate to Configuration > Site Parameters.

Key Site Parameters for Labor Reporting

Allow Edited Transactions to Repost Select this check box to allow edited transactions to repost to the ERP system. Clear this check box to display an ERP error in response to reposted transactions. If supervisors frequently correct labor entries, you need this enabled  otherwise corrected records won’t update the ERP.

Auto-Zero Frozen Posts Select this check box to automatically zero out frozen posts by posting an offsetting negative value; for example, a frozen post of 4 hours will be offset by a post of -4 hours. Clear this check box to display an ERP error in response to frozen posts. This is a quality-of-life setting for payroll administrators dealing with locked pay periods.

Global Posting Error Behavior Select Use Global Posting to block posting of all four records. Clear this check box to post records 1, 2, and 4, and to block only record 3. This determines how a batch of labor records behaves when one record in the group has an error  stop everything, or post the valid ones and flag the bad one.

Report Shift Times Across Days Select this check box to report shift start and end times to ERP even when those times occur on separate days. Clear this field to always report shift start and end times on the same day in accordance with the configuration settings of the shift. Overnight shifts require this to be enabled or you’ll get incorrect date stamps on labor records.

Future Report Date Restriction The parameter Allow Attendance Transactions On Future Report Dates restricts Labor and Attendance transactions to current or past report dates. For payroll integrity, most organizations should disable future-date transactions to prevent accidental pre-dating of labor records.

User Roles and Access Controls for Labor Reporting

Labor reporting parameters are only half the equation. Who can access and modify those parameters is equally important.

Factory Track uses security groups that correspond to roles:

FT-Administrator Administrators also have access to the Time Track Administrator Home Page form to manage time track functionality as well as FT setup forms such as the Transactions Setup page and Transaction Set Maintenance page. Administrators have the highest level of access to all forms. Administrators usually manage and maintain organization, configuration, and security parameters.

FT-Supervisor Supervisors manage the labor and attendance data of Time Track employees. Line supervisors authorize exceptions, approve time sheets, schedule absences, and adjust shifts. Payroll supervisors process payroll data.

FT-User Users report labor and attendance data for themselves. Examples include starting a job they are about to work on or clocking out at the end of the work day. Users have access to a limited number of forms that are directly related to these activities. Users are usually allowed to view, but not edit, their own records on the Hours Summary and Hours Detail forms.

FT-TeamLeader Team leaders manage teams using the Shop Floor module. They are authorized to create teams and to add and remove team members. Team leaders can perform transactions on behalf of their entire team.

FT-SLWMMAKEIT (Mobile/Warehouse) The WMMAKEIT group is authorized to use mobile scanner transactions in the Make It module of Warehouse Mobility, including material issue and labor reporting transactions. This group is also authorized to use the Time Track mobile scanner transactions. Users in this group are not authorized to adjust transaction parameters.

The important distinction is that WMMAKEIT users can perform labor transactions but cannot change the parameters governing those transactions. Only Administrators and specifically authorized users can modify transaction parameters.

For a deeper dive into configuring employee records and security groups for your Factory Track environment, Sama Consulting’s Infor Factory Track consultants can assist with role mapping and access control design.

Time Track vs. Non-Time Track: How Parameters Differ

This is one of the most misunderstood areas in Factory Track configuration, and getting it wrong causes real problems.

When Time Track is NOT implemented:

• Labor is captured through direct job start/stop transactions (Start Run / End Run)
• Machine time can be reported in a dedicated End Machine transaction or as a ratio
• There is no payroll reconciliation  hours are passed directly to the ERP
• Clock-in/Clock-out for attendance is handled at the ERP level (or CSI’s Time & Attendance module)

When Time Track IS implemented:

• You must use the Job Booking transaction instead of Labor Reporting transaction to start or stop jobs.
• All labor is reconciled against clock-in/clock-out records in Time Track
• Shift rules, overtime rules, and absence management all affect how labor time is calculated before posting to the ERP
• Shop Floor can now use the SyteLine Rules to create lunch records, and adjust labor punches (records) as needed.
• Machine time behavior changes: If the Time Track module in Infor Factory Track is implemented, this check box is only available if the Combine Labor and Machine Time check box is selected either for your employee type on the Employee Types form or for your team on the Team Maintenance form.

The practical implication: if you’re transitioning from non-Time Track to Time Track, you cannot simply flip the “Time Track Implemented” parameter and keep your existing parameter configuration. Every labor-related transaction set needs to be reviewed and likely reconfigured.

Quantity Reporting in Both Modes

You can now use parameters for Quantity Reporting and Allow Complete Operation fields, so that sites that do not want to retrieve that data from the shop floor can disable the fields. This is useful for environments where quantity tracking is handled at a different point in the process  for example, at a receiving station rather than at the operation level.

Common Configuration Mistakes and How to Avoid Them

Based on real-world implementation experience, these are the configuration errors that cause the most trouble:

Mistake 1: Enabling Time Track Mid-Implementation Without Full Reconfiguration

Flipping the Time Track Implemented parameter without reviewing all transaction sets leads to broken behavior. Transactions that worked in non-Time Track mode may silently fail to post, or may post incorrectly.

Fix: Treat a Time Track implementation as a new configuration effort, not a parameter change. Review every labor-related transaction in Transaction Set Maintenance.

Mistake 2: Not Setting a Maximum Job Run Hours Limit

Forgetting to set the maximum hours threshold means that if an operator forgets to end a job before leaving for the day, the job can accumulate 16, 24, or more hours before anyone notices. This corrupts job cost data.

Fix: Set a reasonable threshold (e.g., 10 hours for a two-shift operation) in Global Parameters. Error records will flag for supervisor review rather than silently posting bad data.

Mistake 3: Leaving “Allow Quantity Reporting” Disabled

Some implementations turn this off to simplify the operator experience, not realizing that without quantity reporting, WIP and finished goods inventory in the ERP won’t update correctly.

Fix: Unless your production model truly doesn’t require operation-level quantity reporting, enable this parameter. The additional data entry burden is small relative to the inventory accuracy benefit.

Mistake 4: Ignoring the Re-authentication Parameter in Shared Kiosk Environments

In a shared kiosk setup, if generic user re-authentication isn’t configured, one operator can inadvertently post transactions under a different operator’s session.

Fix: Enable the “Require Re-authentication” parameter for all labor transactions used in shared kiosk mode.

Mistake 5: Misaligning Site Parameters with ERP Posting Rules

The ERP code specified on the Site Parameters form must match the Infor Factory Track site code specified in the ERP. A mismatch here causes posting failures that can be difficult to trace.

Fix: Verify ERP code alignment during initial configuration and after any ERP site changes.

Testing Your Labor Reporting Configuration

Configuration is only valid when it’s been tested against real workflows. Here’s a practical testing checklist:

Pre-Go-Live Testing Checklist

Global Parameters

• [ ] Verify Time Track Implemented matches your deployment plan
• [ ] Confirm maximum job run hours is set
• [ ] Test that labor transactions post to ERP in a test environment
• [ ] Verify Display Resource ID behavior matches your operational needs

Transaction Set Maintenance

• [ ] Test End Run with a real job  confirm labor time posts to the ERP job record
• [ ] Test quantity reporting  confirm finished goods inventory updates
• [ ] Test the re-authentication flow in your kiosk setup
• [ ] Test End Machine if applicable  confirm machine time posts separately or as a ratio
• [ ] Test team labor transactions  confirm all team members receive the labor record

Site Parameters

• [ ] Test ERP connection with Test Connection button
• [ ] Simulate a posting error and confirm error handling behaves as configured
• [ ] Test overnight shift posting if applicable

User Role Testing

• [ ] Log in as each security group and confirm access levels
• [ ] Verify that FT-User cannot access Transaction Set Maintenance
• [ ] Verify that supervisors can view but not edit transaction parameters

Edge Cases

• [ ] What happens when an operator forgets to end a job (test max hours threshold)
• [ ] What happens when a job is over-completed (test quantity validation)
• [ ] What happens when a material is not fully issued before job close

If you need expert support during testing or go-live, the Infor ERP implementation team at Sama Consulting provides hands-on validation services.

Workset Configuration and Labor Proration

For manufacturers running complex multi-operation workflows, Factory Track supports worksets  groups of operations bundled together for a single employee or team.

Starting a workset starts all of the related operations, tasks, activities, projects and service labor.

When configuring workset parameters for labor reporting:

• You can configure proration to distribute labor time across workset operations based on planned quantities or run times
• You can configure labor and machine time to use separate proration methods. An additional enhancement for work set machine time is that proration will only occur on jobs using the same machine.
• Workset header creation can be automated: Select this check box to enable the automatic creation of workset header.

Workset-based labor reporting is particularly valuable in high-mix, low-volume manufacturing where operators frequently work across multiple jobs in a single shift and manually tracking each start/stop would be impractical.

Frequently Asked Questions

Q: Can I configure different labor reporting parameters for different warehouses?

Yes. If you are configuring parameters that only apply for a specific warehouse, that warehouse is displayed in the Warehouse field. If you are configuring general parameters, which apply by default throughout the application, the Warehouse field is blank and unavailable. This allows site-specific customization without affecting the global default behavior.

Q: What is the difference between End Run and End Run Only?

End Run stops a job operation and typically prompts for quantity reporting and receiving location. End Run Only stops labor time recording without requiring quantity data  useful for mid-job breaks or operator handoffs where a quantity hasn’t been completed yet. Select this check box to enable the End Run Only transaction.

Q: How do I prevent excessive labor hours from posting to a job when an operator forgets to clock out?

Specify the number of hours a job can be running before it is marked as an error record. You can use this parameter to prevent excessive hours from being clocked to a job in the event that an employee forgets to stop it. Error records flag for supervisor review rather than automatically posting to the ERP.

Q: Do I need separate configuration for mobile scanner labor reporting?

Mobile scanner labor transactions (through the WMMAKEIT group) use the same Transaction Set Maintenance parameters as kiosk-based transactions, but some parameters are specific to the mobile context. The WMMAKEIT group gives users access to labor reporting transactions on mobile devices but does not allow them to change the parameters governing those transactions.

Q: How does Time Sheet Detail work for supervisor approvals?

The enhanced functionality provides a convenient and efficient means for employees and supervisors to sign off and edit hours. Supervisors use the Hours Summary and Hours Detail forms to review, approve, and adjust labor records before they’re processed through payroll.

Q: What happens if a labor transaction fails to post to the ERP?

The behavior depends on your Site Parameters configuration. With global posting enabled, all records in a batch are held if one fails. With global posting disabled, valid records post and only the failed record is held. Either way, error records are visible to supervisors and administrators for correction and reposting. Verify your reposting settings: Select this check box to allow edited transactions to repost to the ERP system.

Summary: The Configuration Order That Works

If you’re building this from scratch, here’s the sequence that avoids common dependency issues:

• Configure Site Parameters first  establish your ERP connection and posting rules before anything else touches labor data.
• Configure Global Parameters  set Time Track mode, labor processing, resource ID display, and max job hours.
• Configure Employee Records  assign employee types, badge numbers, indirect task codes, and security groups.
• Configure Transaction Set Maintenance  work through each labor transaction (End Run, End Machine, Job Booking, Team Run, etc.) and set operation-specific parameters.
• Test in isolation  run each transaction type with test data before connecting to production ERP.
• Test end-to-end  run a complete simulated shift including clock-in, job starts, quantity reporting, job completion, and clock-out.
• Document your configuration  export your parameter settings and keep them versioned alongside your ERP configuration baseline.

For manufacturers on Infor CloudSuite Industrial (SyteLine) or Infor LN, the labor reporting configuration in Factory Track is one of the highest-leverage areas to get right. A well-configured system reduces manual correction work, improves job costing accuracy, and gives management real-time visibility into shop floor performance.

If your team is navigating a Factory Track implementation or upgrade and needs experienced guidance, Sama Consulting’s Infor specialists have deep experience across both SyteLine and LN environments and can help you build a configuration that fits your operations  not just the defaults.

References and Further Reading

• Infor Factory Track Official Product Page
• Infor Factory Track for SyteLine User Guide (v6.00.x)
• Infor Factory Track CSI Administration Guide (v7.00.x)
• Configuring Global Parameters  Infor Docs
• Transaction Set Maintenance  Infor Docs
• Configuring Site Parameters  Infor Docs
• Factory Track Groups  Infor Docs
• U.S. BLS Manufacturing Productivity Data