SAP LXE_BP_CHECK_JOB_NAME Function Module for Batch Job Status
LXE_BP_CHECK_JOB_NAME is a standard lxe bp check job name SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Batch Job Status 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 lxe bp check job name FM, simply by entering the name LXE_BP_CHECK_JOB_NAME into the relevant SAP transaction such as SE37 or SE38.
Function Group: LXE_BP
Program Name: SAPLLXE_BP
Main Program: SAPLLXE_BP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function LXE_BP_CHECK_JOB_NAME 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 'LXE_BP_CHECK_JOB_NAME'"Batch Job Status.
EXPORTING
JOBNAME = "Background job name
IMPORTING
NUMBER_OF_JOBS = "Single-Character Flag
EXCEPTIONS
JOB_NAME_UNKNOWN = 1
IMPORTING Parameters details for LXE_BP_CHECK_JOB_NAME
JOBNAME - Background job name
Data type: BTCJOBOptional: No
Call by Reference: Yes
EXPORTING Parameters details for LXE_BP_CHECK_JOB_NAME
NUMBER_OF_JOBS - Single-Character Flag
Data type: INT4Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
JOB_NAME_UNKNOWN -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for LXE_BP_CHECK_JOB_NAME 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_jobname | TYPE BTCJOB, " | |||
| lv_number_of_jobs | TYPE INT4, " | |||
| lv_job_name_unknown | TYPE INT4. " |
|   CALL FUNCTION 'LXE_BP_CHECK_JOB_NAME' "Batch Job Status |
| EXPORTING | ||
| JOBNAME | = lv_jobname | |
| IMPORTING | ||
| NUMBER_OF_JOBS | = lv_number_of_jobs | |
| EXCEPTIONS | ||
| JOB_NAME_UNKNOWN = 1 | ||
| . " LXE_BP_CHECK_JOB_NAME | ||
ABAP code using 7.40 inline data declarations to call FM LXE_BP_CHECK_JOB_NAME
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