SAP C1I1_TCG53_READ Function Module for NOTRANSL: EHS: Lesen Knoten eines Eigenschaftsbaumes
C1I1_TCG53_READ is a standard c1i1 tcg53 read 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: EHS: Lesen Knoten eines Eigenschaftsbaumes 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 c1i1 tcg53 read FM, simply by entering the name C1I1_TCG53_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: C1I1
Program Name: SAPLC1I1
Main Program: SAPLC1I1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function C1I1_TCG53_READ 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 'C1I1_TCG53_READ'"NOTRANSL: EHS: Lesen Knoten eines Eigenschaftsbaumes.
TABLES
X_TCG53_TAB = "EHS: Property Tree - Value Assignment Type Assignment
E_ERROR_TAB = "
TABLES Parameters details for C1I1_TCG53_READ
X_TCG53_TAB - EHS: Property Tree - Value Assignment Type Assignment
Data type: TCG53Optional: No
Call by Reference: No ( called with pass by value option)
E_ERROR_TAB -
Data type: ESPPT_ERROR_TAB_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for C1I1_TCG53_READ 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: | ||||
| lt_x_tcg53_tab | TYPE STANDARD TABLE OF TCG53, " | |||
| lt_e_error_tab | TYPE STANDARD TABLE OF ESPPT_ERROR_TAB_TYPE. " |
|   CALL FUNCTION 'C1I1_TCG53_READ' "NOTRANSL: EHS: Lesen Knoten eines Eigenschaftsbaumes |
| TABLES | ||
| X_TCG53_TAB | = lt_x_tcg53_tab | |
| E_ERROR_TAB | = lt_e_error_tab | |
| . " C1I1_TCG53_READ | ||
ABAP code using 7.40 inline data declarations to call FM C1I1_TCG53_READ
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