SAP PLAUSI_FOR_CONDITIONS Function Module for Plausibility Checks Between the Condition Items
PLAUSI_FOR_CONDITIONS is a standard plausi for conditions SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Plausibility Checks Between the Condition Items 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 plausi for conditions FM, simply by entering the name PLAUSI_FOR_CONDITIONS into the relevant SAP transaction such as SE37 or SE38.
Function Group: FV06
Program Name: SAPLFV06
Main Program: SAPLFV06
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PLAUSI_FOR_CONDITIONS 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 'PLAUSI_FOR_CONDITIONS'"Plausibility Checks Between the Condition Items.
EXPORTING
I_CURS_FIELD = "
I_CURS_LINE = "
I_ENTRACT = "
I_OK_CODE = "
* I_P_DEFSZ = ' ' "
IMPORTING
E_CURS_FIELD = "
E_CURS_LINE = "
E_ENTRACT = "
E_MESSAGE = "
E_OK_CODE = "
TABLES
IVZZKOPO = "
IMPORTING Parameters details for PLAUSI_FOR_CONDITIONS
I_CURS_FIELD -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
I_CURS_LINE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
I_ENTRACT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
I_OK_CODE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
I_P_DEFSZ -
Data type: RCFLEISTE-DEFSZDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for PLAUSI_FOR_CONDITIONS
E_CURS_FIELD -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
E_CURS_LINE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
E_ENTRACT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
E_MESSAGE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
E_OK_CODE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for PLAUSI_FOR_CONDITIONS
IVZZKOPO -
Data type: VVZZKOPOOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for PLAUSI_FOR_CONDITIONS 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: | ||||
| lt_ivzzkopo | TYPE STANDARD TABLE OF VVZZKOPO, " | |||
| lv_e_curs_field | TYPE VVZZKOPO, " | |||
| lv_i_curs_field | TYPE VVZZKOPO, " | |||
| lv_e_curs_line | TYPE VVZZKOPO, " | |||
| lv_i_curs_line | TYPE VVZZKOPO, " | |||
| lv_e_entract | TYPE VVZZKOPO, " | |||
| lv_i_entract | TYPE VVZZKOPO, " | |||
| lv_e_message | TYPE VVZZKOPO, " | |||
| lv_i_ok_code | TYPE VVZZKOPO, " | |||
| lv_e_ok_code | TYPE VVZZKOPO, " | |||
| lv_i_p_defsz | TYPE RCFLEISTE-DEFSZ. " SPACE |
|   CALL FUNCTION 'PLAUSI_FOR_CONDITIONS' "Plausibility Checks Between the Condition Items |
| EXPORTING | ||
| I_CURS_FIELD | = lv_i_curs_field | |
| I_CURS_LINE | = lv_i_curs_line | |
| I_ENTRACT | = lv_i_entract | |
| I_OK_CODE | = lv_i_ok_code | |
| I_P_DEFSZ | = lv_i_p_defsz | |
| IMPORTING | ||
| E_CURS_FIELD | = lv_e_curs_field | |
| E_CURS_LINE | = lv_e_curs_line | |
| E_ENTRACT | = lv_e_entract | |
| E_MESSAGE | = lv_e_message | |
| E_OK_CODE | = lv_e_ok_code | |
| TABLES | ||
| IVZZKOPO | = lt_ivzzkopo | |
| . " PLAUSI_FOR_CONDITIONS | ||
ABAP code using 7.40 inline data declarations to call FM PLAUSI_FOR_CONDITIONS
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.| "SELECT single DEFSZ FROM RCFLEISTE INTO @DATA(ld_i_p_defsz). | ||||
| DATA(ld_i_p_defsz) | = ' '. | |||
Search for further information about these or an SAP related objects