Periodic activities in sales

Purpose

This page describes the recurring sales activities that must be handled routinely in daily operations. It complements the sales overview with the concrete reports, checks, and exception handling from the legacy wiki documentation.

Typical work rhythm

1. Review imported delivery, detailed, or production-synchronous call-offs.
2. Approve open call-offs in a controlled batch.
3. Register detailed and production-synchronous call-offs.
4. Update material-release and production-release dates on a rolling basis.
5. Execute cancellations according to the real shipping model.

Approve delivery and detailed call-offs

The batch report for delivery and detailed call-offs is the central approval point for still-open call-offs. Without filters, all releasable records are processed. In practice, you should still filter deliberately, for example by customer, plant, ship-to, or order.

The usual sequence is:

1. Open the report for approving delivery and detailed call-offs.
2. Restrict the batch to the business-related subset of documents.
3. Read the preview or protocol instead of simply starting the run.
4. Resolve the protocol errors immediately for all call-offs that were not released.

Typical reasons for a failed release are:

• missing or inconsistent master data
• incomplete item references
• wrong plant, unloading-point, or quality-status information
• price or quantity combinations that are not plausible on the order

Approve production-synchronous call-offs

Production-synchronous call-offs are not only about quantities. The report also compares your delivery progress counters with the customer counters and takes the result into account during approval.

Check these points before the batch run:

• Does the delivery progress counter match the latest order and shipment status?
• Is the scenario really PAB or JIT/JIS and not just a standard detailed call-off?
• Are the sequence or time-slot details already fully imported?

A wrong batch run at this point does not only distort quantities. It can also create misleading progress logic for the later shipping process.

Register FAB and PAB

After review and approval, detailed and production-synchronous call-offs still need to be registered. This step finalizes the pre-processing and applies the desired delivery date to the next operational step.

Use this sequence:

1. Open the report for registering detailed and production-synchronous call-offs.
2. Enter the required delivery date if needed.
3. Transfer only the call-offs that were already checked from a business perspective.
4. Review open detailed call-off lines and order quantities afterwards.

The delivery date is not just a convenience value. It influences which lines become operationally relevant in shipping preparation.

Rolling MF and FF periods

The report for rolling material-release and production-release periods updates the start dates on the affected sales orders. The relevant horizon and start fields must already be maintained on the Automotive FastTab of the order.

Use this run when:

• you work with recurring release windows
• customers expect fixed release horizons
• MF or FF status must be updated continuously on sales lines

The most relevant filters are usually:

• order number
• sell-to customer number

Always review afterwards whether the expected MF or FF status really changed on the affected sales lines.

Delivery cancellation in the standard shipping flow

For a normally posted sales shipment, goods issue can be canceled directly from the posted shipment. The system creates a reversing line with a negative quantity and resets the delivered quantity on the related order.

Important for users:

• the reversal line is part of the same business trace, not a detached side document
• the delivered quantity on the order returns to zero
• the quantity to ship becomes open again
• the delivery progress counter is corrected automatically

If all item lines of the original shipment are canceled, the shipment must additionally be marked as transported. Otherwise it can still appear in transport assignment although it is no longer valid operationally.

Delivery cancellation in EDL or consignment scenarios

In EDL or consignment scenarios, there is often no normal sales shipment because delivery is handled through transfer postings or a comparable stock mechanism. In that case, the classic sales-shipment cancellation is not available.

The typical sequence is:

1. Complete the issue message or current delivery status correctly.
2. Create a sales credit memo.
3. Set the reference to the affected call-off order on the Automotive FastTab.
4. Use the credit-memo action field to define how the delivery progress counter should be corrected.
5. After posting the credit memo, add a new line manually to the automotive sales order.

The last point is critical: the original line is already treated as delivered. To make the demand operational again, you must add a new line with the correct business dates and quantities.

Control points for daily operations

Typical error patterns