SAP BAPI_XBP_JOB_DEFINITION_GET Function Module for Read job definition
BAPI_XBP_JOB_DEFINITION_GET is a standard bapi xbp job definition 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 Read job definition 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 bapi xbp job definition get FM, simply by entering the name BAPI_XBP_JOB_DEFINITION_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: SXBP
Program Name: SAPLSXBP
Main Program: SAPLSXBP
Appliation area: S
Release date: 19-May-1998
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_XBP_JOB_DEFINITION_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 'BAPI_XBP_JOB_DEFINITION_GET'"Read job definition.
EXPORTING
JOBNAME = "Job Name
JOBCOUNT = "Job Count
EXTERNAL_USER_NAME = "Name of the SAP-External User
IMPORTING
JOB_HEAD = "Job Header Data (Name, Class, and so on)
RETURN = "
JOBLG_ATTR = "Job Log Attributes
RECIPIENT = "Structure for Spool List Recipients
TABLES
STEP_TBL = "Job Step Values
* SPOOL_ATTR = "Parameters of a Spool Request
IMPORTING Parameters details for BAPI_XBP_JOB_DEFINITION_GET
JOBNAME - Job Name
Data type: BAPIXMJOB-JOBNAMEOptional: No
Call by Reference: No ( called with pass by value option)
JOBCOUNT - Job Count
Data type: BAPIXMJOB-JOBCOUNTOptional: No
Call by Reference: No ( called with pass by value option)
EXTERNAL_USER_NAME - Name of the SAP-External User
Data type: BAPIXMLOGR-EXTUSEROptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_XBP_JOB_DEFINITION_GET
JOB_HEAD - Job Header Data (Name, Class, and so on)
Data type: BAPIXMJOBOptional: No
Call by Reference: No ( called with pass by value option)
RETURN -
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
JOBLG_ATTR - Job Log Attributes
Data type: BAPIXMJOBLOGOptional: No
Call by Reference: No ( called with pass by value option)
RECIPIENT - Structure for Spool List Recipients
Data type: BAPIXMRECIPOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_XBP_JOB_DEFINITION_GET
STEP_TBL - Job Step Values
Data type: BAPIXMSTEPOptional: No
Call by Reference: No ( called with pass by value option)
SPOOL_ATTR - Parameters of a Spool Request
Data type: BAPIXMSPOOLIDOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_XBP_JOB_DEFINITION_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: | ||||
| lv_jobname | TYPE BAPIXMJOB-JOBNAME, " | |||
| lv_job_head | TYPE BAPIXMJOB, " | |||
| lt_step_tbl | TYPE STANDARD TABLE OF BAPIXMSTEP, " | |||
| lv_return | TYPE BAPIRET2, " | |||
| lv_jobcount | TYPE BAPIXMJOB-JOBCOUNT, " | |||
| lt_spool_attr | TYPE STANDARD TABLE OF BAPIXMSPOOLID, " | |||
| lv_joblg_attr | TYPE BAPIXMJOBLOG, " | |||
| lv_external_user_name | TYPE BAPIXMLOGR-EXTUSER, " | |||
| lv_recipient | TYPE BAPIXMRECIP. " |
|   CALL FUNCTION 'BAPI_XBP_JOB_DEFINITION_GET' "Read job definition |
| EXPORTING | ||
| JOBNAME | = lv_jobname | |
| JOBCOUNT | = lv_jobcount | |
| EXTERNAL_USER_NAME | = lv_external_user_name | |
| IMPORTING | ||
| JOB_HEAD | = lv_job_head | |
| RETURN | = lv_return | |
| JOBLG_ATTR | = lv_joblg_attr | |
| RECIPIENT | = lv_recipient | |
| TABLES | ||
| STEP_TBL | = lt_step_tbl | |
| SPOOL_ATTR | = lt_spool_attr | |
| . " BAPI_XBP_JOB_DEFINITION_GET | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_XBP_JOB_DEFINITION_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 JOBNAME FROM BAPIXMJOB INTO @DATA(ld_jobname). | ||||
| "SELECT single JOBCOUNT FROM BAPIXMJOB INTO @DATA(ld_jobcount). | ||||
| "SELECT single EXTUSER FROM BAPIXMLOGR INTO @DATA(ld_external_user_name). | ||||
Search for further information about these or an SAP related objects