SAP TAXI_ACTIVATE_TAB Function Module for puts Fcode tab on top
TAXI_ACTIVATE_TAB is a standard taxi activate tab SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for puts Fcode tab on top 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 taxi activate tab FM, simply by entering the name TAXI_ACTIVATE_TAB into the relevant SAP transaction such as SE37 or SE38.
Function Group: TAXI
Program Name: SAPLTAXI
Main Program:
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TAXI_ACTIVATE_TAB 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 'TAXI_ACTIVATE_TAB'"puts Fcode tab on top.
EXPORTING
FCODE = "
CHANGING
TABSTRIP = "
EXCEPTIONS
NO_TAB_FCODE = 1
IMPORTING Parameters details for TAXI_ACTIVATE_TAB
FCODE -
Data type: TAXI_PARAMS-FCODEOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for TAXI_ACTIVATE_TAB
TABSTRIP -
Data type: TAXI_TABSTRIPOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_TAB_FCODE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TAXI_ACTIVATE_TAB 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_fcode | TYPE TAXI_PARAMS-FCODE, " | |||
| lv_tabstrip | TYPE TAXI_TABSTRIP, " | |||
| lv_no_tab_fcode | TYPE TAXI_TABSTRIP. " |
|   CALL FUNCTION 'TAXI_ACTIVATE_TAB' "puts Fcode tab on top |
| EXPORTING | ||
| FCODE | = lv_fcode | |
| CHANGING | ||
| TABSTRIP | = lv_tabstrip | |
| EXCEPTIONS | ||
| NO_TAB_FCODE = 1 | ||
| . " TAXI_ACTIVATE_TAB | ||
ABAP code using 7.40 inline data declarations to call FM TAXI_ACTIVATE_TAB
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 FCODE FROM TAXI_PARAMS INTO @DATA(ld_fcode). | ||||
Search for further information about these or an SAP related objects