SAP FB_ICRC_ADD_DATA_RFC Function Module for ICR: Push Data Into Reconciliation Process
FB_ICRC_ADD_DATA_RFC is a standard fb icrc add data rfc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for ICR: Push Data Into Reconciliation Process 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 fb icrc add data rfc FM, simply by entering the name FB_ICRC_ADD_DATA_RFC into the relevant SAP transaction such as SE37 or SE38.
Function Group: FB_ICRC_SERVICES
Program Name: SAPLFB_ICRC_SERVICES
Main Program: SAPLFB_ICRC_SERVICES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function FB_ICRC_ADD_DATA_RFC 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 'FB_ICRC_ADD_DATA_RFC'"ICR: Push Data Into Reconciliation Process.
EXPORTING
ED_RPROC = "Target Reconciliation Process
* ED_MAXRF = "Maximum Number of Parallel Calls for Automatic Assignment
* ET_RCOMP_FDNAM = "Company and Fieldname
* ET_DATA_001 = "ICR: Table of Data Records for Process 001
* ET_DATA_002 = "ICR: Table of Data Records for Process 002
* ET_DATA_003 = "ICR: Table of Data Records for Process 003
* ET_DATA_001_PLAIN = "ICR: Table of Data Records for Process 001
* ET_DATA_002_PLAIN = "ICR: Table of Data Records for Process 002
* ET_DATA_003_PLAIN = "ICR: Table of Data Records for Process 003
* ED_OPACT = "'X' = Specified accounts are operative accounts
ED_RVERS = "Version
ED_RYEAR = "Reconciliation Year
ED_PERID = "Reconciliation Period
* EB_TEST = "'X' = Test Run; ' ' = Update Run
* EB_DO_NOT_POST_ON_ERROR = 'X' "'X' = Post Only If No Errors Occur; ' ' = Error Free Data Records Are Posted
* EB_DISPLAY_LOG = "'X' = Display Log; ' ' = No Log
* EB_RUN_ASSIGNMENT = "'X' Automatic Assignment Program is Started For Posted Data Records
* ED_SVGRP = "Server Group For Automatic Assignment
IMPORTING
IT_MSG = "ICR: Simple Message Table To Pass Back To RFC Caller
EXCEPTIONS
EXC_RPROC_NOT_SUPPORTED = 1 EXC_CONV_NOT_SUPPORT = 2 EXC_PERID_INVALID = 3
IMPORTING Parameters details for FB_ICRC_ADD_DATA_RFC
ED_RPROC - Target Reconciliation Process
Data type: FB_RC_RPROCOptional: No
Call by Reference: No ( called with pass by value option)
ED_MAXRF - Maximum Number of Parallel Calls for Automatic Assignment
Data type: FB_ICRC_MAXRFOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_RCOMP_FDNAM - Company and Fieldname
Data type: FBICRC_T_RCOMP_FDNAMOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_DATA_001 - ICR: Table of Data Records for Process 001
Data type: FBAS_T_CLUSTROptional: Yes
Call by Reference: No ( called with pass by value option)
ET_DATA_002 - ICR: Table of Data Records for Process 002
Data type: FBAS_T_CLUSTROptional: Yes
Call by Reference: No ( called with pass by value option)
ET_DATA_003 - ICR: Table of Data Records for Process 003
Data type: FBAS_T_CLUSTROptional: Yes
Call by Reference: No ( called with pass by value option)
ET_DATA_001_PLAIN - ICR: Table of Data Records for Process 001
Data type: FBICRC_T_SELECT_001Optional: Yes
Call by Reference: No ( called with pass by value option)
ET_DATA_002_PLAIN - ICR: Table of Data Records for Process 002
Data type: FBICRC_T_SELECT_002Optional: Yes
Call by Reference: No ( called with pass by value option)
ET_DATA_003_PLAIN - ICR: Table of Data Records for Process 003
Data type: FBICRC_T_SELECT_003Optional: Yes
Call by Reference: No ( called with pass by value option)
ED_OPACT - 'X' = Specified accounts are operative accounts
Data type: FB_ICRC_FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
ED_RVERS - Version
Data type: RVERSOptional: No
Call by Reference: No ( called with pass by value option)
ED_RYEAR - Reconciliation Year
Data type: GJAHROptional: No
Call by Reference: No ( called with pass by value option)
ED_PERID - Reconciliation Period
Data type: POPEROptional: No
Call by Reference: No ( called with pass by value option)
EB_TEST - 'X' = Test Run; SPACE = Update Run
Data type: FB_ICRC_FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
EB_DO_NOT_POST_ON_ERROR - 'X' = Post Only If No Errors Occur; SPACE = Error Free Data Records Are Posted
Data type: FB_ICRC_FLAGDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EB_DISPLAY_LOG - 'X' = Display Log; SPACE = No Log
Data type: FB_ICRC_FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
EB_RUN_ASSIGNMENT - 'X' Automatic Assignment Program is Started For Posted Data Records
Data type: FB_ICRC_FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
ED_SVGRP - Server Group For Automatic Assignment
Data type: ICRC_SVGRPOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FB_ICRC_ADD_DATA_RFC
IT_MSG - ICR: Simple Message Table To Pass Back To RFC Caller
Data type: FBICRC_T_MSG_RFCOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
EXC_RPROC_NOT_SUPPORTED - Process Not Supported
Data type:Optional: No
Call by Reference: Yes
EXC_CONV_NOT_SUPPORT - Conversion Not Supported
Data type:Optional: No
Call by Reference: Yes
EXC_PERID_INVALID - Period is invalid
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FB_ICRC_ADD_DATA_RFC 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_it_msg | TYPE FBICRC_T_MSG_RFC, " | |||
| lv_ed_rproc | TYPE FB_RC_RPROC, " | |||
| lv_exc_rproc_not_supported | TYPE FB_RC_RPROC, " | |||
| lv_ed_maxrf | TYPE FB_ICRC_MAXRF, " | |||
| lv_et_rcomp_fdnam | TYPE FBICRC_T_RCOMP_FDNAM, " | |||
| lv_et_data_001 | TYPE FBAS_T_CLUSTR, " | |||
| lv_et_data_002 | TYPE FBAS_T_CLUSTR, " | |||
| lv_et_data_003 | TYPE FBAS_T_CLUSTR, " | |||
| lv_et_data_001_plain | TYPE FBICRC_T_SELECT_001, " | |||
| lv_et_data_002_plain | TYPE FBICRC_T_SELECT_002, " | |||
| lv_et_data_003_plain | TYPE FBICRC_T_SELECT_003, " | |||
| lv_ed_opact | TYPE FB_ICRC_FLAG, " | |||
| lv_ed_rvers | TYPE RVERS, " | |||
| lv_exc_conv_not_support | TYPE RVERS, " | |||
| lv_ed_ryear | TYPE GJAHR, " | |||
| lv_exc_perid_invalid | TYPE GJAHR, " | |||
| lv_ed_perid | TYPE POPER, " | |||
| lv_eb_test | TYPE FB_ICRC_FLAG, " | |||
| lv_eb_do_not_post_on_error | TYPE FB_ICRC_FLAG, " 'X' | |||
| lv_eb_display_log | TYPE FB_ICRC_FLAG, " | |||
| lv_eb_run_assignment | TYPE FB_ICRC_FLAG, " | |||
| lv_ed_svgrp | TYPE ICRC_SVGRP. " |
|   CALL FUNCTION 'FB_ICRC_ADD_DATA_RFC' "ICR: Push Data Into Reconciliation Process |
| EXPORTING | ||
| ED_RPROC | = lv_ed_rproc | |
| ED_MAXRF | = lv_ed_maxrf | |
| ET_RCOMP_FDNAM | = lv_et_rcomp_fdnam | |
| ET_DATA_001 | = lv_et_data_001 | |
| ET_DATA_002 | = lv_et_data_002 | |
| ET_DATA_003 | = lv_et_data_003 | |
| ET_DATA_001_PLAIN | = lv_et_data_001_plain | |
| ET_DATA_002_PLAIN | = lv_et_data_002_plain | |
| ET_DATA_003_PLAIN | = lv_et_data_003_plain | |
| ED_OPACT | = lv_ed_opact | |
| ED_RVERS | = lv_ed_rvers | |
| ED_RYEAR | = lv_ed_ryear | |
| ED_PERID | = lv_ed_perid | |
| EB_TEST | = lv_eb_test | |
| EB_DO_NOT_POST_ON_ERROR | = lv_eb_do_not_post_on_error | |
| EB_DISPLAY_LOG | = lv_eb_display_log | |
| EB_RUN_ASSIGNMENT | = lv_eb_run_assignment | |
| ED_SVGRP | = lv_ed_svgrp | |
| IMPORTING | ||
| IT_MSG | = lv_it_msg | |
| EXCEPTIONS | ||
| EXC_RPROC_NOT_SUPPORTED = 1 | ||
| EXC_CONV_NOT_SUPPORT = 2 | ||
| EXC_PERID_INVALID = 3 | ||
| . " FB_ICRC_ADD_DATA_RFC | ||
ABAP code using 7.40 inline data declarations to call FM FB_ICRC_ADD_DATA_RFC
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_eb_do_not_post_on_error) | = 'X'. | |||
Search for further information about these or an SAP related objects