BBP_TREX_CHECK_INDEX SAP Function module - Überprüfung, ob Indizieren von Objekten mit TREX möglich ist

BBP_TREX_CHECK_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_CHECK_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_CHECK_INDEX - BBP TREX CHECK INDEX

CALL FUNCTION 'BBP_TREX_CHECK_INDEX' "Überprüfung, ob Indizieren von Objekten mit TREX  möglich ist
  EXPORTING
    iv_object_type =            " crmt_subobject_category_db  Geschäftsvorgangstyp
    iv_subtype =                " bbp_h_subtype  Ausprägung eines Einkaufsbelegs (z.B. Gutschrift/Rechnung)
  IMPORTING
    ev_index_possible =         " xfeld         Feld zum Ankreuzen
    ev_index_status =           " bbp_trexindex_status  Status BBP TREX Index
* TABLES
*   et_messages =               " bbp_pds_messages  Fehlermeldungen zu einer PD-Methode
    .  "  BBP_TREX_CHECK_INDEX

ABAP code example for Function Module BBP_TREX_CHECK_INDEX

The ABAP code below is a full code listing to execute function module BBP_TREX_CHECK_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:
ld_ev_index_possible  
 
 TYPE XFELD
,
ld_ev_index_status  
 
 TYPE BBP_TREXINDEX_STATUS
,
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'.
 

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

CALL FUNCTION 'BBP_TREX_CHECK_INDEX'
  EXPORTING
    iv_object_type =             ld_iv_object_type
    iv_subtype =                 ld_iv_subtype
  IMPORTING
    ev_index_possible =          ld_ev_index_possible
    ev_index_status =            ld_ev_index_status
* TABLES
*   et_messages =                it_et_messages
    .  "  BBP_TREX_CHECK_INDEX

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_index_possible
 
 TYPE XFELD ,
ld_iv_object_type
 
 TYPE CRMT_SUBOBJECT_CATEGORY_DB ,
it_et_messages
 
 TYPE STANDARD TABLE OF BBP_PDS_MESSAGES ,
wa_et_messages
 
 LIKE LINE OF it_et_messages,
ld_ev_index_status
 
 TYPE BBP_TREXINDEX_STATUS ,
ld_iv_subtype
 
 TYPE BBP_H_SUBTYPE .


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'.