SAP BUS_FMOD_STATUS_GET_BAPI Function Module for
BUS_FMOD_STATUS_GET_BAPI is a standard bus fmod status get bapi 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 bus fmod status get bapi FM, simply by entering the name BUS_FMOD_STATUS_GET_BAPI into the relevant SAP transaction such as SE37 or SE38.
Function Group: BUS5
Program Name: SAPLBUS5
Main Program: SAPLBUS5
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BUS_FMOD_STATUS_GET_BAPI 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 'BUS_FMOD_STATUS_GET_BAPI'".
EXPORTING
* I_OBJAP = "BDT: Application Object
I_FLDGR = "Field Group
IMPORTING
E_STATUS = "
IMPORTING Parameters details for BUS_FMOD_STATUS_GET_BAPI
I_OBJAP - BDT: Application Object
Data type: TBZ1-OBJAPOptional: Yes
Call by Reference: Yes
I_FLDGR - Field Group
Data type: TBZ3W-FLDGROptional: No
Call by Reference: Yes
EXPORTING Parameters details for BUS_FMOD_STATUS_GET_BAPI
E_STATUS -
Data type: COptional: No
Call by Reference: Yes
Copy and paste ABAP code example for BUS_FMOD_STATUS_GET_BAPI 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_objap | TYPE TBZ1-OBJAP, " | |||
| lv_e_status | TYPE C, " | |||
| lv_i_fldgr | TYPE TBZ3W-FLDGR. " |
|   CALL FUNCTION 'BUS_FMOD_STATUS_GET_BAPI' " |
| EXPORTING | ||
| I_OBJAP | = lv_i_objap | |
| I_FLDGR | = lv_i_fldgr | |
| IMPORTING | ||
| E_STATUS | = lv_e_status | |
| . " BUS_FMOD_STATUS_GET_BAPI | ||
ABAP code using 7.40 inline data declarations to call FM BUS_FMOD_STATUS_GET_BAPI
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 OBJAP FROM TBZ1 INTO @DATA(ld_i_objap). | ||||
| "SELECT single FLDGR FROM TBZ3W INTO @DATA(ld_i_fldgr). | ||||
Search for further information about these or an SAP related objects