SAP PPELIBITS_CONDITION_EVALUATE Function Module for NOTRANSL: Auswertung einer Auswahlbedingung bzw. eines Constraints

Search SAP Function Modules

PPELIBITS_CONDITION_EVALUATE is a standard ppelibits condition evaluate 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: Auswertung einer Auswahlbedingung bzw. eines Constraints 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 condition evaluate FM, simply by entering the name PPELIBITS_CONDITION_EVALUATE into the relevant SAP transaction such as SE37 or SE38.

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

Function PPELIBITS_CONDITION_EVALUATE 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_CONDITION_EVALUATE'"NOTRANSL: Auswertung einer Auswahlbedingung bzw. eines Constraints
  EXPORTING
   IT_DDB =  "
   IT_CODE =  "

 IMPORTING
   EV_RESULT =  "Predefined Type

EXCEPTIONS
   ILLEGAL_CODE_FOUND = 1    INTERNAL_ERROR = 2 

.

IMPORTING Parameters details for PPELIBITS_CONDITION_EVALUATE

IT_DDB -

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

IT_CODE -

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

EXPORTING Parameters details for PPELIBITS_CONDITION_EVALUATE

EV_RESULT - Predefined Type

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

EXCEPTIONS details

ILLEGAL_CODE_FOUND -

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

INTERNAL_ERROR -

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

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

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