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

Function FCC_TAB_CHANGES 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 'FCC_TAB_CHANGES'"Changes tab.
EXPORTING
* IR_ITEM = "Node Element
* IX_FORCED_UPDATE = ABAP_FALSE "
* IR_NODE = "Node Element
IMPORTING Parameters details for FCC_TAB_CHANGES
IR_ITEM - Node Element
Data type: CL_FCC_CITEMXOptional: Yes
Call by Reference: Yes
IX_FORCED_UPDATE -
Data type: ABAP_BOOLDefault: ABAP_FALSE
Optional: Yes
Call by Reference: Yes
IR_NODE - Node Element
Data type: CL_FCC_NODEOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for FCC_TAB_CHANGES 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_ir_item | TYPE CL_FCC_CITEMX, " | |||
| lv_ix_forced_update | TYPE ABAP_BOOL, " ABAP_FALSE | |||
| lv_ir_node | TYPE CL_FCC_NODE. " |
|   CALL FUNCTION 'FCC_TAB_CHANGES' "Changes tab |
| EXPORTING | ||
| IR_ITEM | = lv_ir_item | |
| IX_FORCED_UPDATE | = lv_ix_forced_update | |
| IR_NODE | = lv_ir_node | |
| . " FCC_TAB_CHANGES | ||
ABAP code using 7.40 inline data declarations to call FM FCC_TAB_CHANGES
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_ix_forced_update) | = ABAP_FALSE. | |||
Search for further information about these or an SAP related objects