How Can We Help?
To make a report available at a station you create the line + station + report
association described above (optionally with the send-to-printer / send-to-file / station-printer
options). The general steps are:
What, where, who, when, why
| What | The line + station + report association that makes a shop document print (or save) when a batch is released, with per-assignment printer/file options. |
| Where | Part of the partner’s manufacturing/rules configuration, not the order UI (see the warning below). The reports themselves are registered on Report Management with the Production flag. |
| Who | The person maintaining the partner configuration (administrator / support). Station operators cannot change it. |
| When | When a line is set up; when a station needs its own cut list, labels or machine file; when a parent line’s reports should reach several child lines at once. |
| Why it matters | At batch release, reports are generated per line-station pair, walking the route in sequence — a station with no assignment prints nothing, and a unit’s parts on an unrouted station stop scheduling outright. |
Worked example: the Weld line’s QC station should print two copies of the work order to the
shop printer and also save a PDF — assign the Work Order report (Production flag on)
to Weld line + QC station, tick send to printer (Copies 2, station printer
“Shop-Laser”) and send to file (the station’s
Save Directory), and leave the other stations
unassigned.
- Make sure the report exists and is correctly set up on Report Management (name, printer, and the Production flag for shop documents).
- Choose the production line and the station on it that should print the report.
- Add the report to that line + station, and set the options — send to printer and/or send to file, and a station printer if it should not use the report’s default.
- If the report should be available on several child lines, assign it once on their common parent line (see parent-line inheritance).
- To hold a report back at one specific station, add a report-by-station exception for that line/station instead of removing the assignment.
Where this is configured
Report-to-station assignments are part of the manufacturing / rules configuration for a
partner, not the day-to-day order screens — the ERP reads these assignments but does not edit
them from the operator or order UI. If you cannot find the assignment editor in your build,
raise it with your OpenJanela administrator or support: the assignment may be maintained through
the configuration tool or seeded in the partner database.
Report-to-station assignments are part of the manufacturing / rules configuration for a
partner, not the day-to-day order screens — the ERP reads these assignments but does not edit
them from the operator or order UI. If you cannot find the assignment editor in your build,
raise it with your OpenJanela administrator or support: the assignment may be maintained through
the configuration tool or seeded in the partner database.