SAP BBP_MAP_CUST_FIELDS_TO_BAPI Function Module for Mapping von Kundenfeldern auf die BAPI Schnittstelle









BBP_MAP_CUST_FIELDS_TO_BAPI is a standard bbp map cust fields to bapi SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Mapping von Kundenfeldern auf die BAPI Schnittstelle 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 bbp map cust fields to bapi FM, simply by entering the name BBP_MAP_CUST_FIELDS_TO_BAPI into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_MAP_CUST_FIELDS_TO_BAPI 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 'BBP_MAP_CUST_FIELDS_TO_BAPI'"Mapping von Kundenfeldern auf die BAPI Schnittstelle
  EXPORTING
   IV_SRC_REF_1 =  "1. Referenz Komponente des Quellobjekes
   IV_DEST_REF_NAME_1 =  "Bezeichnung der 1. Referenz in der Übergabestruktur
   IV_SRC_REF_2 =  "2. Referenz Komponente des Quellobjekes
   IV_DEST_REF_NAME_2 =  "Bezeichnung der 2. Referenz in der Übergabestruktur
   IV_CUST_STUCT =  "Strukturname des Kunden Includes
   IO_SOURCE =  "Quellobjekt (Struktur/Tabelle)
   IV_DEST_OBJ =  "Objektbezeichnung zur Identifizierung
   IV_EXCEPTION_COMP =  "Komponente die nicht übernommen wird

CHANGING
   CT_DEST_TAB =  "Kundenfelder Schnittstellentabelle
.



IMPORTING Parameters details for BBP_MAP_CUST_FIELDS_TO_BAPI

IV_SRC_REF_1 - 1. Referenz Komponente des Quellobjekes

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

IV_DEST_REF_NAME_1 - Bezeichnung der 1. Referenz in der Übergabestruktur

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

IV_SRC_REF_2 - 2. Referenz Komponente des Quellobjekes

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

IV_DEST_REF_NAME_2 - Bezeichnung der 2. Referenz in der Übergabestruktur

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

IV_CUST_STUCT - Strukturname des Kunden Includes

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

IO_SOURCE - Quellobjekt (Struktur/Tabelle)

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

IV_DEST_OBJ - Objektbezeichnung zur Identifizierung

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

IV_EXCEPTION_COMP - Komponente die nicht übernommen wird

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

CHANGING Parameters details for BBP_MAP_CUST_FIELDS_TO_BAPI

CT_DEST_TAB - Kundenfelder Schnittstellentabelle

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

Copy and paste ABAP code example for BBP_MAP_CUST_FIELDS_TO_BAPI 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_ct_dest_tab  TYPE BBPT_IF_CUSTOMER_FIELDS_PI, "   
lv_iv_src_ref_1  TYPE CHAR30, "   
lv_iv_dest_ref_name_1  TYPE CHAR30, "   
lv_iv_src_ref_2  TYPE CHAR30, "   
lv_iv_dest_ref_name_2  TYPE CHAR30, "   
lv_iv_cust_stuct  TYPE CHAR30, "   
lv_io_source  TYPE ANY, "   
lv_iv_dest_obj  TYPE CHAR30, "   
lv_iv_exception_comp  TYPE CHAR30. "   

  CALL FUNCTION 'BBP_MAP_CUST_FIELDS_TO_BAPI'  "Mapping von Kundenfeldern auf die BAPI Schnittstelle
    EXPORTING
         IV_SRC_REF_1 = lv_iv_src_ref_1
         IV_DEST_REF_NAME_1 = lv_iv_dest_ref_name_1
         IV_SRC_REF_2 = lv_iv_src_ref_2
         IV_DEST_REF_NAME_2 = lv_iv_dest_ref_name_2
         IV_CUST_STUCT = lv_iv_cust_stuct
         IO_SOURCE = lv_io_source
         IV_DEST_OBJ = lv_iv_dest_obj
         IV_EXCEPTION_COMP = lv_iv_exception_comp
    CHANGING
         CT_DEST_TAB = lv_ct_dest_tab
. " BBP_MAP_CUST_FIELDS_TO_BAPI




ABAP code using 7.40 inline data declarations to call FM BBP_MAP_CUST_FIELDS_TO_BAPI

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!