Skip to Content
avatar image
Former Member

Bakground job not updating the SNC string in USRACL table

Hi all,

New users are created into SAP system and a custom program prepares SNC name for the user and updates into USRACL table.

When this program is scheduled as a job, for some new users the SNC string is not updated in the USRACL table, other fields are updated.

When this program is executed in dialog mode, the USRACL table is updated with SNC string.

But, when the same program is updated as a job, in next runs, SNC of the earlier failed users is updated into USRACL table. And this time some new users might/not fail. There is no restriction on the number of users to be updated for each job. But, when executed in foreground, everything  works perfect. As everything runs perfect in foreground, I could identify the cause in debugging.

Below FMs are used for updating user:

BAPI_USER_CHANGE, SNC_CONVERT_PNAME_TO_KNAME, SUSR_USER_EXTID_SET

Please help me understand this behavior. something wrong with job parameters? or something wrong with user profile? something wrong with Bapi?

Your help is greatly appreciated!

Regards,

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Jul 17, 2015 at 12:24 PM

    Hello Srinivasa,

    Did you use the COMMIT WORK after BAPI.

    Did you use any of the function modules with UPDATE TASK or BACKGROUND TASK.

    If so use proper COMMIT WORK and check.

    Regards,

    TP

    Add comment
    10|10000 characters needed characters exceeded