SAP BBP_CTR_NOV_UPDATE Function Module for Change Novation Protocol
BBP_CTR_NOV_UPDATE is a standard bbp ctr nov update SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change Novation Protocol 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 ctr nov update FM, simply by entering the name BBP_CTR_NOV_UPDATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_CTR_NOV
Program Name: SAPLBBP_CTR_NOV
Main Program: SAPLBBP_CTR_NOV
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_CTR_NOV_UPDATE 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_CTR_NOV_UPDATE'"Change Novation Protocol.
EXPORTING
IV_NOVATION_GUID = "Novation GUID
IV_NOVATION_ID = "Novation ID
* IV_X_COMMIT_EXTERNAL = ' ' "'X' = Caller Executes Commit, ' ' = Commit im Module
TABLES
IT_CTR_NOV_LOG_UPD = "Novation Protocol
EXCEPTIONS
NOVATION_NOT_FOUND = 1 MANDATORY_INPUT_MISSING = 2 MULTI_NOVATIONS_NOT_SUPPORTED = 3
IMPORTING Parameters details for BBP_CTR_NOV_UPDATE
IV_NOVATION_GUID - Novation GUID
Data type: CRMT_OBJECT_GUIDOptional: No
Call by Reference: Yes
IV_NOVATION_ID - Novation ID
Data type: BBP_NOVATION_IDOptional: No
Call by Reference: Yes
IV_X_COMMIT_EXTERNAL - 'X' = Caller Executes Commit, SPACE = Commit im Module
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: Yes
TABLES Parameters details for BBP_CTR_NOV_UPDATE
IT_CTR_NOV_LOG_UPD - Novation Protocol
Data type: BBPD_CTR_NOV_LOGOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOVATION_NOT_FOUND - Novation Does Not Exist
Data type:Optional: No
Call by Reference: Yes
MANDATORY_INPUT_MISSING - Either Novation GUID or Novation ID must be entered
Data type:Optional: No
Call by Reference: Yes
MULTI_NOVATIONS_NOT_SUPPORTED - All Lines Must Belong to One Novation
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BBP_CTR_NOV_UPDATE 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_iv_novation_guid | TYPE CRMT_OBJECT_GUID, " | |||
| lt_it_ctr_nov_log_upd | TYPE STANDARD TABLE OF BBPD_CTR_NOV_LOG, " | |||
| lv_novation_not_found | TYPE BBPD_CTR_NOV_LOG, " | |||
| lv_iv_novation_id | TYPE BBP_NOVATION_ID, " | |||
| lv_mandatory_input_missing | TYPE BBP_NOVATION_ID, " | |||
| lv_iv_x_commit_external | TYPE XFELD, " SPACE | |||
| lv_multi_novations_not_supported | TYPE XFELD. " |
|   CALL FUNCTION 'BBP_CTR_NOV_UPDATE' "Change Novation Protocol |
| EXPORTING | ||
| IV_NOVATION_GUID | = lv_iv_novation_guid | |
| IV_NOVATION_ID | = lv_iv_novation_id | |
| IV_X_COMMIT_EXTERNAL | = lv_iv_x_commit_external | |
| TABLES | ||
| IT_CTR_NOV_LOG_UPD | = lt_it_ctr_nov_log_upd | |
| EXCEPTIONS | ||
| NOVATION_NOT_FOUND = 1 | ||
| MANDATORY_INPUT_MISSING = 2 | ||
| MULTI_NOVATIONS_NOT_SUPPORTED = 3 | ||
| . " BBP_CTR_NOV_UPDATE | ||
ABAP code using 7.40 inline data declarations to call FM BBP_CTR_NOV_UPDATE
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.| DATA(ld_iv_x_commit_external) | = ' '. | |||
Search for further information about these or an SAP related objects