Outbound Setup Procedure

This document needs to be completed with details & overview

Outbound Message Control

Message control uses pre-defined rules to propose output to the user. If alternate output is necessary, then the user may override the proposal. Based on the accepted messages, message control will create the appropriate messages from the application documents.

Within SAP, message control may generate output to paper, e-mail, EDI, etc.

The message control processing table is TNAPR. This table also indicates which processing program will generate the output.

Output Timing

Both the IDoc interface (partner/port profiles) and message control have a timing aspect.
Both also give the option immediate vs. some time later.

Hence, you could set message control to be immediate, but the IDoc interface will queue the document for later transmission. Or, you could queue documents in message control and have them sent immediately once you release the batch to the IDoc interface.

Essentially, you have two places to queue messages: message control and IDoc and if real-time messaging is not required, then some effort is necessary to determine where the stop point(s) will be.


SD and MM are examples. This is the top level of message control, and the application producing output is the starting point for message control.

Condition Types
These define:
  1. How output will be generated (Paper, email, EDI, workflow, etc)
  2. Output timing (immediate or collect for later), and
  3. The partner function to which this condition type applies.
Access Sequences
These are cross-client objects and define:
  1. Which tables holds the condition records.
Condition Records
These define output:
  1. medium
  2. recipient
  3. language
  4. timing
These are not defined in the IMG

Entity Relationships:

  1. An SAP application may have many message control procedures. Each message control procedure is related to only one application.
  2. Each procedure may be related to several condition types. Each condition type may be related to several procedures.
  3. Each condition type may be related to exactly one access sequence. An access sequence may be shared by multiple condition types.
  4. Each access sequence may use multiple accesses. An access may be used by many access sequences.

Essentially, an application has many output procedures assigned to it.

On the conditioning side, several access sequences exist that describe the order in which to retrieve condition records from various access tables.

In the end, the condition type ties these two sides together – the application message and the condition lookup.

Multiple Outputs:

  1. Multiple outputs may be defined at the partner level.
  2. Also, the “exclusive” flag (if “yes”) on the access sequence tells SAP to stop looking for more messages if a match is found. By turning off this flag, multiple messages may be generated.
  3. Also of note, VOFM (Requirements / Output Control) allows custom requirements routines to be written. This pertains to the requirements feature of the Procedure and Access tables.

Partner Definition

Transaction: WE20

Output options
  1. Transfer Immediate vs. Collect
  2. Start Subsystem vs. Do not start Subsystem