SAP CO_TA_TCN41_READ Function Module for NOTRANSL: Lesen Tabelle TCN41
CO_TA_TCN41_READ is a standard co ta tcn41 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: Lesen Tabelle TCN41 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 co ta tcn41 read FM, simply by entering the name CO_TA_TCN41_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: COTA
Program Name: SAPLCOTA
Main Program: SAPLCOTA
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CO_TA_TCN41_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 'CO_TA_TCN41_READ'"NOTRANSL: Lesen Tabelle TCN41.
EXPORTING
PLNAW = "
PROFIDNETZ = "
IMPORTING
TCN41_EXP = "
EXCEPTIONS
NOT_FOUND = 1
IMPORTING Parameters details for CO_TA_TCN41_READ
PLNAW -
Data type: TCN41-PLNAWOptional: No
Call by Reference: No ( called with pass by value option)
PROFIDNETZ -
Data type: TCN41-PROFIDNETZOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CO_TA_TCN41_READ
TCN41_EXP -
Data type: TCN41Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND - No data found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CO_TA_TCN41_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: | ||||
| lv_plnaw | TYPE TCN41-PLNAW, " | |||
| lv_not_found | TYPE TCN41, " | |||
| lv_tcn41_exp | TYPE TCN41, " | |||
| lv_profidnetz | TYPE TCN41-PROFIDNETZ. " |
|   CALL FUNCTION 'CO_TA_TCN41_READ' "NOTRANSL: Lesen Tabelle TCN41 |
| EXPORTING | ||
| PLNAW | = lv_plnaw | |
| PROFIDNETZ | = lv_profidnetz | |
| IMPORTING | ||
| TCN41_EXP | = lv_tcn41_exp | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| . " CO_TA_TCN41_READ | ||
ABAP code using 7.40 inline data declarations to call FM CO_TA_TCN41_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.| "SELECT single PLNAW FROM TCN41 INTO @DATA(ld_plnaw). | ||||
| "SELECT single PROFIDNETZ FROM TCN41 INTO @DATA(ld_profidnetz). | ||||
Search for further information about these or an SAP related objects