Start of Content Area

Procedure documentation Checking Partner Profiles  Locate the document in its SAP Library structure

You have generated the partner profiles without an error being displayed in the log. We nevertheless recommend that you check the partner profiles with the following procedures, especially when the SAP systems in your Central User Administration (CUA) have different release statuses.

Check Technical Consistency of Partner Profile

...

       1.      After you have generated the partner profiles, choose Environment Change Partner Profile (transaction WE20) in both the central and the child system.

The Partner Profiles screen appears.

       2.      Expand the Partner Type LS node.

       3.      Select the system to be checked (such as PRDCLNT324) and choose Check (This graphic is explained in the accompanying text).

The system displays the Select Partner dialog box, in which the name of the system and partner type are automatically entered.

       4.      Choose Execute.

The system displays the Display Log screen, on which the result of the check is displayed in the appropriate colors (see color legend).

       5.      To display a detailed list of the check results, choose Edit Display Long Text.

If an error occurs, you can start the corresponding Customizing transaction directly by double clicking the error message, and can correct the error there.

Check the Message Type USERCLONE in the Central System

...

       1.      Log on to the central system (in this example, ADMCLNT070).

       2.      Call transaction WE20.

The Partner Profiles screen appears.

       3.      Choose the Partner Type LS (Logical System) folder, and choose the child system (such as PRDCLNT324).

       4.      In the group box, call USERCLONE in the Message Type column in the Outbound Parameters group box by double clicking it.

       5.      Check whether the basis type of the message type USERCLONE corresponds to the release status of your central and child system (See SAP Note 389426). The following message types exist:

Basis Type

Release

USERCLONE01

4.5

USERCLONE02

4.6B

USERCLONE03

4.6C

USERCLONE04

610 and higher

Example

For example, if your central system has a release status of SAP R/3 4.6C and a child system SAP R/3 4.6B, define USERCLONE02 for this partner profile.

Note

To provide the greatest possible number of functions, the highest possible Basis type, that is supported by both the child and central systems, is entered. Therefore, if you enter Basis type USERCLONE03 and this entry is automatically changed to USERCLONE04, this means that both the central and the child system already support USERCLONE04.

       6.      If an incorrect Basis type is used, correct the error as described in the Procedure for an Error in the Central System section of Correcting Errors for Partner Profiles.

Check the Process Code of Inbound Processing in the Child Systems

...

       1.      Log on to the child system (in this example, PRDCLNT324).

       2.      Call transaction WE20.

The Partner Profiles screen appears.

       3.      Expand the Partner Type LS (Logical System) folder, and choose the central system (such as ADMCLNT070).

       4.      In the Inbound Parameters group box, choose the USERCLONE option in the Message Type column.

       5.      If the value of the process code is BAPP, change it to BAPI.

Note

As of SAP R/3 4.6C you can use BAPP, while BAPI is valid for all releases as of SAP R/3 4.5.

 

End of Content Area