SAP I_CHANGE_STATUS Function Module for Change a status for an object









I_CHANGE_STATUS is a standard i change status SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change a status for an object 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 i change status FM, simply by entering the name I_CHANGE_STATUS into the relevant SAP transaction such as SE37 or SE38.

Function Group: ISMPM_STATUS
Program Name: SAPLISMPM_STATUS
Main Program: SAPLISMPM_STATUS
Appliation area: I
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1



Function I_CHANGE_STATUS 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 'I_CHANGE_STATUS'"Change a status for an object
EXPORTING
OBJNR = "Object number
ESTAT_INACTIVE = "Current status (internal number)
ESTAT_ACTIVE = "Status to set active
* STSMA = "Profile

EXCEPTIONS
CANNOT_UPDATE = 1
.



IMPORTING Parameters details for I_CHANGE_STATUS

OBJNR - Object number

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

ESTAT_INACTIVE - Current status (internal number)

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

ESTAT_ACTIVE - Status to set active

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

STSMA - Profile

Data type: JSTO-STSMA
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

CANNOT_UPDATE - Status could not be updated

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

Copy and paste ABAP code example for I_CHANGE_STATUS 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_objnr  TYPE JEST-OBJNR, "   
lv_cannot_update  TYPE JEST, "   
lv_estat_inactive  TYPE TJ30-ESTAT, "   
lv_estat_active  TYPE TJ30-ESTAT, "   
lv_stsma  TYPE JSTO-STSMA. "   

  CALL FUNCTION 'I_CHANGE_STATUS'  "Change a status for an object
    EXPORTING
         OBJNR = lv_objnr
         ESTAT_INACTIVE = lv_estat_inactive
         ESTAT_ACTIVE = lv_estat_active
         STSMA = lv_stsma
    EXCEPTIONS
        CANNOT_UPDATE = 1
. " I_CHANGE_STATUS




ABAP code using 7.40 inline data declarations to call FM I_CHANGE_STATUS

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 OBJNR FROM JEST INTO @DATA(ld_objnr).
 
 
"SELECT single ESTAT FROM TJ30 INTO @DATA(ld_estat_inactive).
 
"SELECT single ESTAT FROM TJ30 INTO @DATA(ld_estat_active).
 
"SELECT single STSMA FROM JSTO INTO @DATA(ld_stsma).
 


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!