SAP GSS_DATA_GET_CONTENT Function Module for GSS: Get data back from RFC-System
GSS_DATA_GET_CONTENT is a standard gss data get content SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for GSS: Get data back from RFC-System 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 gss data get content FM, simply by entering the name GSS_DATA_GET_CONTENT into the relevant SAP transaction such as SE37 or SE38.
Function Group: S4HGSS
Program Name: SAPLS4HGSS
Main Program: SAPLS4HGSS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function GSS_DATA_GET_CONTENT 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 'GSS_DATA_GET_CONTENT'"GSS: Get data back from RFC-System.
EXPORTING
* IS_TABLES = "One line in ET_TABLES
* I_SCENARIO = "GSS: Scenario for dependent tables
* I_COMPRESS = 'X' "Compress via Index tables
* I_TEMPERATURE_COLD = "Read Cold Data
* I_MASTER_ID = "Master ID from IRF
* I_CALL_ID = "Caller ID from IRF
IMPORTING
ET_TRANSFER = "GSS: Transferstructure for RFC-Calls of Content
EV_COMPLETED = "'X' if function has been processed
ET_LOOKUP_DATA = "GSS: Index Transferstructure for RFC-Calls of Content
ET_LOOKUP_FIELD = "GSS: Lookup-Index Transferstructure for Field
ET_LOOKUP_VALUE = "GSS: Lookup-Index Transferstructure for Values
ET_LOOKUP_HIERARCHY = "GSS: Lookup-Index Transferstructure for Hierarchy
ET_RUNTIME = "GSS: Table Type for runtime analysis
TABLES
* ET_DFIES = "
EXCEPTIONS
ERROR_IN_SQL = 1 KEY_DOES_NOT_EXIST = 2 NOT_AUTHORIZED = 3 TABLE_NOT_AVAILABLE = 4 NO_WHERE_CLAUSE = 5 ENDLESS_LOOP = 6
IMPORTING Parameters details for GSS_DATA_GET_CONTENT
IS_TABLES - One line in ET_TABLES
Data type: GSS_S_SEARCH_AREAOptional: Yes
Call by Reference: No ( called with pass by value option)
I_SCENARIO - GSS: Scenario for dependent tables
Data type: GSS_SCENARIOOptional: Yes
Call by Reference: No ( called with pass by value option)
I_COMPRESS - Compress via Index tables
Data type: CHAR1Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_TEMPERATURE_COLD - Read Cold Data
Data type: CHAR1Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MASTER_ID - Master ID from IRF
Data type: SYSUUID_C32Optional: Yes
Call by Reference: No ( called with pass by value option)
I_CALL_ID - Caller ID from IRF
Data type: SYSUUID_C32Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for GSS_DATA_GET_CONTENT
ET_TRANSFER - GSS: Transferstructure for RFC-Calls of Content
Data type: GSS_T_TRANSFEROptional: No
Call by Reference: No ( called with pass by value option)
EV_COMPLETED - 'X' if function has been processed
Data type: BOOLEANOptional: No
Call by Reference: No ( called with pass by value option)
ET_LOOKUP_DATA - GSS: Index Transferstructure for RFC-Calls of Content
Data type: GSS_T_TRANSFER_DATAOptional: No
Call by Reference: No ( called with pass by value option)
ET_LOOKUP_FIELD - GSS: Lookup-Index Transferstructure for Field
Data type: GSS_T_TRANSFER_FIELDOptional: No
Call by Reference: No ( called with pass by value option)
ET_LOOKUP_VALUE - GSS: Lookup-Index Transferstructure for Values
Data type: GSS_T_TRANSFER_VALUEOptional: No
Call by Reference: No ( called with pass by value option)
ET_LOOKUP_HIERARCHY - GSS: Lookup-Index Transferstructure for Hierarchy
Data type: GSS_T_TRANSFER_HIERARCHYOptional: No
Call by Reference: No ( called with pass by value option)
ET_RUNTIME - GSS: Table Type for runtime analysis
Data type: GSS_T_DB_RUNTIMEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for GSS_DATA_GET_CONTENT
ET_DFIES -
Data type: DFIESOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
ERROR_IN_SQL - SQL-Statement got aborted
Data type:Optional: No
Call by Reference: Yes
KEY_DOES_NOT_EXIST - INDX-Entry does not exist
Data type:Optional: No
Call by Reference: Yes
NOT_AUTHORIZED - No Authority for table
Data type:Optional: No
Call by Reference: Yes
TABLE_NOT_AVAILABLE - Table does not exist
Data type:Optional: No
Call by Reference: Yes
NO_WHERE_CLAUSE - Empty Where-Clause provided
Data type:Optional: No
Call by Reference: Yes
ENDLESS_LOOP - Table is in endless loop
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for GSS_DATA_GET_CONTENT 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: | ||||
| lt_et_dfies | TYPE STANDARD TABLE OF DFIES, " | |||
| lv_is_tables | TYPE GSS_S_SEARCH_AREA, " | |||
| lv_et_transfer | TYPE GSS_T_TRANSFER, " | |||
| lv_error_in_sql | TYPE GSS_T_TRANSFER, " | |||
| lv_i_scenario | TYPE GSS_SCENARIO, " | |||
| lv_ev_completed | TYPE BOOLEAN, " | |||
| lv_key_does_not_exist | TYPE BOOLEAN, " | |||
| lv_i_compress | TYPE CHAR1, " 'X' | |||
| lv_et_lookup_data | TYPE GSS_T_TRANSFER_DATA, " | |||
| lv_not_authorized | TYPE GSS_T_TRANSFER_DATA, " | |||
| lv_et_lookup_field | TYPE GSS_T_TRANSFER_FIELD, " | |||
| lv_i_temperature_cold | TYPE CHAR1, " | |||
| lv_table_not_available | TYPE CHAR1, " | |||
| lv_i_master_id | TYPE SYSUUID_C32, " | |||
| lv_et_lookup_value | TYPE GSS_T_TRANSFER_VALUE, " | |||
| lv_no_where_clause | TYPE GSS_T_TRANSFER_VALUE, " | |||
| lv_i_call_id | TYPE SYSUUID_C32, " | |||
| lv_endless_loop | TYPE SYSUUID_C32, " | |||
| lv_et_lookup_hierarchy | TYPE GSS_T_TRANSFER_HIERARCHY, " | |||
| lv_et_runtime | TYPE GSS_T_DB_RUNTIME. " |
|   CALL FUNCTION 'GSS_DATA_GET_CONTENT' "GSS: Get data back from RFC-System |
| EXPORTING | ||
| IS_TABLES | = lv_is_tables | |
| I_SCENARIO | = lv_i_scenario | |
| I_COMPRESS | = lv_i_compress | |
| I_TEMPERATURE_COLD | = lv_i_temperature_cold | |
| I_MASTER_ID | = lv_i_master_id | |
| I_CALL_ID | = lv_i_call_id | |
| IMPORTING | ||
| ET_TRANSFER | = lv_et_transfer | |
| EV_COMPLETED | = lv_ev_completed | |
| ET_LOOKUP_DATA | = lv_et_lookup_data | |
| ET_LOOKUP_FIELD | = lv_et_lookup_field | |
| ET_LOOKUP_VALUE | = lv_et_lookup_value | |
| ET_LOOKUP_HIERARCHY | = lv_et_lookup_hierarchy | |
| ET_RUNTIME | = lv_et_runtime | |
| TABLES | ||
| ET_DFIES | = lt_et_dfies | |
| EXCEPTIONS | ||
| ERROR_IN_SQL = 1 | ||
| KEY_DOES_NOT_EXIST = 2 | ||
| NOT_AUTHORIZED = 3 | ||
| TABLE_NOT_AVAILABLE = 4 | ||
| NO_WHERE_CLAUSE = 5 | ||
| ENDLESS_LOOP = 6 | ||
| . " GSS_DATA_GET_CONTENT | ||
ABAP code using 7.40 inline data declarations to call FM GSS_DATA_GET_CONTENT
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_i_compress) | = 'X'. | |||
Search for further information about these or an SAP related objects