SAP SXMI_XBP_JOB_ABAP_STEP_MODIFY Function Module for Obsolete: Use BAPI_XBP_JOB_ABAP_STEP_MODIFY









SXMI_XBP_JOB_ABAP_STEP_MODIFY is a standard sxmi xbp job abap step modify 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_ABAP_STEP_MODIFY 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 abap step modify FM, simply by entering the name SXMI_XBP_JOB_ABAP_STEP_MODIFY into the relevant SAP transaction such as SE37 or SE38.

Function Group: SXJI
Program Name: SAPLSXJI
Main Program: SAPLSXJI
Appliation area: S
Release date: 15-Jan-1997
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function SXMI_XBP_JOB_ABAP_STEP_MODIFY 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_ABAP_STEP_MODIFY'"Obsolete: Use BAPI_XBP_JOB_ABAP_STEP_MODIFY
  EXPORTING
   JOBNAME =  "Job Name
   STEP_NUMBER =  "Number of the Step to be Modified
   JOBCOUNT =  "Job Count
   EXTERNAL_USER_NAME =  "Name of the SAP-External User
   ABAP_PROGRAM_NAME =  "ABAP Program Name
*  ABAP_VARIANT_NAME = ' ' "ABAP Variant Name
*  SAP_USER_NAME = SY-UNAME "SAP User Name for Authorization Check
*  LANGUAGE = SY-LANGU "Language for List and Message Output
*  PRINT_PARAMETERS = ' ' "Print Parameters
*  ARCHIVE_PARAMETERS = ' ' "Archive Parameters

EXCEPTIONS
   JOBID_MISSING = 1    INVALID_ARCHIVE_PARAMS = 10    INVALID_STEP_COUNT = 11    STEP_COUNT_MISSING = 12    PROBLEM_DETECTED = 2    EXTERNAL_USER_NAME_MISSING = 3    CANT_LOG_ACTION = 4    NOT_LOGGED_ON = 5    JOB_DOES_NOT_EXIST = 6    PROGRAM_NAME_MISSING = 7    ARCHIVE_INFO_NOT_FOUND = 8    INVALID_PRINT_PARAMS = 9
.



IMPORTING Parameters details for SXMI_XBP_JOB_ABAP_STEP_MODIFY

JOBNAME - Job Name

Data type: TBTCJOB-JOBNAME
Optional: No
Call by Reference: No ( called with pass by value option)

STEP_NUMBER - Number of the Step to be Modified

Data type: TBTCJOB-STEPCOUNT
Optional: No
Call by Reference: No ( called with pass by value option)

JOBCOUNT - Job Count

Data type: TBTCJOB-JOBCOUNT
Optional: No
Call by Reference: No ( called with pass by value option)

EXTERNAL_USER_NAME - Name of the SAP-External User

Data type: TXMILOGRAW-EXTUSER
Optional: No
Call by Reference: No ( called with pass by value option)

ABAP_PROGRAM_NAME - ABAP Program Name

Data type: SY-REPID
Optional: No
Call by Reference: No ( called with pass by value option)

ABAP_VARIANT_NAME - ABAP Variant Name

Data type: RSVAR-VARIANT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

SAP_USER_NAME - SAP User Name for Authorization Check

Data type: TBTCSTEP-AUTHCKNAM
Default: SY-UNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

LANGUAGE - Language for List and Message Output

Data type: TBTCSTEP-LANGUAGE
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

PRINT_PARAMETERS - Print Parameters

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

ARCHIVE_PARAMETERS - Archive Parameters

Data type: TXJIARCPAR
Default: SPACE
Optional: 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)

INVALID_ARCHIVE_PARAMS - Invalid Archiving Parameters

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

INVALID_STEP_COUNT - Invalid Step Number

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

STEP_COUNT_MISSING - No Step Number Specified

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)

PROGRAM_NAME_MISSING - No ABAP Program Specified

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

ARCHIVE_INFO_NOT_FOUND - No Archiving Parameters Specified

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

INVALID_PRINT_PARAMS - Invalid Print Parameters

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

Copy and paste ABAP code example for SXMI_XBP_JOB_ABAP_STEP_MODIFY 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_step_number  TYPE TBTCJOB-STEPCOUNT, "   
lv_invalid_archive_params  TYPE TBTCJOB, "   
lv_invalid_step_count  TYPE TBTCJOB, "   
lv_step_count_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_cant_log_action  TYPE TXMILOGRAW, "   
lv_abap_program_name  TYPE SY-REPID, "   
lv_not_logged_on  TYPE SY, "   
lv_abap_variant_name  TYPE RSVAR-VARIANT, "   SPACE
lv_sap_user_name  TYPE TBTCSTEP-AUTHCKNAM, "   SY-UNAME
lv_job_does_not_exist  TYPE TBTCSTEP, "   
lv_language  TYPE TBTCSTEP-LANGUAGE, "   SY-LANGU
lv_program_name_missing  TYPE TBTCSTEP, "   
lv_print_parameters  TYPE TXJIPRIPAR, "   SPACE
lv_archive_info_not_found  TYPE TXJIPRIPAR, "   
lv_archive_parameters  TYPE TXJIARCPAR, "   SPACE
lv_invalid_print_params  TYPE TXJIARCPAR. "   

  CALL FUNCTION 'SXMI_XBP_JOB_ABAP_STEP_MODIFY'  "Obsolete: Use BAPI_XBP_JOB_ABAP_STEP_MODIFY
    EXPORTING
         JOBNAME = lv_jobname
         STEP_NUMBER = lv_step_number
         JOBCOUNT = lv_jobcount
         EXTERNAL_USER_NAME = lv_external_user_name
         ABAP_PROGRAM_NAME = lv_abap_program_name
         ABAP_VARIANT_NAME = lv_abap_variant_name
         SAP_USER_NAME = lv_sap_user_name
         LANGUAGE = lv_language
         PRINT_PARAMETERS = lv_print_parameters
         ARCHIVE_PARAMETERS = lv_archive_parameters
    EXCEPTIONS
        JOBID_MISSING = 1
        INVALID_ARCHIVE_PARAMS = 10
        INVALID_STEP_COUNT = 11
        STEP_COUNT_MISSING = 12
        PROBLEM_DETECTED = 2
        EXTERNAL_USER_NAME_MISSING = 3
        CANT_LOG_ACTION = 4
        NOT_LOGGED_ON = 5
        JOB_DOES_NOT_EXIST = 6
        PROGRAM_NAME_MISSING = 7
        ARCHIVE_INFO_NOT_FOUND = 8
        INVALID_PRINT_PARAMS = 9
. " SXMI_XBP_JOB_ABAP_STEP_MODIFY




ABAP code using 7.40 inline data declarations to call FM SXMI_XBP_JOB_ABAP_STEP_MODIFY

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 STEPCOUNT FROM TBTCJOB INTO @DATA(ld_step_number).
 
 
 
 
"SELECT single JOBCOUNT FROM TBTCJOB INTO @DATA(ld_jobcount).
 
 
"SELECT single EXTUSER FROM TXMILOGRAW INTO @DATA(ld_external_user_name).
 
 
 
"SELECT single REPID FROM SY INTO @DATA(ld_abap_program_name).
 
 
"SELECT single VARIANT FROM RSVAR INTO @DATA(ld_abap_variant_name).
DATA(ld_abap_variant_name) = ' '.
 
"SELECT single AUTHCKNAM FROM TBTCSTEP INTO @DATA(ld_sap_user_name).
DATA(ld_sap_user_name) = SY-UNAME.
 
 
"SELECT single LANGUAGE FROM TBTCSTEP INTO @DATA(ld_language).
DATA(ld_language) = SY-LANGU.
 
 
DATA(ld_print_parameters) = ' '.
 
 
DATA(ld_archive_parameters) = ' '.
 
 


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!