BAPI_USER_CHANGE

[Former Member]

Dear Fellow ABAPers,

I'm currently writing a program to perform mass user change, and I've found two Function Modules that seem to be the closest match (which I thought I could use): BAPI_USER_CHANGE and SUSR_BAPI_USER_CHANGE.

Unfortunately these two FMs do not seem to work for this solution. The peculiar thing is, when I ran (any of) these two Function Modules using SE37 or from within my program, the Return Message indicates a successful transaction ("user x has changed"). I came across similar problem in the past and I could get it to work using BAPI_TRANSACTION_COMMIT or COMMIT WORK, but not this time.

I have successfully created the tool to Mass-Create Users (SUSR_BAPI_USER_CREATE / BAPI_USER_CREATE1), and it is now in Production. No dramas at all.

We are using CUA in this environment, which I think might be the reason, but then if that was the case, I wouldn't be able to use the user-create and user-delete BAPIs, would I?

Has anyone ever had similar problem, or could give any suggestions?

The alternative solution we're thinking of is using SU10 to perform mass-update of User Details (Logon, Default settings, Password, etc.), but due to the large variety of data this would be inefficient: different business units, various time zones, decimal notation, date format, password combinations, etc.

Any input will be very appreciated.

Regards,

James.

[Former Member]

Ugh... found the answer. Foolish me! I should be using the associated X Import Parameters which works like an indicator of which files to be updated. (e.g. Import Parameter LOGONDATA has an associated LOGONDATAX).

Hope the experience can be useful for anyone else.

Happy ABAPer can go home to watch World Cup

[Former Member]

Haha ... I almost spent 30 minutes trying to debug SUSR_BAPI_USER_CHANGE and then thought to myself .. wait ... lets check SDN first. Glad to see someone else had the same epiphany that I would have had eventually, many precious minutes (hours?) later

Thanks!