SAP BAPI_XBP_JOB_JOBLOG_READ Function Module for Read Job Log for a Job
BAPI_XBP_JOB_JOBLOG_READ is a standard bapi xbp job joblog read 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 Log for a Job 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 joblog read FM, simply by entering the name BAPI_XBP_JOB_JOBLOG_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: SXBP
Program Name: SAPLSXBP
Main Program: SAPLSXBP
Appliation area: S
Release date: 29-Apr-1998
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function BAPI_XBP_JOB_JOBLOG_READ 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_JOBLOG_READ'"Read Job Log for a Job.
EXPORTING
JOBNAME = "Job Name
JOBCOUNT = "Job Count
EXTERNAL_USER_NAME = "Name of the SAP-External User
* PROT_NEW = "Reference type CHAR1 for background processing
* LINES = "No. of Lines
* DIRECTION = "Read Direction (B = From Beginning, E = From End)
IMPORTING
RETURN = "
TABLES
* JOB_PROTOCOL = "Job Log
* JOB_PROTOCOL_NEW = "Job Log Entries in List Format
IMPORTING Parameters details for BAPI_XBP_JOB_JOBLOG_READ
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)
PROT_NEW - Reference type CHAR1 for background processing
Data type: BTCH0000-CHAR1Optional: Yes
Call by Reference: No ( called with pass by value option)
LINES - No. of Lines
Data type: BTCINT4Optional: Yes
Call by Reference: No ( called with pass by value option)
DIRECTION - Read Direction (B = From Beginning, E = From End)
Data type: BTCCHAR1Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_XBP_JOB_JOBLOG_READ
RETURN -
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_XBP_JOB_JOBLOG_READ
JOB_PROTOCOL - Job Log
Data type: BAPIXMPROTOptional: Yes
Call by Reference: Yes
JOB_PROTOCOL_NEW - Job Log Entries in List Format
Data type: TBTC5Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_XBP_JOB_JOBLOG_READ 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_return | TYPE BAPIRET2, " | |||
lv_jobname | TYPE BAPIXMJOB-JOBNAME, " | |||
lt_job_protocol | TYPE STANDARD TABLE OF BAPIXMPROT, " | |||
lv_jobcount | TYPE BAPIXMJOB-JOBCOUNT, " | |||
lt_job_protocol_new | TYPE STANDARD TABLE OF TBTC5, " | |||
lv_external_user_name | TYPE BAPIXMLOGR-EXTUSER, " | |||
lv_prot_new | TYPE BTCH0000-CHAR1, " | |||
lv_lines | TYPE BTCINT4, " | |||
lv_direction | TYPE BTCCHAR1. " |
  CALL FUNCTION 'BAPI_XBP_JOB_JOBLOG_READ' "Read Job Log for a Job |
EXPORTING | ||
JOBNAME | = lv_jobname | |
JOBCOUNT | = lv_jobcount | |
EXTERNAL_USER_NAME | = lv_external_user_name | |
PROT_NEW | = lv_prot_new | |
LINES | = lv_lines | |
DIRECTION | = lv_direction | |
IMPORTING | ||
RETURN | = lv_return | |
TABLES | ||
JOB_PROTOCOL | = lt_job_protocol | |
JOB_PROTOCOL_NEW | = lt_job_protocol_new | |
. " BAPI_XBP_JOB_JOBLOG_READ |
ABAP code using 7.40 inline data declarations to call FM BAPI_XBP_JOB_JOBLOG_READ
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). | ||||
"SELECT single CHAR1 FROM BTCH0000 INTO @DATA(ld_prot_new). | ||||
Search for further information about these or an SAP related objects