SAP BAPI_EMPALTNAME_CREATESUCCESSR Function Module for Create subs.employee alternative name record
BAPI_EMPALTNAME_CREATESUCCESSR is a standard bapi empaltname createsuccessr SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create subs.employee alternative name record 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 createsuccessr FM, simply by entering the name BAPI_EMPALTNAME_CREATESUCCESSR 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_CREATESUCCESSR 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_CREATESUCCESSR'"Create subs.employee alternative name record.
EXPORTING
INEMPLOYEENUMBER = "Personnel Number
INVALIDITYBEGIN = "Start date
INVALIDITYEND = "End Date
NAMETYPE = "Subtype
* ALTERNAME = "Alternative name
* NOCOMMIT = "COMMIT control at BAPI interface
IMPORTING
RETURN = "Structure for return code
EMPLOYEENUMBER = "Personnel Number
SUBTYPE = "Subtype
OBJECTID = "Object identification
LOCKINDICATOR = "Lock indicator for HR master record
VALIDITYBEGIN = "Start date
VALIDITYEND = "End Date
RECORDNUMBER = "Number of infotype record with same key
IMPORTING Parameters details for BAPI_EMPALTNAME_CREATESUCCESSR
INEMPLOYEENUMBER - Personnel Number
Data type: BAPIP0182-EMPLOYEENOOptional: No
Call by Reference: No ( called with pass by value option)
INVALIDITYBEGIN - Start date
Data type: BAPIP0182-VALIDBEGINOptional: No
Call by Reference: No ( called with pass by value option)
INVALIDITYEND - End Date
Data type: BAPIP0182-VALIDENDOptional: No
Call by Reference: No ( called with pass by value option)
NAMETYPE - Subtype
Data type: BAPIP0182-NAMETYPEOptional: No
Call by Reference: No ( called with pass by value option)
ALTERNAME - Alternative name
Data type: BAPIP0182-ALTERNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
NOCOMMIT - COMMIT control at BAPI interface
Data type: BAPI_STAND-NO_COMMITOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_EMPALTNAME_CREATESUCCESSR
RETURN - Structure for return code
Data type: BAPIRETURN1Optional: No
Call by Reference: No ( called with pass by value option)
EMPLOYEENUMBER - Personnel Number
Data type: BAPIP0182-EMPLOYEENOOptional: No
Call by Reference: No ( called with pass by value option)
SUBTYPE - Subtype
Data type: BAPIP0182-SUBTYPEOptional: No
Call by Reference: No ( called with pass by value option)
OBJECTID - Object identification
Data type: BAPIP0182-OBJECTIDOptional: No
Call by Reference: No ( called with pass by value option)
LOCKINDICATOR - Lock indicator for HR master record
Data type: BAPIP0182-LOCKINDICOptional: No
Call by Reference: No ( called with pass by value option)
VALIDITYBEGIN - Start date
Data type: BAPIP0182-VALIDBEGINOptional: No
Call by Reference: No ( called with pass by value option)
VALIDITYEND - End Date
Data type: BAPIP0182-VALIDENDOptional: No
Call by Reference: No ( called with pass by value option)
RECORDNUMBER - Number of infotype record with same key
Data type: BAPIP0182-RECORDNROptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_EMPALTNAME_CREATESUCCESSR 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.| DATA: | ||||
| lv_return | TYPE BAPIRETURN1, " | |||
| lv_inemployeenumber | TYPE BAPIP0182-EMPLOYEENO, " | |||
| lv_employeenumber | TYPE BAPIP0182-EMPLOYEENO, " | |||
| lv_invaliditybegin | TYPE BAPIP0182-VALIDBEGIN, " | |||
| lv_subtype | TYPE BAPIP0182-SUBTYPE, " | |||
| lv_invalidityend | TYPE BAPIP0182-VALIDEND, " | |||
| lv_nametype | TYPE BAPIP0182-NAMETYPE, " | |||
| lv_objectid | TYPE BAPIP0182-OBJECTID, " | |||
| lv_altername | TYPE BAPIP0182-ALTERNAME, " | |||
| lv_lockindicator | TYPE BAPIP0182-LOCKINDIC, " | |||
| lv_nocommit | TYPE BAPI_STAND-NO_COMMIT, " | |||
| lv_validitybegin | TYPE BAPIP0182-VALIDBEGIN, " | |||
| lv_validityend | TYPE BAPIP0182-VALIDEND, " | |||
| lv_recordnumber | TYPE BAPIP0182-RECORDNR. " |
|   CALL FUNCTION 'BAPI_EMPALTNAME_CREATESUCCESSR' "Create subs.employee alternative name record |
| EXPORTING | ||
| INEMPLOYEENUMBER | = lv_inemployeenumber | |
| INVALIDITYBEGIN | = lv_invaliditybegin | |
| INVALIDITYEND | = lv_invalidityend | |
| NAMETYPE | = lv_nametype | |
| ALTERNAME | = lv_altername | |
| NOCOMMIT | = lv_nocommit | |
| IMPORTING | ||
| RETURN | = lv_return | |
| EMPLOYEENUMBER | = lv_employeenumber | |
| SUBTYPE | = lv_subtype | |
| OBJECTID | = lv_objectid | |
| LOCKINDICATOR | = lv_lockindicator | |
| VALIDITYBEGIN | = lv_validitybegin | |
| VALIDITYEND | = lv_validityend | |
| RECORDNUMBER | = lv_recordnumber | |
| . " BAPI_EMPALTNAME_CREATESUCCESSR | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_EMPALTNAME_CREATESUCCESSR
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.| "SELECT single EMPLOYEENO FROM BAPIP0182 INTO @DATA(ld_inemployeenumber). | ||||
| "SELECT single EMPLOYEENO FROM BAPIP0182 INTO @DATA(ld_employeenumber). | ||||
| "SELECT single VALIDBEGIN FROM BAPIP0182 INTO @DATA(ld_invaliditybegin). | ||||
| "SELECT single SUBTYPE FROM BAPIP0182 INTO @DATA(ld_subtype). | ||||
| "SELECT single VALIDEND FROM BAPIP0182 INTO @DATA(ld_invalidityend). | ||||
| "SELECT single NAMETYPE FROM BAPIP0182 INTO @DATA(ld_nametype). | ||||
| "SELECT single OBJECTID FROM BAPIP0182 INTO @DATA(ld_objectid). | ||||
| "SELECT single ALTERNAME FROM BAPIP0182 INTO @DATA(ld_altername). | ||||
| "SELECT single LOCKINDIC FROM BAPIP0182 INTO @DATA(ld_lockindicator). | ||||
| "SELECT single NO_COMMIT FROM BAPI_STAND INTO @DATA(ld_nocommit). | ||||
| "SELECT single VALIDBEGIN FROM BAPIP0182 INTO @DATA(ld_validitybegin). | ||||
| "SELECT single VALIDEND FROM BAPIP0182 INTO @DATA(ld_validityend). | ||||
| "SELECT single RECORDNR FROM BAPIP0182 INTO @DATA(ld_recordnumber). | ||||
Search for further information about these or an SAP related objects