SAP BBP_CT_UPD_PARTNER_MAPPING Function Module for









BBP_CT_UPD_PARTNER_MAPPING is a standard bbp ct upd partner mapping 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 bbp ct upd partner mapping FM, simply by entering the name BBP_CT_UPD_PARTNER_MAPPING into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_CT_UPD_PARTNER_MAPPING 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_CT_UPD_PARTNER_MAPPING'"
EXPORTING
I_CONTENT_PROVIDER_GUID = "

TABLES
* T_PART_MAP = "

EXCEPTIONS
CP_NOT_FOUND = 1
.



IMPORTING Parameters details for BBP_CT_UPD_PARTNER_MAPPING

I_CONTENT_PROVIDER_GUID -

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

TABLES Parameters details for BBP_CT_UPD_PARTNER_MAPPING

T_PART_MAP -

Data type: BBP_CTS_MAPPART_FB
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

CP_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BBP_CT_UPD_PARTNER_MAPPING 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_t_part_map  TYPE STANDARD TABLE OF BBP_CTS_MAPPART_FB, "   
lv_cp_not_found  TYPE BBP_CTS_MAPPART_FB, "   
lv_i_content_provider_guid  TYPE BBPT_CT_PARTNER_GUID. "   

  CALL FUNCTION 'BBP_CT_UPD_PARTNER_MAPPING'  "
    EXPORTING
         I_CONTENT_PROVIDER_GUID = lv_i_content_provider_guid
    TABLES
         T_PART_MAP = lt_t_part_map
    EXCEPTIONS
        CP_NOT_FOUND = 1
. " BBP_CT_UPD_PARTNER_MAPPING




ABAP code using 7.40 inline data declarations to call FM BBP_CT_UPD_PARTNER_MAPPING

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!