API for AWS Service Catalog App Registry¶

ABAP Package	`/AWS1/API_SCA_IMPL`
ABAP SDK "TLA"	`SCA`
ABAP Interface	`/AWS1/IF_SCA`

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 Service Catalog App Registry is SCA. 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 Service Catalog AppRegistry 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 Service Catalog AppRegistry enables organizations to understand the application context of their Amazon Web Services resources. AppRegistry provides a repository of your applications, their resources, and the application metadata that you use within your enterprise.

Using the SDK¶

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

Your variable go_sca is an instance of /AWS1/IF_SCA, and all of the operations in the AWS Service Catalog App Registry service are accessed by calling methods in /AWS1/IF_SCA.

API Operations¶

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

Factory Method¶

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

Creates an object of type /AWS1/IF_SCA.

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_SCA` `/AWS1/IF_SCA`¶

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

Configuring Programmatically¶

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

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

Paginators¶

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