The shop floor flow in your manufacturing setup is built to guide users step by step through a registration process. Nothing gets posted until the user confirms, which makes it easy to register time and output correctly without mistakes along the way.
You control whether the flow posts the output journal directly or just leaves a line for someone else to post afterwards. The choice depends on your background setup.
How the shop floor flow guides the user
The whole point of the shop floor flow is to gather information from the user and then end with some kind of registration. The flow walks the user through each step, and nothing happens until the user is done entering the data.
If you want to register time on an operation, the process looks like this:
- Select the production order number
- Select the operation number on that production order
- State the amount of time you have used
- State whether you want to set the routing status to finished, or leave it as it is
Only when the user confirms by saying yes to registering the data does anything get posted. This guided approach keeps registrations simple and reduces the risk of errors.
Posting the output journal or leaving a line for later
When the user confirms, the system posts an output journal with the time registration. Depending on how you have set things up in the background, the flow can instead just leave a line in the output journal for someone else to post later.
This gives you flexibility. Some setups let the shop floor worker post directly, while others route the registration to a colleague who reviews and posts it.
Why guided registrations matter on the shop floor
Every flow in the shop floor module is meant for guidance. By leading the user through each step and holding off on posting until the end, the process becomes very easy to follow. That makes accurate registrations much more achievable on the floor.
Q&A
When does the shop floor flow actually post data?
Nothing is posted until the user confirms at the end of the flow. Until the user says yes to registering the data, the steps only gather information. No registration happens in the background during the process.
What steps does a user follow to register time on an operation?
The user selects the production order number, selects the operation number on that order, states the amount of time used, and decides whether to set the routing status to finished. After confirming, the system posts the registration.
Can someone else post the output journal instead of the shop floor worker?
Yes. Depending on your background setup, the flow can leave a line in the output journal for someone else to post later, rather than posting it directly.