SAP BCONTACT_MAPTO_OBJREF Function Module for
BCONTACT_MAPTO_OBJREF is a standard bcontact mapto objref 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 bcontact mapto objref FM, simply by entering the name BCONTACT_MAPTO_OBJREF into the relevant SAP transaction such as SE37 or SE38.
Function Group: BPTCRM
Program Name: SAPLBPTCRM
Main Program: SAPLBPTCRM
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BCONTACT_MAPTO_OBJREF 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 'BCONTACT_MAPTO_OBJREF'".
EXPORTING
I_OBJECT = "Business Partner Contact: Related Objects
CHANGING
C_BAPI_OBJREF = "BAPI Structure Replication of Object for BP Activity (CRM)
IMPORTING Parameters details for BCONTACT_MAPTO_OBJREF
I_OBJECT - Business Partner Contact: Related Objects
Data type: BCONT_OBJOptional: No
Call by Reference: Yes
CHANGING Parameters details for BCONTACT_MAPTO_OBJREF
C_BAPI_OBJREF - BAPI Structure Replication of Object for BP Activity (CRM)
Data type: BAPI_BCONT_OBJ_CRM_LOCALOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for BCONTACT_MAPTO_OBJREF 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_i_object | TYPE BCONT_OBJ, " | |||
| lv_c_bapi_objref | TYPE BAPI_BCONT_OBJ_CRM_LOCAL. " |
|   CALL FUNCTION 'BCONTACT_MAPTO_OBJREF' " |
| EXPORTING | ||
| I_OBJECT | = lv_i_object | |
| CHANGING | ||
| C_BAPI_OBJREF | = lv_c_bapi_objref | |
| . " BCONTACT_MAPTO_OBJREF | ||
ABAP code using 7.40 inline data declarations to call FM BCONTACT_MAPTO_OBJREF
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