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

Function HRIQ_VORSW_TEXT_READ 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_VORSW_TEXT_READ'".
EXPORTING
VORSW = "
IMPORTING
VORSW_TEXT = "
IMPORTING Parameters details for HRIQ_VORSW_TEXT_READ
VORSW -
Data type: T535N-TITELOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for HRIQ_VORSW_TEXT_READ
VORSW_TEXT -
Data type: T535N-TTOUTOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for HRIQ_VORSW_TEXT_READ 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_vorsw | TYPE T535N-TITEL, " | |||
| lv_vorsw_text | TYPE T535N-TTOUT. " |
|   CALL FUNCTION 'HRIQ_VORSW_TEXT_READ' " |
| EXPORTING | ||
| VORSW | = lv_vorsw | |
| IMPORTING | ||
| VORSW_TEXT | = lv_vorsw_text | |
| . " HRIQ_VORSW_TEXT_READ | ||
ABAP code using 7.40 inline data declarations to call FM HRIQ_VORSW_TEXT_READ
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 TITEL FROM T535N INTO @DATA(ld_vorsw). | ||||
| "SELECT single TTOUT FROM T535N INTO @DATA(ld_vorsw_text). | ||||
Search for further information about these or an SAP related objects