SAP TZS1_CHECK_CUSTOMIZING Function Module for Check if Customizing is active for Application
TZS1_CHECK_CUSTOMIZING is a standard tzs1 check customizing SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check if Customizing is active for Application 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 tzs1 check customizing FM, simply by entering the name TZS1_CHECK_CUSTOMIZING into the relevant SAP transaction such as SE37 or SE38.
Function Group: TZS1
Program Name: SAPLTZS1
Main Program: SAPLTZS1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TZS1_CHECK_CUSTOMIZING 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 'TZS1_CHECK_CUSTOMIZING'"Check if Customizing is active for Application.
EXPORTING
IS_APPLICATION = "Application Range for Time Zone Activation
IMPORTING
ES_ACTIVATED = "Activation of Time Zone Function
EXCEPTIONS
APPLICATION_NOT_VALID = 1
IMPORTING Parameters details for TZS1_CHECK_CUSTOMIZING
IS_APPLICATION - Application Range for Time Zone Activation
Data type: TZ_D_APPLOptional: No
Call by Reference: Yes
EXPORTING Parameters details for TZS1_CHECK_CUSTOMIZING
ES_ACTIVATED - Activation of Time Zone Function
Data type: TZ_D_ACTIVEOptional: No
Call by Reference: Yes
EXCEPTIONS details
APPLICATION_NOT_VALID - Application not valid
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for TZS1_CHECK_CUSTOMIZING 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_es_activated | TYPE TZ_D_ACTIVE, " | |||
| lv_is_application | TYPE TZ_D_APPL, " | |||
| lv_application_not_valid | TYPE TZ_D_APPL. " |
|   CALL FUNCTION 'TZS1_CHECK_CUSTOMIZING' "Check if Customizing is active for Application |
| EXPORTING | ||
| IS_APPLICATION | = lv_is_application | |
| IMPORTING | ||
| ES_ACTIVATED | = lv_es_activated | |
| EXCEPTIONS | ||
| APPLICATION_NOT_VALID = 1 | ||
| . " TZS1_CHECK_CUSTOMIZING | ||
ABAP code using 7.40 inline data declarations to call FM TZS1_CHECK_CUSTOMIZING
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