HCM
BAPI
RFC
Used the same way in S/4HANA
BAPI_EMPLCOMM_CHANGE Change Employee Communication (Infotype 0105)
Changes the communication ID of an existing infotype 0105 record identified by its full key. Identity management and directory interfaces use it to keep user names and e-mail addresses in sync. Lock the employee first and check RETURN.
- Function group
- 0PBAPI0105
- Remote-enabled (RFC)
- Yes
- Type
- BAPI
Importing parameters
| Parameter | Type | Description | Required |
|---|---|---|---|
| EMPLOYEENUMBER | BAPIP0105N-EMPLOYEENO | Personnel number | Yes |
| SUBTYPE | BAPIP0105N-SUBTYPE | Subtype | Yes |
| OBJECTID | BAPIP0105N-OBJECTID | Object identification | Yes |
| LOCKINDICATOR | BAPIP0105N-LOCKINDIC | Lock indicator | Yes |
| VALIDITYBEGIN | BAPIP0105N-VALIDBEGIN | Valid from | Yes |
| VALIDITYEND | BAPIP0105N-VALIDEND | Valid to | Yes |
| RECORDNUMBER | BAPIP0105N-RECORDNR | Record number | Yes |
| COMMUNICATIONID | BAPIP0105N-ID | Communication ID or number | — |
| NOCOMMIT | BAPI_STAND-NO_COMMIT | No commit (caller commits) | — |
Exporting parameters
| Parameter | Type | Description |
|---|---|---|
| RETURN | BAPIRETURN1 | Return message |
Call template (ABAP)
A skeleton generated from the interface. It lists mandatory importing parameters, exporting parameters and tables; declare the variables with suitable types in your own program.
CALL FUNCTION 'BAPI_EMPLCOMM_CHANGE'
EXPORTING
employeenumber = lv_employeenumber
subtype = lv_subtype
objectid = lv_objectid
lockindicator = lv_lockindicator
validitybegin = lv_validitybegin
validityend = lv_validityend
recordnumber = lv_recordnumber
IMPORTING
return = lv_return.Related tables
Can't find the report you need?
We also build anything that is not in the catalog. Describe it briefly and we will suggest the right solution.