Process catalog

Reference workflows for fine call-off import, delivery call-off, dispatch control, transfer control, consignment, and transport in Controlled Sales Core.

Purpose

This catalog summarizes the key end-to-end workflows in Controlled Sales Core. It helps users execute recurring daily tasks in a clear, reliable sequence.

Context

  • Delivery call-offs are typically processed against blanket sales orders.
  • Fine call-offs provide detailed demand and date input as an upstream process component.
  • Dispatch control turns operational data into actionable processing lists.
  • Transfer control adds location-oriented replenishment execution.
  • Consignment connects sales-side processing with transfer-oriented logistics interpretation.
  • Transport documents capture carrier handoff and final shipping information.

Prerequisites

  • Setup is complete and transport number series is maintained.
  • Blanket and/or sales documents are available in a processable status.
  • Warehouse and shipping responsibilities are aligned across teams.

Process map

graph LR;

%% Nodes
  A(Import fine call-off)
  B[Create delivery call-off]
  C[Release delivery call-off]
  D[Run dispatch control]
  E[Run transfer control if required]
  F[Apply consignment logic]
  G[Post shipment or transfer]
  H[Create transport]
  I[Post transport]
  J[Process completed]

%% Flow
  A -.- B
  linkStyle 0 stroke:#ffffff
  B ==> C
  C ==> D
  D ==> E
  E ==> F
  F ==> G
  G ==> H
  H ==> I
  I ==> J

%% Classes
  class A btProcessTitle
  class B,C,D,E,F,G,H,I,J btProcessActive

Required depth per process page

The linked detail pages should always include at least:

  • Step-by-step user flow with explicit actions and control checkpoints.
  • Complete field coverage per relevant page/FastTab (mandatory, example value, business effect).
  • Calculation logic with formula, example calculation, and rounding rules where relevant.
  • Required master data including dependencies and typical misconfiguration patterns.
  • Variants, exception scenarios, and cancellation/correction paths.
  • Error patterns with root cause, impact, and concrete resolution.

Process catalog

Process Import and assign fine call-offs Use fine call-offs as detailed demand input for downstream call-off processing.
  • Import incoming fine call-offs in the dedicated process entry and assign them to the correct blanket-order context.
  • Validate references, date relation, and quantity consistency per fine call-off line.
  • Resolve deviations before delivery call-off creation to avoid rework in downstream steps.
  • Transfer only business-valid fine call-offs into the next process phase.
Process Create and release delivery call-off From document call-off to operationally usable quantities.
  • Open document call-off data on the blanket order and verify references, plant, and unloading point.
  • Create a new delivery call-off using the related action.
  • Review call-off lines for quantity and date consistency before release.
  • Also review quantity type, date type, and planning type on the call-off lines.
  • Release the call-off to prepare downstream processing quantities.
  • Verify whether relevant sales orders were updated or created as expected.
  • When a zero-setting is reported, review the candidate, link, reset date, and conflicts before execution.
Process Run dispatch control Filter due lines and move them into shipping/pick processing.
  • Start the relevant dispatch control entry with your filter setup.
  • Review the resulting lines for due date and required quantity.
  • Use the highlighting for overdue, due-today, and stock-critical lines to prioritize work.
  • Still check available quantity separately before processing.
  • Select lines and create required documents.
  • Optionally create picks in the same run if your process requires it.
  • Confirm that all selected lines were transferred into the target process.
Process Run transfer control Move transfer-relevant lines into location-oriented shipment/pick execution.
  • Start the relevant transfer-control run for source and destination location.
  • Filter transfer lines by due date, availability, and operational priority.
  • Trigger Create Whse. Shipment, Create Whse. Shipment and Pick, or Create Whse. Pick according to warehouse setup.
  • Verify handover into transfer execution before posting.
Process Steer consignment process Connect sales-side execution with transfer-oriented replenishment and analytics.
  • Enable the Consignment option on the relevant Location Card.
  • Execute sales-side processing through dispatch control.
  • Add downstream transfer replenishment from stockkeeping data where required.
  • Ensure transport process classification is handled as Transfer in consignment context.
  • For consignment withdrawals, check the related location and line context before replenishment.
Process Process inbound consignment messages Review withdrawal notices, match them to existing consignment stock, and process the withdrawal.
  • Open the inbound consignment message and review status, message ID, consignment location, and activity.
  • Match each line to a posted transfer receipt with remaining quantity.
  • Check lot or serial numbers against the open item entries from that provenance.
  • Process the withdrawal only after the resolution is unambiguous, then review the follow-up documents.
Process Create and post transport Bundle posted shipment data into one transport process.
  • Create transport data from posted shipment information.
  • Verify shipping agent, carrier handoff date/time, and delivery date.
  • Add operational data such as vehicle, route, bordero, and shipment notes.
  • Check transport lines and weight totals.
  • Post transport only after all required information is complete.

Result

  • Delivery call-offs are handled in a traceable, repeatable flow.
  • Fine call-off import, delivery call-off, dispatch control, and transfer control are documented as one connected process chain.
  • Dispatch decisions are based on consistent filter-driven line selection.
  • Consignment scenarios and their specific process impact are transparently covered.
  • Transport processing is documented and can be operationally completed.
  • Detail pages serve as operational work instructions for end users with standard BC knowledge.

Links

Further Information

Related content