Shop Floor Control > Generating Reports
  
Generating Reports
The Shop Floor Control Reports menu (16.20.13) contains reports that display data based on the following:
• Transactions
• Downtime
• Input and output
• Utilization and efficiency
Transactions
Transactions are created when you record labor feedback, nonproductive labor, downtime, and operation completions. You can review these transactions by work center, work order, or employee.
The system automatically assigns a transaction number and transaction type that identifies the operation history record. Operation History Transaction Types lists the system-generated types and the name of one or more of the programs that creates the transaction.
Note: Many of these transactions are created in more than one program. In this case, the table simply indicates one or more typical programs associated with the transaction and is not intended to be a complete list.

Operation History Transaction Types
 
Transaction Type
Description
Program
BACKFLSH
Advanced Repetitive labor and material usage.
Backflush Transaction (18.22.13)
CLOSE
Operation closed.
Cumulative Order Close (18.22.10)
DOWN
Non-productive labor reported for Shop Floor Control functions.
Labor Feedback by Work Order (16.20.1)
DOWNTIME
Downtime hours reported for Repetitive and Advanced Repetitive functions.
Repetitive Labor Transaction (18.14)
Down Time Transaction (18.22.20)
EXPENSE
Expense consumed for Customer Services functions.
Call Activity Recording (11.1.1.13)
Project Activity Recording (10.5.13)
FLOORSTK
Floor stock inventory expense posted at order close.
Post Accumulated Usage Variance (18.22.9)
LABOR
Labor hours reported for Repetitive, Advanced Repetitive, and Customer Services functions.
Repetitive Labor Transaction (18.14)
Run Labor Transaction (18.22.14)
Call Activity Recording (11.1.1.13)
Project Activity Recording (10.5.13)
MOVE
Moved to next operation.
Labor Feedback by Work Order (16.20.1)
MUV-CMP
Material usage variance posted for component usage variance at order close.
Post Accumulated Usage Variance (18.22.9)
MUV-WIP
Material usage variance posted for WIP material scrap usage variance at operation close.
Post Accumulated Usage Variance (18.22.9)
RBUV
Run labor burden usage variance posted at operation close.
Post Accumulated Usage Variance (18.22.9)
REWORK
Quantity reworked and labor hours posted.
Rework Transaction (18.22.17)
RLUV
Run labor usage variance posted at operation close.
Post Accumulated Usage Variance (18.22.9)
SBUV
Setup labor burden usage variance posted.
Post Accumulated Usage Variances (18.22.9)
SCRAP
Quantity scrapped at an operation.
Operation Scrap Transaction (16.20.7)
SETUP
Setup hours recorded.
Setup Labor Transaction (18.22.15)
SLUV
Setup labor usage variance posted.
Post Accumulated Usage Variances (18.22.9)
SUBCNT
Subcontract quantity received or returned at an operation.
Purchase Order Receipts (5.13.1)
Purchase Order Returns (5.13.7)
SUBSHIP
Quantity of WIP shipped to a subcontractor.
Sub Shipper Issue (18.22.5.11)
SUV
Subcontract processing usage variance posted at operation close.
Post Accumulated Usage Variance (18.22.9)
TRANSFER
Quantity of WIP transferred to another cumulative order at operation close.
Cumulative Order Close (18.22.10)
VAR-POST
Labor variance posted at work order receipt.
Work Order Receipt Backflush (16.12)
WIPADJ-I
Quantity adjusted for input queue.
WIP Adjust Transaction (18.22.21)
WIPADJ-O
Quantity adjusted for output queue.
WIP Adjust Transaction (18.22.21)
WIPADJ-R
Quantity adjusted for reject queue.
WIP Adjust Transaction (18.22.21)
WO-CLOSE
Work order accounting close post.
Work Order Accounting Close (16.21)
Use either of the following reports to review operation history records:
• Operation Transaction Browse (17.13.8)
• Operation Transaction Detail Inquiry (16.20.13.9)
• Operation Transaction Detail Report (16.20.13.33)
Note: This enhanced report is available only in .NET UI.
Use Operations Numbering Report (16.20.13.22) to review operation transaction history by number or date range. Transaction sequence numbers apply to the database as a whole; as a result, transactions within a domain may appear to have gaps. This report lets you see transactions created in all domains and verify that numbering is sequential.
Downtime
Review recorded downtime by work center or reason code using the following reports:
• Down Time Report (16.20.13.16)
• Down Time by Reason Report (16.20.13.17)
See Recording Nonproductive Labor.
Input and Output
Use Input/Output Report (16.20.13.12) to review the load at work centers. You can use this function to compare planned input and output with actual input and output for a given period. The planned input and output data are based on work order operation start dates, standard setup and run times, and the work center or shop calendar. Actual input is based on the quantities moved to a work center, while actual output is based on the quantities completed at a work center.
Utilization and Efficiency
Two key measures of performance are utilization and efficiency. Utilization is the ratio of the total number of hours worked to the total number of hours available to be worked, as defined in the shop calendar.
Utilization % = Actual Hours Worked/Clock Time Scheduled * 100
Use Work Center Utilization Report (16.20.13.18) to review this information.
Efficiency is the ratio of the total number of standard hours earned by completing units at operations to the total number of hours worked.
Efficiency = Standard Hours Earned/Actual Hours Worked * 100
Productivity is the ratio of standard hours earned divided by the number of available hours. It is not reported, but can be manually calculated by multiplying utilization by efficiency.
Productivity % = Standard Hours Earned/Clock Time Scheduled * 100
Use any of the following reports to review efficiency data:
• Efficiency by Work Center Report (16.20.13.19)
• Efficiency by Work Order Report (16.20.13.20)
• Efficiency by Employee Report (16.20.13.21)
Deleting and Archiving Transactions
Depending on the volume of transactions, you may only want to maintain one to three months of history online. Use Operations History Delete/Archive (16.20.23) to archive old transactions and delete them from the database.
Use this programs carefully to prevent deleting data or archiving data that may be needed online. While recovery of archived data is relatively easy, it is not possible to recover deleted data that has not been archived.