API for Account Access¶
| ABAP Package | /AWS1/API_AAA |
|---|---|
| ABAP SDK "TLA" | AAA |
| ABAP Interface | /AWS1/IF_AAA |
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 Account Access is AAA.
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 Account Access 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¶
Account access manager enables you to manage applications and entitlements that grant IAM Identity Center principals access to IAM roles across accounts.
Using the SDK¶
In your code, create a client using the SDK module for Account Access, which is created with
factory method /AWS1/CL_AAA_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_aaa) = /aws1/cl_aaa_factory=>create( go_session ).
Your variable go_aaa is an instance of /AWS1/IF_AAA,
and all of the operations
in the Account Access service are accessed by calling methods in /AWS1/IF_AAA.
API Operations¶
For an overview of ABAP method calls corresponding to API operations in Account Access, see the Operation List.
Factory Method¶
/AWS1/CL_AAA_FACTORY=>create( )¶
Creates an object of type /AWS1/IF_AAA.
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_aaa /AWS1/IF_AAA¶
/AWS1/IF_AAArepresents the ABAP client for the Account Access service, representing each operation as a method call. For more information see the API Page page.
Configuring Programmatically¶
DATA(lo_config) = DATA(go_aaa)->get_config( ).
lo_config is a variable of type /AWS1/CL_AAA_CONFIG. See the documentation for /AWS1/CL_AAA_CONFIG for
details on the settings that can be configured.
Waiters¶
Waiters for Implementation can be accessed via get_waiter() method followed by the waiter method to be called.
Details about the waiter methods available for service Implementation can be found in interface /AWS1/IF_AAA_WAITER.
Paginators¶
Paginators for Account Access can be created via get_paginator() which returns a paginator object of type /AWS1/IF_AAA_PAGINATOR.
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 Account Access can be found in interface /AWS1/IF_AAA_PAGINATOR.