C.0 Business Application Programming Interfaces (BAPIs)

The following table contains a list of the BAPIs used by the driver.

BAPI Name

Description

BAPI_PDOTYPES_GET_DETAILEDLIST

Used to obtain lists and minimal detailed information for SAP USER objects and other specified business object types.

BAPI_USER_ACTGROUPS_ASSIGN

Used to assign the Activity Groups (Roles) to SAP USER objects in a non-CUA landscape.

BAPI_USER_ACTGROUPS_DELETE

Used to delete the Activity Groups (Roles) from SAP USER objects in a non-CUA landscape.

BAPI_USER_PROFILES_ASSIGN

Used to assign Profiles to SAP USER objects in a non-CUA landscape.

BAPI_USER_PROFILES_DELETE

Used to delete Profiles from SAP USER objects in a non-CUA landscape.

BAPI_USER_CHANGE

Used to modify SAP USER object attributes (fields, structures, and general tables) and non-persistent passwords.

BAPI_USER_CREATE1

Used to create a new SAP USER object.

BAPI_USER_DELETE

Used to delete an SAP USER object.

BAPI_USER_GETDETAIL

Used to read the current data field values, structures, and general table attributes of an SAP USER object.

BAPI_ADDRESSORG_GETDETAIL

Used to read the Company Address attributes of an SAP USER object.

BAPI_USER_LOCK

Used to lock an SAP USER object account. On a CUA Central system, this is a global lock. On a CUA Child system or on a non-CUA system, this is a local lock.

BAPI_USER_UNLOCK

Used to unlock an SAP USER object account. On a CUA Central system, this is a global lock. On a CUA Child system or on a non-CUA system, this is a local lock.

SUSR_BAPI_USER_LOCK

Used to set granular locks on an SAP USER object account. The granular lock types available are LOCK_LOCAL and LOCK_GLOBAL.

By default, this BAPI is not a Remote-Enabled Module and is thus not accessible to the driver. An ABAP developer must modify the Processing Type attribute of the BAPI on the target SAP system. This is accomplished via the SAP Function Builder (Transaction SE37).

SUSR_BAPI_USER_UNLOCK

Used to clear granular locks on an SAP USER object account. The granular lock types available are LOCK_LOCAL, LOCK_GLOBAL, and LOCK_WRONG_LOGON.

By default, this BAPI is not a Remote-Enabled Module and is thus not accessible to the driver. An ABAP developer must modify the Processing Type attribute of the BAPI on the target SAP system. This is accomplished via the SAP Function Builder (Transaction SE37).

SUSR_USER_CHANGE_PASSWORD_RFC

Used to set a persistent password for an SAP USER object.

BAPI_USER_LOCACTGROUPS_ASSIGN

Used to assign client-specific Activity Groups (Roles) to SAP USER objects in a CUA landscape.

BAPI_USER_LOCACTGROUPS_READ

Used to read the current client-specific Activity Groups (Roles) assignments of SAP USER objects in a CUA landscape.

BAPI_USER_LOCACTGROUPS_DELETE

Used to delete the client-specific Activity Groups (Roles) assignments from SAP USER objects in a CUA landscape.

BAPI_USER_LOCPROFILES_ASSIGN

Used to assign client-specific Profiles to SAP USER objects in a CUA landscape.

BAPI_USER_LOCPROFILES_READ

Used to read the current client-specific Profile assignments of SAP USER objects in a CUA landscape.

BAPI_USER_LOCPROFILES_DELETE

Used to delete the client-specific Profile assignments from SAP USER objects in a CUA landscape.

BAPI_USER_CLONE

Sent from the SAP ALE subsystem to communicate SAP-initiated changes of USER objects to the driver Publisher channel.

BAPI_COMPANY_CLONE

Sent from the SAP ALE subsystem to communicate SAP-initiated changes of Company Address information to the driver Publisher channel.