SAP HR_WAGE_COMP_EXT_MANIPULATE Function Module for









HR_WAGE_COMP_EXT_MANIPULATE is a standard hr wage comp ext manipulate SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 hr wage comp ext manipulate FM, simply by entering the name HR_WAGE_COMP_EXT_MANIPULATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: PCIF_EXTSALARY
Program Name: SAPLPCIF_EXTSALARY
Main Program: SAPLPCIF_EXTSALARY
Appliation area: P
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function HR_WAGE_COMP_EXT_MANIPULATE 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 'HR_WAGE_COMP_EXT_MANIPULATE'"
EXPORTING
OPERATION = "
* COSTASSIGNMENT = "
* TESTRUN = "
EMPLOYEENUMBER = "
SUBTYPE = "
* OBJECTID = "
* LOCKINDICATOR = "
VALIDITYEND = "
VALIDITYBEGIN = "
* RECORDNUMBER = "
* WAGECOMPDATA = "

IMPORTING
CREATED_KEY = "

TABLES
RETURN = "
* EXTENSION_IN = "

EXCEPTIONS
NOT_SUCCESSFUL = 1
.



IMPORTING Parameters details for HR_WAGE_COMP_EXT_MANIPULATE

OPERATION -

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

COSTASSIGNMENT -

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

TESTRUN -

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

EMPLOYEENUMBER -

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

SUBTYPE -

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

OBJECTID -

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

LOCKINDICATOR -

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

VALIDITYEND -

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

VALIDITYBEGIN -

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

RECORDNUMBER -

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

WAGECOMPDATA -

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

EXPORTING Parameters details for HR_WAGE_COMP_EXT_MANIPULATE

CREATED_KEY -

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

TABLES Parameters details for HR_WAGE_COMP_EXT_MANIPULATE

RETURN -

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

EXTENSION_IN -

Data type: BAPIPAREX
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

NOT_SUCCESSFUL -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for HR_WAGE_COMP_EXT_MANIPULATE 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:
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_operation  TYPE PSPAR-ACTIO, "   
lv_created_key  TYPE BAPI_WAGE_COMP_KEY, "   
lv_not_successful  TYPE BAPI_WAGE_COMP_KEY, "   
lv_costassignment  TYPE BAPI_WAGE_COMP_COST_ASSIGN, "   
lv_testrun  TYPE BAPI_STAND-NO_COMMIT, "   
lt_extension_in  TYPE STANDARD TABLE OF BAPIPAREX, "   
lv_employeenumber  TYPE BAPI_WAGE_COMP_KEY-EMPLOYEENUMBER, "   
lv_subtype  TYPE BAPI_WAGE_COMP_KEY-SUBTYPE, "   
lv_objectid  TYPE BAPI_WAGE_COMP_KEY-OBJECTID, "   
lv_lockindicator  TYPE BAPI_WAGE_COMP_KEY-LOCKINDICATOR, "   
lv_validityend  TYPE BAPI_WAGE_COMP_KEY-VALIDITYEND, "   
lv_validitybegin  TYPE BAPI_WAGE_COMP_KEY-VALIDITYBEGIN, "   
lv_recordnumber  TYPE BAPI_WAGE_COMP_KEY-RECORDNUMBER, "   
lv_wagecompdata  TYPE BAPI_WAGE_COMP_DATA. "   

  CALL FUNCTION 'HR_WAGE_COMP_EXT_MANIPULATE'  "
    EXPORTING
         OPERATION = lv_operation
         COSTASSIGNMENT = lv_costassignment
         TESTRUN = lv_testrun
         EMPLOYEENUMBER = lv_employeenumber
         SUBTYPE = lv_subtype
         OBJECTID = lv_objectid
         LOCKINDICATOR = lv_lockindicator
         VALIDITYEND = lv_validityend
         VALIDITYBEGIN = lv_validitybegin
         RECORDNUMBER = lv_recordnumber
         WAGECOMPDATA = lv_wagecompdata
    IMPORTING
         CREATED_KEY = lv_created_key
    TABLES
         RETURN = lt_return
         EXTENSION_IN = lt_extension_in
    EXCEPTIONS
        NOT_SUCCESSFUL = 1
. " HR_WAGE_COMP_EXT_MANIPULATE




ABAP code using 7.40 inline data declarations to call FM HR_WAGE_COMP_EXT_MANIPULATE

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 ACTIO FROM PSPAR INTO @DATA(ld_operation).
 
 
 
 
"SELECT single NO_COMMIT FROM BAPI_STAND INTO @DATA(ld_testrun).
 
 
"SELECT single EMPLOYEENUMBER FROM BAPI_WAGE_COMP_KEY INTO @DATA(ld_employeenumber).
 
"SELECT single SUBTYPE FROM BAPI_WAGE_COMP_KEY INTO @DATA(ld_subtype).
 
"SELECT single OBJECTID FROM BAPI_WAGE_COMP_KEY INTO @DATA(ld_objectid).
 
"SELECT single LOCKINDICATOR FROM BAPI_WAGE_COMP_KEY INTO @DATA(ld_lockindicator).
 
"SELECT single VALIDITYEND FROM BAPI_WAGE_COMP_KEY INTO @DATA(ld_validityend).
 
"SELECT single VALIDITYBEGIN FROM BAPI_WAGE_COMP_KEY INTO @DATA(ld_validitybegin).
 
"SELECT single RECORDNUMBER FROM BAPI_WAGE_COMP_KEY INTO @DATA(ld_recordnumber).
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!