Exits for Inbound Distribution


Inbound distribution enables methods to be included for processing incoming send orders according to their recipients and document classes.


You have to have created the exit class that is to be used to process the message. The class has to have implemented the methods CREATE_INSTANCE and PROCESS_INBOUND of the interface IF_INBOUND_EXIT_BCS. For more information, see Inbound Processing in the documentation on Business Communication Services. If there are several suitable exits, processing occurs according to call sequence.

You must be using the SMTP plug-in.


  1. Call transaction SO50.
  2. Make the following entries for the messages that are to be processed:
  • Communication method by which the messages are sent
  • Recipients to whom the messages are addressed (can be specified generically with * as a placeholder if all document types are requested)
  • Document class of messages
  • Class that is to process the incoming messages
  • Call sequence of the classes

The number specified defines the sequence in which the exits are called if more than one suitable exit is found for a send order. Subsequent exits are then only called if the exit that was last executed did not execute the delivery (that is, did not return the return code GC_CONTINUE).


The two exits CL_EXIT_1 and CL_EXIT_2 are entered for the document class XML and the recipient purchaseorder@company.com.

If the processing logics in the exits expect different DTD (Document Type Definition), one of the two exits is always executed. In this case, the call sequence is of no significance.

If both exits expect the same DTD, only the exit called first is executed. This exit then executes the delivery and completes processing. In this case, the call sequence determines which exit is called.

  1. Save.