SAP FVST_ME_STATUS_HIST_CHECK_SET Function Module for

Search SAP Function Modules

FVST_ME_STATUS_HIST_CHECK_SET is a standard fvst me status hist check set SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 fvst me status hist check set FM, simply by entering the name FVST_ME_STATUS_HIST_CHECK_SET into the relevant SAP transaction such as SE37 or SE38.

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

Function FVST_ME_STATUS_HIST_CHECK_SET 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 'FVST_ME_STATUS_HIST_CHECK_SET'"
  EXPORTING
*  I1_VIMIMV_NEW = ' ' "
*  I1_VIMIMV_OLD = ' ' "
*  I2_DBEZU = ' ' "
*  I2_DSTGAB = ' ' "
*  I2_STAT = ' ' "
   I_OBJNR =  "
*  I_SET_STATUS = ' ' "
*  I_KZ_SUPPRESS_EVENT = ' ' "

 IMPORTING
   E_CHANGE_FLAG =  "

EXCEPTIONS
   DBEZU_NOT_VALID = 1    NEW_STATUS_NOT_VALID = 2    NO_CHANGE = 3    OLD_STATUS_NOT_FOUND = 4    NO_EVENT_CREATED = 5 

.

IMPORTING Parameters details for FVST_ME_STATUS_HIST_CHECK_SET

I1_VIMIMV_NEW -

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

I1_VIMIMV_OLD -

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

I2_DBEZU -

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

I2_DSTGAB -

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

I2_STAT -

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

I_OBJNR -

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

I_SET_STATUS -

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

I_KZ_SUPPRESS_EVENT -

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

EXPORTING Parameters details for FVST_ME_STATUS_HIST_CHECK_SET

E_CHANGE_FLAG -

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

EXCEPTIONS details

DBEZU_NOT_VALID -

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

NEW_STATUS_NOT_VALID -

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

NO_CHANGE -

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

OLD_STATUS_NOT_FOUND -

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

NO_EVENT_CREATED -

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

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

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