SAP HR_EVAL_POSSIBLE_ATTR_GET Function Module for









HR_EVAL_POSSIBLE_ATTR_GET is a standard hr eval possible attr get 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 eval possible attr get FM, simply by entering the name HR_EVAL_POSSIBLE_ATTR_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function HR_EVAL_POSSIBLE_ATTR_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_EVAL_POSSIBLE_ATTR_GET'"
EXPORTING
IM_TYPE = "
IM_LANGU = "

TABLES
EX_ATTRTAB = "
.



IMPORTING Parameters details for HR_EVAL_POSSIBLE_ATTR_GET

IM_TYPE -

Data type: PEVST-TYPE
Optional: No
Call by Reference: Yes

IM_LANGU -

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

TABLES Parameters details for HR_EVAL_POSSIBLE_ATTR_GET

EX_ATTRTAB -

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

Copy and paste ABAP code example for HR_EVAL_POSSIBLE_ATTR_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_im_type  TYPE PEVST-TYPE, "   
lt_ex_attrtab  TYPE STANDARD TABLE OF T52E3T, "   
lv_im_langu  TYPE LANGU. "   

  CALL FUNCTION 'HR_EVAL_POSSIBLE_ATTR_GET'  "
    EXPORTING
         IM_TYPE = lv_im_type
         IM_LANGU = lv_im_langu
    TABLES
         EX_ATTRTAB = lt_ex_attrtab
. " HR_EVAL_POSSIBLE_ATTR_GET




ABAP code using 7.40 inline data declarations to call FM HR_EVAL_POSSIBLE_ATTR_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 TYPE FROM PEVST INTO @DATA(ld_im_type).
 
 
 


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!