Scheduling agreements and delivery schedules

Scheduling agreements and delivery schedules in SAP S/4HANA Cloud Public Edition

Automotive supply runs on longer-term agreements and frequent call-offs rather than on individual purchase orders and sales orders. A customer and a supplier agree on a part, a price, and a total or open quantity over a program's life, and the customer then releases actual requirements over time as forecast and short-term call-offs. SAP S/4HANA Cloud Public Edition models this pattern with scheduling agreements and delivery schedules on both the sales and the procurement side. For an automotive supplier, these objects are the backbone of order handling, and understanding how the public cloud edition delivers them is central to a fit-to-standard design.

This article describes sales scheduling agreements, procurement scheduling agreements, and the delivery-schedule types that carry the call-off quantities, and it explains how those schedules drive material requirements planning. It focuses on what is available in SAP S/4HANA Cloud Public Edition. Just-in-time and just-in-sequence processing, which builds on delivery schedules but has its own boundary in the public cloud edition, is covered in a companion article and referenced where relevant.

Sales scheduling agreements

A sales scheduling agreement is an outline agreement with a customer under which the supplier delivers against schedules the customer transmits over time, rather than against separate sales orders. In SAP S/4HANA Cloud Public Edition, sales scheduling agreements carry delivery schedules that come in distinct types:

  • Forecast delivery schedules, which give a medium-term view of the customer's anticipated requirements and support the supplier's planning without each line being an immediate shipping instruction.
  • Just-in-time delivery schedules, which provide short-term, near-firm requirements for the coming days, at a finer time granularity than the forecast schedule.
  • Planning delivery schedules, which the system can generate internally to smooth or consolidate the externally received schedules into a stable planning signal.

A supplier can operate with forecast schedules only, or with forecast and just-in-time schedules together, depending on how its customers transmit requirements. The delivery due from a schedule is fulfilled through the standard outbound delivery process, picking, packing, and goods issue, integrated with inventory and, where used, handling-unit management. SAP has published public cloud enablement material aimed specifically at automotive suppliers that walks through the sales scheduling agreement, its delivery schedule, and the subsequent planning run, which confirms that SAP positions this model for automotive suppliers on the public cloud edition.

Two practical points belong in any design. First, the schedules a customer sends usually arrive electronically; in SAP S/4HANA Cloud Public Edition that exchange is handled through cloud integration rather than the on-premise IDoc model, as described in the supplier-collaboration companion article. Second, the specific best-practice scope item and release that deliver sales scheduling agreements should be confirmed in current SAP documentation for the target release, because the sales-side content has been built up over successive public cloud releases.

Procurement scheduling agreements

On the buying side, an automotive supplier frequently needs to call off its own direct materials against longer-term agreements with sub-tier suppliers, mirroring how its customers call off from it. SAP S/4HANA Cloud Public Edition supports this through scheduling agreements in procurement, delivered as a standard scope item, with variants that use release documentation and variants that do not. Release documentation separates the agreement from the individual schedule releases sent to the supplier, which suits a controlled, auditable call-off process; the simpler variant issues schedule lines directly. SAP notes that the single-item configuration of these agreements is particularly beneficial for industries such as automotive.

Procurement scheduling agreements connect directly to planning. The procurement of direct materials scope item is built so that when material requirements planning identifies a shortage for a material covered by a scheduling agreement, it creates schedule lines against that agreement rather than standalone purchase requisitions. The result is a continuous call-off flow to the sub-tier supplier that follows the supplier's own demand, without a buyer re-creating a purchase order for each requirement.

The releases sent to the sub-tier supplier can be transmitted electronically through SAP Business Network, where the source-to-pay integration explicitly supports scheduling agreements and scheduling-agreement releases. This lets the automotive supplier operate its upstream supply on the same call-off logic that governs its downstream customer relationships.

How delivery schedules drive planning

Scheduling agreements are valuable precisely because their schedules feed the same planning engine that governs the rest of the supplier's operation. Requirements from sales scheduling agreements enter material requirements planning as independent requirements, alongside forecasts and any discrete sales orders. Material requirements planning then nets these requirements against stock and receipts and generates planned orders for in-house production and schedule lines or purchase requisitions for procured materials.

Because SAP S/4HANA Cloud Public Edition uses MRP Live, a planning run designed for large data volumes on in-memory computing, planning can be executed frequently, which matters when automotive call-offs change often. The general mechanics of planning, production execution, and costing are described in the Product Centric manufacturing article and are not repeated here; the automotive-specific point is that the call-off, whether a customer's forecast schedule or the supplier's own procurement schedule, is the demand signal that starts that chain.

A stable planning signal is important in automotive, where short-term call-offs can be volatile. Planning delivery schedules and the review of exception messages let planners work from a consolidated, smoothed view rather than reacting to every fluctuation in the raw customer schedule. Where more advanced constrained scheduling is required than MRP Live provides, SAP offers extended planning as a separate solution, which should be assessed during solution design rather than assumed to be part of core scope.

Scope, boundaries, and design decisions

Scheduling agreements and delivery schedules are standard functionality in SAP S/4HANA Cloud Public Edition, and they cover a large part of an automotive supplier's order-handling requirement. Several design decisions determine how well the standard model fits:

  • Schedule types in use. Confirm whether customers send forecast schedules only or forecast and just-in-time schedules, and whether internally generated planning delivery schedules are needed to stabilize the signal.
  • Release documentation on the procurement side. Decide whether procurement scheduling agreements need release documentation for auditability, or whether direct schedule lines are sufficient.
  • Electronic exchange. Plan how schedules are received from customers and sent to sub-tier suppliers through cloud integration, covered in the supplier-collaboration article.
  • Just-in-time and just-in-sequence. Where call-offs must trigger sequenced production or delivery, review the boundary described in the just-in-time and just-in-sequence article, since the full engine is not native to the public cloud edition.
  • Scope-item and release confirmation. Verify the relevant scope items and their current availability in SAP Signavio Process Navigator or SAP for Me for the target release; procurement-side scheduling agreements and procurement of direct materials are well established, and the sales-side content should be confirmed for the release in question.

Approached this way, scheduling agreements let an automotive supplier represent its real customer and supplier relationships in SAP S/4HANA Cloud Public Edition, with delivery schedules driving planning and execution through the standard, integrated process.