API for AWSBillingConductor¶

ABAP Package	`/AWS1/API_BIC_IMPL`
ABAP SDK "TLA"	`BIC`
ABAP Interface	`/AWS1/IF_BIC`

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 AWSBillingConductor is BIC. 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 billingconductor 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¶

Amazon Web Services Billing Conductor is a fully managed service that you can use to customize a proforma version of your billing data each month, to accurately show or chargeback your end customers. Amazon Web Services Billing Conductor doesn't change the way you're billed by Amazon Web Services each month by design. Instead, it provides you with a mechanism to configure, generate, and display rates to certain customers over a given billing period. You can also analyze the difference between the rates you apply to your accounting groupings relative to your actual rates from Amazon Web Services. As a result of your Amazon Web Services Billing Conductor configuration, the payer account can also see the custom rate applied on the billing details page of the Amazon Web Services Billing console, or configure a cost and usage report per billing group.

This documentation shows how you can configure Amazon Web Services Billing Conductor using its API. For more information about using the Amazon Web Services Billing Conductor user interface, see the Amazon Web Services Billing Conductor User Guide.

Using the SDK¶

In your code, create a client using the SDK module for AWSBillingConductor, which is created with factory method /AWS1/CL_BIC_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_bic)       = /aws1/cl_bic_factory=>create( go_session ).

Your variable go_bic is an instance of /AWS1/IF_BIC, and all of the operations in the AWSBillingConductor service are accessed by calling methods in /AWS1/IF_BIC.

API Operations¶

For an overview of ABAP method calls corresponding to API operations in AWSBillingConductor, see the Operation List.

Factory Method¶

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

Creates an object of type /AWS1/IF_BIC.

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_BIC` `/AWS1/IF_BIC`¶

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

Configuring Programmatically¶

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

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

Paginators¶

Paginators for AWSBillingConductor can be created via get_paginator() which returns a paginator object of type /AWS1/IF_BIC_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 AWSBillingConductor can be found in interface /AWS1/IF_BIC_PAGINATOR.