SAP SD Copy Control Design Worksheet
Copy control decides what moves from one SD document to the next: items, quantities, prices, texts and checks. This worksheet lists each path so you design it once, review it with the business and then configure it.
| Flow | Config t-code | Source type | Target type | Source item cat. | Target item cat. | Pricing type | Copy requirement | Check quantities | Business reason | Priority (1-3) | |
|---|---|---|---|---|---|---|---|---|---|---|---|
Document type and item category codes shown are common SAP standard examples (OR standard order, LF delivery, F2 invoice, RE returns, G2 credit memo, QT quotation). Confirm all codes and routine numbers in your own system.
Extract your live copy control setup
Optional: ask Netray how to pull current copy control settings into a reviewable sheet.
Optional. The tool and every export work without this. No spam.
How to use the worksheet
Add a row for every source and target combination in your process, including item category pairs. Record the pricing type, any copy requirement or data transfer routine, and why the path exists. Export the sheet, review it in a workshop, and use it as the checklist while you configure each path. It also makes later audits much easier because the intent is recorded.
The four copy control tables
VTAA covers sales document to sales document, such as quotation to order or order to returns. VTLA covers sales document to delivery. VTFA covers sales document to billing, for example credit memo from a returns order. VTFL covers delivery to billing. Each has a header level for document types and an item level for item categories, and many fields allow routines assigned in VOFM.
- Header level: document type pair
- Item level: item category pair
- Routines control data transfer and checks
- Pricing type decides repricing
Reading the result
Sort by flow and look for gaps. Every document type that can be delivered needs an order to delivery path, and every deliverable item category needs a delivery to billing path, or the user sees an error when creating the next document. Review rows with Carry out new pricing, because they can change the invoice value after an order was confirmed to the customer.
Common mistakes
Common faults are copying a standard path and forgetting the item category level, enabling new pricing where the price must stay fixed, relying on custom routines nobody documented, and not checking billing quantity handling after partial deliveries. Test every row with a real document, including partial delivery, returns and cancellation, before the transport leaves development.
Frequently Asked Questions
What is the difference between VTAA and VTLA?
VTAA defines copying between sales documents such as quotation to order. VTLA defines copying from a sales document to a delivery. Both have header and item level settings, and each pair of types needs its own entry.
What does pricing type do?
It controls whether the target document keeps the source pricing, redetermines it fully, redetermines only freight conditions, or copies manual conditions. The choice affects whether invoice value can differ from the order.
Where are copy routines maintained?
Routines are created with transaction VOFM and assigned in the copy control entries. They are ABAP routines, so changes need a developer and a transport, and each routine should be documented.
Why can I not create a delivery from my order?
Frequent causes are a missing copy control entry for the document type, no item category pair, a delivery block or incompletion, no delivery type determined for the order type, or the item having no schedule lines for delivery.
Netray can read your existing copy control tables and produce a first matrix for review, so you start from what is configured today rather than from memory.
Related Tools
SAP SD Enhancement Functional Specification Template
A fill-in functional spec for SD enhancements: requirement, trigger point, logic rules, data touched, test cases and sign-off. Exports to PDF or Word.
SAPSAP SD Partner Determination Design Template
Document your partner functions, partner determination procedures and sources per document level, then export a design page for review.
SAPSAP SD Transaction Codes Reference
A searchable list of common SAP sales and distribution transaction codes, grouped by process area, for daily use and onboarding.
SAPSAP SD Customer Master Sales Area Load Worksheet
Collect sales area data per customer: sales org, channel, division, shipping, incoterms, payment terms and tax classification, then export to Excel.