SAP HR_DE_GET_GARNISHMENT_RESULTS Function Module for

Search SAP Function Modules

HR_DE_GET_GARNISHMENT_RESULTS is a standard hr de get garnishment results 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 de get garnishment results FM, simply by entering the name HR_DE_GET_GARNISHMENT_RESULTS into the relevant SAP transaction such as SE37 or SE38.

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

Function HR_DE_GET_GARNISHMENT_RESULTS 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_DE_GET_GARNISHMENT_RESULTS'"
  EXPORTING
   PERNR =  "
   PFART =  "
   PFNUM =  "
*  LAST =  "
*  PABRJ =  "
*  PABRP =  "
*  PABRJ_END =  "
*  PABRP_END =  "
*  WAERS =  "

TABLES
   RESULT_TAB =  "

EXCEPTIONS
   NO_RESULTS = 1    PERIOD_MISMATCH_ERROR = 2    CLUSTER_VERSION_MISMATCH = 3    INCONSISTENCY_DP_DQ = 4    NO_AUTHORITY = 5    ERROR_IN_CURRENCY_CONVERSION = 6 

.

IMPORTING Parameters details for HR_DE_GET_GARNISHMENT_RESULTS

PERNR -

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

PFART -

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

PFNUM -

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

LAST -

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

PABRJ -

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

PABRP -

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

PABRJ_END -

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

PABRP_END -

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

WAERS -

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

TABLES Parameters details for HR_DE_GET_GARNISHMENT_RESULTS

RESULT_TAB -

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

EXCEPTIONS details

NO_RESULTS -

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

PERIOD_MISMATCH_ERROR -

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

CLUSTER_VERSION_MISMATCH -

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

INCONSISTENCY_DP_DQ -

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

NO_AUTHORITY -

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

ERROR_IN_CURRENCY_CONVERSION -

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

Copy and paste ABAP code example for HR_DE_GET_GARNISHMENT_RESULTS 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 HR_DE_GET_GARNISHMENT_RESULTS

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