SAP FC_CONSISTENCY_CHECK1 Function Module for









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

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



Function FC_CONSISTENCY_CHECK1 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_CONSISTENCY_CHECK1'"
  EXPORTING
*  IT_RA_DIMEN =  "
*  IT_RA_ITEM =  "
*  IT_RA_RVERS =  "
*  IT_RA_RYEAR =  "
   I_ITCLG =  "
*  I_FLG_WAIT =  "

CHANGING
*  CS_ITEM_PROC =  "
*  CS_ITGRP_PROC =  "

EXCEPTIONS
   OBJECT_NOT_DETERMINED = 1    CHECK_UPD_CONFLICT = 2    OBJECT_FOR_DELETION_USED = 3    LOCK_ERROR = 4    REQUIRED_BRKDOWN_FIELD_MISSING = 5    PROCESSING_ABORTED = 6    YEAR_INTERVAL_NOT_SPECIFIED = 7
.



IMPORTING Parameters details for FC_CONSISTENCY_CHECK1

IT_RA_DIMEN -

Data type: FC00_T_RA_DIMEN
Optional: Yes
Call by Reference: Yes

IT_RA_ITEM -

Data type: FC00_T_RA_ITEM
Optional: Yes
Call by Reference: Yes

IT_RA_RVERS -

Data type: FC00_T_RA_RVERS
Optional: Yes
Call by Reference: Yes

IT_RA_RYEAR -

Data type: FC00_T_RA_RYEAR
Optional: Yes
Call by Reference: Yes

I_ITCLG -

Data type: FC_ITCLG
Optional: No
Call by Reference: Yes

I_FLG_WAIT -

Data type: FC_FLG
Optional: Yes
Call by Reference: Yes

CHANGING Parameters details for FC_CONSISTENCY_CHECK1

CS_ITEM_PROC -

Data type: FC31_S_ITEM_PROC
Optional: Yes
Call by Reference: Yes

CS_ITGRP_PROC -

Data type: FC31_S_ITGRP_PROC
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

OBJECT_NOT_DETERMINED -

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

CHECK_UPD_CONFLICT -

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

OBJECT_FOR_DELETION_USED -

Data type:
Optional: No
Call by Reference: Yes

LOCK_ERROR -

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

REQUIRED_BRKDOWN_FIELD_MISSING -

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

PROCESSING_ABORTED -

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

YEAR_INTERVAL_NOT_SPECIFIED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FC_CONSISTENCY_CHECK1 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_ra_dimen  TYPE FC00_T_RA_DIMEN, "   
lv_cs_item_proc  TYPE FC31_S_ITEM_PROC, "   
lv_object_not_determined  TYPE FC31_S_ITEM_PROC, "   
lv_it_ra_item  TYPE FC00_T_RA_ITEM, "   
lv_cs_itgrp_proc  TYPE FC31_S_ITGRP_PROC, "   
lv_check_upd_conflict  TYPE FC31_S_ITGRP_PROC, "   
lv_it_ra_rvers  TYPE FC00_T_RA_RVERS, "   
lv_object_for_deletion_used  TYPE FC00_T_RA_RVERS, "   
lv_lock_error  TYPE FC00_T_RA_RVERS, "   
lv_it_ra_ryear  TYPE FC00_T_RA_RYEAR, "   
lv_i_itclg  TYPE FC_ITCLG, "   
lv_required_brkdown_field_missing  TYPE FC_ITCLG, "   
lv_i_flg_wait  TYPE FC_FLG, "   
lv_processing_aborted  TYPE FC_FLG, "   
lv_year_interval_not_specified  TYPE FC_FLG. "   

  CALL FUNCTION 'FC_CONSISTENCY_CHECK1'  "
    EXPORTING
         IT_RA_DIMEN = lv_it_ra_dimen
         IT_RA_ITEM = lv_it_ra_item
         IT_RA_RVERS = lv_it_ra_rvers
         IT_RA_RYEAR = lv_it_ra_ryear
         I_ITCLG = lv_i_itclg
         I_FLG_WAIT = lv_i_flg_wait
    CHANGING
         CS_ITEM_PROC = lv_cs_item_proc
         CS_ITGRP_PROC = lv_cs_itgrp_proc
    EXCEPTIONS
        OBJECT_NOT_DETERMINED = 1
        CHECK_UPD_CONFLICT = 2
        OBJECT_FOR_DELETION_USED = 3
        LOCK_ERROR = 4
        REQUIRED_BRKDOWN_FIELD_MISSING = 5
        PROCESSING_ABORTED = 6
        YEAR_INTERVAL_NOT_SPECIFIED = 7
. " FC_CONSISTENCY_CHECK1




ABAP code using 7.40 inline data declarations to call FM FC_CONSISTENCY_CHECK1

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!