KBPS_BUDGETTEXT SAP Function module

KBPS_BUDGETTEXT 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 KBPS_BUDGETTEXT into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: KBPS
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM KBPS_BUDGETTEXT - KBPS BUDGETTEXT

CALL FUNCTION 'KBPS_BUDGETTEXT' "
  EXPORTING
    i_bptx =                    " bptx
*   i_index =                   " sy-tabix
*   i_show = ON                 " fmdy-xfeld
*   i_hide = OFF                " fmdy-xfeld
*   i_multi = OFF               " fmdy-xfeld
*   i_multitext = OFF           " fmdy-xfeld
  IMPORTING
    e_data_changed =            " fmdy-xfeld
    e_longtext_changed =        " fmdy-xfeld
    e_new_text =                " fmdy-xfeld
    e_navi_code =               "
    .  "  KBPS_BUDGETTEXT

ABAP code example for Function Module KBPS_BUDGETTEXT

The ABAP code below is a full code listing to execute function module KBPS_BUDGETTEXT 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_e_data_changed  
 
 TYPE FMDY-XFELD
,
ld_e_longtext_changed  
 
 TYPE FMDY-XFELD
,
ld_e_new_text  
 
 TYPE FMDY-XFELD
,
ld_e_navi_code  
 
 TYPE STRING
.


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

DATA(ld_i_index) = '123 '.


DATA(ld_i_show) = some text here


DATA(ld_i_hide) = some text here


DATA(ld_i_multi) = some text here


DATA(ld_i_multitext) = some text here
.

CALL FUNCTION 'KBPS_BUDGETTEXT'
  EXPORTING
    i_bptx =                     ld_i_bptx
*   i_index =                    ld_i_index
*   i_show =                     ld_i_show
*   i_hide =                     ld_i_hide
*   i_multi =                    ld_i_multi
*   i_multitext =                ld_i_multitext
  IMPORTING
    e_data_changed =             ld_e_data_changed
    e_longtext_changed =         ld_e_longtext_changed
    e_new_text =                 ld_e_new_text
    e_navi_code =                ld_e_navi_code
    .  "  KBPS_BUDGETTEXT

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_e_data_changed
 
 TYPE FMDY-XFELD ,
ld_i_bptx
 
 TYPE BPTX ,
ld_e_longtext_changed
 
 TYPE FMDY-XFELD ,
ld_i_index
 
 TYPE SY-TABIX ,
ld_e_new_text
 
 TYPE FMDY-XFELD ,
ld_i_show
 
 TYPE FMDY-XFELD ,
ld_e_navi_code
 
 TYPE STRING ,
ld_i_hide
 
 TYPE FMDY-XFELD ,
ld_i_multi
 
 TYPE FMDY-XFELD ,
ld_i_multitext
 
 TYPE FMDY-XFELD .


ld_i_bptx = '123 '.
ld_i_index = '123 '.

ld_i_show = some text here

ld_i_hide = some text here

ld_i_multi = some text here

ld_i_multitext = some text here