/AWS1/IF_PTB=>AMENDBENEFITAPPLICATION()¶
About AmendBenefitApplication¶
Modifies an existing benefit application by applying amendments to specific fields while maintaining revision control.
Method Signature¶
METHODS /AWS1/IF_PTB~AMENDBENEFITAPPLICATION
IMPORTING
!IV_CATALOG TYPE /AWS1/PTBCATALOGNAME OPTIONAL
!IV_CLIENTTOKEN TYPE /AWS1/PTBSTRING OPTIONAL
!IV_REVISION TYPE /AWS1/PTBSTRING OPTIONAL
!IV_IDENTIFIER TYPE /AWS1/PTBBENEFITAPPIDENTIFIER OPTIONAL
!IV_AMENDMENTREASON TYPE /AWS1/PTBSTRING OPTIONAL
!IT_AMENDMENTS TYPE /AWS1/CL_PTBAMENDMENT=>TT_AMENDMENTLIST OPTIONAL
RETURNING
VALUE(OO_OUTPUT) TYPE REF TO /aws1/cl_ptbamendbenefappout
RAISING
/AWS1/CX_PTBACCESSDENIEDEX
/AWS1/CX_PTBCONFLICTEXCEPTION
/AWS1/CX_PTBINTERNALSERVEREX
/AWS1/CX_PTBRESOURCENOTFOUNDEX
/AWS1/CX_PTBTHROTTLINGEX
/AWS1/CX_PTBVLDTNEXCEPTION
/AWS1/CX_PTBCLIENTEXC
/AWS1/CX_PTBSERVEREXC
/AWS1/CX_RT_TECHNICAL_GENERIC
/AWS1/CX_RT_SERVICE_GENERIC.
IMPORTING¶
Required arguments:¶
iv_catalog TYPE /AWS1/PTBCATALOGNAME /AWS1/PTBCATALOGNAME¶
The catalog identifier that specifies which benefit catalog the application belongs to.
iv_clienttoken TYPE /AWS1/PTBSTRING /AWS1/PTBSTRING¶
A unique, case-sensitive identifier to ensure idempotent processing of the amendment request.
iv_revision TYPE /AWS1/PTBSTRING /AWS1/PTBSTRING¶
The current revision number of the benefit application to ensure optimistic concurrency control.
iv_identifier TYPE /AWS1/PTBBENEFITAPPIDENTIFIER /AWS1/PTBBENEFITAPPIDENTIFIER¶
The unique identifier of the benefit application to be amended.
iv_amendmentreason TYPE /AWS1/PTBSTRING /AWS1/PTBSTRING¶
A descriptive reason explaining why the benefit application is being amended.
it_amendments TYPE /AWS1/CL_PTBAMENDMENT=>TT_AMENDMENTLIST TT_AMENDMENTLIST¶
A list of specific field amendments to apply to the benefit application.
RETURNING¶
oo_output TYPE REF TO /aws1/cl_ptbamendbenefappout /AWS1/CL_PTBAMENDBENEFAPPOUT¶
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->amendbenefitapplication(
it_amendments = VALUE /aws1/cl_ptbamendment=>tt_amendmentlist(
(
new /aws1/cl_ptbamendment(
iv_fieldpath = |string|
iv_newvalue = |string|
)
)
)
iv_amendmentreason = |string|
iv_catalog = |string|
iv_clienttoken = |string|
iv_identifier = |string|
iv_revision = |string|
).
This is an example of reading all possible response values
lo_result = lo_result.
IF lo_result IS NOT INITIAL.
ENDIF.