SAP SXMB_MSG_INDEX_SERVICE_START Function Module for









SXMB_MSG_INDEX_SERVICE_START is a standard sxmb msg index service start SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 sxmb msg index service start FM, simply by entering the name SXMB_MSG_INDEX_SERVICE_START into the relevant SAP transaction such as SE37 or SE38.

Function Group: SXMB_MON_INDEX
Program Name: SAPLSXMB_MON_INDEX
Main Program: SAPLSXMB_MON_INDEX
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function SXMB_MSG_INDEX_SERVICE_START 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 'SXMB_MSG_INDEX_SERVICE_START'"
EXPORTING
INDEX_ID = "
SERVICE_ID = "
* JOBINFO = ' ' "

IMPORTING
RETURN_CODE = "
RETURN_TEXT = "
EXETIMEST_BEG = "
EXETIMEST_END = "
COUNT_MSG_SEL = "
COUNT_MSG_OK = "
COUNT_MSG_ERR = "

EXCEPTIONS
INDEX_ID_NOT_FOUND = 1 SERVICE_ID_NOT_FOUND = 2 SERVICE_ID_NOT_ACTIVE = 3 SERVICE_ALREADY_RUNNING = 4 INDEX_CUST_RESETTED = 5 INDEX_CUST_RESET_ERROR = 6
.



IMPORTING Parameters details for SXMB_MSG_INDEX_SERVICE_START

INDEX_ID -

Data type: TREXD_INDEX_ID
Optional: No
Call by Reference: Yes

SERVICE_ID -

Data type: SXMS_MSGIND_SERVID
Optional: No
Call by Reference: Yes

JOBINFO -

Data type: SXMSMSGINDSRV-JOBINFO
Default: SPACE
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for SXMB_MSG_INDEX_SERVICE_START

RETURN_CODE -

Data type: SXMSMSGINDLOG-RETURN_CODE
Optional: No
Call by Reference: Yes

RETURN_TEXT -

Data type: SXMSMSGINDLOG-RETURN_TEXT
Optional: No
Call by Reference: Yes

EXETIMEST_BEG -

Data type: TIMESTAMPL
Optional: No
Call by Reference: Yes

EXETIMEST_END -

Data type: TIMESTAMPL
Optional: No
Call by Reference: Yes

COUNT_MSG_SEL -

Data type: SYDBCNT
Optional: No
Call by Reference: Yes

COUNT_MSG_OK -

Data type: SYDBCNT
Optional: No
Call by Reference: Yes

COUNT_MSG_ERR -

Data type: SYDBCNT
Optional: No
Call by Reference: Yes

EXCEPTIONS details

INDEX_ID_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

SERVICE_ID_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

SERVICE_ID_NOT_ACTIVE -

Data type:
Optional: No
Call by Reference: Yes

SERVICE_ALREADY_RUNNING -

Data type:
Optional: No
Call by Reference: Yes

INDEX_CUST_RESETTED -

Data type:
Optional: No
Call by Reference: Yes

INDEX_CUST_RESET_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SXMB_MSG_INDEX_SERVICE_START 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_index_id  TYPE TREXD_INDEX_ID, "   
lv_return_code  TYPE SXMSMSGINDLOG-RETURN_CODE, "   
lv_index_id_not_found  TYPE SXMSMSGINDLOG, "   
lv_service_id  TYPE SXMS_MSGIND_SERVID, "   
lv_return_text  TYPE SXMSMSGINDLOG-RETURN_TEXT, "   
lv_service_id_not_found  TYPE SXMSMSGINDLOG, "   
lv_jobinfo  TYPE SXMSMSGINDSRV-JOBINFO, "   SPACE
lv_exetimest_beg  TYPE TIMESTAMPL, "   
lv_service_id_not_active  TYPE TIMESTAMPL, "   
lv_exetimest_end  TYPE TIMESTAMPL, "   
lv_service_already_running  TYPE TIMESTAMPL, "   
lv_count_msg_sel  TYPE SYDBCNT, "   
lv_index_cust_resetted  TYPE SYDBCNT, "   
lv_count_msg_ok  TYPE SYDBCNT, "   
lv_index_cust_reset_error  TYPE SYDBCNT, "   
lv_count_msg_err  TYPE SYDBCNT. "   

  CALL FUNCTION 'SXMB_MSG_INDEX_SERVICE_START'  "
    EXPORTING
         INDEX_ID = lv_index_id
         SERVICE_ID = lv_service_id
         JOBINFO = lv_jobinfo
    IMPORTING
         RETURN_CODE = lv_return_code
         RETURN_TEXT = lv_return_text
         EXETIMEST_BEG = lv_exetimest_beg
         EXETIMEST_END = lv_exetimest_end
         COUNT_MSG_SEL = lv_count_msg_sel
         COUNT_MSG_OK = lv_count_msg_ok
         COUNT_MSG_ERR = lv_count_msg_err
    EXCEPTIONS
        INDEX_ID_NOT_FOUND = 1
        SERVICE_ID_NOT_FOUND = 2
        SERVICE_ID_NOT_ACTIVE = 3
        SERVICE_ALREADY_RUNNING = 4
        INDEX_CUST_RESETTED = 5
        INDEX_CUST_RESET_ERROR = 6
. " SXMB_MSG_INDEX_SERVICE_START




ABAP code using 7.40 inline data declarations to call FM SXMB_MSG_INDEX_SERVICE_START

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 RETURN_CODE FROM SXMSMSGINDLOG INTO @DATA(ld_return_code).
 
 
 
"SELECT single RETURN_TEXT FROM SXMSMSGINDLOG INTO @DATA(ld_return_text).
 
 
"SELECT single JOBINFO FROM SXMSMSGINDSRV INTO @DATA(ld_jobinfo).
DATA(ld_jobinfo) = ' '.
 
 
 
 
 
 
 
 
 
 


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!