SAP FC_ECCS_MASTER_DATA_UPDATE Function Module for
FC_ECCS_MASTER_DATA_UPDATE is a standard fc eccs master data update 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 fc eccs master data update FM, simply by entering the name FC_ECCS_MASTER_DATA_UPDATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FCIN
Program Name: SAPLFCIN
Main Program: SAPLFCIN
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FC_ECCS_MASTER_DATA_UPDATE 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 'FC_ECCS_MASTER_DATA_UPDATE'".
EXPORTING
* I_FLG_T000K_READ = "
CHANGING
C_PERIV = "
TABLES
* T_TFIN000 = "
* T_CONTP_TRANS = "
* I_T_CONTP_BUNIT = "
EXCEPTIONS
ECCS_NOT_ACTIVE = 1 NO_ACTIVE_CONSTYPE = 2 NO_T000K_ENTRIES = 3 NO_DATA_STREAM = 4 NO_ACTIVE_DATA_STREAM = 5 NO_ECCS_LEDGER = 6 CU_MASSCHANGE_ERROR = 7
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLFCIN_100 Integration: User Exit for Identifier and Texts from Cons Org Units
EXIT_SAPLFCIN_110 Integration: User Exit for 'Parents' of Cons Org Units
EXIT_SAPLFCIN_200 Integration: User Exit for Definition of the Data Stream on Rollup
EXIT_SAPLFCIN_210 Integration: Output Fields of Incorrect Data Records in Rollup
EXIT_SAPLFCIN_220 Integration: Sender Fields for Organizational Units on Rollup
EXIT_SAPLFCIN_230 Integration: Sender Fields for Subitems on Rollup
EXIT_SAPLFCIN_240 Integration: Edit from Value Fields before Update with Rollup
EXIT_SAPLFCIN_250 Integration: Get Custom Subassignments
IMPORTING Parameters details for FC_ECCS_MASTER_DATA_UPDATE
I_FLG_T000K_READ -
Data type: FC_FLGOptional: Yes
Call by Reference: Yes
CHANGING Parameters details for FC_ECCS_MASTER_DATA_UPDATE
C_PERIV -
Data type: FCIN_PERIVOptional: No
Call by Reference: Yes
TABLES Parameters details for FC_ECCS_MASTER_DATA_UPDATE
T_TFIN000 -
Data type: FCIN_T_TFIN000Optional: Yes
Call by Reference: No ( called with pass by value option)
T_CONTP_TRANS -
Data type: FCIN_T_CONTP_TRANSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_T_CONTP_BUNIT -
Data type: FCIN_T_CONTP_BUNITOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ECCS_NOT_ACTIVE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_ACTIVE_CONSTYPE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_T000K_ENTRIES -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_DATA_STREAM -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_ACTIVE_DATA_STREAM -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_ECCS_LEDGER -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CU_MASSCHANGE_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FC_ECCS_MASTER_DATA_UPDATE 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_c_periv | TYPE FCIN_PERIV, " | |||
| lt_t_tfin000 | TYPE STANDARD TABLE OF FCIN_T_TFIN000, " | |||
| lv_eccs_not_active | TYPE FCIN_T_TFIN000, " | |||
| lv_i_flg_t000k_read | TYPE FC_FLG, " | |||
| lt_t_contp_trans | TYPE STANDARD TABLE OF FCIN_T_CONTP_TRANS, " | |||
| lv_no_active_constype | TYPE FCIN_T_CONTP_TRANS, " | |||
| lt_i_t_contp_bunit | TYPE STANDARD TABLE OF FCIN_T_CONTP_BUNIT, " | |||
| lv_no_t000k_entries | TYPE FCIN_T_CONTP_BUNIT, " | |||
| lv_no_data_stream | TYPE FCIN_T_CONTP_BUNIT, " | |||
| lv_no_active_data_stream | TYPE FCIN_T_CONTP_BUNIT, " | |||
| lv_no_eccs_ledger | TYPE FCIN_T_CONTP_BUNIT, " | |||
| lv_cu_masschange_error | TYPE FCIN_T_CONTP_BUNIT. " |
|   CALL FUNCTION 'FC_ECCS_MASTER_DATA_UPDATE' " |
| EXPORTING | ||
| I_FLG_T000K_READ | = lv_i_flg_t000k_read | |
| CHANGING | ||
| C_PERIV | = lv_c_periv | |
| TABLES | ||
| T_TFIN000 | = lt_t_tfin000 | |
| T_CONTP_TRANS | = lt_t_contp_trans | |
| I_T_CONTP_BUNIT | = lt_i_t_contp_bunit | |
| EXCEPTIONS | ||
| ECCS_NOT_ACTIVE = 1 | ||
| NO_ACTIVE_CONSTYPE = 2 | ||
| NO_T000K_ENTRIES = 3 | ||
| NO_DATA_STREAM = 4 | ||
| NO_ACTIVE_DATA_STREAM = 5 | ||
| NO_ECCS_LEDGER = 6 | ||
| CU_MASSCHANGE_ERROR = 7 | ||
| . " FC_ECCS_MASTER_DATA_UPDATE | ||
ABAP code using 7.40 inline data declarations to call FM FC_ECCS_MASTER_DATA_UPDATE
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