SAP GET_JOB_HIST_MESSAGE Function Module for MS SQL server function to get the list of SAP Job History Messages









GET_JOB_HIST_MESSAGE is a standard get job hist message SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for MS SQL server function to get the list of SAP Job History Messages 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 get job hist message FM, simply by entering the name GET_JOB_HIST_MESSAGE into the relevant SAP transaction such as SE37 or SE38.

Function Group: SFMSS_JOBS
Program Name: SAPLSFMSS_JOBS
Main Program: SAPLSFMSS_JOBS
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function GET_JOB_HIST_MESSAGE 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 'GET_JOB_HIST_MESSAGE'"MS SQL server function to get the list of SAP Job History Messages
  EXPORTING
*  NUM_OF_DAYS = 30 "MS SQL server - run time limit for dbcc commands
*  LINE_LEN = 70 "MS SQL server - run time limit for dbcc commands
*  CON_NAME = 'DEFAULT' "Logical name for a database connection
*  SCHEMA = '' "Schema name

TABLES
   TASKLIST =  "

EXCEPTIONS
   DB_ERROR = 1    INTERNAL_ERROR = 2    CONNECT_ERROR = 3    NOT_RUNNING_ON_MSSQL = 4
.



IMPORTING Parameters details for GET_JOB_HIST_MESSAGE

NUM_OF_DAYS - MS SQL server - run time limit for dbcc commands

Data type: MSQIMPORT-RUNTIME
Default: 30
Optional: Yes
Call by Reference: No ( called with pass by value option)

LINE_LEN - MS SQL server - run time limit for dbcc commands

Data type: MSQIMPORT-RUNTIME
Default: 70
Optional: Yes
Call by Reference: No ( called with pass by value option)

CON_NAME - Logical name for a database connection

Data type: DBCON-CON_NAME
Default: 'DEFAULT'
Optional: Yes
Call by Reference: No ( called with pass by value option)

SCHEMA - Schema name

Data type: MSSSCHEMA
Default: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for GET_JOB_HIST_MESSAGE

TASKLIST -

Data type: MSQJOBMESS
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

DB_ERROR -

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

CONNECT_ERROR -

Data type:
Optional: No
Call by Reference: Yes

NOT_RUNNING_ON_MSSQL -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for GET_JOB_HIST_MESSAGE 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_db_error  TYPE STRING, "   
lt_tasklist  TYPE STANDARD TABLE OF MSQJOBMESS, "   
lv_num_of_days  TYPE MSQIMPORT-RUNTIME, "   30
lv_line_len  TYPE MSQIMPORT-RUNTIME, "   70
lv_internal_error  TYPE MSQIMPORT, "   
lv_con_name  TYPE DBCON-CON_NAME, "   'DEFAULT'
lv_connect_error  TYPE DBCON, "   
lv_schema  TYPE MSSSCHEMA, "   ''
lv_not_running_on_mssql  TYPE MSSSCHEMA. "   

  CALL FUNCTION 'GET_JOB_HIST_MESSAGE'  "MS SQL server function to get the list of SAP Job History Messages
    EXPORTING
         NUM_OF_DAYS = lv_num_of_days
         LINE_LEN = lv_line_len
         CON_NAME = lv_con_name
         SCHEMA = lv_schema
    TABLES
         TASKLIST = lt_tasklist
    EXCEPTIONS
        DB_ERROR = 1
        INTERNAL_ERROR = 2
        CONNECT_ERROR = 3
        NOT_RUNNING_ON_MSSQL = 4
. " GET_JOB_HIST_MESSAGE




ABAP code using 7.40 inline data declarations to call FM GET_JOB_HIST_MESSAGE

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 RUNTIME FROM MSQIMPORT INTO @DATA(ld_num_of_days).
DATA(ld_num_of_days) = 30.
 
"SELECT single RUNTIME FROM MSQIMPORT INTO @DATA(ld_line_len).
DATA(ld_line_len) = 70.
 
 
"SELECT single CON_NAME FROM DBCON INTO @DATA(ld_con_name).
DATA(ld_con_name) = 'DEFAULT'.
 
 
DATA(ld_schema) = ''.
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!