SAP FMCA_COREL_CHANGE Function Module for Change Contract Object relationship
FMCA_COREL_CHANGE is a standard fmca corel change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change Contract Object relationship 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 fmca corel change FM, simply by entering the name FMCA_COREL_CHANGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMCA_COREL_MAINTAIN
Program Name: SAPLFMCA_COREL_MAINTAIN
Main Program: SAPLFMCA_COREL_MAINTAIN
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FMCA_COREL_CHANGE 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 'FMCA_COREL_CHANGE'"Change Contract Object relationship.
EXPORTING
IS_FMCA_COREL = "Data Table for Relationship
* IV_VALID_FROM_NEW = "Valid From Date
* IV_VALID_TO_NEW = "Valid To Date
* IV_COMMIT_X = ' ' "Checkbox
IMPORTING
ET_FMCA_COREL_CONFLICTS = "Table Type for Master Data Relationship Memory
ET_FMCA_COREL_FINAL = "Table Type for Master Data Relationship Memory
ET_MESSAGE = "FI-CA: Standard Table for Structure BAPIRET2
EV_ERROR_X = "Checkbox
IMPORTING Parameters details for FMCA_COREL_CHANGE
IS_FMCA_COREL - Data Table for Relationship
Data type: FMCA_CORELOptional: No
Call by Reference: Yes
IV_VALID_FROM_NEW - Valid From Date
Data type: DATE_FROMOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_VALID_TO_NEW - Valid To Date
Data type: DATE_TOOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_COMMIT_X - Checkbox
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FMCA_COREL_CHANGE
ET_FMCA_COREL_CONFLICTS - Table Type for Master Data Relationship Memory
Data type: FMCA_COREL_MEMORY_TABOptional: No
Call by Reference: Yes
ET_FMCA_COREL_FINAL - Table Type for Master Data Relationship Memory
Data type: FMCA_COREL_MEMORY_TABOptional: No
Call by Reference: Yes
ET_MESSAGE - FI-CA: Standard Table for Structure BAPIRET2
Data type: BAPIRET2_TAB_KKOptional: No
Call by Reference: Yes
EV_ERROR_X - Checkbox
Data type: XFELDOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FMCA_COREL_CHANGE 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_is_fmca_corel | TYPE FMCA_COREL, " | |||
| lv_et_fmca_corel_conflicts | TYPE FMCA_COREL_MEMORY_TAB, " | |||
| lv_iv_valid_from_new | TYPE DATE_FROM, " | |||
| lv_et_fmca_corel_final | TYPE FMCA_COREL_MEMORY_TAB, " | |||
| lv_et_message | TYPE BAPIRET2_TAB_KK, " | |||
| lv_iv_valid_to_new | TYPE DATE_TO, " | |||
| lv_ev_error_x | TYPE XFELD, " | |||
| lv_iv_commit_x | TYPE XFELD. " SPACE |
|   CALL FUNCTION 'FMCA_COREL_CHANGE' "Change Contract Object relationship |
| EXPORTING | ||
| IS_FMCA_COREL | = lv_is_fmca_corel | |
| IV_VALID_FROM_NEW | = lv_iv_valid_from_new | |
| IV_VALID_TO_NEW | = lv_iv_valid_to_new | |
| IV_COMMIT_X | = lv_iv_commit_x | |
| IMPORTING | ||
| ET_FMCA_COREL_CONFLICTS | = lv_et_fmca_corel_conflicts | |
| ET_FMCA_COREL_FINAL | = lv_et_fmca_corel_final | |
| ET_MESSAGE | = lv_et_message | |
| EV_ERROR_X | = lv_ev_error_x | |
| . " FMCA_COREL_CHANGE | ||
ABAP code using 7.40 inline data declarations to call FM FMCA_COREL_CHANGE
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_iv_commit_x) | = ' '. | |||
Search for further information about these or an SAP related objects