SAP MAP_CHANGE_FUTURE_VFSFHAPO Function Module for bapi_ftr_change_future -> vfsfhapo
MAP_CHANGE_FUTURE_VFSFHAPO is a standard map change future vfsfhapo SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for bapi_ftr_change_future -> vfsfhapo 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 map change future vfsfhapo FM, simply by entering the name MAP_CHANGE_FUTURE_VFSFHAPO into the relevant SAP transaction such as SE37 or SE38.
Function Group: FTR_BAPI_FUTURE
Program Name: SAPLFTR_BAPI_FUTURE
Main Program: SAPLFTR_BAPI_FUTURE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MAP_CHANGE_FUTURE_VFSFHAPO 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 'MAP_CHANGE_FUTURE_VFSFHAPO'"bapi_ftr_change_future -> vfsfhapo.
EXPORTING
BAPI_FTR_CHANGE_FUTURE = "
CHANGING
VFSFHAPO = "
EXCEPTIONS
ERROR_CONVERTING_ISO_CODE = 1 ERROR_CONVERTING_CURR_AMOUNT = 2
IMPORTING Parameters details for MAP_CHANGE_FUTURE_VFSFHAPO
BAPI_FTR_CHANGE_FUTURE -
Data type: BAPI_FTR_CHANGE_FUTUREOptional: No
Call by Reference: Yes
CHANGING Parameters details for MAP_CHANGE_FUTURE_VFSFHAPO
VFSFHAPO -
Data type: VFSFHAPOOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR_CONVERTING_ISO_CODE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR_CONVERTING_CURR_AMOUNT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MAP_CHANGE_FUTURE_VFSFHAPO 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_vfsfhapo | TYPE VFSFHAPO, " | |||
| lv_bapi_ftr_change_future | TYPE BAPI_FTR_CHANGE_FUTURE, " | |||
| lv_error_converting_iso_code | TYPE BAPI_FTR_CHANGE_FUTURE, " | |||
| lv_error_converting_curr_amount | TYPE BAPI_FTR_CHANGE_FUTURE. " |
|   CALL FUNCTION 'MAP_CHANGE_FUTURE_VFSFHAPO' "bapi_ftr_change_future -> vfsfhapo |
| EXPORTING | ||
| BAPI_FTR_CHANGE_FUTURE | = lv_bapi_ftr_change_future | |
| CHANGING | ||
| VFSFHAPO | = lv_vfsfhapo | |
| EXCEPTIONS | ||
| ERROR_CONVERTING_ISO_CODE = 1 | ||
| ERROR_CONVERTING_CURR_AMOUNT = 2 | ||
| . " MAP_CHANGE_FUTURE_VFSFHAPO | ||
ABAP code using 7.40 inline data declarations to call FM MAP_CHANGE_FUTURE_VFSFHAPO
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