The objective of Message Control is the exchange of information between various partners and the

launching of subsequent processing that is partner-independent. Message Control provides interfaces to

make this possible.
You can use the Message Control interfaces to describe various data combinations along with the
required processing. If one of these data combinations is found to be applicable during the processing of
an application object, the appropriate processing is started (synchronously or asynchronously).
Message Control is a "service program" for other applications. It is initiated via ABAP function
modules. Information about which programs carry out the subsequent processing is managed in
tables . The conditions determining when programs are called are often very complex and also depend
on the individual customer situation. Message Control offers the flexibility needed to represent these
various situations .

Invoice Message Control Configuration

Below is an example of how to set up message control for the automatic creation of
INVOIC IDocs when an Invoice is created.
STEP 1: Output Type Config

Create Z810 output type with access sequence key Billing Type \ Sales Org \
Customer. Z810 is based on the SAP standard RD00.
The following steps are executed in the IMG at the following path:

1.

2.

3.

Create Condition table (Tx: V/63)

Table 950

Description Bill.type / Sales org. / Bill to

Selected fields Billing type, Sales organization, Bill-to party

Maintain access sequence (V/54)

Access sequence ZEDI

Description Bill.type / Sales org. / Bill to

Access Table 950, Exclusive

Fields:
o

FKART, KOMKBV3, FKART

VKORG, KOMKBV3, VKORG

KUNRE, KOMKBV3, KUNRE

Maintain output type (Tx: V/40)

Output type: Z810

Description: Invoice
o

4.

General data:

Access sequence: ZEDI

Check: Access to conditions

Default Values:

Time: 1

Transmission medium: 6

Partner function: BP

Processing routines:
o

Medium: 6

Program: RSNASTED

Form routine: EDI_PROCESSING

Partner functions:
o

Medium: 6

Function: BP

Maintain Output Determination Procedure

Procedure: V10000


5.

Control data: Insert step 11: Condition type: Z810 after RD00. No
requirement

Assign output determination procedure (V/25)

Doc type: ZF1

Output procedure: V10000. Clear output type => Either RD00 or ZD00 can be
used

STEP 2: Condition Record (VV32)

The table below shows the values for the condition records.

Part Fn: Partner function

Med: Transmission medium

o

6 = EDI

Time
o

Timing = 1 implies that a background job (running program RSNAST00)

will process the output.

Timing = 4 implies that the output will be created immediately on

document save.
MESSAGE
KEY
VALUES
PART MED TIME DESCRIPTION
TYPE
FN
Z810
6 4
Outbound EDI Invoice
0001
Sales Org:
BP
ZF1
Bill type:
100000004,
Bill to:
100000005,

TX
VV32

Additionally: Inbound Invoice Configuration

EDI - Inbound INVOIC posting configuration
Background

Message type: INVOIC

Processing function module for LIV (Logistics Invoice Verification):

IDOC_INPUT_INVOIC_MRM

Posts a MIRO document

Some pointers

If the P04 segment filled with tax condition I0 then you need to maintain the config
tables for it

Initial set up to attach the Partner Profile with this transaction below:

Transaction: OBCA

Transaction: OBCE

Also need to go to SPRO- because it has a couple of additional parameters

OCBD Need to assign the external tax type to the internal tax type.

OBYC need to put the variance in the certain G/L account