SAP ABAP Message Class 01 Message Number 384 (No partner profile for target system &1 exists in the central system)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-SEC-USR-ADM (Application Component) User and Authorization Management
⤷
SUSR (Package) ABAP User Administration
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-SEC-USR-ADM (Application Component) User and Authorization Management⤷
SUSR (Package) ABAP User Administration 
Attribute
| Message class |  |
01 | |
| Short Description |  |
General Basis, e.g. user and authorization maintenance | |
| Message Number |  |
384 | |
| Documentation status | Space: object requires documentation |
||
| Authorization check Error Message | |||
| Changed On |  |
20130531 |
Message Text
No partner profile for target system &1 exists in the central system
Help Document
Diagnosis
No partner profile exists for the target system in the central system.
Procedure
In the central system, start transaction BD64, and generate the partner profiles for the distribution model for Central User Administration.
Then use transaction WE20 to check the outbound parameters of message type USERCLONE. Use the newest basic type of message type USERLCLONE, which is available both in the central and the child systems (See SAP Note 389426).
History
| Last changed on/by | |
20140121 | SAP |
| SAP Release Created in |
