SAP MAP_BAPI_CHANGE_TO_VTS_COND Function Module for bapi_ftr_cond_change -> vts_cond









MAP_BAPI_CHANGE_TO_VTS_COND is a standard map bapi change to vts cond 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_cond_change -> vts_cond 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 bapi change to vts cond FM, simply by entering the name MAP_BAPI_CHANGE_TO_VTS_COND into the relevant SAP transaction such as SE37 or SE38.

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



Function MAP_BAPI_CHANGE_TO_VTS_COND 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_BAPI_CHANGE_TO_VTS_COND'"bapi_ftr_cond_change -> vts_cond
EXPORTING
BAPI_FTR_COND_CHANGE = "

CHANGING
VTS_COND = "

EXCEPTIONS
ERROR_CONVERTING_CURR_AMOUNT = 1
.



IMPORTING Parameters details for MAP_BAPI_CHANGE_TO_VTS_COND

BAPI_FTR_COND_CHANGE -

Data type: BAPI_FTR_COND_CHANGE
Optional: No
Call by Reference: Yes

CHANGING Parameters details for MAP_BAPI_CHANGE_TO_VTS_COND

VTS_COND -

Data type: VTS_COND
Optional: No
Call by Reference: Yes

EXCEPTIONS details

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_BAPI_CHANGE_TO_VTS_COND 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_cond  TYPE VTS_COND, "   
lv_bapi_ftr_cond_change  TYPE BAPI_FTR_COND_CHANGE, "   
lv_error_converting_curr_amount  TYPE BAPI_FTR_COND_CHANGE. "   

  CALL FUNCTION 'MAP_BAPI_CHANGE_TO_VTS_COND'  "bapi_ftr_cond_change -> vts_cond
    EXPORTING
         BAPI_FTR_COND_CHANGE = lv_bapi_ftr_cond_change
    CHANGING
         VTS_COND = lv_vts_cond
    EXCEPTIONS
        ERROR_CONVERTING_CURR_AMOUNT = 1
. " MAP_BAPI_CHANGE_TO_VTS_COND




ABAP code using 7.40 inline data declarations to call FM MAP_BAPI_CHANGE_TO_VTS_COND

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!