<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic BAPI_USER_CHANGE in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-user-change/m-p/1411276#M198055</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Fellow ABAPers,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone ever had similar problem, or could give any suggestions?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any input will be very appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;James.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 14 Jun 2006 11:43:20 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-06-14T11:43:20Z</dc:date>
    <item>
      <title>BAPI_USER_CHANGE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-user-change/m-p/1411276#M198055</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Fellow ABAPers,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone ever had similar problem, or could give any suggestions?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any input will be very appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;James.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Jun 2006 11:43:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-user-change/m-p/1411276#M198055</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-06-14T11:43:20Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_USER_CHANGE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-user-change/m-p/1411277#M198056</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;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). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope the experience can be useful for anyone else.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Happy ABAPer can go home to watch World Cup &lt;SPAN __jive_emoticon_name="happy"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Jun 2006 11:54:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-user-change/m-p/1411277#M198056</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-06-14T11:54:03Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI_USER_CHANGE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-user-change/m-p/1411278#M198057</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;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 &lt;SPAN __jive_emoticon_name="happy"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Apr 2009 17:09:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-user-change/m-p/1411278#M198057</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-04-09T17:09:39Z</dc:date>
    </item>
  </channel>
</rss>

