Study guide

2.1 The Order-to-Cash Process: Sales Order, Shipping, Billing, and Finance Integration

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

2.1 The Order-to-Cash Process: Sales Order, Shipping, Billing, and Finance Integration

Key Takeaways Explain This Topic AI

A standard sales process can be delivery-related (stock material, billed after goods issue) or order-related (services, billed from the order), and one order can mix both.

To create a sales order you enter the sold-to party, material, and quantity; the system proposes header, item, and schedule line data, checks availability, and transfers requirements.

An outbound delivery has a header and items but no schedule lines; each due schedule line of the order can become a delivery item.

Posting goods issue updates inventory and requirements, posts the inventory value change, creates accounting and controlling documents, adds the delivery to the billing due list, and updates document statuses.

Saving a billing document posts to the general ledger, creates CO-PA documents, updates sales statistics and credit data, and updates the status of all related documents.

Last updated: October 2026

The Order-to-Cash Process: Sales Order, Shipping, Billing, and Finance Integration

Every configuration setting in this guide serves one end-to-end process. The S46000 course introduces it with three people: Sally from sales creates the sales order, Mark from shipping creates the outbound delivery and posts goods issue, and Felix from billing creates the invoice. Accounting then posts the customer's payment. Each step creates a document that refers to the previous one, which is why SAP calls the chain the document flow . Presales Sales order Shipping Billing Finance

  • Inquiry ----> Sales order ---> Outbound delivery ---> Invoice ---> Incoming payment
  • Quotation (sourcing) Picking, packing, GI Posting to FI Clearing
  • Two Ways to Set Up the Process

The official course names two basic process variants for a standard sales order:

Delivery-related process : a physical, usually inventory-managed product (the course uses a bike) goes through shipping. It is billed after shipping is complete and goods issue has been posted.

Order-related process : a service product, such as consulting or a repair, does not go through shipping. The billing process is triggered directly from the sales order.

Both can be combined: a mixed order contains materials and services, and each product is scheduled for its own follow-on processing. Technically, the item category of each item decides which variant applies (section 4.1).

Creating the Sales Order

When creating a sales document, such as an order or a quotation, you first assign it to a sales area (sales organization, distribution channel, division). Every sales document must contain a customer number and at least one item with a material number . As a sales representative, you enter only the sold-to party , the material , and the order quantity ; the system does the rest:

Entering the sold-to party fills the header data , such as terms of payment and Incoterms.

Entering material and quantity fills the item data , such as pricing.

The schedule line data , such as delivery dates and quantities, follows automatically.

The system checks availability for the requested delivery date and, if necessary, transfers requirements to materials planning.

The system completes the billing information .

All of this works only if the system is set up properly and the master data exists.

Document Structure

A sales document has three levels:

  • Level Content Rule
  • Header Data valid for the whole document, such as document number and sold-to party One header per document

Item Material, quantity, and item-specific data; items can be controlled differently (material item, service item, free-of-charge item, text item) Any number of items

Schedule line Confirmed delivery quantities and dates Every item that is physically delivered needs at least one schedule line; partial deliveries create several

Some header data, such as the ship-to party, can also be maintained at item level; the item entry then drives the follow-on processes.

Sourcing the Ordered Material

Before the material can be delivered, it must be sourced. The process is organized in Materials Management, and the course names three ways:

Directly from stock , if stock exists.

External procurement from a vendor, through a purchase requisition or purchase order.

In-house production , through a planned order or production order.

Shipping: Outbound Delivery and Goods Issue

The outbound delivery is the first step of shipping and the basis for all shipping activities. It controls, supports, and monitors picking (optional), packing (optional), transportation planning with freight orders in SAP S/4HANA Transportation Management (optional), and posting goods issue . It is created with reference to at least one sales order, so material and quantity are copied.

A delivery has two levels, header (ship-to party, deadlines) and item (material, quantities, weights, stock data). Unlike the sales order, it has no schedule lines : each schedule line in the sales document can become an item in the delivery.

The goods issue document is created from the delivery and cannot be changed manually; changes must be made in the delivery. Posting goods issue triggers these updates automatically:

Inventory management and requirements : stock quantity reduced, delivery requirement in planning removed.

Material ledger / balance sheet : the inventory value change is posted, based on the material's cost.

Accounting and controlling documents are created.

Billing due list : the delivery becomes due for billing.

Document flow : the status of all related documents is updated.

In the course exercise, the stock of the material drops from 1,000 to 995 pieces after goods issue for 5 pieces, which you can check in the Stock - Single Material app.

Billing and the Integration with Finance

Billing can be done manually, automatically, or in a background job. It supports creating invoices for goods and services, cancelling posted billing documents, and transferring billing data to accounting automatically. For physical products, the billing document refers to one or more outbound deliveries ; for services, to sales orders . The system can combine several documents in one billing document if relevant characteristics are the same, for example the payer , the billing date , and the destination country . The main billing document type is the invoice ( F1 or F2 ).

When the billing document is saved, the system creates:

Postings on general ledger accounts (receivable, revenue, output tax).

Controlling documents , such as for profitability analysis (CO-PA).

An update of sales statistics in SAP S/4HANA embedded analytics or SAP BW/4HANA.

An update of the customer's credit data , if credit management is used.

A status update of all related sales, delivery, and billing documents.

Posting the incoming payment is done in Financial Accounting: it posts payments against invoices and reconciles differences, with a debit to the cash (bank) account and a credit to the customer's receivables account . Strictly speaking, this is not part of the core sales process, but unpaid invoices can affect it if the credit line is checked during order entry.

Linking the Documents: Document Flow and Process Flow

Each business step is represented by a specifically designed document type: sales document types (inquiry, quotation, standard order), delivery types (outbound delivery, returns delivery), and billing types (invoice, credit memo, debit memo). Each document has a unique number and an overall status derived from the status values of its processing steps. SAP S/4HANA displays the chain of documents as a process flow in SAP Fiori apps such as Manage Sales Orders , and as the document flow in classic transactions such as VA02 or VA03 . From either view, you can check the history and the current status of every document in the chain.

Step Document What the System Does

Sales order Sales document (e.g., type OR ) Proposes data, prices the items, checks availability, transfers requirements

Delivery Outbound delivery (e.g., type LF ) Copies due schedule lines, supports picking and packing

Goods issue Material and accounting documents Reduces stock, posts the inventory value change, makes the delivery due for billing

  • Billing Invoice (e.g., type F2 ) Posts receivable and revenue, updates CO-PA and statistics
  • Payment FI payment document Clears the receivable

Note

The rest of this guide configures each step: sales document types, item categories, and schedule lines (chapters 3 and 4), pricing (chapter 5), availability and scheduling (chapter 6), shipping (chapter 7), billing (chapter 8), and basic functions such as partners, incompletion, texts, and output (chapter 9).

Loading diagram... Order-to-Cash Document Flow in SAP S/4HANA Sales