Study guide

3.6 Value Contracts: Releases, Partner Authorization, Contract Data, and Billing

SAP S/4HANA Sales C_TS462

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: SAP S/4HANA Sales Overview and Enterprise Structure

1.1 SAP Business Suite, SAP S/4HANA Sales, Deployment Options, and User Interfaces 1.2 Sales Organization, Distribution Channel, Division, and Sales Area Architecture 1.3 Sales Office, Sales Group, Plant, Storage Location, and Shipping Point Assignments 1.4 Cross-Company and Multi-Plant Sales Enterprise Setup & SD-FI Integration

2 Chapter 2: The Order-to-Cash Process and Sales Master Data

2.1 The Order-to-Cash Process: Sales Order, Shipping, Billing, and Finance Integration 2.2 Business Partner (BP) Approach, Customer Roles, and Partner Functions 2.3 Material Master / Product Master Sales Views, Tax Classifications, and Unit of Measure 2.4 Customer-Material Information Records (CMIR), Item Proposals, and Cross-Selling

3 Chapter 3: Sales Documents, Copying Control, Presales, and Outline Agreements

3.1 Sales Document Header Architecture and Customizing Sales Document Types 3.2 Special Functions in Sales Documents: Business Data, Blocks, and Reasons for Rejection 3.3 Copying Control and Document Flow Between Sales Documents 3.4 Pre-Sales Processing: Inquiries, Quotations, and Document Validity 3.5 Outline Agreements: Scheduling Agreements, Quantity Contracts, and Release Orders 3.6 Value Contracts: Releases, Partner Authorization, Contract Data, and Billing 3.7 Special Business Processes: Consignment, Rush Orders, Cash Sales, and Free-of-Charge Deliveries

4 Chapter 4: Item Categories, Schedule Line Categories, and Sales BOMs

4.1 Item Category Customizing Controls and Item Category Determination Logic 4.2 Schedule Line Categories and Determination Mechanics 4.3 Bill of Materials (BOM) Explosion in Sales Orders

5 Chapter 5: Pricing and the Condition Technique

5.1 Condition Technique Architecture: Field Catalogs, Tables, and Access Sequences 5.2 Condition Types, Calculation Types, Scales, and Condition Classes 5.3 Pricing Procedure Determination and Calculation Schema Configuration 5.4 Working with Condition Records: Maintenance Tools, Price Lists, Pricing Reports, and Manage Prices 5.5 Special Pricing Functions: Condition Exclusion, Group Conditions, Header Conditions, Condition Update, and Supplements 5.6 Special Condition Types: Manual Net Pricing, Minimum Values, Customer Hierarchy, Pallet Discounts, and Rounding 5.7 Statistical Condition Types and Tax Determination 5.8 Condition Contract Management: Contracts, Business Volume, Accruals, and Settlement

6 Chapter 6: Availability Check (ATP) and Delivery Scheduling

6.1 Availability Check Fundamentals: Checking Groups, Checking Rules, and Scope of Check 6.2 Delivery Scheduling & Routing: Transit Time, Loading Time, and Pick/Pack Time Calculations 6.3 Advanced ATP (aATP), Backorder Processing (BOP), and Transfer of Requirements

7 Chapter 7: Delivery Processing and Embedded EWM

7.1 Delivery Documents and Organizational Units for Delivery Processing, Including EWM 7.2 Shipping Point Determination and Route Determination Mechanics 7.3 Outbound Delivery Creation, Delivery Document Types, and Delivery Item Categories 7.4 Warehouse Execution: Picking, Packing, and Post Goods Issue (PGI) 7.5 Picking and Goods Issue with Embedded EWM 7.6 Inbound Deliveries with EWM and Special Functions in Deliveries

8 Chapter 8: Billing and Integration with Financial Accounting

8.1 Billing Document Types, Categories, and Billing Due List Processing 8.2 Order-Related vs. Delivery-Related Billing, Invoice Splits, and Collective Invoicing 8.3 Credit and Debit Memos, Down Payments, and Invoice Cancellation Workflows 8.4 Special Types of Settlement: Invoice Lists, External Billing Document Requests, and Preliminary Billing Documents 8.5 Billing Plans, Down Payment Agreements, and Installment Payments 8.6 Revenue Account Determination and FI-SD General Ledger Integration 8.7 The Interface Between Sales and Financial Accounting, Billing Output, and Technical Options

9 Chapter 9: Basic Functions: Partners, Incompletion, Texts, Material Determination, and Output

9.1 Partner Determination Procedures and Account Group Linkage 9.2 Incompletion Procedures, Status Groups, and Log Configuration 9.3 Text Control I: Text Objects, Text Types, Text Determination Procedures, and Manual Text Entry 9.4 Text Control II: Automatic Text Transfer, Text Determination Analysis, and Special Features 9.5 Material Determination, Material Listing, and Material Exclusion 9.6 Output Management: Modern BRFplus Architecture and Migration from Classical NAST 9.7 Output Parameter Determination with Decision Tables

10 Chapter 10: SAP Fiori, Sales Analytics, RISE with SAP, and Clean Core

10.1 SAP Fiori Sales Apps, Smart Business Monitoring, and Embedded Analytics 10.2 Working with the SAP Fiori Launchpad: My Home, Spaces and Pages, Help, Joule, Responsibilities, Situations, and Workflows 10.3 RISE with SAP Methodology: Standardized Framework, Transformation Preparation Service, Toolchain, Expert Guidance, and Dashboard 10.4 Clean Core: Definition, Benefits, the Five Principles, and Clean Core Levels

11 Chapter 11: Implementing SAP S/4HANA Cloud Private Edition

11.1 SAP S/4HANA Cloud Private Edition: Characteristics, Transition Paths, and the Implementation Team 11.2 System Landscapes, System Provisioning, and Release Upgrades 11.3 Setting Up the Project in SAP Cloud ALM and Preparing a System Conversion 11.4 Identity and Access Management: Users, Business Roles, Catalogs, Spaces, and Pages 11.5 Fit-to-Standard Workshops, Design Workshops, and Business Process Configuration 11.6 Extensibility in SAP S/4HANA Cloud Private Edition: Key User, Developer, and Side-by-Side 11.7 Integration: ISA-M, SAP Integration Suite, Prepackaged Content, and Monitoring 11.8 Data Migration with the SAP S/4HANA Migration Cockpit and Testing in SAP Cloud ALM

3.6 Value Contracts: Releases, Partner Authorization, Contract Data, and Billing

Key Takeaways Explain This Topic AI

A release order releases part of the agreed total value of a value contract; it is a sales order created with reference to the contract.

Release orders can be created in any currency, but the contract value is updated in the contract currency, and the system compares the release value with the open value of the contract.

Assigning an order to a contract later is possible at header and item level; pricing is rerun in both cases, but the contract values are updated only for an item-level assignment.

The Check partner authorization field in the sales document type controls who may release: rule A uses a customer list (partner function AA, alternative ship-to AW), rule B the customer hierarchy.

You can bill each release order (order-related or delivery-related) or bill the value contract itself with order type WA, also through a billing plan.

Last updated: October 2026

Value Contracts: Releases, Partner Authorization, Contract Data, and Billing

A value contract is an outline agreement in which the customer commits to buying goods or services for a total value within a period, rather than a fixed quantity of specific materials. The S46051 course spends 100 minutes on value contracts, more than on scheduling agreements and quantity contracts together, because value contracts combine several mechanisms: releases, value tracking, partner authorization, contract data, and billing. In the standard system, the general value contract WK1 can be restricted to the materials of an assortment module , while the material-related value contract WK2 refers to specific materials. Value contract items are completed after the full target value has been referenced (completion rule E ).

Releases Against a Value Contract

A release order releases a partial amount of the agreed total value. It is a normal sales order type (the standard order OR can be used) created with reference to the contract. The official course lists the key rules:

Finding the contract : you can search for suitable contracts using the partner number , or, for customer lists, search for suitable partners using the contract number .

Selecting items : the item selection function shows all valid materials. You choose materials directly or by exploding an assortment module .

Delivery data : quantities and dates are stored in the schedule lines of the release order , not in the contract.

Currency : releases can be created in any currency , but the total value is updated in the currency of the contract .

Checks : when you create a release order, the system checks the contract's requirements, such as the release rule and the validity period , and compares the value of the release with the value still open in the contract. You define how the system responds when the open value is exceeded (for example, a warning or an error).

Assigning an Order to a Contract Later

An order that was entered without reference can be assigned to the contract retrospectively, at header level or at item level . In both cases, the system reruns pricing automatically, so contract prices apply. However, the values in the contract are updated only when the assignment is made at item level . A header-level assignment changes the order's pricing but does not reduce the open contract value.

Partners Authorized to Release

Often several partners may release from one contract: the central office of a company decides which branches may order, and there can be several ship-to parties. You control this with the Check partner authorization field in the sales document type of the contract:

Rule Meaning How Partners Are Maintained

A Check contract partners (customer list) Partners authorized to release are stored in the partner screen of the contract with partner function AA (optional in the standard procedure KAB ). Alternative ship-to parties use partner function AW .

B Check via customer hierarchy All customers below the contract's node in the customer hierarchy may release.

Further rules from the course:

The partner determination procedure assigns the partners authorized to release.

If several partners are authorized, you choose the releasing partner from a list when creating the release order; the same applies to several authorized ship-to parties.

If the customer master of the sold-to party already contains several sold-to parties (functions SP and AA), a selection screen appears when the contract is created, so you can copy several partners in one step.

Partners authorized to release are checked at header level only .

Because the releasing sold-to party can differ from the contract's sold-to party, copying control uses requirement 002 (Header - Diff. Customer) instead of the standard header requirement.

In sales documents, normally only one partner can be assigned to each partner function; outline agreements with AA and AW are the exception.

Contract Data: Dates, Duration, and Contract Profiles

Contracts carry contract data that a normal order does not need: start and end dates, a duration, cancellation rules, and follow-up actions. The course explains how much of it can be proposed automatically:

Date determination rules , defined in Customizing, start from a date you choose (for example, today's date or an installation date), can add an interval, and can move the result to the beginning or end of a month.

A duration category generates the duration of the contract automatically and can be part of a date rule, for example to determine the contract end.

A contract profile assigned to the sales document type proposes contract-specific defaults: the rules for the start and end of the contract, the duration category, subsequent activities , and the cancellation procedure .

Contract data can be maintained at header level and, where needed, differently for individual items.

Billing a Value Contract

The course describes two billing approaches:

Approach How It Works Typical Use

Bill each release order Use the standard order OR as release order; billing is order-related or delivery-related like any order Customer receives an invoice per release

Bill the value contract In the standard system, order type WA is used for the release, and the value contract itself is billed according to the order Customer receives invoices from the contract

A billing plan in the contract lets you bill for several dates and partial amounts at once (section 8.5). If you later change the target value of a contract item, the system automatically adjusts the open billing dates. The system does not allow you to bill value contracts automatically that have not been completely released.

Worked Example

A customer signs a value contract WK1 for 50,000 EUR of spare parts in calendar year 2027, restricted to an assortment module, with check partner authorization rule A .

The contract lists the head office as sold-to party and three branches with partner function AA, plus two alternative ship-to parties with AW.

Branch 2 places a release order in USD for parts worth 8,000 EUR. The system checks that branch 2 is authorized (header level), that the parts belong to the assortment module, and that the release is within the validity period. The release value is converted and updated in EUR, leaving 42,000 EUR open.

A later order for 3,000 EUR was entered without reference. You assign it to the contract at item level : pricing is rerun with the contract prices, and the open value drops to 39,000 EUR. Had you assigned it only at header level, the prices would change but the open value would stay at 42,000 EUR.

Each release order is delivered and billed separately with delivery-related billing.

Tip

Releasing partner differs from the contract's sold-to party and copying fails? Check that copying control for the release order uses header requirement 002 , and that the partner is maintained with function AA in the contract.