SAP FTR_STAV_STATUS_CHANGE_INTERN Function Module for Set/Delete System Status









FTR_STAV_STATUS_CHANGE_INTERN is a standard ftr stav status change intern SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Set/Delete System Status 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 ftr stav status change intern FM, simply by entering the name FTR_STAV_STATUS_CHANGE_INTERN into the relevant SAP transaction such as SE37 or SE38.

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



Function FTR_STAV_STATUS_CHANGE_INTERN 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 'FTR_STAV_STATUS_CHANGE_INTERN'"Set/Delete System Status
EXPORTING
OBJNR = "Object Number
* CHECK_ONLY = ' ' "Selection Indicator

TABLES
STATUS = "

EXCEPTIONS
OBJECT_NOT_FOUND = 1 STATUS_INCONSISTENT = 2 STATUS_NOT_ALLOWED = 3
.



IMPORTING Parameters details for FTR_STAV_STATUS_CHANGE_INTERN

OBJNR - Object Number

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

CHECK_ONLY - Selection Indicator

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

TABLES Parameters details for FTR_STAV_STATUS_CHANGE_INTERN

STATUS -

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

EXCEPTIONS details

OBJECT_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

STATUS_INCONSISTENT -

Data type:
Optional: No
Call by Reference: Yes

STATUS_NOT_ALLOWED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FTR_STAV_STATUS_CHANGE_INTERN 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 JSTO-OBJNR, "   
lt_status  TYPE STANDARD TABLE OF JSTAT, "   
lv_object_not_found  TYPE JSTAT, "   
lv_check_only  TYPE BOOLEAN, "   SPACE
lv_status_inconsistent  TYPE BOOLEAN, "   
lv_status_not_allowed  TYPE BOOLEAN. "   

  CALL FUNCTION 'FTR_STAV_STATUS_CHANGE_INTERN'  "Set/Delete System Status
    EXPORTING
         OBJNR = lv_objnr
         CHECK_ONLY = lv_check_only
    TABLES
         STATUS = lt_status
    EXCEPTIONS
        OBJECT_NOT_FOUND = 1
        STATUS_INCONSISTENT = 2
        STATUS_NOT_ALLOWED = 3
. " FTR_STAV_STATUS_CHANGE_INTERN




ABAP code using 7.40 inline data declarations to call FM FTR_STAV_STATUS_CHANGE_INTERN

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 JSTO INTO @DATA(ld_objnr).
 
 
 
DATA(ld_check_only) = ' '.
 
 
 


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!