SD / O2Cadvanced

SD Output Management Part 9: Troubleshooting Output Determination and Form Rendering

Key takeaway

Diagnose why output was not determined or used the wrong parameters: NAST determination analysis (requirements, condition records, procedure assignment), BRF+ decision table simulation, wrong receiver, channel or form template, missing output relevance, and incorrect form content.

Explanation

📌 KEY POINTS
✅ NAST: determination analysis in the document's output screen shows accesses, records found and requirements.
✅ S/4HANA: BRF+ decision tables can be simulated; missing rows or wrong conditions explain wrong/no output.
✅ Typical causes: procedure not assigned to a new document type, missing condition record/row, requirement not met, wrong partner function.
✅ Wrong form usually = form template determination rule, not the form itself.
⚠️ Maintaining condition records per customer for every exception creates unmanageable determination.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 8 covered processing failures. Now determination.

━━━━━━━━━━━━━━━━━━━━
▶ 1. NAST DETERMINATION ANALYSIS

Output screen > determination analysis.
Procedure → output type → access → record found or not; requirement results.

━━━━━━━━━━━━━━━━━━━━
▶ 2. BRF+ ANALYSIS

Simulate decision tables with document values.
Check each step (type, receiver, channel, printer, form).

━━━━━━━━━━━━━━━━━━━━
▶ 3. COMMON CAUSES

New document type without procedure (NAST) or without BRF+ row.
Record keys not matching (sales org, customer).
Requirement routines excluding output.
Receiver partner not in document.

━━━━━━━━━━━━━━━━━━━━
▶ 4. FORMS

Wrong template due to country/language rule.
Content errors from missing master data (texts, addresses).

━━━━━━━━━━━━━━━━━━━━
▶ 5. DESIGN FIXES

Use general rules plus few exceptions.
Fallback rows to avoid "no output".

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

Run determination analysis or BRF+ simulation.
Identify the failing step.
Fix record/row/assignment.
Re-determine output and test.

✅ CHECKPOINT: you can explain why each output type was or wasn't determined for a document.

Code example

ABAP Code

===== STEP 1: NAST =====VA03 / VL03N / VF03 > Output > Determination analysis: procedure, output type, accesses, records, requirements ===== STEP 2: S/4HANA OM =====BRF+ output parameter determination: simulate decision table with document values (sales org, billing type, customer)Check steps: output type → receiver → channel → printer/email → form template ===== STEP 3: typical fixes =====Assign procedure / add BRF+ row | fix record keys | adjust requirement | add fallback rule

Real project scenario

A distribution company configured delivery notes so that only certain shipping points printed, via a custom requirement. After adding new shipping points, deliveries had no delivery notes. Determination analysis showed the requirement excluded unknown shipping points. Replacing the hard-coded list with a condition table keyed by shipping point and adding a default rule fixed it.

Common mistakes

Hard-coded requirements.
Too many customer-specific records.
No fallback rules.
Forgetting procedure assignment for new types.
Blaming forms for determination issues.

Best practices

Use analysis/simulation tools first.
Prefer general rules with few exceptions.
Add fallbacks.
Include output in new document type checklists.
Keep forms free of determination logic.

Interview angle

Questions: "No output was determined — how do you analyse?", "How do you troubleshoot BRF+ output determination?", "Why is the wrong form used?"
Strong answer: NAST determination analysis (procedure, accesses, records, requirements), BRF+ simulation per step, typical causes and fixes, form template determination rules, general rules with fallbacks.

Practice this lesson

Quick check

1. Invoices use the wrong form template in one country. Where is the cause most likely?

2. Why add fallback rules in output determination?

3. In NAST, which tool shows why an output type was not determined?

Interview questions

1. An output determination access sequence for order confirmations is finding condition records inconsistently — some customers get the output automatically, others don't despite similar setup. What steps do you take to diagnose the access sequence configuration issue?

Answer it in your own words first, then compare.

2. Invoices in one country show the wrong form and some customers receive print instead of email. How do you troubleshoot output parameter determination?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.