Study guide
3.3 Copying Control and Document Flow Between Sales Documents
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.3 Copying Control and Document Flow Between Sales Documents
Key Takeaways Explain This Topic AI
Copying control defines which target document types can be created from which source document types, separately at header, item, and schedule line level.
Each level uses data transfer routines (which fields are copied), copying requirements (conditions that must be met), and switches such as the transfer of item numbers.
The Document flow update field at item level makes the system record referenced quantities or values so that completion rules can update the preceding item's status.
Copying control for sales documents is maintained in VTAA; related tables cover sales to delivery (VTLA), sales to billing (VTFA), delivery to billing (VTFL), billing to sales (VTAF), and billing to billing (VTFF).
Copying requirements and data transfer routines are ABAP routines maintained with VOFM; SAP uses numbers 001-599 and customers use 600-999.
Last updated: October 2026
Copying Control and Document Flow Between Sales Documents
The order-to-cash process is a chain of documents that refer to each other: an inquiry leads to a quotation, the quotation to a sales order, the order to a delivery, and the delivery to an invoice. Copying control is the Customizing that decides which of these references are allowed and what happens to the data when you create a document with reference . The official course calls the copy control tables important elements of your SAP S/4HANA system, because they control many functions executed whenever a document references a preceding one.
What Copying Control Determines
In Customizing, you define the business processes your company needs by deciding which document types can be copied to which other document types. You first define the target document and the source document , and you do this at the level that matches the document structure:
- Level Target and Source Example
- Header Target sales document type ← source sales document type Standard order OR ← quotation QT
- Item Target ← source item category (within the header combination) TAN ← AGN
- Schedule line Target ← source schedule line category CP ← BN
If a header combination does not exist, the business process is not possible: you cannot create the target document type with reference to that source document type.
At each level you maintain three kinds of settings:
Data transfer routines : control which fields of the preceding document are transferred, for example header data, partner data, or business data.
Copying requirements : conditions checked before copying. If they are not met, the system issues a warning or error and, if necessary, stops processing.
Switches : specific controls, for example whether item numbers are transferred from the preceding document (a header switch) or whether the reference must be complete .
At item and schedule line level, the target category is optional. If you enter no target or an invalid one, the system determines the target from the normal item category or schedule line category assignment . Any value you do enter must exist in that assignment, at least as an allowed alternative.
Copying Requirements
Before data is copied, the system checks whether certain requirements are met. The official course gives these examples:
Do the source and target documents have the same sold-to party ?
Is the item being copied already rejected in the source document?
Have the items being copied already been fully referenced ?
Has the validity period of the source document been exceeded?
The data transfer routines run only after the copying requirements are fulfilled. Requirements and routines are ABAP routines, maintained in Customizing for Sales and Distribution under System Modifications → Routines → Define Copying Requirements (transaction VOFM ). In a project, you first check whether the delivered requirements fit. If they do not, a developer creates a copy in the customer number range: routine numbers 001-599 are reserved for SAP , and 600-999 are for customers . A standard example from outline agreements: header requirement 002 ( Header - Diff. Customer ) allows the releasing sold-to party to differ from the contract's sold-to party.
Updating the Preceding Document: Completion Rule and Reference Status
When you create a document with reference, the preceding document must know how much has been referenced. To make this happen, the Document flow update field must be set at item level in copying control (official S46050 content). The system then updates the referenced quantity or value, and the completion rule of the preceding item category decides the status:
Completion rule A : an inquiry item becomes Completed as soon as it is referenced in a quotation, even if only part of the quantity is copied.
Completion rule B : a quotation item becomes Completed only when the complete quantity has been copied into orders. Until then it is Partially referenced , so further orders can be created from it.
Contracts use further rules (target quantity, target value).
Entering a reason for rejection also gives the item the status Completed .
Using Create with Reference
The Create with reference function is available on the initial screen when you create a sales document and on the overview screen during entry. It lets you, for example, combine several quotations of one customer in one sales order . On the reference screen you can copy complete documents or select individual items and quantities.
Process Flow and Document Flow
The result of all references is visible in two forms:
In UI5-based apps such as Manage Sales Orders or Manage Sales Quotations , the chain is shown as a process flow .
In classic transactions such as VA02 , it is shown as the document flow , from which you can branch to each document and back.
For each document in the flow you can display the status overview , for example the delivery status of the order, the picking status of the delivery, the billing status, and the posting status of the billing document. This is the quickest way to find where a process is stuck.
The Family of Copying Control Tables
- Transaction Source → Target Typical Use
- VTAA Sales document → sales document Inquiry → quotation, quotation → order, contract → release order
- VTLA Sales document → delivery Order → outbound delivery (section 7.3)
- VTFA Sales document → billing document Order-related billing, credit memo request → credit memo (section 8.2)
- VTFL Delivery → billing document Delivery-related billing (section 8.2)
- VTAF Billing document → sales document Credit or debit memo request created with reference to an invoice
- VTFF Billing document → billing document Cancellation, invoice list
- Worked Example: Quotation to Order
A customer accepts quotation QT 20000050 for 100 units but orders only 60 now.
In VA01 , you create a standard order with reference to the quotation. Copying control OR ← QT exists, so the reference is allowed.
The header copying requirement checks, for example, that the sold-to party matches and the quotation is still valid. The data transfer routines copy partners and business data.
At item level, TAN ← AGN is maintained with Document flow update set. You copy 60 units.
Because AGN uses completion rule B, the quotation item becomes Partially referenced with 40 units still open. A second order for 40 units makes it Completed .
The process flow in Manage Sales Quotations now shows the quotation with two successor orders.
Tip
If a reference fails with "copying is not possible", check in this order: does the header combination exist in VTAA , does a copying requirement block it (for example, a different sold-to party or an expired validity date), and is the item already fully referenced or rejected?