DESCRPENDINGMAINTENANCEACTS()`¶

About DescribePendingMaintenanceActions¶

Returns a list of resources (for example, DB instances) that have at least one pending maintenance action.

Method Signature¶

IMPORTING¶

Optional arguments:¶

`iv_resourceidentifier` `TYPE /AWS1/NEPSTRING` `/AWS1/NEPSTRING`¶

The ARN of a resource to return pending maintenance actions for.

`it_filters` `TYPE /AWS1/CL_NEPFILTER=>TT_FILTERLIST` `TT_FILTERLIST`¶

A filter that specifies one or more resources to return pending maintenance actions for.

Supported filters:

db-cluster-id - Accepts DB cluster identifiers and DB cluster Amazon Resource Names (ARNs). The results list will only include pending maintenance actions for the DB clusters identified by these ARNs.

db-instance-id - Accepts DB instance identifiers and DB instance ARNs. The results list will only include pending maintenance actions for the DB instances identified by these ARNs.

`iv_marker` `TYPE /AWS1/NEPSTRING` `/AWS1/NEPSTRING`¶

An optional pagination token provided by a previous DescribePendingMaintenanceActions request. If this parameter is specified, the response includes only records beyond the marker, up to a number of records specified by MaxRecords.

`iv_maxrecords` `TYPE /AWS1/NEPINTEGEROPTIONAL` `/AWS1/NEPINTEGEROPTIONAL`¶

The maximum number of records to include in the response. If more records exist than the specified MaxRecords value, a pagination token called a marker is included in the response so that the remaining results can be retrieved.

Default: 100

Constraints: Minimum 20, maximum 100.

RETURNING¶

`oo_output` `TYPE REF TO /aws1/cl_neppendingmaintenan01` `/AWS1/CL_NEPPENDINGMAINTENAN01`¶

Domain /AWS1/RT_ACCOUNT_ID

Primitive Type NUMC

Examples¶

Syntax Example¶

This is an example of the syntax for calling the method. It includes every possible argument and initializes every possible value. The data provided is not necessarily semantically accurate (for example the value "string" may be provided for something that is intended to be an instance ID, or in some cases two arguments may be mutually exclusive). The syntax shows the ABAP syntax for creating the various data structures.

DATA(lo_result) = lo_client->/aws1/if_nep~descrpendingmaintenanceacts(
  it_filters = VALUE /aws1/cl_nepfilter=>tt_filterlist(
    (
      new /aws1/cl_nepfilter(
        it_values = VALUE /aws1/cl_nepfiltervaluelist_w=>tt_filtervaluelist(
          ( new /aws1/cl_nepfiltervaluelist_w( |string| ) )
        )
        iv_name = |string|
      )
    )
  )
  iv_marker = |string|
  iv_maxrecords = 123
  iv_resourceidentifier = |string|
).

This is an example of reading all possible response values

lo_result = lo_result.
IF lo_result IS NOT INITIAL.
  LOOP AT lo_result->get_pendingmaintenanceacts( ) into lo_row.
    lo_row_1 = lo_row.
    IF lo_row_1 IS NOT INITIAL.
      lv_string = lo_row_1->get_resourceidentifier( ).
      LOOP AT lo_row_1->get_pendingmaintenanceactd00( ) into lo_row_2.
        lo_row_3 = lo_row_2.
        IF lo_row_3 IS NOT INITIAL.
          lv_string = lo_row_3->get_action( ).
          lv_tstamp = lo_row_3->get_autoappliedafterdate( ).
          lv_tstamp = lo_row_3->get_forcedapplydate( ).
          lv_string = lo_row_3->get_optinstatus( ).
          lv_tstamp = lo_row_3->get_currentapplydate( ).
          lv_string = lo_row_3->get_description( ).
        ENDIF.
      ENDLOOP.
    ENDIF.
  ENDLOOP.
  lv_string = lo_result->get_marker( ).
ENDIF.

/AWS1/IF_NEP=>DESCRPENDINGMAINTENANCEACTS()¶