API for AWSMarketplace Metering¶
ABAP Package | /AWS1/API_MPM_IMPL |
---|---|
ABAP SDK "TLA" | MPM |
ABAP Interface | /AWS1/IF_MPM |
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 AWSMarketplace Metering is MPM
.
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 Marketplace Metering 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 low-level AWS Marketplace Metering Service API.
AWS Marketplace sellers can use this API to submit usage data for custom usage dimensions.
For information on the permissions you need to use this API, see AWS Marketplace metering and entitlement API permissions in the AWS Marketplace Seller Guide.
Submitting Metering Records
-
MeterUsage - Submits the metering record for an AWS Marketplace product.
MeterUsage
is called from an EC2 instance or a container running on EKS or ECS. -
BatchMeterUsage - Submits the metering record for a set of customers.
BatchMeterUsage
is called from a software-as-a-service (SaaS) application.
Accepting New Customers
-
ResolveCustomer - Called by a SaaS application during the registration process. When a buyer visits your website during the registration process, the buyer submits a Registration Token through the browser. The Registration Token is resolved through this API to obtain a
CustomerIdentifier
along with theCustomerAWSAccountId
andProductCode
.
Entitlement and Metering for Paid Container Products
-
Paid container software products sold through AWS Marketplace must integrate with the AWS Marketplace Metering Service and call the
RegisterUsage
operation for software entitlement and metering. Free and BYOL products for Amazon ECS or Amazon EKS aren't required to callRegisterUsage
, but you can do so if you want to receive usage data in your seller reports. For more information on using theRegisterUsage
operation, see Container-Based Products.
BatchMeterUsage
API calls are captured by AWS CloudTrail. You can use
Cloudtrail to verify that the SaaS metering records that you sent are accurate by
searching for records with the eventName
of BatchMeterUsage
.
You can also use CloudTrail to audit records over time. For more information, see the
AWS CloudTrail User Guide.
Using the SDK¶
In your code, create a client using the SDK module for AWSMarketplace Metering, which is created with
factory method /AWS1/CL_MPM_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_mpm) = /aws1/cl_mpm_factory=>create( go_session ).
Your variable go_mpm
is an instance of /AWS1/IF_MPM
,
and all of the operations
in the AWSMarketplace Metering service are accessed by calling methods in /AWS1/IF_MPM
.
API Operations¶
For an overview of ABAP method calls corresponding to API operations in AWSMarketplace Metering, see the Operation List.
Factory Method¶
/AWS1/CL_MPM_FACTORY=>create( )
¶
Creates an object of type /AWS1/IF_MPM
.
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_MPM
/AWS1/IF_MPM
¶
/AWS1/IF_MPM
represents the ABAP client for the Marketplace Metering service, representing each operation as a method call. For more information see the API Page page.
Configuring Programmatically¶
DATA(lo_config) = DATA(go_mpm)->get_config( ).
lo_config
is a variable of type /AWS1/CL_MPM_CONFIG
. See the documentation for /AWS1/CL_MPM_CONFIG
for
details on the settings that can be configured.