SAP FVAY_N_OBJECT_CHANGE Function Module for
FVAY_N_OBJECT_CHANGE is a standard fvay n object change 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 fvay n object change FM, simply by entering the name FVAY_N_OBJECT_CHANGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVAY_N
Program Name: SAPLFVAY_N
Main Program: SAPLFVAY_N
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FVAY_N_OBJECT_CHANGE 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 'FVAY_N_OBJECT_CHANGE'".
EXPORTING
* I_FUNCTION = "
I_VZOBJECT_INT = "Object Data (Virtual Object) - Internal
* I_ADDRESS = "
* I_CHECK_ADDRESS = 'X' "
* I_ACCEPT_REG_DATA_ERROR = 'X' "
IMPORTING
E_VZOBJECT_INT = "Object Data (Virtual Object)
E_ADDRESS = "
E_RC = "
TABLES
* E_VZOBJECT_TAB = "Object Data (Virtual Object)
* E_MESG = "
EXCEPTIONS
GENERAL_ERROR = 1
IMPORTING Parameters details for FVAY_N_OBJECT_CHANGE
I_FUNCTION -
Data type: COptional: Yes
Call by Reference: No ( called with pass by value option)
I_VZOBJECT_INT - Object Data (Virtual Object) - Internal
Data type: VZOBJECT_INTOptional: No
Call by Reference: No ( called with pass by value option)
I_ADDRESS -
Data type: SZADR_ADDR1_COMPLETEOptional: Yes
Call by Reference: Yes
I_CHECK_ADDRESS -
Data type: BOOLE_DDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_ACCEPT_REG_DATA_ERROR -
Data type: BOOLE_DDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FVAY_N_OBJECT_CHANGE
E_VZOBJECT_INT - Object Data (Virtual Object)
Data type: VZOBJECT_INTOptional: No
Call by Reference: No ( called with pass by value option)
E_ADDRESS -
Data type: SZADR_ADDR1_COMPLETEOptional: No
Call by Reference: Yes
E_RC -
Data type: BOOLE_DOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FVAY_N_OBJECT_CHANGE
E_VZOBJECT_TAB - Object Data (Virtual Object)
Data type: VZOBJECT_INTOptional: Yes
Call by Reference: No ( called with pass by value option)
E_MESG -
Data type: MESGOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
GENERAL_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FVAY_N_OBJECT_CHANGE 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_function | TYPE C, " | |||
| lv_general_error | TYPE C, " | |||
| lv_e_vzobject_int | TYPE VZOBJECT_INT, " | |||
| lt_e_vzobject_tab | TYPE STANDARD TABLE OF VZOBJECT_INT, " | |||
| lt_e_mesg | TYPE STANDARD TABLE OF MESG, " | |||
| lv_e_address | TYPE SZADR_ADDR1_COMPLETE, " | |||
| lv_i_vzobject_int | TYPE VZOBJECT_INT, " | |||
| lv_e_rc | TYPE BOOLE_D, " | |||
| lv_i_address | TYPE SZADR_ADDR1_COMPLETE, " | |||
| lv_i_check_address | TYPE BOOLE_D, " 'X' | |||
| lv_i_accept_reg_data_error | TYPE BOOLE_D. " 'X' |
|   CALL FUNCTION 'FVAY_N_OBJECT_CHANGE' " |
| EXPORTING | ||
| I_FUNCTION | = lv_i_function | |
| I_VZOBJECT_INT | = lv_i_vzobject_int | |
| I_ADDRESS | = lv_i_address | |
| I_CHECK_ADDRESS | = lv_i_check_address | |
| I_ACCEPT_REG_DATA_ERROR | = lv_i_accept_reg_data_error | |
| IMPORTING | ||
| E_VZOBJECT_INT | = lv_e_vzobject_int | |
| E_ADDRESS | = lv_e_address | |
| E_RC | = lv_e_rc | |
| TABLES | ||
| E_VZOBJECT_TAB | = lt_e_vzobject_tab | |
| E_MESG | = lt_e_mesg | |
| EXCEPTIONS | ||
| GENERAL_ERROR = 1 | ||
| . " FVAY_N_OBJECT_CHANGE | ||
ABAP code using 7.40 inline data declarations to call FM FVAY_N_OBJECT_CHANGE
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.| DATA(ld_i_check_address) | = 'X'. | |||
| DATA(ld_i_accept_reg_data_error) | = 'X'. | |||
Search for further information about these or an SAP related objects