SAP BUPA_MAP_VEND_SAVE Function Module for NOTRANSL: Sichernbaustein für Vendor-Mapping Tabelle









BUPA_MAP_VEND_SAVE is a standard bupa map vend save SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Sichernbaustein für Vendor-Mapping Tabelle 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 bupa map vend save FM, simply by entering the name BUPA_MAP_VEND_SAVE into the relevant SAP transaction such as SE37 or SE38.

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



Function BUPA_MAP_VEND_SAVE 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 'BUPA_MAP_VEND_SAVE'"NOTRANSL: Sichernbaustein für Vendor-Mapping Tabelle
EXPORTING
IV_IN_UPDATE_TASK = "

TABLES
IT_MAP_VEND_NEW = "
IT_MAP_VEND_OLD = "
.



IMPORTING Parameters details for BUPA_MAP_VEND_SAVE

IV_IN_UPDATE_TASK -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BUPA_MAP_VEND_SAVE

IT_MAP_VEND_NEW -

Data type: CRMLIFNR
Optional: No
Call by Reference: No ( called with pass by value option)

IT_MAP_VEND_OLD -

Data type: CRMLIFNR
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for BUPA_MAP_VEND_SAVE 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_map_vend_new  TYPE STANDARD TABLE OF CRMLIFNR, "   
lv_iv_in_update_task  TYPE CRMLIFNR, "   
lt_it_map_vend_old  TYPE STANDARD TABLE OF CRMLIFNR. "   

  CALL FUNCTION 'BUPA_MAP_VEND_SAVE'  "NOTRANSL: Sichernbaustein für Vendor-Mapping Tabelle
    EXPORTING
         IV_IN_UPDATE_TASK = lv_iv_in_update_task
    TABLES
         IT_MAP_VEND_NEW = lt_it_map_vend_new
         IT_MAP_VEND_OLD = lt_it_map_vend_old
. " BUPA_MAP_VEND_SAVE




ABAP code using 7.40 inline data declarations to call FM BUPA_MAP_VEND_SAVE

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!