SAP HRIQ_PROGRAM_LEVEL_CHECK Function Module for IQ: Check Whether Stage Valid for Program
HRIQ_PROGRAM_LEVEL_CHECK is a standard hriq program level check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IQ: Check Whether Stage Valid for Program 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 hriq program level check FM, simply by entering the name HRIQ_PROGRAM_LEVEL_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: HRPIQ00ACPROG
Program Name: SAPLHRPIQ00ACPROG
Main Program: SAPLHRPIQ00ACPROG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HRIQ_PROGRAM_LEVEL_CHECK 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 'HRIQ_PROGRAM_LEVEL_CHECK'"IQ: Check Whether Stage Valid for Program.
EXPORTING
PROGRAM = "Program
LEVEL = "Stage
DATE = "
EXCEPTIONS
LEVEL_NOT_VALID = 1 LEVEL_MISSING = 2
IMPORTING Parameters details for HRIQ_PROGRAM_LEVEL_CHECK
PROGRAM - Program
Data type: HROBJECTOptional: No
Call by Reference: No ( called with pass by value option)
LEVEL - Stage
Data type: T7PIQLEVEL-ACLEVELOptional: No
Call by Reference: No ( called with pass by value option)
DATE -
Data type: DOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
LEVEL_NOT_VALID -
Data type:Optional: No
Call by Reference: Yes
LEVEL_MISSING -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for HRIQ_PROGRAM_LEVEL_CHECK 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_program | TYPE HROBJECT, " | |||
| lv_level_not_valid | TYPE HROBJECT, " | |||
| lv_level | TYPE T7PIQLEVEL-ACLEVEL, " | |||
| lv_level_missing | TYPE T7PIQLEVEL, " | |||
| lv_date | TYPE D. " |
|   CALL FUNCTION 'HRIQ_PROGRAM_LEVEL_CHECK' "IQ: Check Whether Stage Valid for Program |
| EXPORTING | ||
| PROGRAM | = lv_program | |
| LEVEL | = lv_level | |
| DATE | = lv_date | |
| EXCEPTIONS | ||
| LEVEL_NOT_VALID = 1 | ||
| LEVEL_MISSING = 2 | ||
| . " HRIQ_PROGRAM_LEVEL_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM HRIQ_PROGRAM_LEVEL_CHECK
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 ACLEVEL FROM T7PIQLEVEL INTO @DATA(ld_level). | ||||
Search for further information about these or an SAP related objects