SAP SCPR_CTRL_IF_KEY_CONFLICTS Function Module for
SCPR_CTRL_IF_KEY_CONFLICTS is a standard scpr ctrl if key conflicts 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 ctrl if key conflicts FM, simply by entering the name SCPR_CTRL_IF_KEY_CONFLICTS into the relevant SAP transaction such as SE37 or SE38.
Function Group: SCPRCTRL
Program Name: SAPLSCPRCTRL
Main Program: SAPLSCPRCTRL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SCPR_CTRL_IF_KEY_CONFLICTS 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_CTRL_IF_KEY_CONFLICTS'".
EXPORTING
BCSET_ID = "
BCSET_TYPE = "
* CATEGORY = ' ' "
* WITH_DIALOG = 'X' "
IMPORTING
USER_FUNCTION = "
KEY_CONFLICT = "
TABLES
VALUES = "
* VALUESL = "
FIELDDESCRS = "
IMPORTING Parameters details for SCPR_CTRL_IF_KEY_CONFLICTS
BCSET_ID -
Data type: SCPR_IDOptional: No
Call by Reference: Yes
BCSET_TYPE -
Data type: SCPR_TYPEOptional: No
Call by Reference: Yes
CATEGORY -
Data type: SCPR_CTGRYDefault: SPACE
Optional: Yes
Call by Reference: Yes
WITH_DIALOG -
Data type: CDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SCPR_CTRL_IF_KEY_CONFLICTS
USER_FUNCTION -
Data type: SCPR_TXT20Optional: No
Call by Reference: Yes
KEY_CONFLICT -
Data type: COptional: No
Call by Reference: Yes
TABLES Parameters details for SCPR_CTRL_IF_KEY_CONFLICTS
VALUES -
Data type: SCPRVALSOptional: No
Call by Reference: Yes
VALUESL -
Data type: SCPRVALLOptional: Yes
Call by Reference: Yes
FIELDDESCRS -
Data type: SCPR_RECORDSOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for SCPR_CTRL_IF_KEY_CONFLICTS 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: | ||||
| lt_values | TYPE STANDARD TABLE OF SCPRVALS, " | |||
| lv_bcset_id | TYPE SCPR_ID, " | |||
| lv_user_function | TYPE SCPR_TXT20, " | |||
| lt_valuesl | TYPE STANDARD TABLE OF SCPRVALL, " | |||
| lv_bcset_type | TYPE SCPR_TYPE, " | |||
| lv_key_conflict | TYPE C, " | |||
| lv_category | TYPE SCPR_CTGRY, " SPACE | |||
| lt_fielddescrs | TYPE STANDARD TABLE OF SCPR_RECORDS, " | |||
| lv_with_dialog | TYPE C. " 'X' |
|   CALL FUNCTION 'SCPR_CTRL_IF_KEY_CONFLICTS' " |
| EXPORTING | ||
| BCSET_ID | = lv_bcset_id | |
| BCSET_TYPE | = lv_bcset_type | |
| CATEGORY | = lv_category | |
| WITH_DIALOG | = lv_with_dialog | |
| IMPORTING | ||
| USER_FUNCTION | = lv_user_function | |
| KEY_CONFLICT | = lv_key_conflict | |
| TABLES | ||
| VALUES | = lt_values | |
| VALUESL | = lt_valuesl | |
| FIELDDESCRS | = lt_fielddescrs | |
| . " SCPR_CTRL_IF_KEY_CONFLICTS | ||
ABAP code using 7.40 inline data declarations to call FM SCPR_CTRL_IF_KEY_CONFLICTS
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_category) | = ' '. | |||
| DATA(ld_with_dialog) | = 'X'. | |||
Search for further information about these or an SAP related objects