SAP CORU_TS_FETCH_DATA Function Module for NOTRANSL: Return data to touchscreen application









CORU_TS_FETCH_DATA is a standard coru ts fetch data 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: Return data to touchscreen application 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 coru ts fetch data FM, simply by entering the name CORU_TS_FETCH_DATA into the relevant SAP transaction such as SE37 or SE38.

Function Group: CORU_PROC
Program Name: SAPLCORU_PROC
Main Program:
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function CORU_TS_FETCH_DATA 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 'CORU_TS_FETCH_DATA'"NOTRANSL: Return data to touchscreen application
  EXPORTING
   COMMAND =  "Confirmation Using Touch Screen: Commands

 IMPORTING
   EXPORT_DATA_ATTRIBUTES =  "Character Field with Length 5

TABLES
*  GUID_HIERARCHY =  "Confirmation Using Touch Screen: GUID Hierarchy
*  LIST_STRUCTURE =  "Confirmation Using Touch Screen: List Structure
*  PROPERTY_STRUC =  "Property Structure
*  LIST_VALUES =  "Confirmation Using Touch Screen: List Values
*  PROPERTY_VALUES =  "Confirmation Using Touch Screen: Property Values
*  AVAILABLE_COMMANDS =  "Confirmation Using Touch Screen: Commands
*  ERRORS =  "Confirmation Using Touch Screen: Error Messages

EXCEPTIONS
   INVALID_TCODE = 1    INVALID_COMMAND = 2
.



IMPORTING Parameters details for CORU_TS_FETCH_DATA

COMMAND - Confirmation Using Touch Screen: Commands

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

EXPORTING Parameters details for CORU_TS_FETCH_DATA

EXPORT_DATA_ATTRIBUTES - Character Field with Length 5

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

TABLES Parameters details for CORU_TS_FETCH_DATA

GUID_HIERARCHY - Confirmation Using Touch Screen: GUID Hierarchy

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

LIST_STRUCTURE - Confirmation Using Touch Screen: List Structure

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

PROPERTY_STRUC - Property Structure

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

LIST_VALUES - Confirmation Using Touch Screen: List Values

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

PROPERTY_VALUES - Confirmation Using Touch Screen: Property Values

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

AVAILABLE_COMMANDS - Confirmation Using Touch Screen: Commands

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

ERRORS - Confirmation Using Touch Screen: Error Messages

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

EXCEPTIONS details

INVALID_TCODE - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

INVALID_COMMAND -

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

Copy and paste ABAP code example for CORU_TS_FETCH_DATA 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_command  TYPE CORU_TSCOM, "   
lv_invalid_tcode  TYPE CORU_TSCOM, "   
lt_guid_hierarchy  TYPE STANDARD TABLE OF CORU_TSGUH, "   
lv_export_data_attributes  TYPE CHAR05, "   
lt_list_structure  TYPE STANDARD TABLE OF CORU_TSLS, "   
lv_invalid_command  TYPE CORU_TSLS, "   
lt_property_struc  TYPE STANDARD TABLE OF CORU_TSPS, "   
lt_list_values  TYPE STANDARD TABLE OF CORU_TSLV, "   
lt_property_values  TYPE STANDARD TABLE OF CORU_TSPV, "   
lt_available_commands  TYPE STANDARD TABLE OF CORU_TSCOM, "   
lt_errors  TYPE STANDARD TABLE OF CORU_TSEM. "   

  CALL FUNCTION 'CORU_TS_FETCH_DATA'  "NOTRANSL: Return data to touchscreen application
    EXPORTING
         COMMAND = lv_command
    IMPORTING
         EXPORT_DATA_ATTRIBUTES = lv_export_data_attributes
    TABLES
         GUID_HIERARCHY = lt_guid_hierarchy
         LIST_STRUCTURE = lt_list_structure
         PROPERTY_STRUC = lt_property_struc
         LIST_VALUES = lt_list_values
         PROPERTY_VALUES = lt_property_values
         AVAILABLE_COMMANDS = lt_available_commands
         ERRORS = lt_errors
    EXCEPTIONS
        INVALID_TCODE = 1
        INVALID_COMMAND = 2
. " CORU_TS_FETCH_DATA




ABAP code using 7.40 inline data declarations to call FM CORU_TS_FETCH_DATA

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!