SAP MAP2I_BAPI_BILLCONTR_TR_CHANGE Function Module for









MAP2I_BAPI_BILLCONTR_TR_CHANGE is a standard map2i bapi billcontr tr 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 map2i bapi billcontr tr change FM, simply by entering the name MAP2I_BAPI_BILLCONTR_TR_CHANGE into the relevant SAP transaction such as SE37 or SE38.

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



Function MAP2I_BAPI_BILLCONTR_TR_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 'MAP2I_BAPI_BILLCONTR_TR_CHANGE'"
EXPORTING
BAPI_BILLCONTR_TR_CHANGE = "
BAPI_BILLCONTR_TR_CHANGEX = "

CHANGING
FKK_VT_TR_DI = "
.



IMPORTING Parameters details for MAP2I_BAPI_BILLCONTR_TR_CHANGE

BAPI_BILLCONTR_TR_CHANGE -

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

BAPI_BILLCONTR_TR_CHANGEX -

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

CHANGING Parameters details for MAP2I_BAPI_BILLCONTR_TR_CHANGE

FKK_VT_TR_DI -

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

Copy and paste ABAP code example for MAP2I_BAPI_BILLCONTR_TR_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_fkk_vt_tr_di  TYPE FKK_VT_TR_DI, "   
lv_bapi_billcontr_tr_change  TYPE BAPI_BILLCONTR_TR_CHANGE, "   
lv_bapi_billcontr_tr_changex  TYPE BAPI_BILLCONTR_TR_CHANGEX. "   

  CALL FUNCTION 'MAP2I_BAPI_BILLCONTR_TR_CHANGE'  "
    EXPORTING
         BAPI_BILLCONTR_TR_CHANGE = lv_bapi_billcontr_tr_change
         BAPI_BILLCONTR_TR_CHANGEX = lv_bapi_billcontr_tr_changex
    CHANGING
         FKK_VT_TR_DI = lv_fkk_vt_tr_di
. " MAP2I_BAPI_BILLCONTR_TR_CHANGE




ABAP code using 7.40 inline data declarations to call FM MAP2I_BAPI_BILLCONTR_TR_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.

 
 
 


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!