API for AWS Application Cost Profiler¶

ABAP Package	`/AWS1/API_ACO_IMPL`
ABAP SDK "TLA"	`ACO`
ABAP Interface	`/AWS1/IF_ACO`

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 AWS Application Cost Profiler is ACO. 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 ApplicationCostProfiler 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¶

This reference provides descriptions of the AWS Application Cost Profiler API.

The AWS Application Cost Profiler API provides programmatic access to view, create, update, and delete application cost report definitions, as well as to import your usage data into the Application Cost Profiler service.

For more information about using this service, see the AWS Application Cost Profiler User Guide.

Using the SDK¶

In your code, create a client using the SDK module for AWS Application Cost Profiler, which is created with factory method /AWS1/CL_ACO_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_aco)       = /aws1/cl_aco_factory=>create( go_session ).

Your variable go_aco is an instance of /AWS1/IF_ACO, and all of the operations in the AWS Application Cost Profiler service are accessed by calling methods in /AWS1/IF_ACO.

API Operations¶

For an overview of ABAP method calls corresponding to API operations in AWS Application Cost Profiler, see the Operation List.

Factory Method¶

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

Creates an object of type /AWS1/IF_ACO.

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_ACO` `/AWS1/IF_ACO`¶

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

Configuring Programmatically¶

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

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

Paginators¶

Paginators for AWS Application Cost Profiler can be created via get_paginator() which returns a paginator object of type /AWS1/IF_ACO_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 AWS Application Cost Profiler can be found in interface /AWS1/IF_ACO_PAGINATOR.