SAP HRIQAUDS_MAINTAIN_DLG Function Module for Subrequirements: Modal Maintenance
HRIQAUDS_MAINTAIN_DLG is a standard hriqauds maintain dlg SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Subrequirements: Modal Maintenance 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 hriqauds maintain dlg FM, simply by entering the name HRIQAUDS_MAINTAIN_DLG into the relevant SAP transaction such as SE37 or SE38.
Function Group: HRPIQ00AUDS_DLG
Program Name: SAPLHRPIQ00AUDS_DLG
Main Program: SAPLHRPIQ00AUDS_DLG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HRIQAUDS_MAINTAIN_DLG 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 'HRIQAUDS_MAINTAIN_DLG'"Subrequirements: Modal Maintenance.
EXPORTING
* IV_MODE = 'INS' "Field (3 Bytes in Length)
* IV_MODAL = ' ' "Indicator
* IV_CUST = ' ' "Direct Call from Customizing
* IV_AUTHORITY_CHECK = 'X' "Perform Authority Check
* IV_ADD_COND = "Subrequirement as Auxiliary Condition
* IV_SUBREQ_TYPE = 'SUB1' "Subrequirement Category
IMPORTING
EV_CANCEL = "Indicator
CHANGING
CV_RULEMODULE = "Rule Module
EXCEPTIONS
SUBREQ_EXISTS = 1 INVALID_PARAMETERS = 2 NOTHING_FOUND = 3 NUMBER_ERROR = 4 ENQUEUE_ERROR = 5 OBJECT_ERROR = 6
IMPORTING Parameters details for HRIQAUDS_MAINTAIN_DLG
IV_MODE - Field (3 Bytes in Length)
Data type: CHAR3Default: 'INS'
Optional: No
Call by Reference: Yes
IV_MODAL - Indicator
Data type: PIQFLAGDefault: ' '
Optional: Yes
Call by Reference: Yes
IV_CUST - Direct Call from Customizing
Data type: PIQFLAGDefault: ' '
Optional: Yes
Call by Reference: Yes
IV_AUTHORITY_CHECK - Perform Authority Check
Data type: PIQFLAGDefault: 'X'
Optional: Yes
Call by Reference: Yes
IV_ADD_COND - Subrequirement as Auxiliary Condition
Data type: PIQFLAGOptional: Yes
Call by Reference: Yes
IV_SUBREQ_TYPE - Subrequirement Category
Data type: PIQRMTYPEDefault: 'SUB1'
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for HRIQAUDS_MAINTAIN_DLG
EV_CANCEL - Indicator
Data type: PIQFLAGOptional: No
Call by Reference: Yes
CHANGING Parameters details for HRIQAUDS_MAINTAIN_DLG
CV_RULEMODULE - Rule Module
Data type: PIQRULEMODULEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
SUBREQ_EXISTS - A Subrequirement Already Exists for the Key
Data type:Optional: No
Call by Reference: Yes
INVALID_PARAMETERS - Incorrect Call of Function Module
Data type:Optional: No
Call by Reference: Yes
NOTHING_FOUND - No Data Available
Data type:Optional: No
Call by Reference: Yes
NUMBER_ERROR - Error During Internal Number Assignment
Data type:Optional: No
Call by Reference: Yes
ENQUEUE_ERROR - Error While Locking Object
Data type:Optional: No
Call by Reference: Yes
OBJECT_ERROR - Error While Checking Customizing Object
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for HRIQAUDS_MAINTAIN_DLG 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_iv_mode | TYPE CHAR3, " 'INS' | |||
| lv_ev_cancel | TYPE PIQFLAG, " | |||
| lv_cv_rulemodule | TYPE PIQRULEMODULE, " | |||
| lv_subreq_exists | TYPE PIQRULEMODULE, " | |||
| lv_iv_modal | TYPE PIQFLAG, " ' ' | |||
| lv_invalid_parameters | TYPE PIQFLAG, " | |||
| lv_iv_cust | TYPE PIQFLAG, " ' ' | |||
| lv_nothing_found | TYPE PIQFLAG, " | |||
| lv_number_error | TYPE PIQFLAG, " | |||
| lv_iv_authority_check | TYPE PIQFLAG, " 'X' | |||
| lv_iv_add_cond | TYPE PIQFLAG, " | |||
| lv_enqueue_error | TYPE PIQFLAG, " | |||
| lv_object_error | TYPE PIQFLAG, " | |||
| lv_iv_subreq_type | TYPE PIQRMTYPE. " 'SUB1' |
|   CALL FUNCTION 'HRIQAUDS_MAINTAIN_DLG' "Subrequirements: Modal Maintenance |
| EXPORTING | ||
| IV_MODE | = lv_iv_mode | |
| IV_MODAL | = lv_iv_modal | |
| IV_CUST | = lv_iv_cust | |
| IV_AUTHORITY_CHECK | = lv_iv_authority_check | |
| IV_ADD_COND | = lv_iv_add_cond | |
| IV_SUBREQ_TYPE | = lv_iv_subreq_type | |
| IMPORTING | ||
| EV_CANCEL | = lv_ev_cancel | |
| CHANGING | ||
| CV_RULEMODULE | = lv_cv_rulemodule | |
| EXCEPTIONS | ||
| SUBREQ_EXISTS = 1 | ||
| INVALID_PARAMETERS = 2 | ||
| NOTHING_FOUND = 3 | ||
| NUMBER_ERROR = 4 | ||
| ENQUEUE_ERROR = 5 | ||
| OBJECT_ERROR = 6 | ||
| . " HRIQAUDS_MAINTAIN_DLG | ||
ABAP code using 7.40 inline data declarations to call FM HRIQAUDS_MAINTAIN_DLG
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_iv_mode) | = 'INS'. | |||
| DATA(ld_iv_modal) | = ' '. | |||
| DATA(ld_iv_cust) | = ' '. | |||
| DATA(ld_iv_authority_check) | = 'X'. | |||
| DATA(ld_iv_subreq_type) | = 'SUB1'. | |||
Search for further information about these or an SAP related objects