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

Function FC_ROUND 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_ROUND'".
EXPORTING
E_DIMEN = "
* E_RKFIG = "
E_CTRGR = "
ET_ENTRY = "
ET_ENTRY_AAA = "
ES_DATA_KEY = "
E_ITCLG = "
E_RYEAR = "
E_PERID = "
E_RTCUR = "
* E_RPFLG = "
* E_RTFLG = "
ET_FIELDS = "
ET_KFIG = "
IMPORTING
IT_RDATA = "
IT_ERROR = "
IT_MESSAGE = "
CHANGING
CT_DATA = "
EXCEPTIONS
FIELDNAME_WRONG = 1 FIELDNAME_MISSING = 2
IMPORTING Parameters details for FC_ROUND
E_DIMEN -
Data type: FC_DIMENOptional: No
Call by Reference: Yes
E_RKFIG -
Data type: FC_FIELDNAMEOptional: Yes
Call by Reference: Yes
E_CTRGR -
Data type: FC_CTRGROptional: No
Call by Reference: Yes
ET_ENTRY -
Data type: FC04_T_ENTRYOptional: No
Call by Reference: Yes
ET_ENTRY_AAA -
Data type: FC04_T_ENTRY_AAAOptional: No
Call by Reference: Yes
ES_DATA_KEY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
E_ITCLG -
Data type: FC_ITCLGOptional: No
Call by Reference: Yes
E_RYEAR -
Data type: FC_RYEAROptional: No
Call by Reference: Yes
E_PERID -
Data type: FC_PERIDOptional: No
Call by Reference: Yes
E_RTCUR -
Data type: FC_RTCUROptional: No
Call by Reference: Yes
E_RPFLG -
Data type: FC_RPFLGOptional: Yes
Call by Reference: Yes
E_RTFLG -
Data type: FC_RTFLGOptional: Yes
Call by Reference: Yes
ET_FIELDS -
Data type: FC00_T_FIELDSOptional: No
Call by Reference: Yes
ET_KFIG -
Data type: FC00_T_FIELDSOptional: No
Call by Reference: Yes
EXPORTING Parameters details for FC_ROUND
IT_RDATA -
Data type: ANY TABLEOptional: No
Call by Reference: Yes
IT_ERROR -
Data type: FC04_T_ROUND_ERROROptional: No
Call by Reference: Yes
IT_MESSAGE -
Data type: FC00_T_MESSAGEOptional: No
Call by Reference: Yes
CHANGING Parameters details for FC_ROUND
CT_DATA -
Data type: ANY TABLEOptional: No
Call by Reference: Yes
EXCEPTIONS details
FIELDNAME_WRONG -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FIELDNAME_MISSING -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FC_ROUND 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_ct_data | TYPE ANY TABLE, " | |||
| lv_e_dimen | TYPE FC_DIMEN, " | |||
| lv_it_rdata | TYPE ANY TABLE, " | |||
| lv_fieldname_wrong | TYPE ANY TABLE, " | |||
| lv_e_rkfig | TYPE FC_FIELDNAME, " | |||
| lv_e_ctrgr | TYPE FC_CTRGR, " | |||
| lv_et_entry | TYPE FC04_T_ENTRY, " | |||
| lv_et_entry_aaa | TYPE FC04_T_ENTRY_AAA, " | |||
| lv_es_data_key | TYPE FC04_T_ENTRY_AAA, " | |||
| lv_e_itclg | TYPE FC_ITCLG, " | |||
| lv_it_error | TYPE FC04_T_ROUND_ERROR, " | |||
| lv_fieldname_missing | TYPE FC04_T_ROUND_ERROR, " | |||
| lv_e_ryear | TYPE FC_RYEAR, " | |||
| lv_it_message | TYPE FC00_T_MESSAGE, " | |||
| lv_e_perid | TYPE FC_PERID, " | |||
| lv_e_rtcur | TYPE FC_RTCUR, " | |||
| lv_e_rpflg | TYPE FC_RPFLG, " | |||
| lv_e_rtflg | TYPE FC_RTFLG, " | |||
| lv_et_fields | TYPE FC00_T_FIELDS, " | |||
| lv_et_kfig | TYPE FC00_T_FIELDS. " |
|   CALL FUNCTION 'FC_ROUND' " |
| EXPORTING | ||
| E_DIMEN | = lv_e_dimen | |
| E_RKFIG | = lv_e_rkfig | |
| E_CTRGR | = lv_e_ctrgr | |
| ET_ENTRY | = lv_et_entry | |
| ET_ENTRY_AAA | = lv_et_entry_aaa | |
| ES_DATA_KEY | = lv_es_data_key | |
| E_ITCLG | = lv_e_itclg | |
| E_RYEAR | = lv_e_ryear | |
| E_PERID | = lv_e_perid | |
| E_RTCUR | = lv_e_rtcur | |
| E_RPFLG | = lv_e_rpflg | |
| E_RTFLG | = lv_e_rtflg | |
| ET_FIELDS | = lv_et_fields | |
| ET_KFIG | = lv_et_kfig | |
| IMPORTING | ||
| IT_RDATA | = lv_it_rdata | |
| IT_ERROR | = lv_it_error | |
| IT_MESSAGE | = lv_it_message | |
| CHANGING | ||
| CT_DATA | = lv_ct_data | |
| EXCEPTIONS | ||
| FIELDNAME_WRONG = 1 | ||
| FIELDNAME_MISSING = 2 | ||
| . " FC_ROUND | ||
ABAP code using 7.40 inline data declarations to call FM FC_ROUND
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