SAP FTR_STAV_MAINTAIN_TRANSACTION Function Module for Status Maintenance: Call as FM with BUKR and RFHA









FTR_STAV_MAINTAIN_TRANSACTION is a standard ftr stav maintain transaction SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Status Maintenance: Call as FM with BUKR and RFHA 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 maintain transaction FM, simply by entering the name FTR_STAV_MAINTAIN_TRANSACTION 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_MAINTAIN_TRANSACTION 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_MAINTAIN_TRANSACTION'"Status Maintenance: Call as FM with BUKR and RFHA
EXPORTING
BUKRS = "Company Code
RFHA = "Financial Transaction
* DISPLAY = "Boolean Variable (X=true, -=false, space=unknown)

IMPORTING
EXIT_CODE = "Screens, Function Code That Triggered PAI
.



IMPORTING Parameters details for FTR_STAV_MAINTAIN_TRANSACTION

BUKRS - Company Code

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

RFHA - Financial Transaction

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

DISPLAY - Boolean Variable (X=true, -=false, space=unknown)

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

EXPORTING Parameters details for FTR_STAV_MAINTAIN_TRANSACTION

EXIT_CODE - Screens, Function Code That Triggered PAI

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

Copy and paste ABAP code example for FTR_STAV_MAINTAIN_TRANSACTION 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_bukrs  TYPE VTBFHA-BUKRS, "   
lv_exit_code  TYPE RSEUL_KEYS-CODE, "   
lv_rfha  TYPE VTBFHA-RFHA, "   
lv_display  TYPE BOOLEAN. "   

  CALL FUNCTION 'FTR_STAV_MAINTAIN_TRANSACTION'  "Status Maintenance: Call as FM with BUKR and RFHA
    EXPORTING
         BUKRS = lv_bukrs
         RFHA = lv_rfha
         DISPLAY = lv_display
    IMPORTING
         EXIT_CODE = lv_exit_code
. " FTR_STAV_MAINTAIN_TRANSACTION




ABAP code using 7.40 inline data declarations to call FM FTR_STAV_MAINTAIN_TRANSACTION

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 BUKRS FROM VTBFHA INTO @DATA(ld_bukrs).
 
"SELECT single CODE FROM RSEUL_KEYS INTO @DATA(ld_exit_code).
 
"SELECT single RFHA FROM VTBFHA INTO @DATA(ld_rfha).
 
 


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!