Managing purchase contracts in SAP S/4HANA Fiori

SAP S/4HANA lets you create and maintain purchase contracts in Fiori — from a template, a model specification, or an Excel upload — and manage prices and items at scale. The core app is Manage Purchase Contracts (F1600A).

Creating a contract

A purchase contract can be set up from several starting points:

• From a template / reference contract — copy an existing contract as the basis.
• From a Model Product Specification — convert an MPS straight into a contract, carrying its items and structure.
• From an Excel upload — load items in bulk.

Items are typically lean-service products or materials, each with price conditions.

Prices and validity periods

Contract items carry net price conditions with multiple validity periods, so prices are time-dependent. A common convention: the prices valid on the contract's start date count as the base prices, with later periods layered on top (for example for indexation). This lets one contract hold a full price timeline rather than needing a new contract per price change.

Managing at scale

Large contracts are maintained efficiently in bulk rather than line by line:

• Mass change within Manage Purchase Contracts (F1600A).
• Excel-based maintenance (app F2669) to change prices per period or add new items/positions, edited in a spreadsheet and uploaded back.

Contract changes can trigger an approval workflow — useful for a four-eyes check or to obtain a supplier's agreement before a change takes effect.

Common questions

Which app manages purchase contracts? Manage Purchase Contracts (F1600A); price/item mass changes via Excel use F2669.

How are price changes over time handled? Through multiple validity periods on the item's price conditions, not separate contracts.

Can I bulk-load a contract? Yes — from a template, from an MPS, or via Excel upload.

---

Related: model product specification · lean services · contract item hierarchies. Want to run contracts well in S/4HANA? Explore our SAP MM training.