SAP GRPCRTA_SCRIPT_RTA_ENTRY Function Module for Search for table or view from DDIC
GRPCRTA_SCRIPT_RTA_ENTRY is a standard grpcrta script rta entry SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Search for table or view from DDIC 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 grpcrta script rta entry FM, simply by entering the name GRPCRTA_SCRIPT_RTA_ENTRY into the relevant SAP transaction such as SE37 or SE38.
Function Group: GRPCRTA_PC_UTILITY
Program Name: SAPLGRPCRTA_PC_UTILITY
Main Program: SAPLGRPCRTA_PC_UTILITY
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function GRPCRTA_SCRIPT_RTA_ENTRY 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 'GRPCRTA_SCRIPT_RTA_ENTRY'"Search for table or view from DDIC.
EXPORTING
* I_COPY_SCRIPT = "Single-character flag
* I_SEARCH_SCRIPT_ENTRY = "Single-character flag
* I_ADD_SCRIPT_ENTRY = "Single-character flag
* I_DEL_SCRIPT_ENTRY = "Single-character flag
I_CLASSNAME = "Class Name
* I_CLASSNAME_NEW = "GRPCRTA Class name
* I_SYSTEMINFO = "Object ID
* IS_CTRLDEF_RTA_ENTRY = "Control Definition
* IS_SCRIPTOB_RTA_ENTRY = "Change log : Script->Table relationship
IMPORTING
ES_CTRLDEF_RTA_ENTRY = "Control Definition
ES_SCRIPTOB_RTA_ENTRY = "Change log : Script->Table relationship
E_RETURN_CODE = "Return value, return value after ABAP statements
ES_MESSAGE = "Return parameter
IMPORTING Parameters details for GRPCRTA_SCRIPT_RTA_ENTRY
I_COPY_SCRIPT - Single-character flag
Data type: CHAR1Optional: Yes
Call by Reference: No ( called with pass by value option)
I_SEARCH_SCRIPT_ENTRY - Single-character flag
Data type: CHAR1Optional: Yes
Call by Reference: No ( called with pass by value option)
I_ADD_SCRIPT_ENTRY - Single-character flag
Data type: CHAR1Optional: Yes
Call by Reference: No ( called with pass by value option)
I_DEL_SCRIPT_ENTRY - Single-character flag
Data type: CHAR1Optional: Yes
Call by Reference: No ( called with pass by value option)
I_CLASSNAME - Class Name
Data type: GRPCRTA_CLASSNAMEOptional: No
Call by Reference: No ( called with pass by value option)
I_CLASSNAME_NEW - GRPCRTA Class name
Data type: GRPCRTA_CLASSNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_SYSTEMINFO - Object ID
Data type: GRPCRTA_API_OBJECT_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_CTRLDEF_RTA_ENTRY - Control Definition
Data type: GRPCRTA_CTRLDEFOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_SCRIPTOB_RTA_ENTRY - Change log : Script->Table relationship
Data type: GRPCRTA_SCRIPTOBOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for GRPCRTA_SCRIPT_RTA_ENTRY
ES_CTRLDEF_RTA_ENTRY - Control Definition
Data type: GRPCRTA_CTRLDEFOptional: No
Call by Reference: No ( called with pass by value option)
ES_SCRIPTOB_RTA_ENTRY - Change log : Script->Table relationship
Data type: GRPCRTA_SCRIPTOBOptional: No
Call by Reference: No ( called with pass by value option)
E_RETURN_CODE - Return value, return value after ABAP statements
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
ES_MESSAGE - Return parameter
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for GRPCRTA_SCRIPT_RTA_ENTRY 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_i_copy_script | TYPE CHAR1, " | |||
lv_es_ctrldef_rta_entry | TYPE GRPCRTA_CTRLDEF, " | |||
lv_es_scriptob_rta_entry | TYPE GRPCRTA_SCRIPTOB, " | |||
lv_i_search_script_entry | TYPE CHAR1, " | |||
lv_e_return_code | TYPE SY-SUBRC, " | |||
lv_i_add_script_entry | TYPE CHAR1, " | |||
lv_es_message | TYPE BAPIRET2, " | |||
lv_i_del_script_entry | TYPE CHAR1, " | |||
lv_i_classname | TYPE GRPCRTA_CLASSNAME, " | |||
lv_i_classname_new | TYPE GRPCRTA_CLASSNAME, " | |||
lv_i_systeminfo | TYPE GRPCRTA_API_OBJECT_ID, " | |||
lv_is_ctrldef_rta_entry | TYPE GRPCRTA_CTRLDEF, " | |||
lv_is_scriptob_rta_entry | TYPE GRPCRTA_SCRIPTOB. " |
  CALL FUNCTION 'GRPCRTA_SCRIPT_RTA_ENTRY' "Search for table or view from DDIC |
EXPORTING | ||
I_COPY_SCRIPT | = lv_i_copy_script | |
I_SEARCH_SCRIPT_ENTRY | = lv_i_search_script_entry | |
I_ADD_SCRIPT_ENTRY | = lv_i_add_script_entry | |
I_DEL_SCRIPT_ENTRY | = lv_i_del_script_entry | |
I_CLASSNAME | = lv_i_classname | |
I_CLASSNAME_NEW | = lv_i_classname_new | |
I_SYSTEMINFO | = lv_i_systeminfo | |
IS_CTRLDEF_RTA_ENTRY | = lv_is_ctrldef_rta_entry | |
IS_SCRIPTOB_RTA_ENTRY | = lv_is_scriptob_rta_entry | |
IMPORTING | ||
ES_CTRLDEF_RTA_ENTRY | = lv_es_ctrldef_rta_entry | |
ES_SCRIPTOB_RTA_ENTRY | = lv_es_scriptob_rta_entry | |
E_RETURN_CODE | = lv_e_return_code | |
ES_MESSAGE | = lv_es_message | |
. " GRPCRTA_SCRIPT_RTA_ENTRY |
ABAP code using 7.40 inline data declarations to call FM GRPCRTA_SCRIPT_RTA_ENTRY
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 SUBRC FROM SY INTO @DATA(ld_e_return_code). | ||||
Search for further information about these or an SAP related objects