SAP FWEV_VALUATION_CHECK Function Module for Check if Closing Operations Performed for a Position

Search SAP Function Modules

FWEV_VALUATION_CHECK is a standard fwev valuation 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 Check if Closing Operations Performed for a Position 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 fwev valuation check FM, simply by entering the name FWEV_VALUATION_CHECK into the relevant SAP transaction such as SE37 or SE38.

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

Function FWEV_VALUATION_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 'FWEV_VALUATION_CHECK'"Check if Closing Operations Performed for a Position
  EXPORTING
*  I_STICHTAG = SY-DATUM "Key Date
   I_BEVI =  "Posted Flows
   I_BEPP =  "noch zu buchende Bewegungen
*  I_STORNO = ' ' "Storno = 'X' oder Normallauf = ' '
*  I_SVORGANG = 'REVALUE' "Transaction description

EXCEPTIONS
   PERIOD_END_CLOSING_MISSING = 1    ERROR_POSITION_VALUATION = 2    ERROR_ACCOUNT_TRANSFER = 3    PERIOD_END_CLOSING = 4    ERROR_POSITION_ACCRUAL = 5    ERROR_SEC_ACTIVITY = 6 

.

IMPORTING Parameters details for FWEV_VALUATION_CHECK

I_STICHTAG - Key Date

Data type: SY-DATUM
Default: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_BEVI - Posted Flows

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

I_BEPP - noch zu buchende Bewegungen

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

I_STORNO - Storno = 'X' oder Normallauf = ' '

Data type: C
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_SVORGANG - Transaction description

Data type: VWBEPP-SVORGANG
Default: 'REVALUE'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

PERIOD_END_CLOSING_MISSING - Periodenabschluß zuvor durchführen

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

ERROR_POSITION_VALUATION - Bewertung per oder nach Stichtag

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

ERROR_ACCOUNT_TRANSFER - Depotumbuchung nach Stichtag

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

PERIOD_END_CLOSING - Periodenabschluß nach Stichtag

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

ERROR_POSITION_ACCRUAL - Abgrenzung per oder nach Stichtag

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

ERROR_SEC_ACTIVITY - unzulässiger Vorgang

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

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

ABAP code using 7.40 inline data declarations to call FM FWEV_VALUATION_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.

Search for further information about these or an SAP related objects