Syntech Manufacturing

Syntech Manufacturing · component guide

Order queue

The component gathers everything the plant has to make into one ranked queue — sales order lines, state contract deliveries and unit requests — and calculates a promised date for every item from ATP and CTP. It commits the promise with a reservation and a production order, re-promises the queue after a rank change and shows the reason chain behind every date.

Where it lives

  • Production planning workplace → home page tab “Order queue”.
  • Contract card → tab “Order queue” (only that contract’s items, without the load chart and without reordering).

What it needs

Package
orderqueuesyntech (view element syn.OrderQueue), installed together with the SynManufacturing package.
Licence
Licence operation SynManufacturing.Use. Without it the element shows a “Licence required” card and loads no data; an administrator grants it in System designer → Licence manager.
Service
SynOrderPromiseWebService — GetQueue reads the queue, PromiseItem runs the what-if, CommitPromise commits the promise, Reorder changes the rank, RepromiseAll recalculates everything.
Rights
Operation right CanPromiseOrders — committing a promise, reordering and “Re-promise all”. Reading the queue and “What-if” are open to everyone.
Settings
SynPromiseSafetyDays, SynPromiseHorizonDays, SynPromiseRepromiseEnabled, SynPromiseIncludeForecastDemand, the finite-capacity mode and the BOM explosion depth. The component prints the current values in its footer.
Data
Sales orders in status Confirmation or In progress, state contract schedule deliveries with a remaining quantity, and unit requests in status Submitted or Accepted.

The screen

Order queue on the Production planning workplace
Real screenOrder queue on the Production planning workplace
  • Indicator tiles“Open demand”, “On-time promises”, “At risk”, “Late” and “Not promised”; a click on a tile filters the table by that status, while “On-time promises” is a percentage with a bar only.
  • Header buttons“Refresh” reloads the queue, “What-if” opens the check of a new demand, “Re-promise all” recalculates the whole queue and sends the notifications.
  • FiltersThe sources “All sources”, “Sales order”, “State contract”, “Unit request”, “Forecast”, the checkbox “Only at risk and late” and a search over demand, product and customer.
  • Queue table“Rank”, “Demand”, “Product”, “Qty”, “Priority”, “Requested”, “Promised”, “Calculated”, “Confidence”, “Status”, “Limited by” and “Promised routing” — the routing the date was calculated on; the mark “Alternative” means an alternative routing finishes earlier than the primary one. On the left the drag grip and the move up and move down buttons.
  • Promise panelOpens on a click on the item number: “Available to promise”, “To produce”, “Reason chain”, “Linked production orders”, “Promised date”, the reservation and order checkboxes and the button “Promise”.
  • “What-if: new demand”“Product”, “Quantity”, “Requested date” and “Priority class” → “Calculate” answers with “Could be promised on …”, “Queue position” and “Other demand that would move later”. Nothing is saved.
  • “Weekly load vs capacity”Compares “Booked operations” and “Queue (CTP)” against the capacity week by week and names the bottleneck with its utilization.
  • “Forecast demand”A separate list under the table with the count of forecast rows. Its caption follows the setting “Order promising: include demand forecast”: “not netted against supply” or “netted against supply”, and in the second case every row also shows its “Available …” date and its limiting factor. The block is not shown on the contract card.

Typical actions

Find the problem items

  1. Press the tile “At risk” or “Late” — the table narrows to that status.
  2. Tick “Only at risk and late” to see both groups together.
  3. Read the column “Limited by”: Stock, Supply, Material, Capacity, Lead time or No routing.

Commit a promised date

  1. Click the item number — the promise panel opens.
  2. Check the “Reason chain”: it explains how the calculated date was built.
  3. Leave “Promised date” empty to promise the calculated one, or type your own; tick the reservation, the order creation or the customer confirmation.
  4. Press “Promise” — the item moves to Promised or Confirmed.

Change the priority of an item

  1. Clear the filters — ranks cannot be changed on a filtered list.
  2. Drag the row by its grip or use the move up and move down buttons.
  3. The queue is re-promised at once; items pushed past their promise turn At risk.

Check a new demand with what-if

  1. Press “What-if” in the header.
  2. Enter the “Product”, “Quantity”, “Requested date” and “Priority class”.
  3. Press “Calculate” and read the date, the queue position and the demand that would move later.

Re-promise the whole queue

  1. Make sure the facts and the expected receipts are up to date.
  2. Press “Re-promise all” — the component recalculates the items in rank order.
  3. The message names how many items are at risk, late and changed.

See whether the forecast is counted

  1. Scroll to the block “Forecast demand” under the queue table.
  2. Read its caption: “not netted against supply” means the rows only inform; “netted against supply” means they consume stock and capacity.
  3. To change that, switch the setting “Order promising: include demand forecast” and reload the page.

Live queue (no period plan)

For plants that work a rolling queue — orders for the next 2–3 days arrive during the day, nothing is planned per period:

  • SynLiveQueueEnabled (default off): a sales order saved into SynLiveQueueTriggerStatus (empty = Confirmation) is queued and promised at once, not overnight. A line without any date is due today. The queue item gets a note “Live queue: promised automatically …”.
  • SynLiveQueueAutoCreateOrder (default off): the automatic promise also creates the plan item and the production order of the line (plan “Order queue yyyy-MM”).
  • Recalculate queue now: recalculates only the items whose order changed since their last calculation (and promises new live lines) — never the whole queue; Re-promise all stays the nightly job. Tick + shift assignments today / tomorrow to add the new work to today’s and the next working day’s shift assignments (draft assignments get the new operations; approved ones are not changed; right CanApproveShift).
  • The chips under the header show the live-queue state, the shortage-gate mode and the active routing season.

Services: rest/SynOrderPromiseWebService/RecalculateNow, ProcessOrderNow.

Shortage gate when promising

With SynOrderShortageGateMode = Warn, Promise on a sales-order line whose materials go short in the stock projection (all committed orders, by day) stops with “Materials run short” and the list; Promise anyway commits it and records the warning. With Block the promise is refused. The projection itself is the “All orders” mode of the Materials check.

Routing seasons

Routings of one season form a set: lookup Routing season (SynRoutingSet, e.g. Summer / Winter) and the field Season on the routing. Routing season in the header: choose the season, an effective date (empty = today; the switch is by temperature, not by calendar) and a note, press Preview, then Switch season. For every product with a routing of that season, that routing is released through the normal revision path (today: it becomes current and the previous one is superseded; a future date: approved and activated by the hourly engineering job). Alternative routings of the other seasons are set inactive. The switch is logged (SynRoutingSeasonLog) and the promise never uses an alternative routing of another season. Right: CanApproveEco. Service rest/SynRoutingSeasonWebService/{GetSeasons, SwitchSeason}.

Limits and known behaviour

  • Committing a promise, reordering and “Re-promise all” need the operation right CanPromiseOrders; without it the panel explains the refusal, while reading and “What-if” stay available.
  • Ranks cannot be changed while a filter or a search is applied — the component asks you to clear the filters first.
  • The contract card has neither the load chart nor reordering: it shows that contract’s items only.
  • “What-if” saves nothing, and forecast demand is always shown as a separate block: whether it is netted against stock and capacity is decided by the setting SynPromiseIncludeForecastDemand, and the block caption says which of the two it is.
  • Preset mobile quick filters are unsupported: the component filters are set on the screen itself.
  • After a package update the page needs a hard reload (Ctrl+F5) — otherwise the browser keeps the previous bundle in cache.

See also

Full Syntech Manufacturing guide — sectionOrder queue and promised dates (ATP / CTP)All Syntech application guideshttps://syntechcompany.github.io/appsguides/
A Syntech Manufacturing component. Section, tab and button names match the product; the component language follows your Creatio profile language.