SAP SCI_GET_INSPECTION_CODE_STAT Function Module for

Search SAP Function Modules

SCI_GET_INSPECTION_CODE_STAT is a standard sci get inspection code stat 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 sci get inspection code stat FM, simply by entering the name SCI_GET_INSPECTION_CODE_STAT into the relevant SAP transaction such as SE37 or SE38.

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

Function SCI_GET_INSPECTION_CODE_STAT 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 'SCI_GET_INSPECTION_CODE_STAT'"
  EXPORTING
   P_INSPECTION_USER =  "
*  P_SOBJNAME =  "
*  P_DEVCLASS =  "
*  P_RESPONSIBL =  "
*  P_UNIQUE =  "
   P_INSPECTION_NAME =  "
*  P_MAX_LINES = 20000 "
*  P_SOTEST =  "
*  P_SOCODE =  "
*  P_SOKIND =  "
*  P_OBJTYPE =  "
*  P_OBJNAME =  "
*  P_SOBJTYPE =  "

 IMPORTING
   P_CODE_STAT =  "
   P_INFO =  "

EXCEPTIONS
   INSP_NOT_EXISTS = 1 

.

IMPORTING Parameters details for SCI_GET_INSPECTION_CODE_STAT

P_INSPECTION_USER -

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

P_SOBJNAME -

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

P_DEVCLASS -

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

P_RESPONSIBL -

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

P_UNIQUE -

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

P_INSPECTION_NAME -

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

P_MAX_LINES -

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

P_SOTEST -

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

P_SOCODE -

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

P_SOKIND -

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

P_OBJTYPE -

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

P_OBJNAME -

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

P_SOBJTYPE -

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

EXPORTING Parameters details for SCI_GET_INSPECTION_CODE_STAT

P_CODE_STAT -

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

P_INFO -

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

EXCEPTIONS details

INSP_NOT_EXISTS -

Data type:
Optional: No
Call by Reference: Yes

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

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