SAP DB_EMSG_BALOBJ_SINGLE Function Module for









DB_EMSG_BALOBJ_SINGLE is a standard db emsg balobj single 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 db emsg balobj single FM, simply by entering the name DB_EMSG_BALOBJ_SINGLE into the relevant SAP transaction such as SE37 or SE38.

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



Function DB_EMSG_BALOBJ_SINGLE 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 'DB_EMSG_BALOBJ_SINGLE'"
EXPORTING
X_OBJECT = "Object Name
* X_ACTUAL = "

EXCEPTIONS
NOT_FOUND = 1
.



IMPORTING Parameters details for DB_EMSG_BALOBJ_SINGLE

X_OBJECT - Object Name

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

X_ACTUAL -

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

EXCEPTIONS details

NOT_FOUND - Object Not Found

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

Copy and paste ABAP code example for DB_EMSG_BALOBJ_SINGLE 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_x_object  TYPE BALOBJ-OBJECT, "   
lv_not_found  TYPE BALOBJ, "   
lv_x_actual  TYPE EETA_GEN-ACTUAL. "   

  CALL FUNCTION 'DB_EMSG_BALOBJ_SINGLE'  "
    EXPORTING
         X_OBJECT = lv_x_object
         X_ACTUAL = lv_x_actual
    EXCEPTIONS
        NOT_FOUND = 1
. " DB_EMSG_BALOBJ_SINGLE




ABAP code using 7.40 inline data declarations to call FM DB_EMSG_BALOBJ_SINGLE

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.

"SELECT single OBJECT FROM BALOBJ INTO @DATA(ld_x_object).
 
 
"SELECT single ACTUAL FROM EETA_GEN INTO @DATA(ld_x_actual).
 


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!