SAP HR_SPA_UPDATE Function Module for Approve a salary package









HR_SPA_UPDATE is a standard hr spa update SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Approve a salary package 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 hr spa update FM, simply by entering the name HR_SPA_UPDATE into the relevant SAP transaction such as SE37 or SE38.

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



Function HR_SPA_UPDATE 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_SPA_UPDATE'"Approve a salary package
EXPORTING
PERSNR = "Personnel number
EFF_DATE = "Date and time, current (application server) date
VARIANT_ID = "Package variant ID

EXCEPTIONS
UPDATE_ERROR = 1 NO_ENQUEUE = 2 PACKAGE_ERROR = 3 PACKAGE_INCONSISTENCY = 4
.



IMPORTING Parameters details for HR_SPA_UPDATE

PERSNR - Personnel number

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

EFF_DATE - Date and time, current (application server) date

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

VARIANT_ID - Package variant ID

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

EXCEPTIONS details

UPDATE_ERROR -

Data type:
Optional: No
Call by Reference: Yes

NO_ENQUEUE -

Data type:
Optional: No
Call by Reference: Yes

PACKAGE_ERROR -

Data type:
Optional: No
Call by Reference: Yes

PACKAGE_INCONSISTENCY -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for HR_SPA_UPDATE 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_persnr  TYPE PERNR-PERNR, "   
lv_update_error  TYPE PERNR, "   
lv_eff_date  TYPE T5W7I-EFFDA, "   
lv_no_enqueue  TYPE T5W7I, "   
lv_variant_id  TYPE T5W7I-VARID, "   
lv_package_error  TYPE T5W7I, "   
lv_package_inconsistency  TYPE T5W7I. "   

  CALL FUNCTION 'HR_SPA_UPDATE'  "Approve a salary package
    EXPORTING
         PERSNR = lv_persnr
         EFF_DATE = lv_eff_date
         VARIANT_ID = lv_variant_id
    EXCEPTIONS
        UPDATE_ERROR = 1
        NO_ENQUEUE = 2
        PACKAGE_ERROR = 3
        PACKAGE_INCONSISTENCY = 4
. " HR_SPA_UPDATE




ABAP code using 7.40 inline data declarations to call FM HR_SPA_UPDATE

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 PERNR FROM PERNR INTO @DATA(ld_persnr).
 
 
"SELECT single EFFDA FROM T5W7I INTO @DATA(ld_eff_date).
 
 
"SELECT single VARID FROM T5W7I INTO @DATA(ld_variant_id).
 
 
 


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!