SAP CETA_T006_READ Function Module for Read units table









CETA_T006_READ is a standard ceta t006 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 Read units table 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 ceta t006 read FM, simply by entering the name CETA_T006_READ into the relevant SAP transaction such as SE37 or SE38.

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



Function CETA_T006_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 'CETA_T006_READ'"Read units table
EXPORTING
MSEHI = "

IMPORTING
T006_EXP = "Line from table

EXCEPTIONS
NO_ENTRY = 1
.



IMPORTING Parameters details for CETA_T006_READ

MSEHI -

Data type: T006-MSEHI
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for CETA_T006_READ

T006_EXP - Line from table

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

EXCEPTIONS details

NO_ENTRY - No entry in table

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

Copy and paste ABAP code example for CETA_T006_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_msehi  TYPE T006-MSEHI, "   
lv_no_entry  TYPE T006, "   
lv_t006_exp  TYPE T006. "   

  CALL FUNCTION 'CETA_T006_READ'  "Read units table
    EXPORTING
         MSEHI = lv_msehi
    IMPORTING
         T006_EXP = lv_t006_exp
    EXCEPTIONS
        NO_ENTRY = 1
. " CETA_T006_READ




ABAP code using 7.40 inline data declarations to call FM CETA_T006_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 MSEHI FROM T006 INTO @DATA(ld_msehi).
 
 
 


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!