SAP FV70_CHECK_POSITION_VALIDITY Function Module for Check Positions for Inconsistencies
FV70_CHECK_POSITION_VALIDITY is a standard fv70 check position validity SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check Positions for Inconsistencies 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 fv70 check position validity FM, simply by entering the name FV70_CHECK_POSITION_VALIDITY into the relevant SAP transaction such as SE37 or SE38.
Function Group: FV70
Program Name: SAPLFV70
Main Program: SAPLFV70
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FV70_CHECK_POSITION_VALIDITY 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 'FV70_CHECK_POSITION_VALIDITY'"Check Positions for Inconsistencies.
EXPORTING
I_REVAL = "
* I_SNOTI = "
IMPORTING
E_CHECK_RESULT = "
IMPORTING Parameters details for FV70_CHECK_POSITION_VALIDITY
I_REVAL -
Data type: REVALOptional: No
Call by Reference: Yes
I_SNOTI -
Data type: VWPANLA-SNOTIOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FV70_CHECK_POSITION_VALIDITY
E_CHECK_RESULT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FV70_CHECK_POSITION_VALIDITY 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_i_reval | TYPE REVAL, " | |||
| lv_e_check_result | TYPE REVAL, " | |||
| lv_i_snoti | TYPE VWPANLA-SNOTI. " |
|   CALL FUNCTION 'FV70_CHECK_POSITION_VALIDITY' "Check Positions for Inconsistencies |
| EXPORTING | ||
| I_REVAL | = lv_i_reval | |
| I_SNOTI | = lv_i_snoti | |
| IMPORTING | ||
| E_CHECK_RESULT | = lv_e_check_result | |
| . " FV70_CHECK_POSITION_VALIDITY | ||
ABAP code using 7.40 inline data declarations to call FM FV70_CHECK_POSITION_VALIDITY
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 SNOTI FROM VWPANLA INTO @DATA(ld_i_snoti). | ||||
Search for further information about these or an SAP related objects