Document Type Configuration and Copy Control Between Sales Documents
Learn how sales document type configuration and copy control rules determine what data is carried forward, blocked, or recalculated when moving between quotations, orders, and contracts.
Explanation
Document type is the primary configuration object that defines the behavior of a sales document at the header level: number ranges, whether a document requires a sold-to party check, screen sequence group, whether it is relevant for credit management, whether it defaults to a particular sales document category (inquiry, quotation, order, contract), and which item category and schedule line category proposals apply through determination tables. Standard document types like a standard order or a quotation type serve as templates that most projects adapt through custom Z-document types rather than modifying SAP-delivered ones directly, preserving upgrade safety. A critical, often underestimated area within document type configuration is copy control (also referred to as copying requirements/control), which governs how data flows when one sales document is created with reference to another — for example, creating a sales order with reference to a quotation, or a contract release order referencing a contract. Copy control is configured at three levels mirroring the document structure: header level copy control (does the new document copy the business partner data, do quantities need to be checked against the source), item level copy control (which item category is proposed in the target document, whether pricing is copied or redetermined, whether quantity is copied or must be re-entered), and schedule line level copy control (whether original confirmed schedule lines are copied or fresh availability check is triggered). A key configuration decision within copy control is the pricing type — this determines whether pricing conditions are copied as-is from the source document, fully redetermined, or partially redetermined (e.g., copy fixed conditions like manual discounts but redetermine tax and freight). Getting pricing type wrong is one of the most common causes of pricing discrepancies between a quotation and the resulting order, particularly when time-sensitive conditions (like a promotional discount) have expired between quotation creation and order conversion. Copy control also includes routines (VOFM-based logic in ECC, and correspondingly BAdI-driven or routine-driven logic in later releases) that can enforce business rules — for instance, blocking copy if the source document is not yet released, or requiring a minimum order value before allowing conversion from quotation to order. These routines are a frequent source of custom development in real projects because standard copy control only covers structural data flow, not sophisticated business validation. In S/4HANA, the underlying configuration transactions and concepts for document type and copy control remain largely consistent with ECC, since this is core, stable SD functionality; however S/4HANA public cloud typically restricts direct access to some copy control configuration behind pre-delivered scope items and configuration apps, meaning consultants in a public cloud engagement may need to work within SAP-delivered Business Configuration content rather than freely creating custom copy control entries, unlike the largely unrestricted access typical in on-premise and private cloud implementations. Consultants should validate current system capability directly rather than assuming full parity with ECC-style configuration freedom in public cloud.
Real project scenario
A retail distribution client reports that sales orders created by referencing an approved quotation show a different total value than the quotation itself, causing customer complaints. Investigation traces the discrepancy to the copy control pricing type between quotation and order document types, which was configured to fully redetermine pricing rather than copy the quotation's fixed manual discount condition. The consultant proposes changing the pricing type to copy manual conditions while still redetermining tax, and validates the fix in a test client against multiple scenarios including expired promotional pricing before promoting the change.
Common mistakes
• Modifying SAP-standard document types directly instead of copying them to custom Z-types, risking issues on system upgrades or support pack updates. • Choosing a copy control pricing type that fully redetermines pricing without considering that manually entered discounts will be lost in the target document. • Forgetting to configure copy control at all three levels (header, item, schedule line) and assuming header-level configuration is sufficient. • Not testing copy control changes against edge cases like partially delivered source documents or documents with rejected items. • Assuming public cloud S/4HANA offers the same unrestricted copy control configuration access as on-premise without verifying current scope item constraints.
Best practices
• Always create custom document types by copying SAP standard types rather than modifying them directly. • Explicitly define pricing type in copy control based on business need — copy fixed conditions for negotiated deals, redetermine for standard catalog pricing. • Configure and test copy control at header, item, and schedule line levels together rather than assuming header settings are sufficient. • Maintain a decision log recording why each copy control combination was chosen, to support future audits and consultant handovers. • In public cloud environments, confirm current configuration scope before committing to a design assuming on-premise-level flexibility.
Interview angle
Candidates are often asked to explain the difference between copying pricing versus redetermining pricing when converting a quotation to an order, and to describe a real scenario where getting this wrong caused a customer-facing issue — this tests both configuration knowledge and practical judgment about business impact.