SAP CRM_CP_O_TO_BP_BP_TRIGGER Function Module for
CRM_CP_O_TO_BP_BP_TRIGGER is a standard crm cp o to bp bp trigger 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 crm cp o to bp bp trigger FM, simply by entering the name CRM_CP_O_TO_BP_BP_TRIGGER into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM_OBJECT_BUPA
Program Name: SAPLCRM_OBJECT_BUPA
Main Program: SAPLCRM_OBJECT_BUPA
Appliation area: H
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CRM_CP_O_TO_BP_BP_TRIGGER 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 'CRM_CP_O_TO_BP_BP_TRIGGER'".
EXPORTING
BUSINESSOBJECT = "Business Object
OPERATION = "Update operation
* LFCOD = "Logical function code
PLOG_TAB_RECORD = "Current PLOG_TAB record
TABLES
EVENTS_PER_OPERATION = "Events
BEFORE_IMAGE = "
AFTER_IMAGE = "
IMPORTING Parameters details for CRM_CP_O_TO_BP_BP_TRIGGER
BUSINESSOBJECT - Business Object
Data type: T779W-BUSOBOptional: No
Call by Reference: No ( called with pass by value option)
OPERATION - Update operation
Data type: T779W-WFOPROptional: No
Call by Reference: No ( called with pass by value option)
LFCOD - Logical function code
Data type: T779W-LFCODOptional: Yes
Call by Reference: No ( called with pass by value option)
PLOG_TAB_RECORD - Current PLOG_TAB record
Data type: HRDBTABOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CRM_CP_O_TO_BP_BP_TRIGGER
EVENTS_PER_OPERATION - Events
Data type: HREVENTSOptional: No
Call by Reference: No ( called with pass by value option)
BEFORE_IMAGE -
Data type: BEF_IMAGEOptional: No
Call by Reference: No ( called with pass by value option)
AFTER_IMAGE -
Data type: AFT_IMAGEOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CRM_CP_O_TO_BP_BP_TRIGGER 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_businessobject | TYPE T779W-BUSOB, " | |||
| lt_events_per_operation | TYPE STANDARD TABLE OF HREVENTS, " | |||
| lv_operation | TYPE T779W-WFOPR, " | |||
| lt_before_image | TYPE STANDARD TABLE OF BEF_IMAGE, " | |||
| lv_lfcod | TYPE T779W-LFCOD, " | |||
| lt_after_image | TYPE STANDARD TABLE OF AFT_IMAGE, " | |||
| lv_plog_tab_record | TYPE HRDBTAB. " |
|   CALL FUNCTION 'CRM_CP_O_TO_BP_BP_TRIGGER' " |
| EXPORTING | ||
| BUSINESSOBJECT | = lv_businessobject | |
| OPERATION | = lv_operation | |
| LFCOD | = lv_lfcod | |
| PLOG_TAB_RECORD | = lv_plog_tab_record | |
| TABLES | ||
| EVENTS_PER_OPERATION | = lt_events_per_operation | |
| BEFORE_IMAGE | = lt_before_image | |
| AFTER_IMAGE | = lt_after_image | |
| . " CRM_CP_O_TO_BP_BP_TRIGGER | ||
ABAP code using 7.40 inline data declarations to call FM CRM_CP_O_TO_BP_BP_TRIGGER
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.| "SELECT single BUSOB FROM T779W INTO @DATA(ld_businessobject). | ||||
| "SELECT single WFOPR FROM T779W INTO @DATA(ld_operation). | ||||
| "SELECT single LFCOD FROM T779W INTO @DATA(ld_lfcod). | ||||
Search for further information about these or an SAP related objects