Question numbers match their folders: folder 01 contains 01-01, 01-02 and so on. The starter dashboard uses 01-05, 01-08 and 01-02; process filter values come from 01-20. OBP identities and SQL filenames remain stable.
Choose a question for the decision you need to make. Find the equivalent saved question by its number in your supplied collection. If it has not been prepared, ask your administrator to create it from the linked English SQL definition before adding it to a dashboard. Filters act on existing output columns and do not override the source conditions.
The headings below match the English SQL variants in this guide. Use the stable question number to find its equivalent in your supplied collection; names can vary by language and environment.
01-01 · Work orders by status
See the current distribution of work orders, including closed orders. This counts orders, not planned units.
Recommended display: Bar chart with value labels
Available filters: Work-order status.
What the columns mean
Work-order status: The current status name recorded on the order. Question 01-01 includes closed statuses too.
Order count: Number of orders in the row's status group, not planned unit quantity.
When checking a discrepancy: Groups by statusname. Other questions filter statustype; a display name is not a status code.
01-02 · Open work orders: details
Find open orders, their process, planned quantity, progress and due date. Includes NEW, IN_PROGRESS and FROZEN.
Recommended display: Table
Available filters: Work order, SKU, Process, Status, Progress, Planned quantity, Due date.
What the columns mean
Work order: The recorded work-order number. Identifies the order, not the individual unit's serial number.
SKU: The part identifier recorded on the order, run or stock record, according to the question. It is not an individual-unit identifier.
Process: The workflow name associated with the result row. Filtering a name does not select a particular workflow version.
Status: Current work-order status name. Status meanings and permissions to change them depend on the organization's process.
Progress: The stored numeric order/run progress value: order in 01-02 and 01-08, run in 02-09. Shown without converting its scale to percentages.
Planned quantity: Planned quantity stored on the order.01-02 shows individual orders;01-13 sums by SKU. Do not add unlike units of measure.
Due date: The planned order-completion timestamp in the due-date field. Not measured shipment or actual completion.
When checking a discrepancy: Missing due dates remain visible at the end. Question 01-05 excludes frozen orders; question 01-20 includes their process names.
01-03 · Work orders created by month
See how many orders were created in each month, regardless of their current status.
Recommended display: Line chart over time
Available filters: Opening month.
What the columns mean
Opening month: The month when orders were created. A displayed first-of-month date represents the month, not a claim that every order was created that day.
Orders: Order count within the question's month, source, SKU or other group.01-11 includes only closed orders with usable, correctly ordered dates.
When checking a discrepancy: Creation month is not a reconstruction of historical open backlog. A missing createdat may create a blank group.
01-04 · Work orders completed by month
Count END orders with a recorded completion date, grouped by completion month.
Recommended display: Line chart over time
Available filters: Completion month.
What the columns mean
Completion month: The month used to summarize completed work orders.
Orders: Order count within the question's month, source, SKU or other group.01-11 includes only closed orders with usable, correctly ordered dates.
When checking a discrepancy: Closed orders without an end date are excluded. Use 06-03 or 01-16 to check missing dates.
01-05 · Open orders by process
Compare NEW and IN_PROGRESS order counts by process. Frozen orders are excluded.
Recommended display: Bar chart with value labels
Available filters: Process.
What the columns mean
Process: The workflow name associated with the result row. Filtering a name does not select a particular workflow version.
Open orders: NEW and IN_PROGRESS order count. This measure excludes frozen and closed orders;01-02 also includes frozen orders.
When checking a discrepancy: Missing workflowname becomes the literal label shown in the SQL. Names may combine multiple process identities. Use 01-20 for the broader open-order dropdown.
01-06 · Open orders by SKU
Compare NEW and IN_PROGRESS order counts by SKU; this is not a quantity total.
Recommended display: Bar chart with value labels
Available filters: SKU.
What the columns mean
SKU: The part identifier recorded on the order, run or stock record, according to the question. It is not an individual-unit identifier.
Open orders: NEW and IN_PROGRESS order count. This measure excludes frozen and closed orders;01-02 also includes frozen orders.
When checking a discrepancy: Process is absent from the output. Filtering this result cannot recover a process breakdown.
01-07 · Age of open orders
See how long NEW and IN_PROGRESS orders have existed. Age is not days overdue.
Recommended display: Bar chart with value labels
Available filters: Order age.
What the columns mean
Order age: Elapsed time since creation of an open order, grouped using 7,03-02 and 90-day boundaries. Not days overdue. Missing creation dates currently fall into 01-07's oldest bucket; that is a classification limitation, not a known age.
Orders: Order count within the question's month, source, SKU or other group.01-11 includes only closed orders with usable, correctly ordered dates.
When checking a discrepancy: Buckets use less than 7,30 and 90 days. Missing creation dates currently fall into the oldest bucket; future dates enter the youngest bucket.
01-12 · Work orders by recorded source
Count work orders by their recorded source.
Recommended display: Bar chart with value labels
Available filters: Source.
What the columns mean
Source: Recorded source of an order or stock record. Questions 01-12 and 03-06 display missing source as local;03-04 shows the stored value.
Orders: Order count within the question's month, source, SKU or other group.01-11 includes only closed orders with usable, correctly ordered dates.
When checking a discrepancy: NULL becomes local; an empty string does not. This does not prove an order was entered manually.
01-13 · Planned and reported quantities by SKU
Compare planned, reported good and reported rejected quantities across all work-order statuses.
Recommended display: Table
Available filters: SKU.
What the columns mean
SKU: The part identifier recorded on the order, run or stock record, according to the question. It is not an individual-unit identifier.
Orders: Order count within the question's month, source, SKU or other group.01-11 includes only closed orders with usable, correctly ordered dates.
Planned quantity: Planned quantity stored on the order.01-02 shows individual orders;01-13 sums by SKU. Do not add unlike units of measure.
Reported good quantity: Good quantity reported on work orders, summed by SKU. Not a test-pass percentage.
Reported rejected quantity: Rejected quantity reported on orders, summed by SKU. Zero or blank does not prove no rejects occurred; reporting can be incomplete.
When checking a discrepancy: The three totals come from different fields. Good plus rejected is not enforced to equal planned quantity. Check units and reporting rules.
01-14 · Work orders by management type
Count orders by status, serial-management flag and bulk-production flag.
Recommended display: Bar chart with value labels
Available filters: Status, Serial-managed, Bulk production.
What the columns mean
Status: Current work-order status name. Status meanings and permissions to change them depend on the organization's process.
Serial-managed: The work order's recorded serial-management flag: true, false or missing. Separate from the serial value itself.
Bulk production: The order's recorded bulk/batch-production flag: true, false or missing. Not a batch count.
Orders: Order count within the question's month, source, SKU or other group.01-11 includes only closed orders with usable, correctly ordered dates.
When checking a discrepancy: Missing flags remain missing; they are not automatically converted to false.
01-15 · Recorded progress in open work orders
Group open orders into missing progress, zero progress and other recorded progress.
Recommended display: Bar chart with value labels
Available filters: Progress.
What the columns mean
Progress: Missing progress, zero progress or another recorded value. Text categories, not percentage bands.
Orders: Order count within the question's month, source, SKU or other group.01-11 includes only closed orders with usable, correctly ordered dates.
When checking a discrepancy: Any non-NULL nonzero value, including a negative value, enters the recorded-progress group. These are categories, not percentage bands.
01-19 · Frozen work orders to review
Find individual FROZEN work orders for follow-up. Empty results are normal if none qualify.
Recommended display: Table
Available filters: Order, SKU, Process, Status, Frozen order creation, Due date, Planned quantity.
What the columns mean
Order: The same kind of identifier as the work-order-number column; different questions use different localized headings.
SKU: The part identifier recorded on the order, run or stock record, according to the question. It is not an individual-unit identifier.
Process: The workflow name associated with the result row. Filtering a name does not select a particular workflow version.
Status: Current work-order status name. Status meanings and permissions to change them depend on the organization's process.
Frozen order creation: Order creation timestamp, not when the order was frozen. Cannot be used to calculate freeze duration.
Due date: The planned order-completion timestamp in the due-date field. Not measured shipment or actual completion.
Planned quantity: Planned quantity stored on the order.01-02 shows individual orders;01-13 sums by SKU. Do not add unlike units of measure.
When checking a discrepancy: Creation is not the freeze timestamp. Freeze reason, duration and history are not available in this question.
01-20 · Open-order processes: filter values
Get distinct nonblank process names from NEW, IN_PROGRESS and FROZEN orders for an open-order dashboard dropdown.
Recommended display: Table
Available filters: Process.
What the columns mean
Process: The workflow name associated with the result row. Filtering a name does not select a particular workflow version.
When checking a discrepancy: Matches the status coverage of 01-02 but excludes missing or blank names. Identical names can merge different process identities. Changing the dropdown source does not change a card's calculation.