SAP SXMI_XBP_JOB_CLOSE Function Module for Obsolete: Use BAPI_XBP_JOB_CLOSE
SXMI_XBP_JOB_CLOSE is a standard sxmi xbp job close SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Obsolete: Use BAPI_XBP_JOB_CLOSE 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 sxmi xbp job close FM, simply by entering the name SXMI_XBP_JOB_CLOSE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SXJI
Program Name: SAPLSXJI
Main Program: SAPLSXJI
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SXMI_XBP_JOB_CLOSE 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 'SXMI_XBP_JOB_CLOSE'"Obsolete: Use BAPI_XBP_JOB_CLOSE.
EXPORTING
JOBNAME = "Job Name
JOBCOUNT = "Job Count
EXTERNAL_USER_NAME = "Name of the SAP-External User
* TARGET_HOST = ' ' "Executing Host for External Program
* TARGET_SERVER = "
EXCEPTIONS
JOBID_MISSING = 1 PROBLEM_DETECTED = 2 EXTERNAL_USER_NAME_MISSING = 3 CANT_LOG_ACTION = 4 NOT_LOGGED_ON = 5 JOB_DOES_NOT_EXIST = 6
IMPORTING Parameters details for SXMI_XBP_JOB_CLOSE
JOBNAME - Job Name
Data type: TBTCJOB-JOBNAMEOptional: No
Call by Reference: No ( called with pass by value option)
JOBCOUNT - Job Count
Data type: TBTCJOB-JOBCOUNTOptional: No
Call by Reference: No ( called with pass by value option)
EXTERNAL_USER_NAME - Name of the SAP-External User
Data type: TXMILOGRAW-EXTUSEROptional: No
Call by Reference: No ( called with pass by value option)
TARGET_HOST - Executing Host for External Program
Data type: TBTCJOB-BTCSYSTEMDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TARGET_SERVER -
Data type: TBTCJOB-EXECSERVEROptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
JOBID_MISSING - Job Name / Job Count Missing
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PROBLEM_DETECTED - Problem Found (See System Log for Explanation)
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXTERNAL_USER_NAME_MISSING - Name of SAP-External User is Missing
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CANT_LOG_ACTION - Error in XMI Logging (See System Log)
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_LOGGED_ON - XMI Logon Missing
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
JOB_DOES_NOT_EXIST - Job Specified Does Not Exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SXMI_XBP_JOB_CLOSE 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 TBTCJOB-JOBNAME, " | |||
| lv_jobid_missing | TYPE TBTCJOB, " | |||
| lv_jobcount | TYPE TBTCJOB-JOBCOUNT, " | |||
| lv_problem_detected | TYPE TBTCJOB, " | |||
| lv_external_user_name | TYPE TXMILOGRAW-EXTUSER, " | |||
| lv_external_user_name_missing | TYPE TXMILOGRAW, " | |||
| lv_target_host | TYPE TBTCJOB-BTCSYSTEM, " SPACE | |||
| lv_cant_log_action | TYPE TBTCJOB, " | |||
| lv_not_logged_on | TYPE TBTCJOB, " | |||
| lv_target_server | TYPE TBTCJOB-EXECSERVER, " | |||
| lv_job_does_not_exist | TYPE TBTCJOB. " |
|   CALL FUNCTION 'SXMI_XBP_JOB_CLOSE' "Obsolete: Use BAPI_XBP_JOB_CLOSE |
| EXPORTING | ||
| JOBNAME | = lv_jobname | |
| JOBCOUNT | = lv_jobcount | |
| EXTERNAL_USER_NAME | = lv_external_user_name | |
| TARGET_HOST | = lv_target_host | |
| TARGET_SERVER | = lv_target_server | |
| EXCEPTIONS | ||
| JOBID_MISSING = 1 | ||
| PROBLEM_DETECTED = 2 | ||
| EXTERNAL_USER_NAME_MISSING = 3 | ||
| CANT_LOG_ACTION = 4 | ||
| NOT_LOGGED_ON = 5 | ||
| JOB_DOES_NOT_EXIST = 6 | ||
| . " SXMI_XBP_JOB_CLOSE | ||
ABAP code using 7.40 inline data declarations to call FM SXMI_XBP_JOB_CLOSE
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 TBTCJOB INTO @DATA(ld_jobname). | ||||
| "SELECT single JOBCOUNT FROM TBTCJOB INTO @DATA(ld_jobcount). | ||||
| "SELECT single EXTUSER FROM TXMILOGRAW INTO @DATA(ld_external_user_name). | ||||
| "SELECT single BTCSYSTEM FROM TBTCJOB INTO @DATA(ld_target_host). | ||||
| DATA(ld_target_host) | = ' '. | |||
| "SELECT single EXECSERVER FROM TBTCJOB INTO @DATA(ld_target_server). | ||||
Search for further information about these or an SAP related objects