Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table
Output Determination for EDI in SAP S/4HANA: Output Control vs NACE Condition Records

Course quiz

Output Determination for EDI in SAP S/4HANA: Output Control vs NACE Condition Records

Keep this: job aid

Why did no IDoc go out? Output triage card

  • First ask which framework the document uses: Manage Application Object Type Activation (Cross-Application Components > Output Control).
  • NAST: open the document's output screen. No BA00/LAVA line at all → run determination analysis (condition record, requirement, partner).
  • NAST line in status 0 (not processed) → check dispatch time: 1 or 2 waits for RSNAST00; 3 waits for the application's own send transaction.
  • NAST line in status 2 (incorrectly processed) → read the processing log; "no process code" means the WE20 message control line is missing.
  • Output control: open the output items in the document or app; "in preparation" usually means the output relevance step or missing data.
  • Output control rules live in OPD: output type, receiver, channel, then channel settings; entries run top-down, specific before general.
  • An IDoc exists → it is no longer an output problem: check its status in WE02 (03, 30, 02, 26) and the partner profile row.
  • Duplicates: check two matching condition records, change output (BA00 on order change), manual repeats, and non-exclusive OPD rows.
  • Medium 6 = EDI in NAST; partner function in the output record must match the WE20 outbound row.
  • Evidence for sign-off: output record or item, IDoc number with status, and the partner acknowledgment for each EDI output type.