‎2018 Aug 06 10:20 AM
we have a FM 'BAPI_USER_CREATE1' but this allows us to create only one user at a time.
‎2018 Aug 06 12:29 PM
How about writing a wrapper function module around the bapi_user_create1?
‎2018 Aug 06 12:35 PM
‎2018 Aug 10 11:48 AM
b.wallagh that is what i am doing now but this is causing performance because commit work will happen for each user, i want commit work to happen only once.
‎2018 Aug 13 1:47 PM
Well, how about this:
- loop over your users
--- call bapi_user_create1
- endloop
- commit
‎2018 Aug 13 2:33 PM
b.wallagh initially i was also thinking to do like what you are suggesting, but problem is we don't have any parameter to skip the commit work happening inside bapi_user_create1.

‎2018 Aug 14 8:26 PM
Why is this causing such a huge performance issue? Commit after every user seems justified to me. Each account is a separate transaction. And keeping data without committing has its own drawbacks.
You might want to offer more information about the architecture here.
‎2018 Aug 15 8:18 AM
I can't help but wonder why performance is important? It's not the type of thing you do every day.
‎2018 Aug 15 3:02 PM
Hmmm ... if i peak into the documentation of this module, this catches my eye:
'If you want to choose when the COMMIT WORK takes place, you must use the new identity API (class CL_IDENTITY_FACTORY) instead of the BAPIs for the user.'
Can you use these methods by any change?