API for AWS Marketplace Catalog Service¶

ABAP Package	`/AWS1/API_MPC_IMPL`
ABAP SDK "TLA"	`MPC`
ABAP Interface	`/AWS1/IF_MPC`

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 Marketplace Catalog Service is MPC. 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 Catalog 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¶

Catalog API actions allow you to manage your entities through list, describe, and update capabilities. An entity can be a product or an offer on AWS Marketplace.

You can automate your entity update process by integrating the AWS Marketplace Catalog API with your AWS Marketplace product build or deployment pipelines. You can also create your own applications on top of the Catalog API to manage your products on AWS Marketplace.

Using the SDK¶

In your code, create a client using the SDK module for AWS Marketplace Catalog Service, which is created with factory method /AWS1/CL_MPC_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_mpc)       = /aws1/cl_mpc_factory=>create( go_session ).

Your variable go_mpc is an instance of /AWS1/IF_MPC, and all of the operations in the AWS Marketplace Catalog Service service are accessed by calling methods in /AWS1/IF_MPC.

API Operations¶

For an overview of ABAP method calls corresponding to API operations in AWS Marketplace Catalog Service, see the Operation List.

Factory Method¶

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

Creates an object of type /AWS1/IF_MPC.

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_MPC` `/AWS1/IF_MPC`¶

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

Configuring Programmatically¶

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

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

Paginators¶

Paginators for AWS Marketplace Catalog Service can be created via get_paginator() which returns a paginator object of type /AWS1/IF_MPC_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 Marketplace Catalog Service can be found in interface /AWS1/IF_MPC_PAGINATOR.