BBP_BID_INV_SET_ALERT_PARAMS SAP Function module - Set Error Parameters for QUOT/PO Resubmit

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

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

Pattern for FM BBP_BID_INV_SET_ALERT_PARAMS - BBP BID INV SET ALERT PARAMS

CALL FUNCTION 'BBP_BID_INV_SET_ALERT_PARAMS' "Set Error Parameters for QUOT/PO Resubmit
  EXPORTING
    iv_user =                   " bbp_user      B2B Benutzer mit Prüftabelle auf BBP_USR01
    iv_process_type_po =        " crmt_process_type_db  Geschäftsvorgangsart
    iv_set_params =             " xfeld         Feld zum Ankreuzen
    iv_get_params =             " xfeld         Feld zum Ankreuzen
  IMPORTING
    ev_user =                   " bbp_user      B2B Benutzer mit Prüftabelle auf BBP_USR01
    ev_process_type_po =        " crmt_process_type_db  Geschäftsvorgangsart
    .  "  BBP_BID_INV_SET_ALERT_PARAMS

ABAP code example for Function Module BBP_BID_INV_SET_ALERT_PARAMS

The ABAP code below is a full code listing to execute function module BBP_BID_INV_SET_ALERT_PARAMS 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_ev_user  
 
 TYPE BBP_USER
,
ld_ev_process_type_po  
 
 TYPE CRMT_PROCESS_TYPE_DB
.


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

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

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

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

CALL FUNCTION 'BBP_BID_INV_SET_ALERT_PARAMS'
  EXPORTING
    iv_user =                    ld_iv_user
    iv_process_type_po =         ld_iv_process_type_po
    iv_set_params =              ld_iv_set_params
    iv_get_params =              ld_iv_get_params
  IMPORTING
    ev_user =                    ld_ev_user
    ev_process_type_po =         ld_ev_process_type_po
    .  "  BBP_BID_INV_SET_ALERT_PARAMS

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_ev_user
 
 TYPE BBP_USER ,
ld_iv_user
 
 TYPE BBP_USER ,
ld_ev_process_type_po
 
 TYPE CRMT_PROCESS_TYPE_DB ,
ld_iv_process_type_po
 
 TYPE CRMT_PROCESS_TYPE_DB ,
ld_iv_set_params
 
 TYPE XFELD ,
ld_iv_get_params
 
 TYPE XFELD .


ld_iv_user = 'Check type of data required'.
ld_iv_process_type_po = 'Check type of data required'.
ld_iv_set_params = 'Check type of data required'.
ld_iv_get_params = 'Check type of data required'.