SAP SCPR_CPROF_DB_OBJ_UNCOMPLETE Function Module for
SCPR_CPROF_DB_OBJ_UNCOMPLETE is a standard scpr cprof db obj uncomplete 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 scpr cprof db obj uncomplete FM, simply by entering the name SCPR_CPROF_DB_OBJ_UNCOMPLETE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SCPRCP
Program Name: SAPLSCPRCP
Main Program: SAPLSCPRCP
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SCPR_CPROF_DB_OBJ_UNCOMPLETE 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 'SCPR_CPROF_DB_OBJ_UNCOMPLETE'".
EXPORTING
OBJECTNAME = "Customizing Obj
OBJECTTYPE = "Object Type
TABNAME = "
IMPORTING Parameters details for SCPR_CPROF_DB_OBJ_UNCOMPLETE
OBJECTNAME - Customizing Obj
Data type: SCPRCOBJ-OBJECTNAMEOptional: No
Call by Reference: No ( called with pass by value option)
OBJECTTYPE - Object Type
Data type: SCPRCOBJ-OBJECTTYPEOptional: No
Call by Reference: No ( called with pass by value option)
TABNAME -
Data type: SCPRCOBJ-TABLENAMEOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SCPR_CPROF_DB_OBJ_UNCOMPLETE 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_objectname | TYPE SCPRCOBJ-OBJECTNAME, " | |||
| lv_objecttype | TYPE SCPRCOBJ-OBJECTTYPE, " | |||
| lv_tabname | TYPE SCPRCOBJ-TABLENAME. " |
|   CALL FUNCTION 'SCPR_CPROF_DB_OBJ_UNCOMPLETE' " |
| EXPORTING | ||
| OBJECTNAME | = lv_objectname | |
| OBJECTTYPE | = lv_objecttype | |
| TABNAME | = lv_tabname | |
| . " SCPR_CPROF_DB_OBJ_UNCOMPLETE | ||
ABAP code using 7.40 inline data declarations to call FM SCPR_CPROF_DB_OBJ_UNCOMPLETE
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 OBJECTNAME FROM SCPRCOBJ INTO @DATA(ld_objectname). | ||||
| "SELECT single OBJECTTYPE FROM SCPRCOBJ INTO @DATA(ld_objecttype). | ||||
| "SELECT single TABLENAME FROM SCPRCOBJ INTO @DATA(ld_tabname). | ||||
Search for further information about these or an SAP related objects