SAP TFC_SREP_ITEM_GET_HRY_STRUCT Function Module for
TFC_SREP_ITEM_GET_HRY_STRUCT is a standard tfc srep item get hry struct 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 tfc srep item get hry struct FM, simply by entering the name TFC_SREP_ITEM_GET_HRY_STRUCT into the relevant SAP transaction such as SE37 or SE38.
Function Group: TFC_SREP
Program Name: SAPLTFC_SREP
Main Program: SAPLTFC_SREP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TFC_SREP_ITEM_GET_HRY_STRUCT 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 'TFC_SREP_ITEM_GET_HRY_STRUCT'".
EXPORTING
* I_REQUNR = "
* I_OSOURCE = "DataSource
* I_MAXSIZE = "Maximum Number of Table Entries in Extraction API Interface
* I_INITFLAG = "Flag: Callup of the extraction APIs for initialization
* I_S_HIEBAS = "
* I_S_HIEFLAG = "
* I_S_HIERSEL = "
IMPORTING
E_S_HEADER = "
E_PACKAGES = "
TABLES
* I_T_LANGU = "
* E_T_HIETEXT = "
* E_T_HIENODE = "Task Element: Hierarchy Information
EXCEPTIONS
ERROR_PASSED_TO_MESS_HANDLER = 1
IMPORTING Parameters details for TFC_SREP_ITEM_GET_HRY_STRUCT
I_REQUNR -
Data type: SBIWA_S_INTERFACE-REQUNROptional: Yes
Call by Reference: No ( called with pass by value option)
I_OSOURCE - DataSource
Data type: RSDS_DATASOURCEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_MAXSIZE - Maximum Number of Table Entries in Extraction API Interface
Data type: RSMAXSIZEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_INITFLAG - Flag: Callup of the extraction APIs for initialization
Data type: RSINITFLGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_S_HIEBAS -
Data type: RSAP_S_HIEBASOptional: Yes
Call by Reference: No ( called with pass by value option)
I_S_HIEFLAG -
Data type: RSAP_S_HIEFLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_S_HIERSEL -
Data type: RSAP_S_HIER_LISTOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for TFC_SREP_ITEM_GET_HRY_STRUCT
E_S_HEADER -
Data type: DATAOptional: No
Call by Reference: Yes
E_PACKAGES -
Data type: SBIWA_FLAGOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for TFC_SREP_ITEM_GET_HRY_STRUCT
I_T_LANGU -
Data type: SBIWA_T_LANGUOptional: Yes
Call by Reference: Yes
E_T_HIETEXT -
Data type: RSAP_T_HIETEXTOptional: Yes
Call by Reference: Yes
E_T_HIENODE - Task Element: Hierarchy Information
Data type: STANDARD TABLEOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
ERROR_PASSED_TO_MESS_HANDLER -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for TFC_SREP_ITEM_GET_HRY_STRUCT 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_requnr | TYPE SBIWA_S_INTERFACE-REQUNR, " | |||
| lt_i_t_langu | TYPE STANDARD TABLE OF SBIWA_T_LANGU, " | |||
| lv_e_s_header | TYPE DATA, " | |||
| lv_error_passed_to_mess_handler | TYPE DATA, " | |||
| lv_i_osource | TYPE RSDS_DATASOURCE, " | |||
| lv_e_packages | TYPE SBIWA_FLAG, " | |||
| lt_e_t_hietext | TYPE STANDARD TABLE OF RSAP_T_HIETEXT, " | |||
| lv_i_maxsize | TYPE RSMAXSIZE, " | |||
| lt_e_t_hienode | TYPE STANDARD TABLE OF STANDARD TABLE, " | |||
| lv_i_initflag | TYPE RSINITFLG, " | |||
| lv_i_s_hiebas | TYPE RSAP_S_HIEBAS, " | |||
| lv_i_s_hieflag | TYPE RSAP_S_HIEFLAG, " | |||
| lv_i_s_hiersel | TYPE RSAP_S_HIER_LIST. " |
|   CALL FUNCTION 'TFC_SREP_ITEM_GET_HRY_STRUCT' " |
| EXPORTING | ||
| I_REQUNR | = lv_i_requnr | |
| I_OSOURCE | = lv_i_osource | |
| I_MAXSIZE | = lv_i_maxsize | |
| I_INITFLAG | = lv_i_initflag | |
| I_S_HIEBAS | = lv_i_s_hiebas | |
| I_S_HIEFLAG | = lv_i_s_hieflag | |
| I_S_HIERSEL | = lv_i_s_hiersel | |
| IMPORTING | ||
| E_S_HEADER | = lv_e_s_header | |
| E_PACKAGES | = lv_e_packages | |
| TABLES | ||
| I_T_LANGU | = lt_i_t_langu | |
| E_T_HIETEXT | = lt_e_t_hietext | |
| E_T_HIENODE | = lt_e_t_hienode | |
| EXCEPTIONS | ||
| ERROR_PASSED_TO_MESS_HANDLER = 1 | ||
| . " TFC_SREP_ITEM_GET_HRY_STRUCT | ||
ABAP code using 7.40 inline data declarations to call FM TFC_SREP_ITEM_GET_HRY_STRUCT
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 REQUNR FROM SBIWA_S_INTERFACE INTO @DATA(ld_i_requnr). | ||||
Search for further information about these or an SAP related objects