Enterprise Resource Planning Portal ERPGenie.COM Enterprise Resource Planning Portal

   Advertise | BLOG

Web ERPGenie.COM

Home | Vote for us |

ERPGenie.COM -> SAP Interfacing Technology -> EDI -> Message Control

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.       Create Condition table (Tx: V/63)

·         Table 950

·         Description Bill.type / Sales org. / Bill to

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

2.       Maintain access sequence (V/54)

·         Access sequence ZEDI

·         Description Bill.type / Sales org. / Bill to

·         Access Table 950, Exclusive

·         Fields:

o        FKART, KOMKBV3, FKART

o        VKORG, KOMKBV3, VKORG

o        KUNRE, KOMKBV3, KUNRE

3.       Maintain output type (Tx: V/40)

·         Output type: Z810

·         Description: Invoice

o        General data:

§         Access sequence: ZEDI

§         Check: Access to conditions

o        Default Values:

§         Time: 1

§         Transmission medium: 6

§         Partner function: BP

·         Processing routines:

o        Medium: 6

o        Program: RSNASTED

o        Form routine: EDI_PROCESSING

·         Partner functions:

o        Medium: 6

o        Function: BP

4.       Maintain Output Determination Procedure

·         Procedure: V10000

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

5.       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.

o        Timing = 4 implies that the output will be created immediately on document save.

Tx

Message
Type

Key

Values

Part
FN

Med

TimE

Description

VV32

Z810

Sales Org:

Bill type:

Bill to:

0001

ZF1

100000004,

100000005,

BP

6

4

Outbound EDI Invoice 

Additionally: Inbound Invoice Configuration

Contact Us | Polls | Add URL | Contribute | About | Privacy | Terms | Feedback | Help!

Message Board | Discussion Forum | BLOG | Consultants: Post your resume | Companies: Advertise on ERPGenie.COM | Post Job