SAP HR_SPA_EFFECTIVE_DATE_GET Function Module for Salary packaging: company car regulation









HR_SPA_EFFECTIVE_DATE_GET is a standard hr spa effective date get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Salary packaging: company car regulation 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 effective date get FM, simply by entering the name HR_SPA_EFFECTIVE_DATE_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function HR_SPA_EFFECTIVE_DATE_GET 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_EFFECTIVE_DATE_GET'"Salary packaging: company car regulation
EXPORTING
PERNR = "
DATE = "Date
* MOLGA = "

IMPORTING
EFF_DATE = "Date and time, current (application server) date
VIA_IT41 = "Date retrieved via infotype 41

EXCEPTIONS
ERROR = 1
.



IMPORTING Parameters details for HR_SPA_EFFECTIVE_DATE_GET

PERNR -

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

DATE - Date

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

MOLGA -

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

EXPORTING Parameters details for HR_SPA_EFFECTIVE_DATE_GET

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

Data type: DATUM
Optional: No
Call by Reference: Yes

VIA_IT41 - Date retrieved via infotype 41

Data type: FLAG
Optional: No
Call by Reference: Yes

EXCEPTIONS details

ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for HR_SPA_EFFECTIVE_DATE_GET 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_error  TYPE STRING, "   
lv_pernr  TYPE PERNR-PERNR, "   
lv_eff_date  TYPE DATUM, "   
lv_date  TYPE DATUM, "   
lv_via_it41  TYPE FLAG, "   
lv_molga  TYPE T500L-MOLGA. "   

  CALL FUNCTION 'HR_SPA_EFFECTIVE_DATE_GET'  "Salary packaging: company car regulation
    EXPORTING
         PERNR = lv_pernr
         DATE = lv_date
         MOLGA = lv_molga
    IMPORTING
         EFF_DATE = lv_eff_date
         VIA_IT41 = lv_via_it41
    EXCEPTIONS
        ERROR = 1
. " HR_SPA_EFFECTIVE_DATE_GET




ABAP code using 7.40 inline data declarations to call FM HR_SPA_EFFECTIVE_DATE_GET

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_pernr).
 
 
 
 
"SELECT single MOLGA FROM T500L INTO @DATA(ld_molga).
 


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!