Controlled Sales Core on Product Documentation

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Controlled Sales Core supports day-to-day automotive supply workflows in Business Central, from delivery call-offs to dispatch control and transport handling. This page helps you understand where the solution is used and which pages you should start with.

Business Value

Less manual coordination between sales, shipping, and warehouse teams.
Clear handling of customer call-offs against blanket sales orders.
Faster creation of shipping and pick documents using reusable filters.
Traceable transport handling with carrier handoff and delivery details.
Better visibility of cumulative quantities and in-transit quantities.

Functional Focus

Delivery call-offs from blanket orders

You use document call-offs and delivery call-offs when customers continuously update required quantities and dates. The system keeps references, unloading points, and item-related data aligned for downstream processing.

Setup

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page guides you through the base setup of Controlled Sales Core. The goal is a stable operational start so delivery call-offs, dispatch control, and transport processing work together smoothly.

Prerequisites

Permissions for setup and administration in Business Central.
Core master data for customers, items, locations, and shipping agents is available.
Number series for transport documents is defined with the business team.

Recommended Sequence

Open Controlled Sales Core Setup and define core parameters.
Maintain transport number series and create base data.
Create dispatch control records for recurring daily routines.
Run an end-to-end test with sample documents.

Setup Building Blocks

Controlled Sales Core Setup

Use the setup page to control key switches for call-off and shipping behavior. For the first rollout, focus on these fields:

Processing delivery and fine call-offs

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes daily call-off processing in Controlled Sales Core: from blanket order and document call-off through delivery and fine call-offs to updated sales lines and downstream logistics processing. It is intended for teams that verify customer call-offs, align quantities and dates, and process released demand in dispatch control, consignment, or transport.

Business context

Blanket order or blanket agreement: Long-running customer agreement against which recurring call-offs are processed.
Document call-off: The business master record on the sales document. It connects customer, item, reference, plant, unloading point, contract data, and cumulative quantities.
Delivery call-off: A new call-off state with its own call-off number, call-off date, and call-off lines. It is released before operational processing.
Fine call-off: Detailed date and quantity demand. In daily work, these values appear as call-off lines; additionally, a separate Detailed Call Off can be created and released.
Cumulative quantities: Quantity progression from customer and internal shipment perspective. These values control which call-off quantity is actually transferred to sales lines.

Typical roles

Sales operations: verifies call-off data, references, and release readiness.
Order processing: checks sales lines, dates, open quantities, and downstream documents.
Warehouse and shipping: process released lines in dispatch control, picking, and transport.
Key user: handles exceptions for cumulative quantities, corrections, zero settings, and rerelease.

Prerequisites

Setup and number series are maintained.
The blanket order or sales document is available in a processable status.
Item, customer, reference number, plant, and unloading point are maintained correctly.
If mandatory logic is active, cumulative received quantity is available in the call-off.
Warehouse and shipping responsibilities are aligned across teams.

Process map

flowchart LR
  A[Review document call-off] --> B[Review fine call-off data]
  B --> C[Create delivery call-off]
  C --> D[Validate quantities and dates]
  D --> E[Release delivery call-off]
  E --> F[Update sales lines]
  F --> G[Run dispatch control]
  G --> H[Hand over downstream processes if required]
  H --> I[Continue logistics processing]

Operational flow

Process 1) Review document call-off on the blanket order The document call-off is the central link for call-off number, customer, item, and delivery context. +

Open document call-off data from the blanket order or sales document.
Verify reference number, item, customer order number, plant, and unloading point.
Check contract start, contract end, and the latest released call-off state.
Review cumulative delivered quantity, cumulative received quantity, and quantity in transit.
Clarify deviations before creating a new call-off state.

Process 2) Review and assign fine call-off data Fine call-off data provides detailed demand input for dates and quantities. +

Review or enter incoming fine call-off data if your process provides it separately.
Assign the fine call-off data to the correct customer, item, plant, unloading point, and blanket order.
Validate date relation, quantities, start/end date, and references per call-off line.
Use cumulative values and differences to quickly compare against the previous call-off state.
Transfer only business-valid fine call-off data into release processing.

Process 3) Create delivery call-off or Detailed Call Off A new releasable call-off state is created from the document call-off. +

Use Create Delivery Call Off when a new delivery call-off should be created for the existing document call-off.
Use Create Detailed Call Off when detailed fine call-off data should be processed as its own call-off type.
The system copies reference, item, customer, customer order number, plant, unloading point, and cumulative received quantity from the document call-off.
The new call-off number is continued from the latest released call-off state.
Until release, the new call-off remains business-editable.
Review proposed call-off lines by date and correct only business-relevant deviations.

Process 4) Validate quantities and dates before release Release should happen only when call-off data and quantity status are aligned. +

Check call-off date, call-off number, call-off lines, quantities, and dates.
Verify that the new call-off number is higher than the latest accepted call-off state.
Check whether requested dates are operationally feasible, and align deviations with sales operations, warehouse, or shipping.
Align unclear cumulative received quantities, delivery progress, or in-transit quantities with the customer process.
Check whether items are blocked or contract dates restrict the call-off period.
Confirm whether Ignore Qty. In Transit is intentionally set and matches the current business agreement.
Use the review and documentation rules further below on this page for corrections and zero settings.

Process 5) Release delivery call-off Release updates the call-off state and prepares operational sales quantities. +

Release only after completing the business checks.
On release, cumulative received quantity is written back to the document call-off.
The system updates the latest delivery call-off state and stores release date and released-by user.
Errors are recorded on the call-off so that they can be corrected directly.
If needed, the latest delivery call-off can be rereleased after quantity corrections.

Process 6) Verify sales lines Released call-off lines update matching lines or create new ones. +

If a matching sales line exists for item and date, the line is updated.
If no matching line exists, the system creates a new sales line.
Call Off Quantity remains visible as dedicated business information on the sales line.
Already shipped quantities, open order quantities, and existing warehouse documents are respected.
After release, verify quantity, Requested Delivery Date, location, and downstream readiness.

Process 7) Run dispatch control Due sales lines are transferred into shipment or picking processes. +

Start the relevant dispatch control entry with your filter setup.
Dispatch control works on released sales order lines and follows the relevant location setup.
Review the resulting lines for due date and required quantity.
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.
This keeps demand planning in the call-off and logistics execution in dispatch control clearly separated.

Process 8) Hand over downstream processes After call-off release, logistics runs the appropriate downstream process. +

Hand over released sales lines only to the downstream processes required for the specific location and customer scenario.
Run transfer control where location-based replenishment is required.
Consider consignment when the target location is managed as a consignment location.
Continue shipment, transfer, consignment, or transport in the dedicated process pages.
Create transports only from posted shipment information.

Field catalog for end users

Document call-off

Field	Mandatory	Example	Meaning
Item No.	Yes	70000	Item controlled by call-off data
Reference No.	Yes	VDA-REL-2026-0815	Customer-specific item reference
Order No.	Process-dependent	RA-4711	Customer order or blanket-agreement reference
Plant	Yes	1000	Customer plant
Unloading Point	Yes	GATE-03	Customer unloading point
Last Del. Call Off No. (new)	No	2026-0141	Latest released call-off state
Cumulative Delivered Quantity	No	13,800	Internally cumulative shipped quantity
Cumulative Received Quantity	Setup-dependent	15,000	Customer-side cumulative received quantity
Quantity in Transit	No	400	Shipped but not yet confirmed as received by customer
Ignore Qty. In Transit	Process-dependent	Off	Controls whether in-transit quantity is considered in call-off calculation

Delivery and fine call-off

Field	Mandatory	Example	Meaning
Delivery Call Off Type	Yes	Delivery Call Off	Differentiates delivery call-off and Detailed Call Off
Del. Call Off No. (old)	No	2026-0141	Previous call-off number
Del. Call Off No. (new)	Yes	2026-0142	New call-off number
Del. Call Off Date (new)	Yes	2026-06-01	Business call-off date
Customer No.	Yes	10000	Customer of the call-off
Utilisation Key	Process-dependent	S	Utilisation key for reporting and downstream documents
Released	No	Yes	Indicates whether the call-off has been released
Last Error	No	Item blocked	Last release-check error

Call-off lines

Field	Mandatory	Example	Meaning
Call Off Date	Yes	2026-06-03	Demand date of the call-off line
Quantity	Yes	800	Call-off quantity for the date
Cumm. Quantity	No	15,800	Cumulative call-off quantity up to the date
Quantity Last Call Off	No	600	Quantity from the previous call-off on the same date
Difference	No	200	Difference to the previous call-off state
Start Date / End Date	Process-dependent	2026-06-01 to 2026-06-07	Period for multi-day or periodic demand

Handover to downstream process

Field	Mandatory	Example	Meaning
Requested Delivery Date	Yes	2026-06-03	Planned date on the sales line
Call Off Quantity	No	800	Business quantity transferred from the call-off
Outstanding Qty. in Orders	No	300	Open quantity from linked orders against the blanket order
Qty. to Ship	Process-dependent	0	Checked after call-off release and set later in shipment processing
Location Code	Yes	MAIN	Warehouse context for shipment or picking

Cumulative quantities and calculation logic

Cumulative quantities prevent customer call-offs from being processed twice or too low. The decisive comparison is between customer-side quantity status, internal delivery progress, and quantities already considered.

Logistics scenarios

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page explains which standard Business Central logistics variants are available and how Controlled Sales Core fits into the operational flow. The key question is simple: Which action belongs to which location setup and document type?

Core Principle

In Business Central, the location setup determines whether a document can be posted directly or whether shipment and/or pick documents must be created first. Controlled Sales Core sits exactly at that decision point: it filters the relevant lines, creates the necessary follow-up documents, and keeps the operational selection transparent.

Dispatch control

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Dispatch control helps you bundle due document lines and move them into shipping, picking, or posting flows in a controlled way.

Standard BC setup context

Dispatch control always runs against a standard location setup. The relevant question is whether the location requires shipment, picking, or both:

No warehouse requirement: standard posting without warehouse documents.
Shipment required: dispatch control creates or fills the warehouse shipment step.
Picking required: dispatch control creates pick documents.
Shipment and pick required: both steps are processed in sequence.

For sales control, the relevant actions are Create Document, Create Document And Pick, Create Pick, Post Document, and Add to Whse. Shipment. For transfer control, the equivalent transfer actions are Create Whse. Shipment, Create Whse. Shipment and Pick, Create Whse. Pick, Add to Whse. Shipment, and Post Document.

Consignment process

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the implemented consignment process in Controlled Sales Core from an end-user perspective. The focus is shipment handling, transport creation, and process-type behavior.

Business context

At consignment locations, documents are still processed operationally like sales flows, but transport logic classifies them as transfer-oriented where required. This preserves the logistics view of replenishment and transfer-like movement.

Clear split of process roles

Process role	Sales control	Transfer control
Trigger	Customer demand and delivery call-off	Replenishment need at consignment location
Primary function	Start operational shipment and pick process	Execute transfer order for location replenishment
Target documents	Sales-related shipment/pick documents	Transfer-related shipment/pick documents
Business focus	Deliver customer demand on time	Keep location stock availability stable

Required setup for consignment

For a stable process, these setup elements should be maintained consistently:

Transport processing

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page explains how to combine posted shipment data into transport documents, validate them, and complete transport posting safely.

Standard BC setup context

A transport does not replace the shipping process. It consolidates already posted delivery documents into one operational handoff to a carrier or internal transport chain.

Transport sources in Controlled Sales Core are:

posted sales shipments
posted transfer shipments
posted warehouse shipments or shipment-derived lines
in exceptional cases, posted warehouse picks with a sales reference

Depending on the source, the transport process type is handled as Sales or Transfer. At consignment locations, a sales shipment can still be treated as transfer from a business perspective.

Process catalog

Mon, 01 Jan 0001 00:00:00 +0000

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

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

Required depth per process page

The linked detail pages should always include at least:

FAQ

Mon, 01 Jan 0001 00:00:00 +0000

FAQ When should I use delivery call-offs instead of the standard sales process? Use delivery call-offs when customers continuously adjust required quantities and dates against blanket orders. +

Delivery call-offs are the right choice when customer schedules are dynamic and reference data must stay consistent. They support structured quantity/date updates before downstream shipment processing.

FAQ Why do expected lines not appear in dispatch control? In most cases, filter settings or due-date logic do not match current document status. +

Check dispatch control type, filter fields, filter values, and due-date calculation first. Depending on setup, already processed or non-eligible lines are intentionally excluded.

FAQ Why is cumulative received quantity important? It helps keep call-off quantities aligned in sensitive customer supply scenarios. +

If cumulative received quantity is required in setup, users can better align internal and customer-side quantity progression. This reduces mismatches and improves follow-up call-off quality.

FAQ What must be checked before posting a transport? Transport header data, handoff details, and lines must be complete and plausible. +

Verify shipping agent, carrier handoff date/time, delivery date, and included transport lines before posting. Post only when all required transport information is complete.