Inbound Partner Profile

This section describes how to define which messages are to be accepted from which partner. Here you must enter the data manually. Alternatively, you can also transfer the default values from Customizing .

Procedure

...

       1.      If you are not yet in the change screen of your desired partner, choose SAP Menu ® Tools ® IDoc Interface/ALE ® Administration ®Runtime Settings ® Partner Agreement (WE20).

...

       1.      Position the mouse on your partner in the required partner type node. Choose  in the Inbound parameter table.

Key Fields

       2.      You have already determined partner number and partner type in general partner processing. The partner function is optional.

Partner B (vendor 1014) wishes to be able to accept electronic sales orders from partner A (customer 1110). Partner B enters partner A in the partner type “KU” (customer) and can select the partner function “SP” (sold-to party).

       3.      The 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 subdivide the message type using the message codeand function.

       4.      Together with the test indicator (and the client), the values for message and partner form the key fields of the inbound partner profiles. This is identical to (general) outbound processing. Also see the figure at the end of this section.

Other Fields

       5.      The process code specifies the process (function module or workflow) which is to be triggered when the IDoc is received (tab page Inbound options).

F4 input help can be used to display the permitted process codes for the message type (logical message). To display a list of all messages with process codes, choose SAP Menu ® Tools ® IDoc Interface/ALE ® Administration ® Services ® Documentation ® Process Codes for Messages (WE64).

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

       7.      You can decide whether syntax errors in the IDoc are to be ignored or are to lead to exception handling (tab page inbound options, field syntaxcheck).

       8.      In the inbound options tab page, you can define whether the inbound IDoc is to be processed immediately.

The indicator only affects direct inbound processing. In ALE distribution scenarios for example, inbound IDocs can first be “left idle” and processed later in the background.

       9.      If your hardware supports it, create partner and message specific telephony data for inbound IDocs. For more information, read the following section: General Partner Profile

Graphic: Inbound partner profile fields

Key fields are shown in gray and the IDoc Interface assignments with arrows: Partner, message and test indicator (and the client) for an inbound IDoc therefore provide a unique ID for both the process code and the type of inbound processing.