Call BRF+ application(interest) in report in ABAP

                    Refer BRF+ application link- BRF+ basic application

Step1: Goto BRF+ application in edit mode.

Step2: Click on settings and change user mode simple to expert. Click on save.

Step 3: Close BRF+ application and open again.

Step 4: Goto Function and click on create code template.



Step 5: Copy code and paste in report program.

Report


REPORT zab_rp_brf_intrest.

CONSTANTS:lv_function_id TYPE if_fdt_types=>id VALUE '1C98EC1899D41EDEBDC07101629184E0'.
DATA:lv_timestamp  TYPE timestamp,
     lt_name_value TYPE abap_parmbind_tab,
     ls_name_value TYPE abap_parmbind,
     lr_data       TYPE REF TO data,
     lx_fdt        TYPE REF TO cx_fdt,
     la_pinput     TYPE if_fdt_types=>element_text.
FIELD-SYMBOLS <la_any> TYPE any.

PARAMETERS: p_year TYPE zab_dt_year.
****************************************************************************************************
* All method calls within one processing cycle calling the same function must use the same timestamp.
* For subsequent calls of the same function, we recommend to use the same timestamp for all calls.
* This is to improve the system performance.
****************************************************************************************************
* If you are using structures or tables without DDIC binding, you have to declare the respective types
* by yourself. Insert the according data type at the respective source code line.
****************************************************************************************************
GET TIME STAMP FIELD lv_timestamp.
****************************************************************************************************
* Process a function without recording trace data, passing context data objects via a name/value table.
****************************************************************************************************
* Prepare function processing:
****************************************************************************************************
ls_name_value-name = 'PINPUT'.
la_PINPUT = p_year. "[insert CONTEXT VALUE here OR DELETE the line].
GET REFERENCE OF la_PINPUT INTO lr_data.
ls_name_value-value = lr_data.
INSERT ls_name_value INTO TABLE lt_name_value.
CLEAR ls_name_value.
****************************************************************************************************
* Create the data to store the result value after processing the function
* You can skip the following call, if you already have
* a variable for the result. Please replace also the parameter
* EA_RESULT in the method call CL_FDT_FUNCTION_PROCESS=>PROCESS
* with the desired variable.
****************************************************************************************************
cl_fdt_function_process=>get_data_object_reference( EXPORTING iv_function_id      = lv_function_id
                                                              iv_data_object      = '_V_RESULT'
                                                              iv_timestamp        = lv_timestamp
                                                              iv_trace_generation = abap_false
                                                    IMPORTING er_data             = lr_data ).
ASSIGN lr_data->* TO <la_any>.
TRY.
    cl_fdt_function_process=>process( EXPORTING iv_function_id = lv_function_id
                                                iv_timestamp   = lv_timestamp
                                      IMPORTING ea_result      = <la_any>
                                      CHANGING  ct_name_value  = lt_name_value ).
  CATCH cx_fdt INTO lx_fdt.
****************************************************************************************************
* You can check CX_FDT->MT_MESSAGE for error handling.
****************************************************************************************************
ENDTRY.

WRITE: <la_any>.


Input1


Output1



Input2

Output2



******************************Thank you ******************************

Comments

Post a Comment

Popular posts from this blog

Custom entity/Action dialog in RAP using Unmanaged scenario

Image
A custom action is like a button (e.g., Approve , Submit ) shown in the Fiori app. A dialog is a popup where the user can enter some input before performing the action.                    Refer:-  Determination + Side effects(On Modify) in RAP Unmanaged                    Refer:-  Determination + Side effects (On Save) in RAP Unmanaged Step 1:   Create behavior definition for abstract entity.          * Right click on Core data service - New - data definition.          * Give name and description.          * Click on Next.          * Select Abstract entity with parameters and click on finish. @EndUserText.label: 'Abstart entity for status field' @Metadata.allowExtensions: true define abstract entity ZA_AB_STUH_13 //with parameters parameter_name : paramet...
Read more

New syntax for append- VALUE (new syntax 7.4+) in ABAP

Image
* We use APPEND statement to insert the records at the last of the internal table. * In SAP ABAP new syntax, we can use VALUE expression instead of APPEND statement. * Value expression is a powerful mechanism to declare as well as initialize the internal tables. * It is a powerful utility where we can achieve the result with minimal coding. * Value expression is of 2 types.      -  Define the type before using it with VALUE keyword. The type defined is structure type  or table type.      -  Using # character for type and use it with VALUE keyword. Report REPORT  zab_rp_append_value . TYPES :  BEGIN  OF  ls_stu ,          st_id ( 10 )    TYPE  n ,          st_name ( 15 )  TYPE  c ,         END  OF  ls_stu . DATA :  lt_stu  TYPE  TABLE...
Read more

Read statement new syntax in ABAP. (7.4+).

Image
*  Before ABAP 7.4, we used READ TABLE statement to read the first matching record from the internal table  based upon key or index . * In SAP ABAP new syntax, instead of READ TABLE , we can use the table expressions. * We need to use the square bracket [ ], In the square bracket, we need to specify the key or index. * While using table expression, If the table entry does not exist, system throws the exception CX_SY_ITAB_LINE_NOT_FOUND. * Use line_exists statement to check the existence of a record. Report REPORT  zab_rp_read_new . TABLES :   vbak . SELECT-OPTIONS :   s_vbeln  FOR  vbak - vbeln . SELECT  vbeln , erdat , erzet , ernam , auart         FROM  vbak         INTO  TABLE  @DATA ( lt_vbak )          WHERE  vbeln  IN  @s_vbeln . WRITE :   'Index value'  COLOR  5 . READ  T...
Read more