Creating Outbound Partner Profile 
Here you must enter the data manually. Alternatively, you can
also transfer the default values from Customizing .- If you are not yet in the change screen of your required partner, choose IDoc ® Partner profile in the
Initial node of the IDoc interface.
Position the mouse on your partner in the required partner type node. Choose 
in the Outbound parameter table.
Key fields
You have already determined partner number and partner type in general partner processing. The partner function from the master data defines the addressee, that is, it is used for further classification purposes. If you have selected outbound processing under Message Control (MC), the function must be identical to the corresponding Message Control field. Otherwise, it is optional.
Partner A wants to order a material from partner B. Partner B is of the partner type "LI" (vendor) and must choose the Message Control value "VD" (vendor) as the partner function because orders must always be processed via Message Control.
- Specify the business process with the "logical" message, within which the IDoc type is used. The logical message is described by three parameters: the message type is based on EDIFACT message types, for example, a purchase order is of type "ORDERS". You can further divide the message type with the optional fields message code and message function.
- Configure the test indicator if you want to send the message as a test.
Message, partner and test indicator are the seven key fields of the outbound partner profiles (the client comes in addition to these). Also see the figure at the end of this section.
Other fields
In the tab page
Outbound options, you can determine whether IDocs are forwarded immediately to the receiving system. You should ensure that your entries are compatible with the Message Control priorities, if you have chosen outbound processing under Message Control. A list of recommended combinations is provided in the following section:
Outbound Processing under M C: Procedure.
You have already defined the Recipient port in
Port definition.
Specify the IDoc type as the
Basic type with or without extension. If you want to use a
view of your IDoc type (for example, to improve the performance), specify this here.
The figure below shows the m-to-n relationship between logical messages (business meaning) and IDoc types (technical format). Message 1, for example, is always assigned to one IDoc type, while message 3 is assigned to two IDoc types. IDoc type 2, in turn, is also assigned to 2 logical messages.
The segment release specifies the release from which the segment definitions (not the IDoc type definition) originates. We recommend that you leave this field blank so that the most recent segment definition is used. This field should only be maintained as support information for the EDI subsystem if communication with older R/3 releases takes place via EDI subsystems.
- You can propose an EDI standard, version and EDI message type for the receiving system in the tab page EDI Standard. Most subsystems, however, should be able to determine these EDI settings themselves (from the logical message).
- You can define permitted agents for cases in which exceptions occur. This entry overrides the entry in the general partner profiles. Depending on the message, therefore, the exception can be handled by different agents of the same partner.
- You can specify whether syntax errors are to be ignored or are to lead to a processing error (syntax check in the tab page outbound options). For more information about exception handling and permitted agents, refer to the following section:
Exception Handling
- If your hardware supports it, create partner and message specific telephony data for outbound IDocs. For more information, read the following section:
General Partner Profile
Figure: Outbound partner profile fields (general)
Key fields are shown in gray. The values for partner, message and test indicator (and client) therefore provide a unique ID for the IDoc type in outbound processing.
