API for AWS Cost and Usage Report Service¶

ABAP Package	`/AWS1/API_CUR_IMPL`
ABAP SDK "TLA"	`CUR`
ABAP Interface	`/AWS1/IF_CUR`

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 Cost and Usage Report Service is CUR. 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 Cost and Usage Report Service 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 AWS Cost and Usage Report API enables you to programmatically create, query, and delete AWS Cost and Usage report definitions.

AWS Cost and Usage reports track the monthly AWS costs and usage associated with your AWS account. The report contains line items for each unique combination of AWS product, usage type, and operation that your AWS account uses. You can configure the AWS Cost and Usage report to show only the data that you want, using the AWS Cost and Usage API.

Service Endpoint

The AWS Cost and Usage Report API provides the following endpoint:

cur.us-east-1.amazonaws.com

Using the SDK¶

In your code, create a client using the SDK module for AWS Cost and Usage Report Service, which is created with factory method /AWS1/CL_CUR_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_cur)       = /aws1/cl_cur_factory=>create( go_session ).

Your variable go_cur is an instance of /AWS1/IF_CUR, and all of the operations in the AWS Cost and Usage Report Service service are accessed by calling methods in /AWS1/IF_CUR.

API Operations¶

For an overview of ABAP method calls corresponding to API operations in AWS Cost and Usage Report Service, see the Operation List.

Factory Method¶

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

Creates an object of type /AWS1/IF_CUR.

IMPORTING¶

Required arguments:¶

`IO_SESSION` `TYPE REF TO` `/AWS1/CL_RT_SESSION_BASE`¶

Optional arguments:¶

`IV_PROTOCOL` `TYPE` `/AWS1/RT_PROTOCOL`¶

`IV_REGION` `TYPE` `/AWS1/RT_REGION_ID`¶

`IV_CUSTOM_ENDPOINT` `TYPE` `/AWS1/RT_ENDPOINT`¶

RETURNING¶

`OO_CLIENT` `TYPE REF TO` `/AWS1/IF_CUR`¶

/AWS1/IF_CUR represents the ABAP client for the Cost and Usage Report Service service, representing each operation as a method call. For more information see the API Page page.

Configuring Programmatically¶

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

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

Paginators¶

Paginators for AWS Cost and Usage Report Service can be created via get_paginator() which returns a paginator object of type /AWS1/IF_CUR_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 Cost and Usage Report Service can be found in interface /AWS1/IF_CUR_PAGINATOR.