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

Function RHGA_READ_ATTRIBUTES_SET 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 'RHGA_READ_ATTRIBUTES_SET'".
EXPORTING
SCENARIO = "General Attribute Maintenance: Application Scenario
OBJECTS = "
* ATTRIBUTES = "Table: Attribute Names
* CHECK_AUTHORITY = ' ' "Execute authorization check
* PPOMA_MODE = ' ' "Call from PPOMA
* NO_CHECKS = 'X' "
* NO_INH_RESOLUTION = ' ' "
IMPORTING
ATTRIB_EXT = "Table: Attributes of Several Objects (Inherited)
EXCEPTIONS
INTERNAL_ERROR = 1 INVALID_OBJECT = 2 INVALID_SCENARIO = 3 INVALID_ATTRIBUTE = 4 NO_AUTHORITY = 5
IMPORTING Parameters details for RHGA_READ_ATTRIBUTES_SET
SCENARIO - General Attribute Maintenance: Application Scenario
Data type: OM_ATTRSCNOptional: No
Call by Reference: Yes
OBJECTS -
Data type: HRTB_OBJECTOptional: No
Call by Reference: Yes
ATTRIBUTES - Table: Attribute Names
Data type: HRTB_ATTRIBOptional: Yes
Call by Reference: Yes
CHECK_AUTHORITY - Execute authorization check
Data type: FLAGDefault: SPACE
Optional: Yes
Call by Reference: Yes
PPOMA_MODE - Call from PPOMA
Data type: FLAGDefault: SPACE
Optional: Yes
Call by Reference: Yes
NO_CHECKS -
Data type: FLAGDefault: 'X'
Optional: Yes
Call by Reference: Yes
NO_INH_RESOLUTION -
Data type: FLAGDefault: SPACE
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for RHGA_READ_ATTRIBUTES_SET
ATTRIB_EXT - Table: Attributes of Several Objects (Inherited)
Data type: HRTB_ATTVALRTXOptional: No
Call by Reference: Yes
EXCEPTIONS details
INTERNAL_ERROR - System Error
Data type:Optional: No
Call by Reference: Yes
INVALID_OBJECT - Invalid Object
Data type:Optional: No
Call by Reference: Yes
INVALID_SCENARIO -
Data type:Optional: No
Call by Reference: Yes
INVALID_ATTRIBUTE -
Data type:Optional: No
Call by Reference: Yes
NO_AUTHORITY - No Authorization
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RHGA_READ_ATTRIBUTES_SET 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_scenario | TYPE OM_ATTRSCN, " | |||
| lv_attrib_ext | TYPE HRTB_ATTVALRTX, " | |||
| lv_internal_error | TYPE HRTB_ATTVALRTX, " | |||
| lv_objects | TYPE HRTB_OBJECT, " | |||
| lv_invalid_object | TYPE HRTB_OBJECT, " | |||
| lv_attributes | TYPE HRTB_ATTRIB, " | |||
| lv_invalid_scenario | TYPE HRTB_ATTRIB, " | |||
| lv_check_authority | TYPE FLAG, " SPACE | |||
| lv_invalid_attribute | TYPE FLAG, " | |||
| lv_ppoma_mode | TYPE FLAG, " SPACE | |||
| lv_no_authority | TYPE FLAG, " | |||
| lv_no_checks | TYPE FLAG, " 'X' | |||
| lv_no_inh_resolution | TYPE FLAG. " SPACE |
|   CALL FUNCTION 'RHGA_READ_ATTRIBUTES_SET' " |
| EXPORTING | ||
| SCENARIO | = lv_scenario | |
| OBJECTS | = lv_objects | |
| ATTRIBUTES | = lv_attributes | |
| CHECK_AUTHORITY | = lv_check_authority | |
| PPOMA_MODE | = lv_ppoma_mode | |
| NO_CHECKS | = lv_no_checks | |
| NO_INH_RESOLUTION | = lv_no_inh_resolution | |
| IMPORTING | ||
| ATTRIB_EXT | = lv_attrib_ext | |
| EXCEPTIONS | ||
| INTERNAL_ERROR = 1 | ||
| INVALID_OBJECT = 2 | ||
| INVALID_SCENARIO = 3 | ||
| INVALID_ATTRIBUTE = 4 | ||
| NO_AUTHORITY = 5 | ||
| . " RHGA_READ_ATTRIBUTES_SET | ||
ABAP code using 7.40 inline data declarations to call FM RHGA_READ_ATTRIBUTES_SET
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_check_authority) | = ' '. | |||
| DATA(ld_ppoma_mode) | = ' '. | |||
| DATA(ld_no_checks) | = 'X'. | |||
| DATA(ld_no_inh_resolution) | = ' '. | |||
Search for further information about these or an SAP related objects