SAP HRIQ_GET_TRANSCRIPT_TYPE_DATA Function Module for Read Data for Transcript Category
HRIQ_GET_TRANSCRIPT_TYPE_DATA is a standard hriq get transcript type data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read Data for Transcript Category 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 get transcript type data FM, simply by entering the name HRIQ_GET_TRANSCRIPT_TYPE_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: HRPIQ00TRANSCRIPT
Program Name: SAPLHRPIQ00TRANSCRIPT
Main Program: SAPLHRPIQ00TRANSCRIPT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HRIQ_GET_TRANSCRIPT_TYPE_DATA 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_GET_TRANSCRIPT_TYPE_DATA'"Read Data for Transcript Category.
EXPORTING
I_TRTYPE = "Transcript Category
IMPORTING
FA_RELEVANT = "
FA_TRANSSTRAT = "
EXCEPTIONS
TYPE_NOT_FOUND = 1
IMPORTING Parameters details for HRIQ_GET_TRANSCRIPT_TYPE_DATA
I_TRTYPE - Transcript Category
Data type: PIQTRTRANSTYPEOptional: No
Call by Reference: Yes
EXPORTING Parameters details for HRIQ_GET_TRANSCRIPT_TYPE_DATA
FA_RELEVANT -
Data type: PIQ_FARELEVANTOptional: No
Call by Reference: Yes
FA_TRANSSTRAT -
Data type: PIQTRANSSTRATOptional: No
Call by Reference: Yes
EXCEPTIONS details
TYPE_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for HRIQ_GET_TRANSCRIPT_TYPE_DATA 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_i_trtype | TYPE PIQTRTRANSTYPE, " | |||
| lv_fa_relevant | TYPE PIQ_FARELEVANT, " | |||
| lv_type_not_found | TYPE PIQ_FARELEVANT, " | |||
| lv_fa_transstrat | TYPE PIQTRANSSTRAT. " |
|   CALL FUNCTION 'HRIQ_GET_TRANSCRIPT_TYPE_DATA' "Read Data for Transcript Category |
| EXPORTING | ||
| I_TRTYPE | = lv_i_trtype | |
| IMPORTING | ||
| FA_RELEVANT | = lv_fa_relevant | |
| FA_TRANSSTRAT | = lv_fa_transstrat | |
| EXCEPTIONS | ||
| TYPE_NOT_FOUND = 1 | ||
| . " HRIQ_GET_TRANSCRIPT_TYPE_DATA | ||
ABAP code using 7.40 inline data declarations to call FM HRIQ_GET_TRANSCRIPT_TYPE_DATA
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.Search for further information about these or an SAP related objects