CON_ACC_BME_CHANGE_VALID SAP Function module

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

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

Pattern for FM CON_ACC_BME_CHANGE_VALID - CON ACC BME CHANGE VALID

CALL FUNCTION 'CON_ACC_BME_CHANGE_VALID' "
  EXPORTING
    id_product =                " any
    id_location =               " any
*   id_display = ' '            " boole_d
  IMPORTING
    ed_valid =                  " boole_d
    et_bapiret2 =               " bapirettab
  EXCEPTIONS
    FAILED = 1                  "
    .  "  CON_ACC_BME_CHANGE_VALID

ABAP code example for Function Module CON_ACC_BME_CHANGE_VALID

The ABAP code below is a full code listing to execute function module CON_ACC_BME_CHANGE_VALID 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_ed_valid  
 
 TYPE BOOLE_D
,
ld_et_bapiret2  
 
 TYPE BAPIRETTAB
.


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

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

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

CALL FUNCTION 'CON_ACC_BME_CHANGE_VALID'
  EXPORTING
    id_product =                 ld_id_product
    id_location =                ld_id_location
*   id_display =                 ld_id_display
  IMPORTING
    ed_valid =                   ld_ed_valid
    et_bapiret2 =                ld_et_bapiret2
  EXCEPTIONS
    FAILED =                     1
    .  "  CON_ACC_BME_CHANGE_VALID

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
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_ed_valid
 
 TYPE BOOLE_D ,
ld_id_product
 
 TYPE ANY ,
ld_et_bapiret2
 
 TYPE BAPIRETTAB ,
ld_id_location
 
 TYPE ANY ,
ld_id_display
 
 TYPE BOOLE_D .


ld_id_product = 'Check type of data required'.
ld_id_location = 'Check type of data required'.
ld_id_display = 'Check type of data required'.