API for Service Quotas¶
ABAP Package | /AWS1/API_SQT_IMPL |
---|---|
ABAP SDK "TLA" | SQT |
ABAP Interface | /AWS1/IF_SQT |
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 Service Quotas is SQT
.
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 Service Quotas 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¶
With Service Quotas, you can view and manage your quotas easily as your Amazon Web Services workloads grow. Quotas, also referred to as limits, are the maximum number of resources that you can create in your Amazon Web Services account. For more information, see the Service Quotas User Guide.
You need Amazon Web Services CLI version 2.13.20 or higher to view and manage resource-level quotas such as Instances
per domain
for Amazon OpenSearch Service.
Using the SDK¶
In your code, create a client using the SDK module for Service Quotas, which is created with
factory method /AWS1/CL_SQT_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_sqt) = /aws1/cl_sqt_factory=>create( go_session ).
Your variable go_sqt
is an instance of /AWS1/IF_SQT
,
and all of the operations
in the Service Quotas service are accessed by calling methods in /AWS1/IF_SQT
.
API Operations¶
For an overview of ABAP method calls corresponding to API operations in Service Quotas, see the Operation List.
Factory Method¶
/AWS1/CL_SQT_FACTORY=>create( )
¶
Creates an object of type /AWS1/IF_SQT
.
IMPORTING¶
Optional arguments:¶
iv_protocol
TYPE /aws1/rt_protocol
/AWS1/RT_PROTOCOL
¶
Domain /AWS1/RT_ACCOUNT_ID Primitive Type NUMC
io_session
TYPE REF TO /aws1/cl_rt_session_base
/AWS1/CL_RT_SESSION_BASE
¶
Domain /AWS1/RT_ACCOUNT_ID Primitive Type NUMC
iv_region
TYPE /aws1/rt_region_id
/AWS1/RT_REGION_ID
¶
Domain /AWS1/RT_ACCOUNT_ID Primitive Type NUMC
iv_custom_endpoint
TYPE /aws1/rt_endpoint
/AWS1/RT_ENDPOINT
¶
Domain /AWS1/RT_ACCOUNT_ID Primitive Type NUMC
RETURNING¶
oo_client
TYPE REF TO /aws1/if_sqt
/AWS1/IF_SQT
¶
/AWS1/IF_SQT
represents the ABAP client for the Service Quotas service, representing each operation as a method call. For more information see the API Page page.
Configuring Programmatically¶
DATA(lo_config) = DATA(go_sqt)->get_config( ).
lo_config
is a variable of type /AWS1/CL_SQT_CONFIG
. See the documentation for /AWS1/CL_SQT_CONFIG
for
details on the settings that can be configured.
Paginators¶
Paginators for Service Quotas can be created via `get_paginator()` which returns a paginator object of type [`/AWS1/IF_SQT_PAGINATOR`](./_AWS1_IF_SQT_PAGINATOR.md). The operation method that is being paginated is called using the paginator object, which accepts any necessary parameters to provide to the underlying API operation. This returns an iterator object which can be used to iterate over paginated results using `has_next()` and `get_next()` methods.
Details about the paginator methods available for service Service Quotas can be found in interface [`/AWS1/IF_SQT_PAGINATOR`](./_AWS1_IF_SQT_PAGINATOR.md).