SAP CACS_CHECK_TCACSF_VALUES Function Module for NOTRANSL: Überprüft TCACSF Werte
CACS_CHECK_TCACSF_VALUES is a standard cacs check tcacsf values SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Überprüft TCACSF Werte 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 cacs check tcacsf values FM, simply by entering the name CACS_CHECK_TCACSF_VALUES into the relevant SAP transaction such as SE37 or SE38.
Function Group: CACSIS_FC
Program Name: SAPLCACSIS_FC
Main Program: SAPLCACSIS_FC
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CACS_CHECK_TCACSF_VALUES 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 'CACS_CHECK_TCACSF_VALUES'"NOTRANSL: Überprüft TCACSF Werte.
EXPORTING
I_FNAM = "Field Name
CHANGING
C_ERROR = "Generic Type
IMPORTING Parameters details for CACS_CHECK_TCACSF_VALUES
I_FNAM - Field Name
Data type: TCACSF-FIENMOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for CACS_CHECK_TCACSF_VALUES
C_ERROR - Generic Type
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CACS_CHECK_TCACSF_VALUES 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_i_fnam | TYPE TCACSF-FIENM, " | |||
| lv_c_error | TYPE C. " |
|   CALL FUNCTION 'CACS_CHECK_TCACSF_VALUES' "NOTRANSL: Überprüft TCACSF Werte |
| EXPORTING | ||
| I_FNAM | = lv_i_fnam | |
| CHANGING | ||
| C_ERROR | = lv_c_error | |
| . " CACS_CHECK_TCACSF_VALUES | ||
ABAP code using 7.40 inline data declarations to call FM CACS_CHECK_TCACSF_VALUES
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 FIENM FROM TCACSF INTO @DATA(ld_i_fnam). | ||||
Search for further information about these or an SAP related objects