Shop-Trak Transaction Flow Overview

After being entered into Shop-Trak Shop Floor, transactions flow through different paths depending on the transaction type. Transactions can be transferred automatically or manually.

Transaction Flow by Type

Indirect, Setup, Run, Move, Direct, Project, Service Repair Order, and Work Center - These transactions are held in the Shop-Trak Edit Transactions form. They are then transferred to Infor SyteLine forms or posted to Infor SyteLine depending on the transaction type:

Indirect, Setup, Run, Move, and Direct - These transactions transfer to the Unposted Job Transactions form. To view transactions that did not transfer successfully, run the Shop-Trak Transfer to SyteLine Report. After the transactions transfer successfully, they are then posted to Infor SyteLine. The User Initials field on the Unposted Job Transactions form will indicate that the transaction originated from a Shop Floor user by displaying one of the following:

LTI for an Indirect transaction
LTS for a Setup transaction
LTR for a Run transaction
LTM for a Move transaction
LTD for a Direct transaction

NOTE: If the transaction requires approval, the approver's initials will display in the User Initials field after the transaction is approved.

Project - These transactions transfer to the Project Labor Transactions form. To view transactions that did not transfer automatically using Background Polling, view the Shop-Trak Background Polling Log. After the transactions transfer successfully, they are posted to the Infor SyteLine Project Module.
Service Repair Order - These transactions post to the Labor tab of the SRO Transactions form of the Infor SyteLine Service module.
Work Center Labor - These transactions post to the corresponding Work Center in Infor SyteLine.

NOTE: Transactions that do not successfully transfer will remain in the Shop-Trak Edit Transactions form until the error condition is resolved. You can run the Shop-Trak Transfer to SyteLine Report to view these transactions.

QCS Test Results - These transactions post to the corresponding Disposition form in the Infor SyteLine Quality module.
Prod Schedule Complete, JIT, Work Center Material, and Job Material transactions - These transaction types post directly to Infor SyteLine using the Infor Framework TaskMan service. To view transactions that did not transfer due to errors, view the Shop-Trak Pending Prod Sched Transactions, Pending JIT Transactions, Pending Work Center Transactions, and Pending Material Transactions forms.

For a graphical representation of the transaction flow, see the Transaction Flow Chart.

Transaction Error Conditions

A transaction will not transfer if any of the following are true:

The transaction type is Punchin or Multi-Job.
The transaction has no end time or hours assigned.
A Team transaction in which quantities have not been allocated.
A Team transaction that has open transactions for other team members for the same Job/Suffix/Operation.
A Team, Run, Setup, or Direct transaction without a job and operation assigned.
Approval is required.
The employee is locked.
The employee forgot to punch out.
The employee has an open transaction with the same Job/Suffix/Operation for the same work date.
The employee has a break or lunch transaction with no end time or hours assigned.
The transaction is missing an SRO Indirect Labor Code.
The transaction has an invalid Cost Code.
The transaction is not in the selected range of Transfer Options on the Shop-Trak Parameters form's Background tab.
Payroll Rate or Job Cost Rate is blank.

Shop-Trak Transaction Flow Overview

Transaction Flow by Type

Transaction Error Conditions

Related Topics