Skip to content

API for AWS Billing and Cost Management Data Exports

ABAP Package /AWS1/API_BCE_IMPL
ABAP SDK "TLA" BCE
ABAP Interface /AWS1/IF_BCE

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 Billing and Cost Management Data Exports is BCE. 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 BCM Data Exports 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

You can use the Data Exports API to create customized exports from multiple Amazon Web Services cost management and billing datasets, such as cost and usage data and cost optimization recommendations.

The Data Exports API provides the following endpoint:

  • https://bcm-data-exports.us-east-1.api.aws

Using the SDK

In your code, create a client using the SDK module for AWS Billing and Cost Management Data Exports, which is created with factory method /AWS1/CL_BCE_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_bce)       = /aws1/cl_bce_factory=>create( go_session ).

Your variable go_bce is an instance of /AWS1/IF_BCE, and all of the operations in the AWS Billing and Cost Management Data Exports service are accessed by calling methods in /AWS1/IF_BCE.

API Operations

For an overview of ABAP method calls corresponding to API operations in AWS Billing and Cost Management Data Exports, see the Operation List.

Factory Method

/AWS1/CL_BCE_FACTORY=>create( )

Creates an object of type /AWS1/IF_BCE.

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_BCE /AWS1/IF_BCE

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

Configuring Programmatically

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

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

Paginators

Paginators for AWS Billing and Cost Management Data Exports can be created via get_paginator() which returns a paginator object of type /AWS1/IF_BCE_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 Billing and Cost Management Data Exports can be found in interface /AWS1/IF_BCE_PAGINATOR.