SAP CACS_FIELD_EXIST_TEST Function Module for NOTRANSL: (intern) Prüft, ob Feld in Struktur vorhanden ist









CACS_FIELD_EXIST_TEST is a standard cacs field exist test 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: (intern) Prüft, ob Feld in Struktur vorhanden ist 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 field exist test FM, simply by entering the name CACS_FIELD_EXIST_TEST into the relevant SAP transaction such as SE37 or SE38.

Function Group: CACS_DESIGN_LOGIC
Program Name: SAPLCACS_DESIGN_LOGIC
Main Program: SAPLCACS_DESIGN_LOGIC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function CACS_FIELD_EXIST_TEST 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_FIELD_EXIST_TEST'"NOTRANSL: (intern) Prüft, ob Feld in Struktur vorhanden ist
  EXPORTING
   I_OBJECT =  "
   I_FIELDNAME =  "Field Name
*  I_ROLLNAME =  "Data element (semantic domain)
*  I_ORIGIN =  "Origin of a Field in a Generated Object

 IMPORTING
   S_FIELD =  "
   E_KEYFLAG =  "Identifies a key field of a table
   E_ROLLNAME =  "Data element (semantic domain)
   E_ORIGIN =  "Origin of a Field in a Generated Object

EXCEPTIONS
   NOT_FOUND = 1    WRONG_ROLLNAME = 2    WRONG_ORIGIN = 3
.



IMPORTING Parameters details for CACS_FIELD_EXIST_TEST

I_OBJECT -

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

I_FIELDNAME - Field Name

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

I_ROLLNAME - Data element (semantic domain)

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

I_ORIGIN - Origin of a Field in a Generated Object

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

EXPORTING Parameters details for CACS_FIELD_EXIST_TEST

S_FIELD -

Data type: SCACS_OBJFIELDINFO
Optional: No
Call by Reference: Yes

E_KEYFLAG - Identifies a key field of a table

Data type: KEYFLAG
Optional: No
Call by Reference: Yes

E_ROLLNAME - Data element (semantic domain)

Data type: ROLLNAME
Optional: No
Call by Reference: Yes

E_ORIGIN - Origin of a Field in a Generated Object

Data type: CACSORIGIN
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NOT_FOUND - Field does not exist

Data type:
Optional: No
Call by Reference: Yes

WRONG_ROLLNAME -

Data type:
Optional: No
Call by Reference: Yes

WRONG_ORIGIN -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CACS_FIELD_EXIST_TEST 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_s_field  TYPE SCACS_OBJFIELDINFO, "   
lv_i_object  TYPE CACSGENOBJ30, "   
lv_not_found  TYPE CACSGENOBJ30, "   
lv_e_keyflag  TYPE KEYFLAG, "   
lv_i_fieldname  TYPE FIELDNAME, "   
lv_wrong_rollname  TYPE FIELDNAME, "   
lv_e_rollname  TYPE ROLLNAME, "   
lv_i_rollname  TYPE ROLLNAME, "   
lv_wrong_origin  TYPE ROLLNAME, "   
lv_e_origin  TYPE CACSORIGIN, "   
lv_i_origin  TYPE CACSORIGIN. "   

  CALL FUNCTION 'CACS_FIELD_EXIST_TEST'  "NOTRANSL: (intern) Prüft, ob Feld in Struktur vorhanden ist
    EXPORTING
         I_OBJECT = lv_i_object
         I_FIELDNAME = lv_i_fieldname
         I_ROLLNAME = lv_i_rollname
         I_ORIGIN = lv_i_origin
    IMPORTING
         S_FIELD = lv_s_field
         E_KEYFLAG = lv_e_keyflag
         E_ROLLNAME = lv_e_rollname
         E_ORIGIN = lv_e_origin
    EXCEPTIONS
        NOT_FOUND = 1
        WRONG_ROLLNAME = 2
        WRONG_ORIGIN = 3
. " CACS_FIELD_EXIST_TEST




ABAP code using 7.40 inline data declarations to call FM CACS_FIELD_EXIST_TEST

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



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!