SAP BUS_OBUSED_FOLDER_CHECK Function Module for
BUS_OBUSED_FOLDER_CHECK is a standard bus obused folder check 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 obused folder check FM, simply by entering the name BUS_OBUSED_FOLDER_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: BUSS_USED
Program Name: SAPLBUSS_USED
Main Program: SAPLBUSS_USED
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BUS_OBUSED_FOLDER_CHECK 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_OBUSED_FOLDER_CHECK'".
EXPORTING
IV_OBJAP = "
IMPORTING
EV_FOLDER_EXIST = "Data Element for Domain BOOLE: TRUE (='X') and FALSE (=' ')
IMPORTING Parameters details for BUS_OBUSED_FOLDER_CHECK
IV_OBJAP -
Data type: TBZ1-OBJAPOptional: No
Call by Reference: Yes
EXPORTING Parameters details for BUS_OBUSED_FOLDER_CHECK
EV_FOLDER_EXIST - Data Element for Domain BOOLE: TRUE (='X') and FALSE (=' ')
Data type: BOOLE-BOOLEOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for BUS_OBUSED_FOLDER_CHECK 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_iv_objap | TYPE TBZ1-OBJAP, " | |||
| lv_ev_folder_exist | TYPE BOOLE-BOOLE. " |
|   CALL FUNCTION 'BUS_OBUSED_FOLDER_CHECK' " |
| EXPORTING | ||
| IV_OBJAP | = lv_iv_objap | |
| IMPORTING | ||
| EV_FOLDER_EXIST | = lv_ev_folder_exist | |
| . " BUS_OBUSED_FOLDER_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM BUS_OBUSED_FOLDER_CHECK
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_iv_objap). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_ev_folder_exist). | ||||
Search for further information about these or an SAP related objects