SAP GRAPH_CUA_SEND Function Module for









GRAPH_CUA_SEND is a standard graph cua send SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 graph cua send FM, simply by entering the name GRAPH_CUA_SEND into the relevant SAP transaction such as SE37 or SE38.

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



Function GRAPH_CUA_SEND 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 'GRAPH_CUA_SEND'"
EXPORTING
* NO_EXTH = ' ' "
* TEST_IT = ' ' "
* EXT_HELP = "

IMPORTING
EMPTY = "
TEST_RETURN = "

EXCEPTIONS
INV_CUA_INFO = 1
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLGRAP_001 Customer-specific authorization check and trace for download
EXIT_SAPLGRAP_002 Customer-specific check of the upload data (for example, for viruses)

IMPORTING Parameters details for GRAPH_CUA_SEND

NO_EXTH -

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

TEST_IT -

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

EXT_HELP -

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

EXPORTING Parameters details for GRAPH_CUA_SEND

EMPTY -

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

TEST_RETURN -

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

EXCEPTIONS details

INV_CUA_INFO - Invalid CUA information

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

Copy and paste ABAP code example for GRAPH_CUA_SEND 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_empty  TYPE STRING, "   
lv_no_exth  TYPE STRING, "   SPACE
lv_inv_cua_info  TYPE STRING, "   
lv_test_it  TYPE STRING, "   SPACE
lv_test_return  TYPE STRING, "   
lv_ext_help  TYPE C. "   

  CALL FUNCTION 'GRAPH_CUA_SEND'  "
    EXPORTING
         NO_EXTH = lv_no_exth
         TEST_IT = lv_test_it
         EXT_HELP = lv_ext_help
    IMPORTING
         EMPTY = lv_empty
         TEST_RETURN = lv_test_return
    EXCEPTIONS
        INV_CUA_INFO = 1
. " GRAPH_CUA_SEND




ABAP code using 7.40 inline data declarations to call FM GRAPH_CUA_SEND

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.

 
DATA(ld_no_exth) = ' '.
 
 
DATA(ld_test_it) = ' '.
 
 
 


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!