NACE — Classic Output Control Configuration
NACE is used to configure classic condition-technique output control applications, output types, procedures and processing routines. It is most useful when supporting ECC or S/4HANA processes that still use classic message/output determination rather than new Output Management. For reliable SAP support, capture the exact system, client, user, time and object context first, then use the transaction's evidence before making configuration or data changes.
Verified practitioner reference for NACE — Classic Output Control Configuration. It explains what the transaction does, when it is appropriate, which parameters and evidence matter, how to use it safely, common diagnostic traps, and how its role changes or remains relevant in S/4HANA.
Published 19 Sept 2026· 636 words
Esta página ainda não está disponível em português.
Purpose
configure classic condition-technique output control applications, output types, procedures and processing routines. The transaction is most valuable when used as part of an evidence chain rather than as a shortcut. Start from the exact business or technical incident, preserve its user, time, system and object context, and distinguish display/analysis functions from actions that can alter system state.
When it is used
NACE is typically used when supporting ECC or S/4HANA processes that still use classic message/output determination rather than new Output Management. Consultants also use it during project testing and post-change validation because a repeatable selection gives objective evidence. In production, keep the initial scope narrow and widen it only after confirming that the first result matches the reported incident.
How to use it in practice
- Identify the application and output framework actually used by the document.
- Review the output type, access and procedure assignment.
- Check processing program/form and transmission medium.
- Maintain condition records through the appropriate application transaction.
- Test output creation and dispatch separately.
Key data objects
These are the most useful anchors for work in NACE. Capture them in incident notes or test evidence so another consultant can reproduce the same result.
- application — verify the exact value and its relationship to the affected execution or business object.
- output type — verify the exact value and its relationship to the affected execution or business object.
- access sequence/procedure — verify the exact value and its relationship to the affected execution or business object.
- processing routine/form — verify the exact value and its relationship to the affected execution or business object.
- transmission medium/partner — verify the exact value and its relationship to the affected execution or business object.
How to prove it in the data
Build a reproducible before-and-after proof. Capture the exact selection or object, record the status, log or result that demonstrates the issue, then apply one controlled correction and repeat the same check. Correlate with neighboring SAP logs, documents or repository objects where needed. A successful retry with changed input is not the same as proving the original root cause.
ECC vs S/4HANA
NACE is a classic output-control transaction. S/4HANA uses new Output Management for an increasing set of applications, so the active framework must be confirmed first. Availability of a classic transaction does not automatically make it the preferred implementation pattern for new work; distinguish support compatibility from clean-core and cloud-oriented design guidance.
Common pitfalls and how to diagnose them
- Using NACE for a document type that has moved to S/4HANA Output Management. Validate the exact object, user, timestamp and release context before applying a fix.
- Changing output type configuration when the condition record is simply missing. Validate the exact object, user, timestamp and release context before applying a fix.
- Treating successful output determination as proof that email/print transmission succeeded. Validate the exact object, user, timestamp and release context before applying a fix.
Whose problem this is
Primary ownership is usually with the SD O2C team. Bring in Basis, Security, functional or development specialists only when the evidence crosses those boundaries. A high-quality escalation includes the exact transaction, selection or object, timestamp, expected result, actual result and checks already completed.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/naceERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.