Additional Parameters for Outbound Processing under MC (SAP Library - IDoc Interface/Electronic Data Interchange (BC-SRV-EDI))

Additional Parameters for Outbound Processing under MC

This section describes how to define additional outbound parameters, which correspond to the fields from Message default of Message Control (MC). Since the IDoc interface is responsible for generating the IDocs in this case, you must also select a process code.

Prerequisites

Message Control is available in the system

You have already created a partner with partner function in the create screen of the outbound partner profile.

The partner function comes from the master data and is forwarded by Message Control via table MC to the IDoc interface.

Procedure

If you are not yet in the change screen with the required partner role, select this in the Outbound parameter table. If necessary, choose This graphic is explained in the accompanying text

to display the change mode and choose This graphic is explained in the accompanying text

in the table Outbound parameter.

Now choose the tab page Message Control. For the table, choose This graphic is explained in the accompanying text

Key fields

Like the partner function, the Message type is used to allocate the corresponding condition element of the MC. A purchase order, for example, has the output type "NEU" (new).

Enter a name for the application in the column Application (for example "EF" for "purchase order").

Together with the change indicator (for example, for a purchase order change) and the client, the values for partner, output type and application form the key fields of the additional outbound partner profiles under Message Control. Also see the figure at the end of this section.

Example

The following table contains the most common assignments between Message Control fields (application, partner function and output type) and logical messages in the IDoc interface.

Application	Partner function	Output type	Change	Log. message
EA	VD	NEU (new)		REQOTE
EF	VD	NEU (new)		ORDERS
EF	VD	NEU (new)	X	ORDCHG
V1	SP	AN00		QUOTES
V1	SP	BA00		ORDRSP
V2	SH	LAVA		DESADV
V3	SH	AUS1		EXPINV
V3	BP	RD00		INVOIC

Note

A message default for MC is always stored as a record in table MC. Therefore, if a message default has already been generated from your application document, you can get the "correct" application, partner function and output type from this table. Use your document number as the key in transaction SE16.

You must determine in general the partner role of a message (synonym: condition record) in the corresponding application. Thus, you can read this parameter straight from the message definition.

Other fields

The process code indicates the function module which converts the document into an IDoc.

F4 Help can be used to display the permitted process codes for the message type (logical message) and IDoc type. A list of all messages with process codes can be found by selecting Documentation ® Process codes from the initial node of the IDoc interface.

Result

You have assigned the fields in the IDoc interface so that they correspond to the Message Control fields. In addition you have performed an assignment to the general outbound partner profiles (see figure) and indirectly to the general partner profiles.

You should check your settings.

Graphic: Outbound partner profile fields (general and MC specific)

Key fields are shown in gray and the IDoc interface assignments with arrows: partner, applicationand output type (with change indicator) therefore provide a unique ID for the IDoc type in outbound processing (together with the client).

This graphic is explained in the accompanying text