SAP GET_CI_NAME_REMOTE Function Module for Get Code Inspection Names from a Remote System

Search SAP Function Modules

GET_CI_NAME_REMOTE is a standard get ci name remote SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get Code Inspection Names from a Remote System 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 get ci name remote FM, simply by entering the name GET_CI_NAME_REMOTE into the relevant SAP transaction such as SE37 or SE38.

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

Function GET_CI_NAME_REMOTE 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 'GET_CI_NAME_REMOTE'"Get Code Inspection Names from a Remote System
  EXPORTING
*  IV_MAX_NUMBER_RECORDS = 200 "Natural number
*  IT_RANGE_CI_INSPECTION_NAME =  "Range Table Type for Code Inspection Name
*  IT_RANGE_CI_INSPECTION_VERSION =  "Range Table Type for Code Inspection Version
*  IT_RANGE_CI_INSPECTION_USER =  "Range Table Type for Code Inspection User
*  IT_RANGE_CI_INSP_CREATION_DATE =  "Range Table Type for Code Inspection Creation Date
*  IT_RANGE_CI_INSP_EXEC_DATE =  "Range Table Type for Code Inspection Execution Date

 IMPORTING
   EV_SYSTEM_NAME =  "Name of SAP System

TABLES
   ET_RESULT =  "Code Inspection Search Help Result

.

IMPORTING Parameters details for GET_CI_NAME_REMOTE

IV_MAX_NUMBER_RECORDS - Natural number

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

IT_RANGE_CI_INSPECTION_NAME - Range Table Type for Code Inspection Name

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

IT_RANGE_CI_INSPECTION_VERSION - Range Table Type for Code Inspection Version

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

IT_RANGE_CI_INSPECTION_USER - Range Table Type for Code Inspection User

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

IT_RANGE_CI_INSP_CREATION_DATE - Range Table Type for Code Inspection Creation Date

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

IT_RANGE_CI_INSP_EXEC_DATE - Range Table Type for Code Inspection Execution Date

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

EXPORTING Parameters details for GET_CI_NAME_REMOTE

EV_SYSTEM_NAME - Name of SAP System

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

TABLES Parameters details for GET_CI_NAME_REMOTE

ET_RESULT - Code Inspection Search Help Result

Data type: SCIS_NAME_SEARCH_RESULT
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for GET_CI_NAME_REMOTE 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.

ABAP code using 7.40 inline data declarations to call FM GET_CI_NAME_REMOTE

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