SAP VBHT_COMPONENTS_DETERMINE Function Module for Determine structure for index table

Search SAP Function Modules

VBHT_COMPONENTS_DETERMINE is a standard vbht components determine SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine structure for index table processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.

See here to view full function module documentation and code listing for vbht components determine FM, simply by entering the name VBHT_COMPONENTS_DETERMINE into the relevant SAP transaction such as SE37 or SE38.

Function Group: VBHT
Program Name: SAPLVBHT
Main Program: SAPLVBHT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function VBHT_COMPONENTS_DETERMINE pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.

CALL FUNCTION 'VBHT_COMPONENTS_DETERMINE'"Determine structure for index table
  EXPORTING
   IV_BHOBJ_TYPE =  "Batch-Related Object Types
   IV_EVENT =  "Individual input event for further processing

 IMPORTING
   ET_COMPONENTS =  "
   ET_FIELDS =  "Table type of VBHT_INDEX_FIELDS
   ET_FIELD_DATATYPE =  "Table type of VBHT_ATTRIBUTE
   ET_DF_ALL =  "Table for dfies entries

EXCEPTIONS
   OBJECT_NOT_ACTIVE = 1    EVENT_NOT_ACTIVE = 2    BHOBJ_MISSING = 3    EVENT_MISSING = 4    ATTRIBUTES_MISSING = 5    TECHNICAL_ERROR = 6 

.

IMPORTING Parameters details for VBHT_COMPONENTS_DETERMINE

IV_BHOBJ_TYPE - Batch-Related Object Types

Data type: BHOBJ_TYPE
Optional: No
Call by Reference: Yes

IV_EVENT - Individual input event for further processing

Data type: BHOBJ_EVENT
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for VBHT_COMPONENTS_DETERMINE

ET_COMPONENTS -

Data type: ABAP_COMPONENT_TAB
Optional: No
Call by Reference: Yes

ET_FIELDS - Table type of VBHT_INDEX_FIELDS

Data type: VBHT_INDEX_FIELDS_TT
Optional: No
Call by Reference: Yes

ET_FIELD_DATATYPE - Table type of VBHT_ATTRIBUTE

Data type: VBHT_ATTRIBUTE_TT
Optional: No
Call by Reference: Yes

ET_DF_ALL - Table for dfies entries

Data type: DFIES_TABLE
Optional: No
Call by Reference: Yes

EXCEPTIONS details

OBJECT_NOT_ACTIVE - Object is not active

Data type:
Optional: No
Call by Reference: Yes

EVENT_NOT_ACTIVE - Event is not active

Data type:
Optional: No
Call by Reference: Yes

BHOBJ_MISSING - Object is missing

Data type:
Optional: No
Call by Reference: Yes

EVENT_MISSING - Event is missing

Data type:
Optional: No
Call by Reference: Yes

ATTRIBUTES_MISSING - Attributes are missing

Data type:
Optional: No
Call by Reference: Yes

TECHNICAL_ERROR - Technical error appeared

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for VBHT_COMPONENTS_DETERMINE Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

ABAP code using 7.40 inline data declarations to call FM VBHT_COMPONENTS_DETERMINE

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

Search for further information about these or an SAP related objects