SAP FC_CHECK_CONSISTENCY Function Module for

Search SAP Function Modules

FC_CHECK_CONSISTENCY is a standard fc check consistency 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 check consistency FM, simply by entering the name FC_CHECK_CONSISTENCY into the relevant SAP transaction such as SE37 or SE38.

Function Group: FC02
Program Name: SAPLFC02
Main Program: SAPLFC02
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FC_CHECK_CONSISTENCY 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_CHECK_CONSISTENCY'"
  EXPORTING
   E_DIMEN =  "Dimension
   E_ITCLG =  "Consolidation Chart of Accounts
   E_RVERS =  "Version
*  E_BUNIT =  "CU or rollup CU
   E_RYEAR =  "Fiscal Year
   E_PERID =  "Period
   E_CACGR =  "Task group
   E_MONITOR_FLAG =  "

 IMPORTING
   I_SUBRC =  "Return Code

TABLES
   T_CACTI =  "
*  T_CACTI_RESET =  "
*  T_TF260 =  "
*  T_TF261 =  "
*  T_TF270 =  "
*  T_TF271 =  "

.

IMPORTING Parameters details for FC_CHECK_CONSISTENCY

E_DIMEN - Dimension

Data type: FC_DIMEN
Optional: No
Call by Reference: No ( called with pass by value option)

E_ITCLG - Consolidation Chart of Accounts

Data type: FC_ITCLG
Optional: No
Call by Reference: No ( called with pass by value option)

E_RVERS - Version

Data type: FC_RVERS
Optional: No
Call by Reference: No ( called with pass by value option)

E_BUNIT - CU or rollup CU

Data type: FC_BUNIT
Optional: Yes
Call by Reference: No ( called with pass by value option)

E_RYEAR - Fiscal Year

Data type: FC_RYEAR
Optional: No
Call by Reference: No ( called with pass by value option)

E_PERID - Period

Data type: FC_PERID
Optional: No
Call by Reference: No ( called with pass by value option)

E_CACGR - Task group

Data type: FC_ACGR
Optional: No
Call by Reference: No ( called with pass by value option)

E_MONITOR_FLAG -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for FC_CHECK_CONSISTENCY

I_SUBRC - Return Code

Data type: SY-SUBRC
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for FC_CHECK_CONSISTENCY

T_CACTI -

Data type: FC02_T_CACTI
Optional: No
Call by Reference: No ( called with pass by value option)

T_CACTI_RESET -

Data type: FC02_T_CACTISET
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_TF260 -

Data type: TF260
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_TF261 -

Data type: TF261
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_TF270 -

Data type: TF270
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_TF271 -

Data type: TF271
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for FC_CHECK_CONSISTENCY 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.

ABAP code using 7.40 inline data declarations to call FM FC_CHECK_CONSISTENCY

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