UPDATEBILLINGPREFERENCES()`¶

About UpdateBillingPreferences¶

Updates billing preferences for the specified feature. Each feature targets a distinct billing capability and has its own set of supported keys. The action sets the value for each provided key; keys not present in the request are unchanged.

Sharing keys (RI_SHARING, CREDIT_SHARING, CREDIT_LEVEL_SHARING, and sharing keys under CREDIT_PREFERENCE_OPTIONS) may only be set by the management account of a consolidated billing family. The credit/{creditId}/status key may be set by member accounts for credits they own, or by the management account for any credit in the family.

Method Signature¶

METHODS /AWS1/IF_BIL~UPDATEBILLINGPREFERENCES
  IMPORTING
    !IV_FEATURE TYPE /AWS1/BILBILLINGFEATURE OPTIONAL
    !IT_BILLINGPREFERENCESPERKEY TYPE /AWS1/CL_BILBILLINGPREFFORKEY=>TT_BILLINGPREFERENCESPERKEY OPTIONAL
  RETURNING
    VALUE(OO_OUTPUT) TYPE REF TO /aws1/cl_bilupdbllngprefsrsp
  RAISING
    /AWS1/CX_BILACCESSDENIEDEX
    /AWS1/CX_BILINTERNALSERVEREX
    /AWS1/CX_BILTHROTTLINGEX
    /AWS1/CX_BILVALIDATIONEX
    /AWS1/CX_BILCLIENTEXC
    /AWS1/CX_BILSERVEREXC
    /AWS1/CX_RT_TECHNICAL_GENERIC
    /AWS1/CX_RT_SERVICE_GENERIC.

IMPORTING¶

Required arguments:¶

`iv_feature` `TYPE /AWS1/BILBILLINGFEATURE` `/AWS1/BILBILLINGFEATURE`¶

The feature to update. Valid values: BILLING_ALERTS, RI_SHARING, CREDIT_SHARING, CREDIT_LEVEL_SHARING, CREDIT_PREFERENCE_OPTIONS. The history features (RI_SHARING_HISTORY and CREDIT_SHARING_HISTORY) are read-only and cannot be updated.

`it_billingpreferencesperkey` `TYPE /AWS1/CL_BILBILLINGPREFFORKEY=>TT_BILLINGPREFERENCESPERKEY` `TT_BILLINGPREFERENCESPERKEY`¶

Key/value pairs to apply. All keys in a single request must be valid for the specified feature and must not be duplicated. For CREDIT_PREFERENCE_OPTIONS, all keys must reference the same creditId.

RETURNING¶

`oo_output` `TYPE REF TO /aws1/cl_bilupdbllngprefsrsp` `/AWS1/CL_BILUPDBLLNGPREFSRSP`¶

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->updatebillingpreferences(
  it_billingpreferencesperkey = VALUE /aws1/cl_bilbillingprefforkey=>tt_billingpreferencesperkey(
    (
      new /aws1/cl_bilbillingprefforkey(
        iv_key = |string|
        iv_value = |string|
      )
    )
  )
  iv_feature = |string|
).

This is an example of reading all possible response values

lo_result = lo_result.
IF lo_result IS NOT INITIAL.
ENDIF.

/AWS1/IF_BIL=>UPDATEBILLINGPREFERENCES()¶