A Standard BAPIs Used During Connector Operations

Standard BAPIs used during connector operations can be categorized as follows:

A.1 Standard BAPIs Used on Both SAP R/3 and SAP CUA

The following standard BAPIs are used during connector operations on both SAP R/3 and SAP CUA:

  • BAPI_HELPVALUES_GET: Fetches lookup definition values

  • BAPI_USER_GET_DETAIL: Fetches account details

  • RFC_READ_TABLE: Queries the USR02 table for first-time reconciliation

  • BAPI_USER_CREATE1: Creates accounts on the target system

  • BAPI_USER_DELETE: Deletes accounts on the target system

  • BAPI_USER_LOCK: Locks accounts

  • BAPI_USER_UNLOCK: Unlocks accounts

  • BAPI_USER_CHANGE: Modifies account details, also resets the password

  • SUSR_USER_CHANGE_PASSWORD_RFC: Changes the password, so that user does not have change the password on first logon

  • BAPI_USER_EXISTENCE_CHECK: Checks whether a user exists

  • RFC_READ_TABLE: Queries the USH04 table to fetch deleted accounts during reconciliation

A.2 Standard BAPIs Used on SAP R/3

The following standard BAPI is used during connector operations on SAP R/3:

  • RFC_READ_TABLE: Queries the USR04 table for incremental reconciliation, and queries the USH02 table for fetching the account lock status

A.3 Standard BAPIs Used on SAP CUA

The following standard BAPI is used during connector operations on SAP CUA:

  • RFC_READ_TABLE: Fetches lookup definition values for roles, profiles, and child systems

  • BAPI_USER_LOCACTGROUPS_READ: Fetches details of roles assigned to the user

  • BAPI_USER_LOCPROFILES_READ: Fetches details of profiles assigned to the user

  • RFC_READ_TABLE: Queries the USZBVSYS table during incremental reconciliation and queries the USH02 table for fetching the account lock status