SAP SD Copy Control — VTAA, VTLA, VTFA & VTFL
The four T-codes · three levels · pricing type · troubleshooting · Last updated September 2026
Copy control is the quiet machinery behind the whole Order-to-Cash chain. Every time a document is created “with reference to” another, copy control decides whether it is allowed, what carries across, and what gets recalculated.
It is also, by common consent, the most frequently misconfigured area in SD — and the reason behind a large share of “the document cannot be created” tickets. This guide covers all four T-codes, the three levels, the settings that actually bite, and how to diagnose a failure in order.
On this page
What is copy control?
SAP rarely asks you to type the same data twice. A delivery is created from an order; an invoice from a delivery. Copy control is the configuration that governs that act of copying — and it does three jobs:
- →Permission. May this document type be created with reference to that one at all? No entry, no copy.
- →Transfer. Which fields carry across, and which are re-determined from scratch.
- →Linkage. Whether the connection is written to document flow (VBFA), keeping the chain traceable.
The one-line version: if a document “cannot be created with reference”, SAP is not broken — copy control is telling you no. The skill is knowing which of the four tables to open, and at which level.
The four T-codes
Scroll the diagram sideways to see all of it →
SAP SD copy control: VTAA (sales document → sales document), VTLA (sales document → delivery), VTFL (delivery → billing), VTFA (sales document → billing, order-related).
Sales document → Sales document
Quotation (QT) → Order (OR)When it bites: Any order created with reference to another sales document: quotation to order, contract to release order, order to returns, invoice correction requests. If a release order against a contract fails, this is the first place to look.
Sales document → Delivery
Order (OR) → Delivery (LF)When it bites: Every outbound delivery created from an order. Also where the delivery split criteria live — if one order unexpectedly produces two deliveries, the answer is here.
Sales document → Billing
Order (OR) → Invoice (F2)When it bites: Order-related billing — services, third-party items, credit and debit memo requests. Used whenever you bill from the order without a delivery.
Delivery → Billing
Delivery (LF) → Invoice (F2)When it bites: Delivery-related billing — the standard path for physical goods. The single most commonly checked copy control table in SD, and where the billing quantity setting lives.
Memory hook: the second letter is the target document. VTAA → sales document. VTLA → delivery. VTFA and VTFL → billing (the last letter tells you the source: A = order, L = delivery).
Header, item & schedule line
Every copy control entry is maintained at up to three levels. Each level has its own copying requirement and data transfer routine:
Header
How header data moves from the source document to the target.
- •Copying requirement — the routine that decides whether the copy is allowed at all
- •Data transfer routine (DataT) for header fields
- •Whether the pricing date, payment terms and Incoterms are copied or re-determined
- •Copy item number from reference — keeps item numbering identical across documents
Item
How each line is copied — where most of the consequential settings live.
- •Copying requirement at item level
- •Pricing type — whether prices are copied unchanged or re-determined
- •Billing quantity (delivery → billing) — which quantity is invoiced, e.g. delivery quantity less already invoiced quantity
- •Positive/negative quantity — how the copied quantity counts against the open quantity
- •Update document flow — whether the link is recorded in VBFA
Schedule line
How quantities and dates are copied (order → delivery only).
- •Copying requirement at schedule line level
- •Which confirmed quantities and delivery dates carry into the delivery
⚠ The classic mistake
Maintaining the header entry and stopping there. The item level must be maintained for every item category involved — otherwise the document is created with no items, or refuses outright. This is the single most common copy control error on a project.
The settings that matter
Copying requirement
An ABAP routine that must return "allowed" for the copy to proceed. Standard examples: routine 001 (header, same customer), 004 (delivery-related item), 003 (checks POD status is confirmed before billing). If a requirement fails, SAP refuses the copy — often with a message that sounds unrelated.
Symptom when wrong: The target document simply cannot be created, or the item is silently skipped.
Data transfer routine (DataT)
Controls how source fields map into target fields at header, item and schedule line. Custom split logic is often added here, or via a VOFM data transfer routine.
Symptom when wrong: The document is created but a field arrives blank or with the wrong value.
Pricing type
Set at item level. Decides whether prices are copied unchanged or re-determined. See the table below — this single field causes more pricing disputes than any other copy control setting.
Symptom when wrong: The invoice value does not match the order value (or vice versa).
Billing quantity (VTFL)
B = delivery quantity less invoiced quantity (the standard for delivery-related billing), A = order quantity less invoiced quantity, F = invoice receipt quantity less invoiced quantity (third-party). Decides what you actually invoice in a partial delivery scenario.
Symptom when wrong: You bill more or less than you shipped.
Positive / negative quantity
Controls how the copied quantity affects the open quantity of the source document — increases it, reduces it, or leaves it untouched.
Symptom when wrong: An order stays "open" after full delivery, or can be over-delivered without warning.
Update document flow
Decides whether the link between source and target is written to VBFA. Switch it off and the documents exist but the chain is broken.
Symptom when wrong: Document flow in VA03 shows nothing, and status updates never reach the predecessor.
Pricing type explained
Set at item level, pricing type decides whether the target document keeps the source’s prices or works them out again. It is the reason an invoice sometimes disagrees with its order:
| Type | Meaning | Typical use |
|---|---|---|
| A | Copy price components and re-determine scales | Keeps the negotiated price but refreshes quantity-based scales. |
| B | Carry out new pricing | Prices are determined fresh from current condition records. Use where the invoice must reflect today's price, not the order's. |
| C | Copy manual pricing elements and re-determine the others | Protects manually entered conditions while refreshing automatic ones — a common compromise. |
| D | Copy pricing elements unchanged | The invoice shows exactly what the order showed. Common where the customer must be billed the quoted price. |
| G | Copy pricing elements unchanged, re-determine taxes | Price is fixed but tax must reflect current rates and the actual ship-to. Very common in delivery → billing. |
The most common production choice for delivery → billing is G — hold the agreed price, but recalculate tax, because tax must reflect current rates and the actual ship-to party. For the full picture of how prices are found in the first place, see the pricing procedure guide.
Why the document will not copy
Work down this ladder in order. The cause is almost always in the first two.
Does a copy control entry exist for this exact document-type pair?
Open the right T-code (VTAA / VTLA / VTFA / VTFL) and look for the source-to-target combination. A missing entry is by far the most common cause — SAP cannot create a document with reference to a pair it has no rules for.
Does an ITEM-level entry exist for the item category?
The header entry existing is not enough. Each item category involved must also be maintained beneath it. A header-only entry produces a document with no items — or no document at all.
Is a copying requirement blocking it?
Note the routine number on the entry and check what it tests. Routine 003, for example, requires the POD status to be confirmed before billing will proceed — perfectly correct behaviour that looks like a bug.
Is the predecessor in the right status?
Copy control enforces sequence. Delivery-related billing needs goods issue posted; a release order needs an open contract quantity. Check the source document status before suspecting configuration.
Is the target document type correct?
Billing type F2 versus IV (intercompany) versus F8 (proforma) are different targets, each needing its own entry. Creating the wrong billing type will not find the entry you maintained for another one.
If the document IS created but wrong — check pricing type and billing quantity.
A document that exists but carries the wrong value or quantity is never a missing-entry problem. It is the item-level pricing type, the billing quantity indicator, or the data transfer routine.
Field note
Split the problem in two before you start. If the document will not be created, it is a missing entry or a copying requirement. If the document is created but wrong, it is pricing type, billing quantity, or a data transfer routine. Those are two different investigations, and mixing them up costs hours.
Where it sits in the SD chain
Item category and schedule line category configure a document’s lines. Copy control governs the links between documents:
- →Item category decides billing relevance — copy control then decides whether that billing may actually happen — read the guide
- →Schedule line category decides delivery relevance and the movement type behind the goods issue — read the guide
- →Order-to-Cash is the whole chain those links form, end to end — read the guide
What changed in S/4HANA
Nothing material. VTAA, VTLA, VTFA and VTFL work exactly as they did in ECC, and the header/item/schedule line structure is unchanged — ECC copy control knowledge transfers to S/4HANA directly.
What changed is the landscape it operates in: Business Partner for the customer master, advanced ATP for availability, and BRF+ for output. Copy control remains one of the stable foundations — which makes it a reliable thing to be genuinely good at.
Interview questions
What is copy control in SAP SD and why does it matter?
Copy control defines how data is transferred when a document is created with reference to another — quotation to order, order to delivery, delivery to billing. It decides whether the copy is permitted at all, which fields carry across, how prices and quantities behave, and whether the document flow link is recorded. If no copy control entry exists for a document-type pair, the target document simply cannot be created with reference to the source.
Name the four copy control T-codes and what each governs.
VTAA — sales document to sales document (quotation to order, contract to release order). VTLA — sales document to delivery. VTFA — sales document to billing, used for order-related billing. VTFL — delivery to billing, used for delivery-related billing. A useful mnemonic: the second letter is the target — A for sales document, L for delivery, F for billing.
What are the three levels of copy control and what does each control?
Header controls how header data such as pricing date and payment terms is copied. Item controls line-level copying — pricing type, billing quantity, positive/negative quantity, and update document flow. Schedule line (order to delivery only) controls how confirmed quantities and dates carry into the delivery. Each level has its own copying requirement and data transfer routine.
What is pricing type in copy control?
It is an item-level setting deciding how prices behave in the target document. B carries out completely new pricing from current condition records; D copies the pricing elements unchanged; G copies them unchanged but re-determines taxes — very common for delivery to billing, where the price is fixed but tax must reflect current rates and the actual ship-to. Choosing the wrong pricing type is the usual reason an invoice value does not match the order.
What does the billing quantity indicator do in VTFL?
It decides which quantity is invoiced: B bills the delivery quantity less the quantity already invoiced (the standard for delivery-related billing), A bills the order quantity less the quantity already invoiced. It matters most in partial delivery scenarios — with A, the invoice for a delivery can carry the whole remaining order quantity even though only part of it shipped.
What is a copying requirement, and how is it different from a data transfer routine?
A copying requirement is a gatekeeper — an ABAP routine that must be satisfied before copying is allowed at all. A data transfer routine is a mapper — it decides how source fields populate target fields once copying is permitted. One answers "may this copy happen?", the other answers "what does it look like when it does?".
A billing document cannot be created with reference to a delivery. How do you troubleshoot?
Check VTFL for an entry for that delivery type to billing type pair, then confirm an item-level entry exists for the item category involved. Then check the copying requirement routine on the entry, and whether goods issue has actually been posted. Also confirm you are creating the right billing type — an entry maintained for F2 does not help you create IV.
What happens if "update document flow" is switched off?
The target document is still created, but the link is not written to VBFA. Document flow in VA03 will not show the connection, and status updates will not propagate back to the predecessor — so the source document can stay open forever. It is occasionally switched off deliberately for proforma invoices, which should not affect the status of the delivery.
Frequently Asked Questions
What is copy control in SAP SD?
Copy control is the configuration that defines how data is transferred when one document is created with reference to another — for example a delivery created from a sales order, or an invoice created from a delivery. It controls whether the copy is permitted, which fields carry across, how pricing and quantities behave, and whether the link is recorded in document flow table VBFA. Without a copy control entry for a document-type pair, the target document cannot be created with reference to the source.
What is the difference between VTAA, VTLA, VTFA and VTFL?
They govern different document pairs. VTAA is sales document to sales document (quotation to order, contract to release order). VTLA is sales document to delivery. VTFA is sales document to billing, used for order-related billing such as services and third-party items. VTFL is delivery to billing, the standard path for physical goods. A quick mnemonic: the second letter tells you the target — A for sales document, L for delivery, F for billing.
What are the three levels of copy control?
Header, item, and schedule line. Header controls how header data such as pricing date and payment terms is copied. Item is where most consequential settings live — pricing type, billing quantity, positive/negative quantity, and update document flow. Schedule line applies to order-to-delivery copying and controls how confirmed quantities and dates transfer. Each level has its own copying requirement and data transfer routine.
What is pricing type in copy control?
Pricing type is an item-level setting that decides how prices behave in the target document. Common values: B carries out new pricing from current condition records; D copies the pricing elements unchanged; G copies them unchanged but re-determines taxes. G is very common for delivery-to-billing because the agreed price must stay fixed while tax reflects current rates and the actual ship-to party. Choosing the wrong pricing type is the usual explanation when an invoice value does not match its order.
What does the billing quantity setting (A, B, F) mean in copy control?
It decides which quantity is invoiced. B bills the delivery quantity less the quantity already invoiced — the standard in VTFL for physical goods. A bills the order quantity less the quantity already invoiced, and F bills the invoice receipt quantity less the quantity already invoiced, which is used for third-party items. The difference becomes visible in partial delivery scenarios — with A you could invoice the whole remaining order quantity even though only part of it shipped, which is almost never what the business wants for physical goods.
Why can I not create a billing document with reference to my delivery?
Work through it in order: (1) does a VTFL entry exist for that delivery type to billing type pair? (2) does an item-level entry exist for the item category involved — a header-only entry is not enough; (3) is a copying requirement routine blocking it, for example one that requires confirmed POD status; (4) has goods issue actually been posted; (5) are you creating the billing type the entry was maintained for — F2, IV and F8 are different targets. A missing entry at item level is the most common single cause.
What is the difference between a copying requirement and a data transfer routine?
A copying requirement is a gate: an ABAP routine that must be satisfied before copying is allowed at all. A data transfer routine is a mapper: it controls how source fields populate target fields once the copy is permitted. If the document will not be created, suspect the copying requirement. If the document is created but a field is wrong or blank, suspect the data transfer routine.
What does "update document flow" control?
Whether the link between the source and target document is written to VBFA. With it switched off, both documents still exist but the chain is broken — document flow in VA03 shows nothing and status updates never reach the predecessor, so the source can remain open indefinitely. It is sometimes switched off deliberately for proforma invoices, which should not change the delivery status.
Did copy control change in SAP S/4HANA?
No. VTAA, VTLA, VTFA and VTFL work exactly as they did in ECC, and the header/item/schedule line structure is unchanged, so ECC knowledge transfers directly. What changed around it is the wider landscape — Business Partner for the customer master, advanced ATP for availability, and BRF+ for output. Copy control remains one of the stable foundations of SD configuration.
Written by
Rahul Narain Saxena
SAP SD Solution Architect with 17+ years of hands-on implementation experience across SAP ECC and S/4HANA. Every guide on The SD Vault is written from live project experience, not summarised from documentation.
Copy control is where interviews get specific.
“Which T-code, which level, which pricing type” separates people who configured it from people who read about it. The SD Vault has 230+ depth-graded questions and 38 real configuration scenarios covering exactly this ground.
Get Lifetime Access →Or start free with the sample pack, Order-to-Cash guide, and Item Category guide.