SAP VB_DPP_CONNECT_HANDLER Function Module for Connect DPP-Handler to IRF









VB_DPP_CONNECT_HANDLER is a standard vb dpp connect handler SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Connect DPP-Handler to IRF 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 vb dpp connect handler FM, simply by entering the name VB_DPP_CONNECT_HANDLER into the relevant SAP transaction such as SE37 or SE38.

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



Function VB_DPP_CONNECT_HANDLER 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 'VB_DPP_CONNECT_HANDLER'"Connect DPP-Handler to IRF
  EXPORTING
   I_TAB =  "Table Name
   I_ADD_TAB =  "Generic Table Browser: Table Name
   I_EVENT =  "Single-Character Flag
   I_FATHER_ID =  "GSS: ID of Father
   I_SEC_TAB_ID =  "GSS: Dependency ID
   I_EXIT_DATA =  "GSS: Handover data to Application-Exit
*  I_PURPOSE =  "GSS: Scenario for dependent tables

 IMPORTING
   E_ACTION =  "Single-Character Flag
   E_ROWS =  "GSS: Number of Hits Found
   E_DONE =  "Boolean Variable (X=true, -=false, space=unknown)
   E_DATA =  "GSS: Transferstructure for RFC-Calls of Content

CHANGING
   IT_OR_SELTAB =  "GTB: Transfer Table Type for Multiple Selection Criteria
   ET_TABLES_EXIT =  "GSS: Table Type for GSS_S_SEARCH_AREA
.



IMPORTING Parameters details for VB_DPP_CONNECT_HANDLER

I_TAB - Table Name

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

I_ADD_TAB - Generic Table Browser: Table Name

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

I_EVENT - Single-Character Flag

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

I_FATHER_ID - GSS: ID of Father

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

I_SEC_TAB_ID - GSS: Dependency ID

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

I_EXIT_DATA - GSS: Handover data to Application-Exit

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

I_PURPOSE - GSS: Scenario for dependent tables

Data type: GSS_SCENARIO
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for VB_DPP_CONNECT_HANDLER

E_ACTION - Single-Character Flag

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

E_ROWS - GSS: Number of Hits Found

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

E_DONE - Boolean Variable (X=true, -=false, space=unknown)

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

E_DATA - GSS: Transferstructure for RFC-Calls of Content

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

CHANGING Parameters details for VB_DPP_CONNECT_HANDLER

IT_OR_SELTAB - GTB: Transfer Table Type for Multiple Selection Criteria

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

ET_TABLES_EXIT - GSS: Table Type for GSS_S_SEARCH_AREA

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

Copy and paste ABAP code example for VB_DPP_CONNECT_HANDLER 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.

DATA:
lv_i_tab  TYPE TABNAME, "   
lv_e_action  TYPE CHAR1, "   
lv_it_or_seltab  TYPE GTB_T_OR_CLAUSE, "   
lv_e_rows  TYPE GSS_COUNT, "   
lv_i_add_tab  TYPE GTB_TAB, "   
lv_et_tables_exit  TYPE GSS_T_SEARCH_AREA, "   
lv_e_done  TYPE BOOLEAN, "   
lv_i_event  TYPE CHAR1, "   
lv_e_data  TYPE GSS_T_TRANSFER, "   
lv_i_father_id  TYPE GSS_DEP_FATHER, "   
lv_i_sec_tab_id  TYPE GSS_DEP_ID, "   
lv_i_exit_data  TYPE GSS_S_EXIT, "   
lv_i_purpose  TYPE GSS_SCENARIO. "   

  CALL FUNCTION 'VB_DPP_CONNECT_HANDLER'  "Connect DPP-Handler to IRF
    EXPORTING
         I_TAB = lv_i_tab
         I_ADD_TAB = lv_i_add_tab
         I_EVENT = lv_i_event
         I_FATHER_ID = lv_i_father_id
         I_SEC_TAB_ID = lv_i_sec_tab_id
         I_EXIT_DATA = lv_i_exit_data
         I_PURPOSE = lv_i_purpose
    IMPORTING
         E_ACTION = lv_e_action
         E_ROWS = lv_e_rows
         E_DONE = lv_e_done
         E_DATA = lv_e_data
    CHANGING
         IT_OR_SELTAB = lv_it_or_seltab
         ET_TABLES_EXIT = lv_et_tables_exit
. " VB_DPP_CONNECT_HANDLER




ABAP code using 7.40 inline data declarations to call FM VB_DPP_CONNECT_HANDLER

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!