Processing delivery and fine call-offs
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 Offcan 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 Offwhen a new delivery call-off should be created for the existing document call-off. - Use
Create Detailed Call Offwhen 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 Transitis 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 Quantityremains 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.
| Value | Meaning | Maintenance/source |
|---|---|---|
| Cumulative received quantity | Customer-confirmed quantity progression | Maintained on the document call-off or delivery call-off and written back on release |
| Cumulative delivered quantity | Internal delivered quantity progression | Created from posted shipments, returns, credit memos, start values, or corrections |
| Quantity in transit | Difference between internally shipped and customer-confirmed received quantity | Displayed as cumulative delivered quantity minus cumulative received quantity |
| Correction | Manual quantity status adjustment | Entered in Cumulative Shipment as Correction |
| Zero setting | Business reset on a defined date | Documented as Zero setting |
In simplified terms, release processes call-off lines by date. For each date, the customer-side quantity status is continued by the call-off line and compared with the shipped or in-transit quantity already considered. This produces the quantity required on the sales line.
For a quick plausibility check in daily processing, the direct net comparison remains important:
Net call-off quantity = Cumulative received quantity - Cumulative delivered quantity - Quantity in transit
Example:
- Cumulative received quantity: 15,000
- Cumulative delivered quantity: 13,800
- Quantity in transit: 400
Result:
Net call-off quantity = 15,000 - 13,800 - 400 = 800
Example:
- Cumulative received quantity: 15,000
- Cumulative delivered quantity including transit: 14,600
- Call-off line for the date: 800
Calculation:
Continued customer quantity = 15,000 + 800 = 15,800
Open demand for the date = 15,800 - 14,600 = 1,200
Quantity to transfer = maximum call-off line, therefore 800
If the already considered delivery status is higher, the system reduces the quantity to transfer. If the demand is already fully covered, no additional sales quantity is created for that date.
Variants and exception scenarios
| Case | System behavior | Procedure |
|---|---|---|
| Existing sales line matches item and date | The line is updated. | Verify quantity and date after release. |
| No matching sales line exists | A new sales line is created. | Check location, date, and quantity on the new line. |
| Blanket line already has linked order lines | Open order quantities are preserved. | Do not delete manually; rerun release. |
| Detailed Call Off matches a blanket order | The blanket line can be converted into an order. | Check the created sales order after release. |
| Detailed Call Off without matching blanket order | The system can create a new sales order from call-off data. | Carefully verify customer, item, and dates. |
| Warehouse documents already exist | Lines are not removed or reduced blindly. | Clarify warehouse documents before further changes. |
Ignore Qty. In Transit is enabled |
In-transit quantity does not reduce call-off quantity. | Use only when the customer quantity status should be processed without transit deduction. |
| Cumulative shipment correction | The latest delivery call-off is rereleased after correction. | Verify the resulting sales lines. |
Process Blanket line without operational sales line Dispatch control can create operational sales orders from selected blanket lines.
- Depending on the dispatch control run, the work list can process both sales order lines and blanket order lines.
Create Documentfirst creates a sales order for the selected blanket order lines.- The selected quantity is transferred as
Qty. to Shipto the newly created order lines. - Dispatch control then creates the shipment or picking documents based on those order lines.
- Practical rule: The delivery call-off remains business-leading, but operational line creation can happen during the dispatch control run.
Review and documentation rules for cumulative quantities
Process Review quantity status before release Cumulative received quantity, cumulative delivered quantity, and in-transit quantity must fit together.
- Review cumulative received quantity, cumulative delivered quantity, and quantity in transit in the document call-off context.
- Clarify visible deviations before releasing the next delivery or fine call-off.
- Document the aligned customer and system status for follow-up questions.
Process Perform correction or zero setting traceably Corrections and zero settings need an agreed business reason.
- Enter corrections only with a traceable reason.
- After corrections, review the resulting available call-off quantity.
- Release call-offs only after the quantity status is plausible again.
- Use zero settings only on agreed business cutoff dates, for example at year-end.
- Record date and reason internally and then verify the starting values for the new cycle.
Process Detect warning signs early Unusual quantity statuses should be clarified before the next release.
- Call-off quantities look unexpectedly too small or too large.
- Releases fail although the document data looks plausible.
- Quantities in transit remain unchanged for a longer period.
Common error patterns
Process Missing cumulative received quantity Release is blocked when mandatory logic is active and transit is not ignored.
- Cause:
Cumulative Received Quantity Requiredis active, but cumulative received quantity is empty or 0. - Impact: The delivery call-off is not released.
- Fix: Enter the customer-side quantity status or check the intended transit logic, then release again.
Process Call-off number is invalid New call-off numbers must fit the latest valid call-off state.
- Cause: The new call-off number is empty, lower than the latest call-off state, or not continued plausibly.
- Impact: Release is aborted.
- Fix: Compare the call-off number with the latest released state and correct it.
Process Reference or document call-off is not unique Duplicate references prevent clean assignment.
- Cause: Reference number, customer, plant, or unloading point lead to more than one possible document call-off.
- Impact: The system cannot assign the call-off to one clear processing context.
- Fix: Consolidate references and define unique rules per customer/item.
Process Contract period or item status prevents release Blocked items or call-offs outside the contract period stop processing.
- Cause: The item is blocked, does not exist, or the call-off date is outside contract start and contract end.
- Impact: Release is prevented before sales lines are changed.
- Fix: Correct item master data or contract data and review the call-off again.
Completion checklist
- Document call-off, reference, plant, and unloading point are unique.
- Delivery or fine call-off contains plausible dates and quantities.
- Cumulative received quantity, cumulative delivered quantity, and in-transit quantity are aligned.
- Call-off number and call-off date match the latest released state.
- Call-off status is
Released. - Sales lines were updated or created as expected.
- Exceptions and corrections are documented in the team process.
- Dispatch control, consignment, or transport can continue with the released lines.
Result
- Delivery and fine call-offs are traceable from demand notification to operational processing.
- Blanket order, document call-off, sales line, and cumulative quantities stay aligned.
- Dispatch control and warehouse processing receive reliable released quantities.
- Corrections, zero settings, and rereleases are controlled and traceable.
Links