SAP SD copy control is the configuration that decides which data is transferred, and under which conditions, from one sales document to the next: quotation to order, order to delivery, delivery to invoice. If an invoice shows a different price from the order, a missing text or a wrong quantity, the cause is very often here.
Document flow: the links in the chain
In SD every document is created with reference to a preceding one, and these links are stored in the document flow. The typical chain is quotation, order, delivery, goods issue, invoice and accounting document. The document flow shows which order an invoice came from, or how much of an order has been delivered; it is essential for audits and troubleshooting.
Levels of copy control
- Sales document to sales document (for example quotation → order, order → return): VTAA
- Sales document to delivery: VTLA
- Sales document to billing (order-related billing): VTFA
- Delivery to billing: VTFL
At each level settings exist at header and item level; at item level, different rules can be defined per item category.
What is controlled?
- Requirements: under which condition copying is allowed, for example same customer, open quantity or unblocked document.
- Data transfer routines: which fields are taken from where, for example whether partner data on the invoice comes from the order or the delivery.
- Quantity and value update: whether the open quantity of the reference document is reduced.
- Pricing type: whether prices are recalculated or copied. See the pricing procedure article.
- Invoice split: which differences cause deliveries to be split into separate invoices.
The most common problems
- Different price on the invoice: the wrong pricing type was chosen, or a different condition record is valid on the billing date.
- Unexpected invoice splits: small differences in header data (payment terms, Incoterms, currency) split deliveries into separate invoices.
- Price on a return order: if the return is not created with reference to the original invoice, the price is recalculated and the customer is refunded a different amount.
- Missing text or partner: the data transfer routine does not carry the field.
Changes in S/4HANA
The logic of copy control is the same in S/4HANA. What changed is where status information lives: document statuses that ECC kept in separate status tables (VBUK/VBUP) are now part of the document header and item tables. Custom reports and copy routines that read the status tables must be adapted during migration.
Good practice
- Use standard routines where possible instead of copying and modifying them, and document any custom routine.
- For every new document type, test the entire chain: order → delivery → invoice → return → credit memo.
- Include the document flow report in user training; a large share of support tickets can be solved with that screen.
Copy control is invisible, yet it affects every invoice. In SAP SD consulting projects, documenting and testing these settings noticeably reduces the post-go-live support load. Combined with SD–MM–FI integration, it brings the whole document chain under control.
