SAP FKK_VT_MIG_VT Function Module for
FKK_VT_MIG_VT is a standard fkk vt mig vt 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 fkk vt mig vt FM, simply by entering the name FKK_VT_MIG_VT into the relevant SAP transaction such as SE37 or SE38.
Function Group: FKK_VT_MIG
Program Name: SAPLFKK_VT_MIG
Main Program: SAPLFKK_VT_MIG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function FKK_VT_MIG_VT 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 'FKK_VT_MIG_VT'".
EXPORTING
IV_SCENARIO_ID = "
* IV_EXECUTE_CHECKS = 'X' "
* IV_COMMIT_ROLLBACK = 'X' "
* IV_WRITE_CHANGE_DOCUMENTS = 'X' "
TABLES
IT_HEADER = "
* ET_CONTRACT_ID_CREATED = "
* RETURN = "
* IT_ITEMS = "
* IT_ITEM_DISCOUNTS = "
* IT_CHARGING_ITEMS = "
* IT_CHARGING_ITEM_SHRCOUNT = "
* IT_CHARGING_ITEM_PARAMS = "
* IT_CHARGING_ITEM_ACCOUNTS = "
* IT_CHARGING_ITEM_TECH_ID = "
* IT_ADDITIONAL_INFO = "
IMPORTING Parameters details for FKK_VT_MIG_VT
IV_SCENARIO_ID -
Data type: ISX_CTR_SCENARIO_IDOptional: No
Call by Reference: No ( called with pass by value option)
IV_EXECUTE_CHECKS -
Data type: BOOLEANDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_COMMIT_ROLLBACK -
Data type: BOOLEANDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_WRITE_CHANGE_DOCUMENTS -
Data type: BOOLEANDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FKK_VT_MIG_VT
IT_HEADER -
Data type: CRM_ISX_CONTRACT_HEADEROptional: No
Call by Reference: Yes
ET_CONTRACT_ID_CREATED -
Data type: ISX_CONTRACT_HEADER_KEY_ILOptional: Yes
Call by Reference: Yes
RETURN -
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
IT_ITEMS -
Data type: CRM_ISX_CONTRACT_ITEMOptional: Yes
Call by Reference: Yes
IT_ITEM_DISCOUNTS -
Data type: CRM_ISX_CONTRACT_ITEM_DISCOUNTOptional: Yes
Call by Reference: Yes
IT_CHARGING_ITEMS -
Data type: ISX_CONTRACT_CHARGING_ITEM_BKOptional: Yes
Call by Reference: Yes
IT_CHARGING_ITEM_SHRCOUNT -
Data type: ISX_CTR_CHARGING_ITEM_SC_BKOptional: Yes
Call by Reference: Yes
IT_CHARGING_ITEM_PARAMS -
Data type: ISX_CTR_CHARGING_ITEM_PRM_BKOptional: Yes
Call by Reference: Yes
IT_CHARGING_ITEM_ACCOUNTS -
Data type: ISX_CTR_CHARGING_ITEM_ACC_BKOptional: Yes
Call by Reference: Yes
IT_CHARGING_ITEM_TECH_ID -
Data type: ISX_CTR_CHARGING_ITEM_TI_BKOptional: Yes
Call by Reference: Yes
IT_ADDITIONAL_INFO -
Data type: CRM_ISX_CONTRACT_ADD_INFOOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for FKK_VT_MIG_VT 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: | ||||
| lt_it_header | TYPE STANDARD TABLE OF CRM_ISX_CONTRACT_HEADER, " | |||
| lv_iv_scenario_id | TYPE ISX_CTR_SCENARIO_ID, " | |||
| lt_et_contract_id_created | TYPE STANDARD TABLE OF ISX_CONTRACT_HEADER_KEY_IL, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lt_it_items | TYPE STANDARD TABLE OF CRM_ISX_CONTRACT_ITEM, " | |||
| lv_iv_execute_checks | TYPE BOOLEAN, " 'X' | |||
| lt_it_item_discounts | TYPE STANDARD TABLE OF CRM_ISX_CONTRACT_ITEM_DISCOUNT, " | |||
| lv_iv_commit_rollback | TYPE BOOLEAN, " 'X' | |||
| lt_it_charging_items | TYPE STANDARD TABLE OF ISX_CONTRACT_CHARGING_ITEM_BK, " | |||
| lv_iv_write_change_documents | TYPE BOOLEAN, " 'X' | |||
| lt_it_charging_item_shrcount | TYPE STANDARD TABLE OF ISX_CTR_CHARGING_ITEM_SC_BK, " | |||
| lt_it_charging_item_params | TYPE STANDARD TABLE OF ISX_CTR_CHARGING_ITEM_PRM_BK, " | |||
| lt_it_charging_item_accounts | TYPE STANDARD TABLE OF ISX_CTR_CHARGING_ITEM_ACC_BK, " | |||
| lt_it_charging_item_tech_id | TYPE STANDARD TABLE OF ISX_CTR_CHARGING_ITEM_TI_BK, " | |||
| lt_it_additional_info | TYPE STANDARD TABLE OF CRM_ISX_CONTRACT_ADD_INFO. " |
|   CALL FUNCTION 'FKK_VT_MIG_VT' " |
| EXPORTING | ||
| IV_SCENARIO_ID | = lv_iv_scenario_id | |
| IV_EXECUTE_CHECKS | = lv_iv_execute_checks | |
| IV_COMMIT_ROLLBACK | = lv_iv_commit_rollback | |
| IV_WRITE_CHANGE_DOCUMENTS | = lv_iv_write_change_documents | |
| TABLES | ||
| IT_HEADER | = lt_it_header | |
| ET_CONTRACT_ID_CREATED | = lt_et_contract_id_created | |
| RETURN | = lt_return | |
| IT_ITEMS | = lt_it_items | |
| IT_ITEM_DISCOUNTS | = lt_it_item_discounts | |
| IT_CHARGING_ITEMS | = lt_it_charging_items | |
| IT_CHARGING_ITEM_SHRCOUNT | = lt_it_charging_item_shrcount | |
| IT_CHARGING_ITEM_PARAMS | = lt_it_charging_item_params | |
| IT_CHARGING_ITEM_ACCOUNTS | = lt_it_charging_item_accounts | |
| IT_CHARGING_ITEM_TECH_ID | = lt_it_charging_item_tech_id | |
| IT_ADDITIONAL_INFO | = lt_it_additional_info | |
| . " FKK_VT_MIG_VT | ||
ABAP code using 7.40 inline data declarations to call FM FKK_VT_MIG_VT
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_iv_execute_checks) | = 'X'. | |||
| DATA(ld_iv_commit_rollback) | = 'X'. | |||
| DATA(ld_iv_write_change_documents) | = 'X'. | |||
Search for further information about these or an SAP related objects