Purchase Contract

Purpose

Purchase Contracts provide the contractual framework toward vendors in Professional Services. They combine the vendor, duration, project and customer reference, and the concrete contract lines, creating a reliable basis for recurring or planned purchasing scenarios.

Prerequisites

• a vendor with the relevant contact and payment information exists
• project reference and, if needed, customer reference are clarified
• duration, cancellation logic, and the services or items to be procured are defined

Functional focus

Contract header and master-data linkage

The purchase contract stores the contract type, vendor, contact, start and end date, and project or customer reference. This makes the contract not just a purchasing document, but a structured frame for later procurement and assignment processes.

Duration and contract status

Initial duration, follow-up duration, cancellation period, and automatic renewal control how long a purchase contract remains valid and when it can be used for downstream processes. The status determines whether the contract is still in setup or already active for order generation.

Purchase contract lines and service scope

The actual purchasing scope is represented in the purchase contract lines. There you define the type, number, quantity, validity period, and purchase price. Header data is inherited into the lines but can be refined there when needed.

Assignment to sales contracts and purchase-order triggering

Purchase contracts can be linked informatively to sales contracts or individual contract elements. Once activated, they can trigger purchase orders either directly or through batch generation. This keeps the connection between vendor agreements and customer-facing service models transparent.

Outcome

Purchase Contracts connect purchasing, project reference, and contract logic in one shared model. This documents vendor relationships clearly and makes them usable for operational ordering processes.