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

ParameterTypeDescriptionRequired
EMPLOYEENUMBERBAPIP0105N-EMPLOYEENOPersonnel numberYes
SUBTYPEBAPIP0105N-SUBTYPESubtypeYes
OBJECTIDBAPIP0105N-OBJECTIDObject identificationYes
LOCKINDICATORBAPIP0105N-LOCKINDICLock indicatorYes
VALIDITYBEGINBAPIP0105N-VALIDBEGINValid fromYes
VALIDITYENDBAPIP0105N-VALIDENDValid toYes
RECORDNUMBERBAPIP0105N-RECORDNRRecord numberYes
COMMUNICATIONIDBAPIP0105N-IDCommunication ID or number—
NOCOMMITBAPI_STAND-NO_COMMITNo commit (caller commits)—

Exporting parameters

ParameterTypeDescription
RETURNBAPIRETURN1Return 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.

Request a custom report