SAP RETRIEVE_GEO_CONTEXT Function Module for Retrieve Geo Context Configuration
RETRIEVE_GEO_CONTEXT is a standard retrieve geo context SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Retrieve Geo Context Configuration 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 retrieve geo context FM, simply by entering the name RETRIEVE_GEO_CONTEXT into the relevant SAP transaction such as SE37 or SE38.
Function Group: FG_GEO_CONTEXT
Program Name: SAPLFG_GEO_CONTEXT
Main Program: SAPLFG_GEO_CONTEXT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RETRIEVE_GEO_CONTEXT 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 'RETRIEVE_GEO_CONTEXT'"Retrieve Geo Context Configuration.
EXPORTING
IV_GEO_CONTEXT_ID = "Geo Context ID
IT_LAYER_CONF_BASE = "Base Layer Configuration
IT_GEOPRO_CONF_BASE = "GeoProcessing Services Base Configuration
IT_GEOM_CONF_BASE = "Geometry Service Base Configuration
IMPORTING
ET_GEO_CONTEXT_GEN_DATA = "Geo Context
ET_LAYERS_DATA = "Layer Configuration
ET_GEO_PROCESS_DATA = "Geo Processing Configuartion
ET_GEO_PROC_IMPORT = "Import Parameters for Service
ET_GEO_PROC_EXPORT = "Export Parameter
ET_FEAT_LAYER_CONF = "Feature Layer Configuration
ET_MESSAGES = "Geo Processing Message Data
IMPORTING Parameters details for RETRIEVE_GEO_CONTEXT
IV_GEO_CONTEXT_ID - Geo Context ID
Data type: GEO_CONTEXT_IDOptional: No
Call by Reference: Yes
IT_LAYER_CONF_BASE - Base Layer Configuration
Data type: LAYER_CONF_BASE_TOptional: No
Call by Reference: Yes
IT_GEOPRO_CONF_BASE - GeoProcessing Services Base Configuration
Data type: GEOPRO_CONF_BASE_TOptional: No
Call by Reference: Yes
IT_GEOM_CONF_BASE - Geometry Service Base Configuration
Data type: GEOM_CONF_BASE_TOptional: No
Call by Reference: Yes
EXPORTING Parameters details for RETRIEVE_GEO_CONTEXT
ET_GEO_CONTEXT_GEN_DATA - Geo Context
Data type: GEO_CONTEXT_CONF_TOptional: No
Call by Reference: Yes
ET_LAYERS_DATA - Layer Configuration
Data type: LAYER_CONF_TOptional: No
Call by Reference: Yes
ET_GEO_PROCESS_DATA - Geo Processing Configuartion
Data type: GEO_PROCESS_CONF_TOptional: No
Call by Reference: Yes
ET_GEO_PROC_IMPORT - Import Parameters for Service
Data type: GEO_PROC_IMPORT_TOptional: No
Call by Reference: Yes
ET_GEO_PROC_EXPORT - Export Parameter
Data type: GEO_PROC_EXPORT_TOptional: No
Call by Reference: Yes
ET_FEAT_LAYER_CONF - Feature Layer Configuration
Data type: FEAT_LAYER_CONF_TOptional: No
Call by Reference: Yes
ET_MESSAGES - Geo Processing Message Data
Data type: GEOPROCESSING_DATA_TOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for RETRIEVE_GEO_CONTEXT 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_iv_geo_context_id | TYPE GEO_CONTEXT_ID, " | |||
| lv_et_geo_context_gen_data | TYPE GEO_CONTEXT_CONF_T, " | |||
| lv_et_layers_data | TYPE LAYER_CONF_T, " | |||
| lv_it_layer_conf_base | TYPE LAYER_CONF_BASE_T, " | |||
| lv_et_geo_process_data | TYPE GEO_PROCESS_CONF_T, " | |||
| lv_it_geopro_conf_base | TYPE GEOPRO_CONF_BASE_T, " | |||
| lv_it_geom_conf_base | TYPE GEOM_CONF_BASE_T, " | |||
| lv_et_geo_proc_import | TYPE GEO_PROC_IMPORT_T, " | |||
| lv_et_geo_proc_export | TYPE GEO_PROC_EXPORT_T, " | |||
| lv_et_feat_layer_conf | TYPE FEAT_LAYER_CONF_T, " | |||
| lv_et_messages | TYPE GEOPROCESSING_DATA_T. " |
|   CALL FUNCTION 'RETRIEVE_GEO_CONTEXT' "Retrieve Geo Context Configuration |
| EXPORTING | ||
| IV_GEO_CONTEXT_ID | = lv_iv_geo_context_id | |
| IT_LAYER_CONF_BASE | = lv_it_layer_conf_base | |
| IT_GEOPRO_CONF_BASE | = lv_it_geopro_conf_base | |
| IT_GEOM_CONF_BASE | = lv_it_geom_conf_base | |
| IMPORTING | ||
| ET_GEO_CONTEXT_GEN_DATA | = lv_et_geo_context_gen_data | |
| ET_LAYERS_DATA | = lv_et_layers_data | |
| ET_GEO_PROCESS_DATA | = lv_et_geo_process_data | |
| ET_GEO_PROC_IMPORT | = lv_et_geo_proc_import | |
| ET_GEO_PROC_EXPORT | = lv_et_geo_proc_export | |
| ET_FEAT_LAYER_CONF | = lv_et_feat_layer_conf | |
| ET_MESSAGES | = lv_et_messages | |
| . " RETRIEVE_GEO_CONTEXT | ||
ABAP code using 7.40 inline data declarations to call FM RETRIEVE_GEO_CONTEXT
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