SAP BPT_BATCH_Q_SIZE_GET Function Module for Determine background queue status of a server
BPT_BATCH_Q_SIZE_GET is a standard bpt batch q size get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine background queue status of a server 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 bpt batch q size get FM, simply by entering the name BPT_BATCH_Q_SIZE_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: SBPT
Program Name: SAPLSBPT
Main Program: SAPLSBPT
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BPT_BATCH_Q_SIZE_GET 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 'BPT_BATCH_Q_SIZE_GET'"Determine background queue status of a server.
IMPORTING
NEGATIVE_TEST_RESULT = "Flag which displays whether test negative
TABLES
PROTOCOL = "Test log
EXPORTING Parameters details for BPT_BATCH_Q_SIZE_GET
NEGATIVE_TEST_RESULT - Flag which displays whether test negative
Data type: BTCH0000-CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BPT_BATCH_Q_SIZE_GET
PROTOCOL - Test log
Data type: BTCTSTPROTOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BPT_BATCH_Q_SIZE_GET 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: | ||||
| lt_protocol | TYPE STANDARD TABLE OF BTCTSTPROT, " | |||
| lv_negative_test_result | TYPE BTCH0000-CHAR1. " |
|   CALL FUNCTION 'BPT_BATCH_Q_SIZE_GET' "Determine background queue status of a server |
| IMPORTING | ||
| NEGATIVE_TEST_RESULT | = lv_negative_test_result | |
| TABLES | ||
| PROTOCOL | = lt_protocol | |
| . " BPT_BATCH_Q_SIZE_GET | ||
ABAP code using 7.40 inline data declarations to call FM BPT_BATCH_Q_SIZE_GET
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 CHAR1 FROM BTCH0000 INTO @DATA(ld_negative_test_result). | ||||
Search for further information about these or an SAP related objects