SAP BAPI_EMPALTNAME_CHANGE Function Module for Change employee alternative name

Search SAP Function Modules

BAPI_EMPALTNAME_CHANGE is a standard bapi empaltname change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change employee alternative name processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.

See here to view full function module documentation and code listing for bapi empaltname change FM, simply by entering the name BAPI_EMPALTNAME_CHANGE into the relevant SAP transaction such as SE37 or SE38.

Function Group: PALT
Program Name: SAPLPALT
Main Program: SAPLPALT
Appliation area: P
Release date: 28-Jan-2000
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_EMPALTNAME_CHANGE pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.

CALL FUNCTION 'BAPI_EMPALTNAME_CHANGE'"Change employee alternative name
  EXPORTING
   EMPLOYEENUMBER =  "Personnel number
   SUBTYPE =  "Subtype
   OBJECTID =  "Object identification
   LOCKINDICATOR =  "Lock indicator for HR master record
   VALIDITYBEGIN =  "Valid from date
   VALIDITYEND =  "Valid to date
   RECORDNUMBER =  "Number of infotype record
*  NOCOMMIT =  "COMMIT control at BAPI interface
*  ALTERNAME =  "Alternative name

 IMPORTING
   RETURN =  "Structure for return code

.

IMPORTING Parameters details for BAPI_EMPALTNAME_CHANGE

EMPLOYEENUMBER - Personnel number

Data type: BAPIP0182-EMPLOYEENO
Optional: No
Call by Reference: No ( called with pass by value option)

SUBTYPE - Subtype

Data type: BAPIP0182-SUBTYPE
Optional: No
Call by Reference: No ( called with pass by value option)

OBJECTID - Object identification

Data type: BAPIP0182-OBJECTID
Optional: No
Call by Reference: No ( called with pass by value option)

LOCKINDICATOR - Lock indicator for HR master record

Data type: BAPIP0182-LOCKINDIC
Optional: No
Call by Reference: No ( called with pass by value option)

VALIDITYBEGIN - Valid from date

Data type: BAPIP0182-VALIDBEGIN
Optional: No
Call by Reference: No ( called with pass by value option)

VALIDITYEND - Valid to date

Data type: BAPIP0182-VALIDEND
Optional: No
Call by Reference: No ( called with pass by value option)

RECORDNUMBER - Number of infotype record

Data type: BAPIP0182-RECORDNR
Optional: No
Call by Reference: No ( called with pass by value option)

NOCOMMIT - COMMIT control at BAPI interface

Data type: BAPI_STAND-NO_COMMIT
Optional: Yes
Call by Reference: No ( called with pass by value option)

ALTERNAME - Alternative name

Data type: BAPIP0182-ALTERNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BAPI_EMPALTNAME_CHANGE

RETURN - Structure for return code

Data type: BAPIRETURN1
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for BAPI_EMPALTNAME_CHANGE Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

ABAP code using 7.40 inline data declarations to call FM BAPI_EMPALTNAME_CHANGE

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

Search for further information about these or an SAP related objects