Copy Control and Document Flow Chains Between Sales Documents

Explanation

Copy control is the configuration backbone that determines what happens when a user creates a sales document with reference to another document - for example a quotation copied into a sales order, or a sales order copied into a returns document. Without correctly configured copy control, header and item data would not transfer, pricing would not redetermine correctly, and the document flow (the linked chain visible in VA03 document flow display) would break, making it impossible to trace an order back to its quotation or forward to its delivery and billing documents. Copy control exists at three levels: header level (controls whether copying is allowed at all between two document types, and general data transfer routines), item level (controls per item category what quantity, pricing, and configuration data is copied, plus item-specific requirement and data transfer routines), and schedule line level for certain document type combinations. The configuration is maintained per source document type and target document type pair - for instance quotation type QT to order type OR, or order type OR to returns type RE. Key control fields include: copying requirements (a routine that checks whether copying is permitted, for example blocking copy if the source document is not released or is blocked), data transfer routines (which fields and how values like pricing, quantities, dates are transferred or redetermined), and update document flow indicator (whether the target document is recorded in the source document's flow history). Quantity and value copying can be configured as cumulative (deducting already-copied quantities so a quotation is not over-fulfilled) or positive/negative for returns and credit scenarios. Pricing type is a critical copy control field. It decides whether pricing conditions are copied as-is from the source (freezing prices agreed at quotation), redetermined completely from current condition records, or partially redetermined (keeping manual conditions but refreshing tax or freight). Getting pricing type wrong is one of the most common production issues - for example copying a quotation price into an order six months later without redetermination, causing the customer to be charged outdated prices. Document flow itself is stored as a chain of preceding and subsequent document references. Each sales document, delivery, and billing document carries links back to its predecessor. This is what powers the document flow report and is essential for support: when a billing block or delivery discrepancy is reported, the first troubleshooting step is almost always to check document flow to see whether the expected delivery or billing document was even created, and if not, whether copy control or status blocked its creation. In S/4HANA, copy control configuration paths and underlying logic remain largely consistent with ECC, though S/4HANA introduces some simplification in how certain document categories interact, and Fiori apps for document flow display present the same underlying chain in a more consumable list format. Copy control itself is still configured through the same customizing objects; there is no fundamentally new engine, but consultants should verify behavior in each system since custom routines are frequently modified per client. Understanding copy control is essential for anyone configuring new document type combinations, diagnosing why a document did not copy as expected, or explaining to business users why quantities or prices behave differently when creating one document type from another.

Code example

Example copy control entries (illustrative, not exhaustive): Header level: Source Doc Type = QT (Quotation), Target Doc Type = OR (Standard Order) Copying requirements = check quotation validity/release status Data transfer routine (header) = 001 (general header data) Item level: Item Category = AGN (quotation item) -> TAN (standard order item) Data transfer routine (item) = 151 (general item data, incl. plant/quantity) Pricing type = B (carry over pricing elements, redetermine taxes) Copy quantity = cumulative (deduct already copied quantity from quotation) Header level: Source Doc Type = OR (Standard Order), Target Doc Type = RE (Returns) Copying requirements = check billing status is complete before allowing return Pricing type = D (copy pricing elements unchanged, no redetermination)

Real project scenario

A distribution company configured a new contract-to-order copy control combination to let sales reps convert framework agreements into orders. During UAT, testers noticed that a second order created from the same contract line still allowed the full contract quantity to be ordered again, effectively double-fulfilling the contract. Root cause was that the copy control item category was not set to cumulative quantity copying, so it never tracked how much had already been drawn down. The fix involved correcting the data transfer routine and quantity copying settings, followed by regression testing across all existing contract types to confirm no other combination had the same gap.

Common mistakes

• Configuring copy control to redetermine pricing fully when the business requirement is to honor quotation prices, or vice versa, causing customer billing disputes • Forgetting to activate document flow update on a custom document type combination, making downstream tracing impossible for support teams • Not setting cumulative quantity copying for reference-based scenarios (quotation to order, contract to order), leading to over-fulfillment • Copying requirements routines that are too permissive, allowing copies from documents that are incomplete, blocked, or already fully referenced • Assuming copy control changes only affect new documents; not testing impact on documents already in flight during a mid-project configuration change

Best practices

• Always test copy control changes with both first-time and repeat copy scenarios (e.g., partial then full quantity draw-down) • Document the business rationale for each pricing type choice so future consultants do not accidentally reverse it • Keep copy control requirement routines readable and centrally documented, since they are often custom Z-routines with limited inline documentation • Validate document flow visibility end-to-end after any copy control change, not just the immediate target document • Coordinate copy control changes with FI/billing teams since pricing type decisions affect revenue recognition and invoice accuracy

Interview angle

Interviewers use copy control questions to test whether a candidate understands SD beyond transaction-level clicking. Be ready to explain the difference between header, item, and schedule line copy control, what pricing type options mean in practice, and how you would troubleshoot a scenario where a follow-on document is missing expected data or was not created at all - the expected answer path is always to check document flow first, then copy control configuration, then the specific data transfer or requirement routine involved.