BBP_TREX_ENQUEUE_INDEX SAP Function module - BBP TREX Zuordnungstabelle sperren

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

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

Pattern for FM BBP_TREX_ENQUEUE_INDEX - BBP TREX ENQUEUE INDEX

CALL FUNCTION 'BBP_TREX_ENQUEUE_INDEX' "BBP TREX  Zuordnungstabelle sperren
  EXPORTING
    iv_object_type =            " swo_objtyp    Objekttyp
    iv_subtype =                " bbp_h_subtype  Ausprägung eines Einkaufsbelegs (z.B. Gutschrift/Rechnung)
*   iv_index_status = '*'       " bbp_trexindex_status  Status BBP TREX Index
*   iv_enqmode = 'S'            " enqmode       Sperrmodus
* TABLES
*   et_messages =               " bbp_pds_messages  Fehlermeldungen zu einer PD-Methode
  EXCEPTIONS
    FOREIGN_LOCK = 1            "               Objekt ist bereits gesperrt
    SYSTEM_FAILURE = 2          "               Interner Fehler vom Enqueue-Server
    .  "  BBP_TREX_ENQUEUE_INDEX

ABAP code example for Function Module BBP_TREX_ENQUEUE_INDEX

The ABAP code below is a full code listing to execute function module BBP_TREX_ENQUEUE_INDEX 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:
it_et_messages  
 
 TYPE STANDARD TABLE OF BBP_PDS_MESSAGES,"TABLES PARAM
wa_et_messages
 
 LIKE LINE OF it_et_messages
.


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

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

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

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

"populate fields of struture and append to itab
append wa_et_messages to it_et_messages.
.

CALL FUNCTION 'BBP_TREX_ENQUEUE_INDEX'
  EXPORTING
    iv_object_type =             ld_iv_object_type
    iv_subtype =                 ld_iv_subtype
*   iv_index_status =            ld_iv_index_status
*   iv_enqmode =                 ld_iv_enqmode
* TABLES
*   et_messages =                it_et_messages
  EXCEPTIONS
    FOREIGN_LOCK =               1
    SYSTEM_FAILURE =             2
    .  "  BBP_TREX_ENQUEUE_INDEX

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "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_iv_object_type
 
 TYPE SWO_OBJTYP ,
it_et_messages
 
 TYPE STANDARD TABLE OF BBP_PDS_MESSAGES ,
wa_et_messages
 
 LIKE LINE OF it_et_messages,
ld_iv_subtype
 
 TYPE BBP_H_SUBTYPE ,
ld_iv_index_status
 
 TYPE BBP_TREXINDEX_STATUS ,
ld_iv_enqmode
 
 TYPE ENQMODE .


ld_iv_object_type = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_et_messages to it_et_messages.
ld_iv_subtype = 'Check type of data required'.
ld_iv_index_status = 'Check type of data required'.
ld_iv_enqmode = 'Check type of data required'.