SAP Output Determination: The Configuration That Controls Every EDI Message You Send

Picture it: your customer sends in an EDI order, it creates the sales order in SAP. You expect the order acknowledgement (855) to return to them, but the IDoc meant to create it never leaves SAP. Nobody notices. Nobody knows why.

This is an output determination problem and it is not always simple to track down.

What Is Output Determination and Why Does it Matter?

Output determination is SAP’s way of deciding whether to send a message, where it should go and in what format it should be sent. It’s SAP’s primary method for sending EDI data out of the system. It comes out of the system as an IDoc and is then routed to the EDI subsystem for translation and transmission.

This holds true at least until S/4HANA and BRF+, though that is a discussion best saved for a future post.

If this is not configured properly, it could mean hefty fines for missed ASNs, missing components when POs are not sent to vendors, or missed payments when an invoice isn’t sent to a customer on time.

How NACE Output Determination Works

The foundation is the output type, which is set up per business transaction. Many come standard with SAP, for example BA00 as an order confirmation and RD00 for an invoice output. These output types drive what happens when the document is saved. They could trigger a print program for physical or emailed output or, in the case of EDI, a function module that generates an IDoc.

To determine whether an output should fire, SAP uses a layered lookup. Access sequences define which field combinations to check and in what order. Those combinations are stored in condition tables. And the condition records are the actual entries that say 'yes, send this output for this specific scenario.

How Partner Profiles Fit In

Partner profiles control where the output is sent. It’s the handoff between output determination and the IDoc/EDI layer. Even perfectly configured condition records won’t save you if the partner profile is missing or mismatched.

Where It Breaks and How to Find It

The difficulty with output determination troubleshooting is that there is no single failure point. Some of the areas to check are:

• Missing condition records – there isn’t a condition record set up to match your output.
• Access sequence gaps – your specific combination of values doesn’t exist in the access sequence.
• Partner profile alignment – if you don’t have a partner profile set up that matches the parameters of your output, the IDoc can’t be transmitted.

Output determination sits at the intersection of technical configuration and business outcome. When it works, nobody notices. When it doesn't, the business feels it immediately - even if they can't name the cause. Understanding how it works is one of the most critical things an SAP EDI team can do.