SAP HRF_READ_PERSON_ATTRIBS Function Module for
HRF_READ_PERSON_ATTRIBS is a standard hrf read person attribs 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 hrf read person attribs FM, simply by entering the name HRF_READ_PERSON_ATTRIBS into the relevant SAP transaction such as SE37 or SE38.
Function Group: HRF_READ_DIM_ATTRIBUTES
Program Name: SAPLHRF_READ_DIM_ATTRIBUTES
Main Program: SAPLHRF_READ_DIM_ATTRIBUTES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HRF_READ_PERSON_ATTRIBS 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 'HRF_READ_PERSON_ATTRIBS'".
EXPORTING
* SPRSL = SY-LANGU "
ADRS3_NAME_FMT = "
* PERSONID = "
* IGNORE_DATES = "
* BEGDA = '18000101' "
* ENDDA = '99991231' "
* FORMNAME = "
NAME1_FORMAT = "
NAME2_FORMAT = "
NAME3_FORMAT = "
ADRS1_NAME_FMT = "
ADRS2_NAME_FMT = "
CHANGING
* SORT_NAME = "
* FIRE_DATE = "
* GENDER = "
* LANGU = "
* PRINT_NAME2 = "
* PRINT_NAME3 = "
* ADDRESS2 = "
* ADDRESS3 = "
* PERSONID_EXT = "
* MARITAL_STKEY = "
* MARITAL_STTEXT = "
* PRINT_NAME = "
* TELNR = "
* BIRTH_PLACE = "
* MARRIED_SINCE = "
* GENDER_TEXT = "
* NATIO_TEXT = "
* FULL_NAME = "
* LAST_NAME = "
* FIRST_NAME = "
* BIRTH_DATE = "
* NATIONALITY = "
* PERSONNEL_ID = "
* ADDRESS = "
* HIRE_DATE = "
EXCEPTIONS
DISPLAY_ERROR = 1
IMPORTING Parameters details for HRF_READ_PERSON_ATTRIBS
SPRSL -
Data type: SPRASDefault: SY-LANGU
Optional: Yes
Call by Reference: Yes
ADRS3_NAME_FMT -
Data type: PNAFOOptional: No
Call by Reference: Yes
PERSONID -
Data type: PERSONIDOptional: Yes
Call by Reference: Yes
IGNORE_DATES -
Data type: XFELDOptional: Yes
Call by Reference: Yes
BEGDA -
Data type: BEGDADefault: '18000101'
Optional: Yes
Call by Reference: Yes
ENDDA -
Data type: ENDDADefault: '99991231'
Optional: Yes
Call by Reference: Yes
FORMNAME -
Data type: HRF_NAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
NAME1_FORMAT -
Data type: PNAFOOptional: No
Call by Reference: Yes
NAME2_FORMAT -
Data type: PNAFOOptional: No
Call by Reference: Yes
NAME3_FORMAT -
Data type: PNAFOOptional: No
Call by Reference: Yes
ADRS1_NAME_FMT -
Data type: PNAFOOptional: No
Call by Reference: Yes
ADRS2_NAME_FMT -
Data type: PNAFOOptional: No
Call by Reference: Yes
CHANGING Parameters details for HRF_READ_PERSON_ATTRIBS
SORT_NAME -
Data type: SMNAMOptional: Yes
Call by Reference: Yes
FIRE_DATE -
Data type: ENDDAOptional: Yes
Call by Reference: Yes
GENDER -
Data type: GESCHOptional: Yes
Call by Reference: Yes
LANGU -
Data type: PAD_SPRASOptional: Yes
Call by Reference: Yes
PRINT_NAME2 -
Data type: EMNAMOptional: Yes
Call by Reference: Yes
PRINT_NAME3 -
Data type: EMNAMOptional: Yes
Call by Reference: Yes
ADDRESS2 -
Data type: ADRSOptional: Yes
Call by Reference: Yes
ADDRESS3 -
Data type: ADRSOptional: Yes
Call by Reference: Yes
PERSONID_EXT -
Data type: PERSONID_EXTOptional: Yes
Call by Reference: Yes
MARITAL_STKEY -
Data type: FAMSTOptional: Yes
Call by Reference: Yes
MARITAL_STTEXT -
Data type: FATXTOptional: Yes
Call by Reference: Yes
PRINT_NAME -
Data type: EMNAMOptional: Yes
Call by Reference: Yes
TELNR -
Data type: TELNROptional: Yes
Call by Reference: Yes
BIRTH_PLACE -
Data type: PAD_GBORTOptional: Yes
Call by Reference: Yes
MARRIED_SINCE -
Data type: FAMDTOptional: Yes
Call by Reference: Yes
GENDER_TEXT -
Data type: VAL_TEXTOptional: Yes
Call by Reference: Yes
NATIO_TEXT -
Data type: NATIOOptional: Yes
Call by Reference: Yes
FULL_NAME -
Data type: PAD_CNAMEOptional: Yes
Call by Reference: Yes
LAST_NAME -
Data type: PAD_NACHNOptional: Yes
Call by Reference: Yes
FIRST_NAME -
Data type: PAD_VORNAOptional: Yes
Call by Reference: Yes
BIRTH_DATE -
Data type: GBDATOptional: Yes
Call by Reference: Yes
NATIONALITY -
Data type: NATSLOptional: Yes
Call by Reference: Yes
PERSONNEL_ID -
Data type: PRDNIOptional: Yes
Call by Reference: Yes
ADDRESS -
Data type: ADRSOptional: Yes
Call by Reference: Yes
HIRE_DATE -
Data type: BEGDAOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
DISPLAY_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for HRF_READ_PERSON_ATTRIBS 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_sprsl | TYPE SPRAS, " SY-LANGU | |||
| lv_sort_name | TYPE SMNAM, " | |||
| lv_display_error | TYPE SMNAM, " | |||
| lv_fire_date | TYPE ENDDA, " | |||
| lv_adrs3_name_fmt | TYPE PNAFO, " | |||
| lv_gender | TYPE GESCH, " | |||
| lv_personid | TYPE PERSONID, " | |||
| lv_langu | TYPE PAD_SPRAS, " | |||
| lv_ignore_dates | TYPE XFELD, " | |||
| lv_print_name2 | TYPE EMNAM, " | |||
| lv_print_name3 | TYPE EMNAM, " | |||
| lv_address2 | TYPE ADRS, " | |||
| lv_address3 | TYPE ADRS, " | |||
| lv_personid_ext | TYPE PERSONID_EXT, " | |||
| lv_marital_stkey | TYPE FAMST, " | |||
| lv_marital_sttext | TYPE FATXT, " | |||
| lv_begda | TYPE BEGDA, " '18000101' | |||
| lv_print_name | TYPE EMNAM, " | |||
| lv_telnr | TYPE TELNR, " | |||
| lv_birth_place | TYPE PAD_GBORT, " | |||
| lv_married_since | TYPE FAMDT, " | |||
| lv_gender_text | TYPE VAL_TEXT, " | |||
| lv_natio_text | TYPE NATIO, " | |||
| lv_full_name | TYPE PAD_CNAME, " | |||
| lv_endda | TYPE ENDDA, " '99991231' | |||
| lv_last_name | TYPE PAD_NACHN, " | |||
| lv_formname | TYPE HRF_NAME, " | |||
| lv_first_name | TYPE PAD_VORNA, " | |||
| lv_birth_date | TYPE GBDAT, " | |||
| lv_name1_format | TYPE PNAFO, " | |||
| lv_nationality | TYPE NATSL, " | |||
| lv_name2_format | TYPE PNAFO, " | |||
| lv_name3_format | TYPE PNAFO, " | |||
| lv_personnel_id | TYPE PRDNI, " | |||
| lv_address | TYPE ADRS, " | |||
| lv_adrs1_name_fmt | TYPE PNAFO, " | |||
| lv_hire_date | TYPE BEGDA, " | |||
| lv_adrs2_name_fmt | TYPE PNAFO. " |
|   CALL FUNCTION 'HRF_READ_PERSON_ATTRIBS' " |
| EXPORTING | ||
| SPRSL | = lv_sprsl | |
| ADRS3_NAME_FMT | = lv_adrs3_name_fmt | |
| PERSONID | = lv_personid | |
| IGNORE_DATES | = lv_ignore_dates | |
| BEGDA | = lv_begda | |
| ENDDA | = lv_endda | |
| FORMNAME | = lv_formname | |
| NAME1_FORMAT | = lv_name1_format | |
| NAME2_FORMAT | = lv_name2_format | |
| NAME3_FORMAT | = lv_name3_format | |
| ADRS1_NAME_FMT | = lv_adrs1_name_fmt | |
| ADRS2_NAME_FMT | = lv_adrs2_name_fmt | |
| CHANGING | ||
| SORT_NAME | = lv_sort_name | |
| FIRE_DATE | = lv_fire_date | |
| GENDER | = lv_gender | |
| LANGU | = lv_langu | |
| PRINT_NAME2 | = lv_print_name2 | |
| PRINT_NAME3 | = lv_print_name3 | |
| ADDRESS2 | = lv_address2 | |
| ADDRESS3 | = lv_address3 | |
| PERSONID_EXT | = lv_personid_ext | |
| MARITAL_STKEY | = lv_marital_stkey | |
| MARITAL_STTEXT | = lv_marital_sttext | |
| PRINT_NAME | = lv_print_name | |
| TELNR | = lv_telnr | |
| BIRTH_PLACE | = lv_birth_place | |
| MARRIED_SINCE | = lv_married_since | |
| GENDER_TEXT | = lv_gender_text | |
| NATIO_TEXT | = lv_natio_text | |
| FULL_NAME | = lv_full_name | |
| LAST_NAME | = lv_last_name | |
| FIRST_NAME | = lv_first_name | |
| BIRTH_DATE | = lv_birth_date | |
| NATIONALITY | = lv_nationality | |
| PERSONNEL_ID | = lv_personnel_id | |
| ADDRESS | = lv_address | |
| HIRE_DATE | = lv_hire_date | |
| EXCEPTIONS | ||
| DISPLAY_ERROR = 1 | ||
| . " HRF_READ_PERSON_ATTRIBS | ||
ABAP code using 7.40 inline data declarations to call FM HRF_READ_PERSON_ATTRIBS
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.| DATA(ld_sprsl) | = SY-LANGU. | |||
| DATA(ld_begda) | = '18000101'. | |||
| DATA(ld_endda) | = '99991231'. | |||
Search for further information about these or an SAP related objects