on 05-27-2009 4:52 PM
Dear Sirs, in our SRM environement the contact persons (and relative system users) created by suppliers in the auto-registration procedure, should be synchronized between SUS and productive client.
(in our implementation client 150 and 330) .
This sync mechanism should be valid also for lock-unlock status of the user and reset of the password,
but in both cases it does not works (a locked user, manually unlocked from client 150 via SU01, is again locked in client 330, the same from 330 client).
Could you suggest a solution or some checkpoints ?
Could you provide some links for the configuration of this mechanism ? (we have seen only the SPRO node " Maintain Systems for Synchronization of User Data") ?
I am not shure if XI is implicated or not.
Best regards,
Riccardo Galli
Hi Riccardo
you are correct but it is not like CUA system.
if you block in ebp 100 client -sus 100 blocked.
Supplier self services->master data -> maintain systems for synchronisation of user data
br
muthu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Unfortunately it does not works, blocking a user on EBP does not blocks a user in SUS.
However the change of the address (for example) in a user from SUS, is replicated in EBP.
We have EBP and SUS on different clients.
Is the process managed by XI ?
Could you suggest some controls for checking the system (jobs, rfc queues, dumps, applicative log) ??
Riccardo.
HI
Maintain Systems for Synchronization of User Data
In this IMG activity, you specify the RFC destinations to which user data from SUS User Management is replicated.
In the Logical System field, you should enter the backend destination with which the user data should be synchronized when they are entered in SUS. On the basis of this information, the system determines the relevant RFC destination automatically.
Specify the function modules for creating, changing, or deleting a user in the external system for each logical system:
Function Module for Creating User: Function module that is called to create a user in the external system
Function Module for Changing User: Function module that is called to change the user in the external system
Function Module for Deleting User: Function module that is called to delete the user in the external system
If this data exists, you can set the indicator Use Purchasing BP ID to use the business partner ID from the procurement system instead of the business partner ID from SUS.
What are the settings maintained here ?
external system and roles in external system
br
Muthu
hi
learnt that you are trying to synchronise EBP bidder and sus users.
i believe all are correct. what is this z role ?flag use procureemnt Bp
and roles in external system
sus role = ebp role
C_00001 =? - please check
for std.
sap_ec_sus_bidder = sap_ec_bbp_bidder
please check above role mapping is happening between sus role and ebp role.
br
muthu
The flag "use procureemnt Bp ID" is cheched.
The role is a composite role for all our customers.
Excuse me, i should not abuse of your time, does we have to focus our attention on thi role ?
Otherwise, if this settings must GRANT the synchronization for users also for blocking status and password resetting, should we open a OSS message ?
Thanks for all,
Riccardo.
Hi
You can. plz update if you get any update form them
i think this is the place we are matching both roles for synchronisation . i think you might be right since it could send some sus user to EBP system or BW system. sorry i could not help you.
right now i dont have a system to test .. let us wait for others reply ..
this synchronisation is different what we thought earlier.
i checked up with SAP basis friends . it is possible if it is a CUA - Central user administaration and also it does via idocs ..
br
muthu
User | Count |
---|---|
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.