BBP_UI_CTRL_PO SAP Function module

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

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

Pattern for FM BBP_UI_CTRL_PO - BBP UI CTRL PO

CALL FUNCTION 'BBP_UI_CTRL_PO' "
  EXPORTING
    is_header =                 " bbp_pds_po_header_d
    is_item =                   " bbp_pds_po_item_d
    iv_mode =                   " c
    iv_fieldname =              " dynfnam
*   iv_progname =               " sy-repid
    iv_dynpname =               " sy-dynnr
  CHANGING
    cv_screen_invisible =       " c
    cv_screen_input =           " c
    .  "  BBP_UI_CTRL_PO

ABAP code example for Function Module BBP_UI_CTRL_PO

The ABAP code below is a full code listing to execute function module BBP_UI_CTRL_PO 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_cv_screen_invisible) = 'Check type of data required'.

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

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

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

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

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

DATA(ld_iv_progname) = 'some text here'.

DATA(ld_iv_dynpname) = 'some text here'.
.

CALL FUNCTION 'BBP_UI_CTRL_PO'
  EXPORTING
    is_header =                  ld_is_header
    is_item =                    ld_is_item
    iv_mode =                    ld_iv_mode
    iv_fieldname =               ld_iv_fieldname
*   iv_progname =                ld_iv_progname
    iv_dynpname =                ld_iv_dynpname
  CHANGING
    cv_screen_invisible =        ld_cv_screen_invisible
    cv_screen_input =            ld_cv_screen_input
    .  "  BBP_UI_CTRL_PO

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_cv_screen_invisible
 
 TYPE C ,
ld_is_header
 
 TYPE BBP_PDS_PO_HEADER_D ,
ld_cv_screen_input
 
 TYPE C ,
ld_is_item
 
 TYPE BBP_PDS_PO_ITEM_D ,
ld_iv_mode
 
 TYPE C ,
ld_iv_fieldname
 
 TYPE DYNFNAM ,
ld_iv_progname
 
 TYPE SY-REPID ,
ld_iv_dynpname
 
 TYPE SY-DYNNR .


ld_cv_screen_invisible = 'some text here'.
ld_is_header = 'some text here'.
ld_cv_screen_input = 'some text here'.
ld_is_item = 'some text here'.
ld_iv_mode = 'some text here'.
ld_iv_fieldname = 'some text here'.
ld_iv_progname = 'some text here'.
ld_iv_dynpname = 'some text here'.