API for Amazon Location Service Places V2¶

ABAP Package	`/AWS1/API_GEP`
ABAP SDK "TLA"	`GEP`
ABAP Interface	`/AWS1/IF_GEP`

The "TLA" is a Three Letter Abbreviation that appears in ABAP class names, data dictionary objects and other ABAP objects throughout the AWS SDK for SAP ABAP. The TLA for Amazon Location Service Places V2 is GEP. This TLA helps squeeze ABAP objects into the 30-character length limit of the ABAP data dictionary.

Installation¶

To install the AWS SDK for SAP ABAP, import the Core transport, along with the transport for the Geo Places module and other API modules you are interested in. A few modules are included in the Core transport itself. For more information, see the Developer Guide guide.

About The Service¶

The Places API enables powerful location search and geocoding capabilities for your applications, offering global coverage with rich, detailed information. Key features include:

Forward and reverse geocoding for addresses and coordinates. See Geocode and ReverseGeocode.
Comprehensive place searches with detailed information. See SearchText, SearchNearby, and GetPlace. Place information you can find include:
- Business names and addresses
- Contact information
- Hours of operation
- Points of Interest (POI) categories
- Food types for restaurants
- Chain affiliation for relevant businesses
Address and place completion as users type, enhancing input efficiency by completing partial queries with valid addresses. See Autocomplete.
Intelligent place and query recommendation based on user's input or context, returning relevant places, points of interest, query terms, or search categories. See Suggest.
Global data coverage with a wide range of POI categories.
Regular data updates to ensure accuracy and relevance.
Bulk address validation for verifying and standardizing large volumes of addresses in a single operation using Amazon Location Service Jobs.

Using the SDK¶

In your code, create a client using the SDK module for Amazon Location Service Places V2, which is created with factory method /AWS1/CL_GEP_FACTORY=>create(). In this example we will assume you have configured an SDK profile in transaction /AWS1/IMG called ZFINANCE.

DATA(go_session)   = /aws1/cl_rt_session_aws=>create( 'ZFINANCE' ).
DATA(go_gep)       = /aws1/cl_gep_factory=>create( go_session ).

Your variable go_gep is an instance of /AWS1/IF_GEP, and all of the operations in the Amazon Location Service Places V2 service are accessed by calling methods in /AWS1/IF_GEP.

API Operations¶

For an overview of ABAP method calls corresponding to API operations in Amazon Location Service Places V2, see the Operation List.

Factory Method¶

`/AWS1/CL_GEP_FACTORY=>create( )`¶

Creates an object of type /AWS1/IF_GEP.

IMPORTING¶

Optional arguments:¶

`iv_protocol` `TYPE /aws1/rt_protocol` `/AWS1/RT_PROTOCOL`¶

`io_session` `TYPE REF TO /aws1/cl_rt_session_base` `/AWS1/CL_RT_SESSION_BASE`¶

`iv_region` `TYPE /aws1/rt_region_id` `/AWS1/RT_REGION_ID`¶

`iv_custom_endpoint` `TYPE /aws1/rt_endpoint` `/AWS1/RT_ENDPOINT`¶

RETURNING¶

`oo_client` `TYPE REF TO /aws1/if_gep` `/AWS1/IF_GEP`¶

/AWS1/IF_GEP represents the ABAP client for the Geo Places service, representing each operation as a method call. For more information see the API Page page.

Configuring Programmatically¶

DATA(lo_config) = DATA(go_gep)->get_config( ).

lo_config is a variable of type /AWS1/CL_GEP_CONFIG. See the documentation for /AWS1/CL_GEP_CONFIG for details on the settings that can be configured.