Transaction Set Maintenance in Infor Factory Track: A Practical Configuration Guide

If your shop floor operators are seeing the wrong transactions at a workstation, skipping required data entry, or working around the system rather than through it, the root cause is almost always a misconfigured transaction set. Transaction set maintenance is the mechanism in Infor Factory Track (IFT) that determines exactly what operators can do, in what order, and with what data requirements at every station on your production floor. Get it right, and your data capture becomes accurate and consistent. Get it wrong, and you spend months chasing bad production records.

This guide covers how transaction set maintenance works, how to configure it correctly, and how to align it with your real workflow rather than a theoretical one.

What Transaction Set Maintenance Controls in Infor Factory Track

Infor Factory Track is a manufacturing execution system (MES) built to sit between your shop floor and your Infor CloudSuite Industrial (CSI/SyteLine) backend. Its job is to capture real-time production data: labor time, job moves, material issues, scrap, completions, and more. But it does not push every possible transaction to every workstation. That would be chaotic. Instead, IFT uses transaction sets to define a curated menu of actions for each station.

A transaction set is a named configuration record. It contains a list of assigned transactions (such as job issue, job move, backflush, labor start/stop, or scrap reporting), the order in which they appear to the operator, and a set of rules about what data each transaction requires. That transaction set is then bound to one or more workstation records.

This architecture matters because a welding station has no business running a final inspection transaction, and a receiving dock does not need access to production completions. Transaction set maintenance is how you enforce those boundaries at the system level rather than relying on operators to self-govern.

According to MESA International, a manufacturing industry association that has tracked MES adoption and outcomes for over two decades, poor transaction data quality is one of the top three barriers to realising value from an MES deployment. The problem usually starts not at the data entry level, but at the configuration level, where the wrong transactions are made available or the right ones are buried.

The Key Components of a Transaction Set Record

When you open the Transaction Set Maintenance screen in Infor Factory Track, you are working with several distinct configuration elements. Understanding each one before you start building is essential.

Transaction assignment is the first and most fundamental element. You select from IFT’s library of standard transactions and assign them to the set. IFT ships with transactions covering the full production lifecycle: material issues and returns, job moves between operations, labor start and stop, scrap reporting, production completions, non-conformance logging, and more. You only add the transactions that are relevant to the workstation type you are configuring.

Sequence order controls the order in which transactions appear on the operator’s screen. This is more important than it sounds. If an operator needs to start a job before they can move it, the start transaction needs to appear first. Sequence order also affects the default transaction that loads when the station opens, which means it directly influences operator behaviour.

Field-level prompting is where configuration gets granular. For each transaction in the set, you can control which data fields are displayed, which are required, which are optional, and which are hidden. For example, at a simple assembly station, you might hide the lot number field entirely because your production process does not use lot tracking at that step. At a quality hold station, that same field might be mandatory. Configuring prompting incorrectly is one of the most common sources of incomplete records in IFT deployments.

Workstation binding is the final step: assigning the transaction set to one or more workstation records. A single transaction set can serve multiple workstations that share the same process type, which keeps your configuration manageable as your facility scales.

How to Configure a Transaction Set: A Practical Walkthrough

The configuration process in IFT follows a logical sequence. Before you touch the Transaction Set Maintenance screen, you should have a clear map of your shop floor process steps and the data each step needs to capture. Configuring without that map leads to rework.

Step 1: Define the Station’s Purpose

Start by writing a one-sentence description of what the workstation does. A station that performs first-article inspection has a different transaction profile than one that runs a machining operation. That sentence will guide every decision you make in the maintenance screen.

Step 2: Build the Transaction List

Open Transaction Set Maintenance and create a new record. Give it a name that reflects the station type, not a sequential number. Names like “MACH-BASIC” or “QA-HOLD” are far easier to manage in a facility with dozens of workstations than names like “TS001” or “TS002.”

Add only the transactions the station genuinely needs. Resist the temptation to add transactions “just in case.” Extra transactions increase operator confusion and the risk of incorrect entries.

Step 3: Set Sequence and Defaults

Arrange transactions in the order that matches your actual production flow. The transaction at position one will load as the default when the station opens. For most production stations, that should be the job start or labor start transaction. For an inspection station, it might be the non-conformance entry transaction.

For teams managing more complex configurations, the approach to shop floor workstation setup in Infor Factory Track provides additional context on how workstation records relate to transaction set assignments.

Step 4: Configure Field Prompting

For each transaction in the set, review the available fields and set the appropriate prompting behaviour. Fields that are always known from context (such as the workstation ID or the logged-in operator) can be set to automatic. Fields that the operator must confirm should be set to required. Fields that are irrelevant to this station’s workflow should be hidden.

This step requires input from your production supervisors and process engineers. IT teams configuring field prompting in isolation frequently configure it based on what the system can capture, not what the process actually requires.

Step 5: Assign to Workstations and Test

Assign the completed transaction set to the relevant workstation records in IFT, then run a functional test at the station using a test job. Walk through every transaction in sequence and verify that required fields enforce data entry, that hidden fields do not appear, and that the transaction completes and posts to Infor CloudSuite Industrial as expected.

Aligning Transaction Sets with Your Production Workflow

The most technically correct transaction set configuration is worthless if it does not match how work actually flows through your facility. This is the gap that derails most IFT deployments.

A common example: a manufacturer configures a single generic transaction set and applies it to all production workstations to simplify the initial rollout. Operators quickly learn that several of the transactions do not apply to their station, and they start dismissing or skipping them. Within a few weeks, labor data is inconsistent, job move records are missing, and the production supervisor is spending hours per week reconciling discrepancies manually.

The solution is not necessarily a unique transaction set for every workstation. It is a station-type model: one configuration per distinct process type, not per individual machine. A facility with 40 CNC machines running the same process type needs one well-configured transaction set for CNC operations, not 40 variations.

Aberdeen Strategy and Research, which has tracked MES performance benchmarks across discrete manufacturers for many years, has consistently found that manufacturers with standardised shop floor data capture achieve significantly better schedule adherence and first-pass yield tracking than those without. Standardisation at the transaction set level is a direct enabler of that outcome.

Understanding how labor transaction tracking works within IFT is particularly useful when designing transaction sets for time-sensitive operations, where the sequence and prompting configuration for start and stop transactions directly affects payroll and costing accuracy.

Common Transaction Set Configuration Mistakes

Knowing what goes wrong in practice is as useful as knowing the correct configuration steps.

Overloading transaction sets with unused transactions. Every transaction you add is a decision point for the operator. If a transaction appears on the screen and the operator does not know what it does or when to use it, they will either ignore it or use it incorrectly. Build lean.

Ignoring field prompting for auto-populated fields. Many IFT deployments leave all fields at their default prompting setting, which typically requires operator input for everything. When operators have to confirm a field they already know (like their own employee number), they start taking shortcuts. Setting known fields to automatic reduces friction and improves data accuracy simultaneously.

Applying the same transaction set to fundamentally different process types. A fabrication station and a final assembly station share almost nothing in terms of transaction requirements. Applying the same configuration to both produces incomplete records at best and incorrect postings to your ERP at worst.

Not testing with real job data before go-live. Testing with dummy records often misses real-world validation issues, particularly around lot tracking, serial number requirements, and job operation sequences that only surface with genuine production orders. Infor’s own implementation guidance, documented within IFT’s administration module, recommends end-to-end process testing using live job data before any workstation goes into production use.

Failing to version-control your configuration. Transaction sets change over time as production processes evolve. Without a record of what changed and when, diagnosing data anomalies that appeared after a configuration update becomes extremely difficult. Maintain a simple change log, even if it is just a shared spreadsheet with date, modified set, and description of the change.

For organisations managing broader Infor platform complexity, the relationship between Infor OS integration and shop floor data flows is worth understanding before committing to a transaction set architecture, as platform-level decisions affect what data IFT can surface and how it moves downstream.

Conclusion

Transaction set maintenance is not a one-time setup task. It is an ongoing configuration discipline that directly determines the quality of the data your shop floor produces. A well-designed transaction set enforces process standards, reduces operator error, and ensures that every job completion, material issue, and labor entry reaches your ERP cleanly.

The practical starting point is a station-type audit: identify your distinct process types, document what data each type needs to capture, and build one transaction set per type. Configure field prompting based on what operators actually know at the moment of entry, not what the system is theoretically capable of collecting. Test with real jobs before go-live. Review configurations when processes change.

If your Infor Factory Track deployment is producing inconsistent or incomplete production records and you are not sure where the configuration gaps are, Sama Consulting can audit your transaction set setup and map it against your current production workflow. Contact us to arrange a structured review.