SAP GEOCODE_OBJECTS Function Module for









GEOCODE_OBJECTS is a standard geocode objects 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 geocode objects FM, simply by entering the name GEOCODE_OBJECTS into the relevant SAP transaction such as SE37 or SE38.

Function Group: GEOCODING
Program Name: SAPLGEOCODING
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function GEOCODE_OBJECTS 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 'GEOCODE_OBJECTS'"
EXPORTING
TAB_ADDR_APPLOBJECT = "
* FORCE_REGEOCODING = ' ' "
* INTERACTION_ALLOWED = ' ' "

IMPORTING
TAB_GEOOBJECTS = "
MESSAGES = "

EXCEPTIONS
XFATALERROR = 1
.



IMPORTING Parameters details for GEOCODE_OBJECTS

TAB_ADDR_APPLOBJECT -

Data type: ADDR_APPLOBJECT_TABLE
Optional: No
Call by Reference: Yes

FORCE_REGEOCODING -

Data type: XFLAG
Default: SPACE
Optional: Yes
Call by Reference: Yes

INTERACTION_ALLOWED -

Data type: XFLAG
Default: SPACE
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for GEOCODE_OBJECTS

TAB_GEOOBJECTS -

Data type: GEOOBJECTTABLE
Optional: No
Call by Reference: Yes

MESSAGES -

Data type: AES_MSG_TABLE
Optional: No
Call by Reference: Yes

EXCEPTIONS details

XFATALERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for GEOCODE_OBJECTS 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_xfatalerror  TYPE STRING, "   
lv_tab_geoobjects  TYPE GEOOBJECTTABLE, "   
lv_tab_addr_applobject  TYPE ADDR_APPLOBJECT_TABLE, "   
lv_messages  TYPE AES_MSG_TABLE, "   
lv_force_regeocoding  TYPE XFLAG, "   SPACE
lv_interaction_allowed  TYPE XFLAG. "   SPACE

  CALL FUNCTION 'GEOCODE_OBJECTS'  "
    EXPORTING
         TAB_ADDR_APPLOBJECT = lv_tab_addr_applobject
         FORCE_REGEOCODING = lv_force_regeocoding
         INTERACTION_ALLOWED = lv_interaction_allowed
    IMPORTING
         TAB_GEOOBJECTS = lv_tab_geoobjects
         MESSAGES = lv_messages
    EXCEPTIONS
        XFATALERROR = 1
. " GEOCODE_OBJECTS




ABAP code using 7.40 inline data declarations to call FM GEOCODE_OBJECTS

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_force_regeocoding) = ' '.
 
DATA(ld_interaction_allowed) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!