SAP Function Modules

comments icon Comments

BD_APP_READ SAP Function module - Read Budget Billing Data







BD_APP_READ is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name BD_APP_READ into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: BDISU_APP
Released Date: Not Released
Processing type: Remote-Enabled
remote enabled module settings


Pattern for FM BD_APP_READ - BD APP READ 





CALL FUNCTION 'BD_APP_READ' "Read Budget Billing Data
  EXPORTING
*   i_spras = SY-LANGU          " spras         Language Key of Current Text Environment
*   i_datum = SY-DATUM          " regen-ab      Date from Which a Time Slice is Valid
    i_bupa =                    " gpart_kk      Business Partner Number
*   i_vkonto =                  " vkont_kk      Contract Account Number
*   i_user = SY-UNAME           " usr04-bname   User Name in User Master Record
  IMPORTING
    return =                    " bapiret2      Return Parameter(s)
    e_cust =                    " uces_cust_app  UCES: Customizing for Budget Billing Plan Adjustment
    budbiplan =                 " uces_pp_tab   Table Type for UCES_BBP
    e_adj_perm =                " uces_adj_perm_pp_tab  Table Type for Structure UCES_ADJ_PERM
    e_new_pp_dates =            " uces_pp_pay_dates_tab  Table Type for UCES_PAY_DATES
    e_pp_dif_beg_month =        " e_pypla       Month
* TABLES
*   xt_uces_extension =         " uces_extension  UCES: Display Customer-Specific Fields from JSP
    .  "  BD_APP_READ

ABAP code example for Function Module BD_APP_READ





The ABAP code below is a full code listing to execute function module BD_APP_READ including all data declarations. The code uses the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the original method of declaring data variables up front. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8).

DATA:
ld_return    TYPE BAPIRET2
,
ld_e_cust    TYPE UCES_CUST_APP
,
ld_budbiplan    TYPE UCES_PP_TAB
,
ld_e_adj_perm    TYPE UCES_ADJ_PERM_PP_TAB
,
ld_e_new_pp_dates    TYPE UCES_PP_PAY_DATES_TAB
,
ld_e_pp_dif_beg_month    TYPE E_PYPLA
,
it_xt_uces_extension    TYPE STANDARD TABLE OF UCES_EXTENSION,"TABLES PARAM
wa_xt_uces_extension  LIKE LINE OF it_xt_uces_extension
.




DATA(ld_i_spras) = 'Check type of data required'.


DATA(ld_i_datum) = 20210129

DATA(ld_i_bupa) = 'Check type of data required'.

DATA(ld_i_vkonto) = 'Check type of data required'.
 

SELECT single BNAME 
  FROM USR04 
  INTO @DATA(ld_i_user).

 

"populate fields of struture and append to itab
append wa_xt_uces_extension to it_xt_uces_extension.
.

CALL FUNCTION 'BD_APP_READ'
  EXPORTING
*   i_spras =                    ld_i_spras
*   i_datum =                    ld_i_datum
    i_bupa =                     ld_i_bupa
*   i_vkonto =                   ld_i_vkonto
*   i_user =                     ld_i_user
  IMPORTING
    return =                     ld_return
    e_cust =                     ld_e_cust
    budbiplan =                  ld_budbiplan
    e_adj_perm =                 ld_e_adj_perm
    e_new_pp_dates =             ld_e_new_pp_dates
    e_pp_dif_beg_month =         ld_e_pp_dif_beg_month
* TABLES
*   xt_uces_extension =          it_xt_uces_extension
    .  "  BD_APP_READ

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:


ld_return  TYPE BAPIRET2 ,
ld_i_spras  TYPE SPRAS ,
it_xt_uces_extension  TYPE STANDARD TABLE OF UCES_EXTENSION ,
wa_xt_uces_extension  LIKE LINE OF it_xt_uces_extension,
ld_e_cust  TYPE UCES_CUST_APP ,
ld_i_datum  TYPE REGEN-AB ,
ld_budbiplan  TYPE UCES_PP_TAB ,
ld_i_bupa  TYPE GPART_KK ,
ld_e_adj_perm  TYPE UCES_ADJ_PERM_PP_TAB ,
ld_i_vkonto  TYPE VKONT_KK ,
ld_e_new_pp_dates  TYPE UCES_PP_PAY_DATES_TAB ,
ld_i_user  TYPE USR04-BNAME ,
ld_e_pp_dif_beg_month  TYPE E_PYPLA .




ld_i_spras = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_xt_uces_extension to it_xt_uces_extension.

ld_i_datum = 20210129
ld_i_bupa = 'Check type of data required'.
ld_i_vkonto = 'Check type of data required'.

SELECT single BNAME 
  FROM USR04 
  INTO ld_i_user.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name BD_APP_READ or its description.


   
 

BD_APP_READ - Read Budget Billing Data
BD_APP_PREP_ADJ - Preparation of Internet Budget Billing Adjustment
BD_APP_GET_LIM - Determination of Absolute Limits
BD_APP_EMAIL - Send E-Mail with New Budget Billing Data
BD_APP_CREATE_PP - Create Payment Plan
BD_APP_CALCULATE - Calculation of Budget Billing Amounts at Contract Level