SAP MAP_CREATE_TO_VTS_CONTRACT Function Module for bapi_ftr_create -> vts_contract
MAP_CREATE_TO_VTS_CONTRACT is a standard map create to vts contract 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_create -> vts_contract 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 create to vts contract FM, simply by entering the name MAP_CREATE_TO_VTS_CONTRACT into the relevant SAP transaction such as SE37 or SE38.
Function Group: FTR_BAPI
Program Name: SAPLFTR_BAPI
Main Program: SAPLFTR_BAPI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MAP_CREATE_TO_VTS_CONTRACT 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_CREATE_TO_VTS_CONTRACT'"bapi_ftr_create -> vts_contract.
EXPORTING
BAPI_FTR_CREATE = "
CHANGING
VTS_CONTRACT = "
IMPORTING Parameters details for MAP_CREATE_TO_VTS_CONTRACT
BAPI_FTR_CREATE -
Data type: BAPI_FTR_CREATEOptional: No
Call by Reference: Yes
CHANGING Parameters details for MAP_CREATE_TO_VTS_CONTRACT
VTS_CONTRACT -
Data type: VTS_CONTRACTOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for MAP_CREATE_TO_VTS_CONTRACT 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_vts_contract | TYPE VTS_CONTRACT, " | |||
| lv_bapi_ftr_create | TYPE BAPI_FTR_CREATE. " |
|   CALL FUNCTION 'MAP_CREATE_TO_VTS_CONTRACT' "bapi_ftr_create -> vts_contract |
| EXPORTING | ||
| BAPI_FTR_CREATE | = lv_bapi_ftr_create | |
| CHANGING | ||
| VTS_CONTRACT | = lv_vts_contract | |
| . " MAP_CREATE_TO_VTS_CONTRACT | ||
ABAP code using 7.40 inline data declarations to call FM MAP_CREATE_TO_VTS_CONTRACT
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