SAP CAT_IS_ACTIVE Function Module for Query whether CATT active and in which mode
CAT_IS_ACTIVE is a standard cat is active SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Query whether CATT active and in which mode 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 cat is active FM, simply by entering the name CAT_IS_ACTIVE into the relevant SAP transaction such as SE37 or SE38.
Function Group: STTM
Program Name: SAPLSTTM
Main Program: SAPLSTTM
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function CAT_IS_ACTIVE 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 'CAT_IS_ACTIVE'"Query whether CATT active and in which mode.
IMPORTING
ACTIVE = "'X' --> CATT is active
RECORDING = "'X' --> Recording Mode
PLAYBACK = "'X' --> Playback Mode
EXPORTING Parameters details for CAT_IS_ACTIVE
ACTIVE - 'X' --> CATT is active
Data type: CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
RECORDING - 'X' --> Recording Mode
Data type: CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
PLAYBACK - 'X' --> Playback Mode
Data type: CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CAT_IS_ACTIVE 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_active | TYPE CHAR1, " | |||
| lv_recording | TYPE CHAR1, " | |||
| lv_playback | TYPE CHAR1. " |
|   CALL FUNCTION 'CAT_IS_ACTIVE' "Query whether CATT active and in which mode |
| IMPORTING | ||
| ACTIVE | = lv_active | |
| RECORDING | = lv_recording | |
| PLAYBACK | = lv_playback | |
| . " CAT_IS_ACTIVE | ||
ABAP code using 7.40 inline data declarations to call FM CAT_IS_ACTIVE
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.Search for further information about these or an SAP related objects