SAP PPELIBITS_CONSISTENCY_CHECK Function Module for NOTRANSL: Konsistenz- und Vollständigkeitsprüfung









PPELIBITS_CONSISTENCY_CHECK is a standard ppelibits consistency check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Konsistenz- und Vollständigkeitsprüfung 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 ppelibits consistency check FM, simply by entering the name PPELIBITS_CONSISTENCY_CHECK into the relevant SAP transaction such as SE37 or SE38.

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



Function PPELIBITS_CONSISTENCY_CHECK 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 'PPELIBITS_CONSISTENCY_CHECK'"NOTRANSL: Konsistenz- und Vollständigkeitsprüfung
  EXPORTING
   IV_PNGUID =  "Internal Number of iPPE Node
*  IV_RECALCULATE = ' ' "Checkbox
*  IV_CHECK_PRIORITIES = ' ' "Checkbox
*  IV_CHECK_CONSISTENCY = 'X' "Checkbox
*  IV_CHECK_COMPLETENESS = 'X' "Checkbox
*  IV_MAX_OUTPUT = 100 "Natural number
   IT_SELCONDITIONS =  "DE-EN-LANG-SWITCH-NO-TRANSLATION
   IT_RESTRICTIONS =  "DE-EN-LANG-SWITCH-NO-TRANSLATION
   IT_VS =  "Variance Scheme

 IMPORTING
   ET_INCOMPLETE =  "
   ET_INCONSISTENT =  "

EXCEPTIONS
   VARSPACE_TOO_LARGE = 1    ILLEGAL_CODE_FOUND = 2    INTERNAL_ERROR = 3
.



IMPORTING Parameters details for PPELIBITS_CONSISTENCY_CHECK

IV_PNGUID - Internal Number of iPPE Node

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

IV_RECALCULATE - Checkbox

Data type: XFELD
Default: SPACE
Optional: Yes
Call by Reference: Yes

IV_CHECK_PRIORITIES - Checkbox

Data type: XFELD
Default: SPACE
Optional: Yes
Call by Reference: Yes

IV_CHECK_CONSISTENCY - Checkbox

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: Yes

IV_CHECK_COMPLETENESS - Checkbox

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: Yes

IV_MAX_OUTPUT - Natural number

Data type: INT4
Default: 100
Optional: Yes
Call by Reference: Yes

IT_SELCONDITIONS - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

IT_RESTRICTIONS - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

IT_VS - Variance Scheme

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

EXPORTING Parameters details for PPELIBITS_CONSISTENCY_CHECK

ET_INCOMPLETE -

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

ET_INCONSISTENT -

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

EXCEPTIONS details

VARSPACE_TOO_LARGE - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

ILLEGAL_CODE_FOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for PPELIBITS_CONSISTENCY_CHECK 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_iv_pnguid  TYPE PVS_PNGUID, "   
lv_et_incomplete  TYPE PPENV_CUFET_DISJUNCTION, "   
lv_varspace_too_large  TYPE PPENV_CUFET_DISJUNCTION, "   
lv_iv_recalculate  TYPE XFELD, "   SPACE
lv_et_inconsistent  TYPE PPEVS_TAB_SCHNITT, "   
lv_illegal_code_found  TYPE PPEVS_TAB_SCHNITT, "   
lv_internal_error  TYPE PPEVS_TAB_SCHNITT, "   
lv_iv_check_priorities  TYPE XFELD, "   SPACE
lv_iv_check_consistency  TYPE XFELD, "   'X'
lv_iv_check_completeness  TYPE XFELD, "   'X'
lv_iv_max_output  TYPE INT4, "   100
lv_it_selconditions  TYPE PPEVS_TAB_KNOBJ, "   
lv_it_restrictions  TYPE PPEVS_TAB_KNNUM, "   
lv_it_vs  TYPE PPEVS_TAB_VS. "   

  CALL FUNCTION 'PPELIBITS_CONSISTENCY_CHECK'  "NOTRANSL: Konsistenz- und Vollständigkeitsprüfung
    EXPORTING
         IV_PNGUID = lv_iv_pnguid
         IV_RECALCULATE = lv_iv_recalculate
         IV_CHECK_PRIORITIES = lv_iv_check_priorities
         IV_CHECK_CONSISTENCY = lv_iv_check_consistency
         IV_CHECK_COMPLETENESS = lv_iv_check_completeness
         IV_MAX_OUTPUT = lv_iv_max_output
         IT_SELCONDITIONS = lv_it_selconditions
         IT_RESTRICTIONS = lv_it_restrictions
         IT_VS = lv_it_vs
    IMPORTING
         ET_INCOMPLETE = lv_et_incomplete
         ET_INCONSISTENT = lv_et_inconsistent
    EXCEPTIONS
        VARSPACE_TOO_LARGE = 1
        ILLEGAL_CODE_FOUND = 2
        INTERNAL_ERROR = 3
. " PPELIBITS_CONSISTENCY_CHECK




ABAP code using 7.40 inline data declarations to call FM PPELIBITS_CONSISTENCY_CHECK

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_iv_recalculate) = ' '.
 
 
 
 
DATA(ld_iv_check_priorities) = ' '.
 
DATA(ld_iv_check_consistency) = 'X'.
 
DATA(ld_iv_check_completeness) = 'X'.
 
DATA(ld_iv_max_output) = 100.
 
 
 
 


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!