SD Copy Control Part 4: Troubleshooting Copy Control and Document Chains

📌 KEY POINTS
✅ Start with the exact message and the copy direction: which source type/item category → which target type.
✅ "Copying is not possible" = missing header/item entry; "requirement not fulfilled" = a copying requirement routine rejected it.
✅ Wrong prices after copying = pricing type (and condition settings); wrong quantities = copy quantity, pos./neg. quantity, billing quantity.
✅ Document flow (VBFA) and referenced quantities show whether earlier copies consumed the source.
⚠️ Fixing symptoms in the target document (manual edits) hides copy control defects that repeat on every document.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Parts 1–3 covered flows, fields and routines. Now the diagnostic path.

━━━━━━━━━━━━━━━━━━━━
▶ 1. READ THE MESSAGE

• Note source document type, item category, target type.
• Use the message long text; it often names the routine or missing entry.

━━━━━━━━━━━━━━━━━━━━
▶ 2. MISSING ENTRIES

• Header entry in VTAA/VTLA/VTFA/VTFL.
• Item entry for the source item category (and target item category if specified).
• Schedule line entry for sales → sales.

━━━━━━━━━━━━━━━━━━━━
▶ 3. ROUTINE REJECTIONS

• Identify the requirement assigned at the failing level.
• Read its logic in VOFM; debug with a breakpoint in the FORM if needed.
• Common: item rejected, different sold-to/sales area, blocks, statuses.

━━━━━━━━━━━━━━━━━━━━
▶ 4. WRONG DATA AFTER COPY

• Prices: pricing type, manual condition settings, condition exclusion.
• Quantities: copy quantity, pos./neg. quantity, completion rule, billing quantity in VTFL.
• Partners/texts: data transfer routines and partner/text determination.

━━━━━━━━━━━━━━━━━━━━
▶ 5. CHAIN ISSUES

• Contract fully referenced → release orders fail (check referenced quantity).
• Credit memo from invoice with wrong amount → VTFF/VTAF pricing type.
• Invoice missing → document flow, billing status, VTFL copying requirement.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

1. Reproduce with the exact source document.
2. Check header, item, schedule line entries for the direction.
3. Read and, if needed, debug the requirement routine.
4. Compare copied data vs. source per field; map to the controlling setting.
5. Fix configuration and retest the entire chain.

✅ CHECKPOINT: every copy failure is traced to an entry, a routine or a field setting.

On an industrial equipment rollout, users reported that some order items "disappeared" when creating deliveries. The team first suspected ATP. Following the chain showed the delivery was created from the order via VTLA, where the item-level entry for a new Z item category was missing; items of that category were silently not copied (other items were). Adding the item entry fixed the problem. The support runbook now starts every copy issue with "direction + source item category + VTxx entry".

• Editing target documents manually instead of fixing copy control.
• Looking only at header entries.
• Guessing instead of reading/debugging the routine.
• Ignoring referenced quantities when source documents are "used up".
• Retesting only one hop after a fix.

• Always identify direction, source type and item category first.
• Keep a message-to-cause runbook.
• Debug routines with breakpoints in VOFM FORMs.
• Retest the full chain after fixes.
• Log recurring copy issues to improve template settings.

Questions: "Copying is not possible — what do you check?", "Prices changed from quotation to order — why?", "Release order against contract fails — why?"
Strong answer: missing header/item entries vs. routine rejections, pricing type for price differences, quantity controls and referenced quantities for consumed sources, document flow for chain analysis, debugging VOFM routines; fix configuration and retest the chain.