SAP G_BEB_GET_CONTROL Function Module for

Search SAP Function Modules

G_BEB_GET_CONTROL is a standard g beb get control SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 g beb get control FM, simply by entering the name G_BEB_GET_CONTROL into the relevant SAP transaction such as SE37 or SE38.

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

Function G_BEB_GET_CONTROL 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 'G_BEB_GET_CONTROL'"
  EXPORTING
   I_SPLITMETHD =  "Splitting method
   I_PROCESS =  "Business Process
   I_VARIANT =  "Business Process Variant
*  I_READ_BUFFER =  "Read Data from Buffer
*  IB_EURO_MODE = ABAP_FALSE "
*  I_PROCESS_ORG = ' ' "Business Transaction
*  I_VARIANT_ORG = ' ' "Business Transaction Variant

 IMPORTING
   E_CONTROL_BALANCE =  "
   E_SEPER_LOG_PROCESS =  "

TABLES
*  T_CONTROL_SPLIT =  "
*  T_CONTROL_ADDITEM =  "

EXCEPTIONS
   INCONSISTENCY_T8G20 = 1    INCONSISTENCY_T8G21 = 2 

.

IMPORTING Parameters details for G_BEB_GET_CONTROL

I_SPLITMETHD - Splitting method

Data type: T8G01-SPLITMETHD
Optional: No
Call by Reference: No ( called with pass by value option)

I_PROCESS - Business Process

Data type: T8G03-PROCESS
Optional: No
Call by Reference: No ( called with pass by value option)

I_VARIANT - Business Process Variant

Data type: T8G031-VARIANT
Optional: No
Call by Reference: No ( called with pass by value option)

I_READ_BUFFER - Read Data from Buffer

Data type: GLT0_FLAG
Optional: Yes
Call by Reference: No ( called with pass by value option)

IB_EURO_MODE -

Data type: ABAP_BOOL
Default: ABAP_FALSE
Optional: Yes
Call by Reference: Yes

I_PROCESS_ORG - Business Transaction

Data type: GLPROCESS
Default: SPACE
Optional: Yes
Call by Reference: Yes

I_VARIANT_ORG - Business Transaction Variant

Data type: GLPROCVARI
Default: SPACE
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for G_BEB_GET_CONTROL

E_CONTROL_BALANCE -

Data type: GLT0_CONTROL_BALANCE
Optional: No
Call by Reference: No ( called with pass by value option)

E_SEPER_LOG_PROCESS -

Data type: GLT0_FLAG
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for G_BEB_GET_CONTROL

T_CONTROL_SPLIT -

Data type: GLT0_CONTROL_SPLIT_TAB
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_CONTROL_ADDITEM -

Data type: GLT0_CONTROL_ADDITEM_TAB
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

INCONSISTENCY_T8G20 -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

INCONSISTENCY_T8G21 -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

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

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