SAP CUPA_CHECK Function Module for
CUPA_CHECK is a standard cupa check 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 cupa check FM, simply by entering the name CUPA_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: CUPA
Program Name: SAPLCUPA
Main Program:
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CUPA_CHECK 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 'CUPA_CHECK'".
EXPORTING
* EXPRESSION_ID = ' ' "Relationship ID (e.g. constraint name)
EXPRESSION_TYPE = "Type of relationship
* GRAMMAR = 'SAPLCUPA' "Name of an I report containing grammar
* MSGTYPE = 'S' "Type of the message 'E', 'I', 'W', 'S'
IMPORTING
COL = "Positioning cursor in case of error (column)
RESULT = "Result of check ('T' = ok, otherwise error)
EXPR = "Index of the parser result in PARSI_TREE
LINE = "Positioning cursor in case of error (line)
MSG_ARG1 = "Further argument for message
MSG_ARG2 = "Further argument for message
MSG_ARG3 = "Further argument for message
MSG_ARG4 = "Further argument for message
MSG_ID = "Message class
MSG_NUMBER = "Message number
TABLES
PARSD_SOURCE = "Editor buffer
EXCEPTIONS
INTERNAL_ERROR = 1
IMPORTING Parameters details for CUPA_CHECK
EXPRESSION_ID - Relationship ID (e.g. constraint name)
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPRESSION_TYPE - Type of relationship
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
GRAMMAR - Name of an I report containing grammar
Data type:Default: 'SAPLCUPA'
Optional: Yes
Call by Reference: No ( called with pass by value option)
MSGTYPE - Type of the message 'E', 'I', 'W', 'S'
Data type:Default: 'S'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CUPA_CHECK
COL - Positioning cursor in case of error (column)
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
RESULT - Result of check ('T' = ok, otherwise error)
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXPR - Index of the parser result in PARSI_TREE
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
LINE - Positioning cursor in case of error (line)
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MSG_ARG1 - Further argument for message
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MSG_ARG2 - Further argument for message
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MSG_ARG3 - Further argument for message
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MSG_ARG4 - Further argument for message
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MSG_ID - Message class
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MSG_NUMBER - Message number
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CUPA_CHECK
PARSD_SOURCE - Editor buffer
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INTERNAL_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CUPA_CHECK 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_col | TYPE STRING, " | |||
| lt_parsd_source | TYPE STANDARD TABLE OF STRING, " | |||
| lv_expression_id | TYPE STRING, " SPACE | |||
| lv_internal_error | TYPE STRING, " | |||
| lv_result | TYPE STRING, " | |||
| lv_expr | TYPE STRING, " | |||
| lv_expression_type | TYPE STRING, " | |||
| lv_line | TYPE STRING, " | |||
| lv_grammar | TYPE STRING, " 'SAPLCUPA' | |||
| lv_msgtype | TYPE STRING, " 'S' | |||
| lv_msg_arg1 | TYPE STRING, " | |||
| lv_msg_arg2 | TYPE STRING, " | |||
| lv_msg_arg3 | TYPE STRING, " | |||
| lv_msg_arg4 | TYPE STRING, " | |||
| lv_msg_id | TYPE STRING, " | |||
| lv_msg_number | TYPE STRING. " |
|   CALL FUNCTION 'CUPA_CHECK' " |
| EXPORTING | ||
| EXPRESSION_ID | = lv_expression_id | |
| EXPRESSION_TYPE | = lv_expression_type | |
| GRAMMAR | = lv_grammar | |
| MSGTYPE | = lv_msgtype | |
| IMPORTING | ||
| COL | = lv_col | |
| RESULT | = lv_result | |
| EXPR | = lv_expr | |
| LINE | = lv_line | |
| MSG_ARG1 | = lv_msg_arg1 | |
| MSG_ARG2 | = lv_msg_arg2 | |
| MSG_ARG3 | = lv_msg_arg3 | |
| MSG_ARG4 | = lv_msg_arg4 | |
| MSG_ID | = lv_msg_id | |
| MSG_NUMBER | = lv_msg_number | |
| TABLES | ||
| PARSD_SOURCE | = lt_parsd_source | |
| EXCEPTIONS | ||
| INTERNAL_ERROR = 1 | ||
| . " CUPA_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM CUPA_CHECK
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_expression_id) | = ' '. | |||
| DATA(ld_grammar) | = 'SAPLCUPA'. | |||
| DATA(ld_msgtype) | = 'S'. | |||
Search for further information about these or an SAP related objects