SAP CP_BD_EDIT_KNOWLEDGE Function Module for NOTRANSL: Beziehungswissen-Zuordnungen zu Planobjekten speichern (DIRECT I
CP_BD_EDIT_KNOWLEDGE is a standard cp bd edit knowledge SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Beziehungswissen-Zuordnungen zu Planobjekten speichern (DIRECT I 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 cp bd edit knowledge FM, simply by entering the name CP_BD_EDIT_KNOWLEDGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CPBD
Program Name: SAPLCPBD
Main Program: SAPLCPBD
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CP_BD_EDIT_KNOWLEDGE 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 'CP_BD_EDIT_KNOWLEDGE'"NOTRANSL: Beziehungswissen-Zuordnungen zu Planobjekten speichern (DIRECT I.
EXPORTING
* DISPLAY = ' ' "
ALLOCATION_NUMBER = "Number of Object with Assigned Dependencies
TABLE = "Table ID for object
* ECM_NUMBER = "Change Number
IMPORTING
ALLOCATION_NUMBER = "Number of Object with Assigned Dependencies
UPDATE = "Generic Type
TABLES
KNOWL_ALLOC_DI_TAB = "API Structure for Allocations for Object Dependencies
* KNOWL_BASIC_DI_TAB = "API Structure for Basic Data of Dependency
* KNOWL_NAMES_DI_TAB = "API Structure for Lang-Dependent Dependency Descriptions
* KNOWL_DOCUS_DI_TAB = "API Structure for Dependency Documentation
* KNOWL_SOURCE_DI_TAB = "API Structure for Sources of Dependency
EXCEPTIONS
ERRORS = 1
IMPORTING Parameters details for CP_BD_EDIT_KNOWLEDGE
DISPLAY -
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
ALLOCATION_NUMBER - Number of Object with Assigned Dependencies
Data type: CUOB-KNOBJOptional: No
Call by Reference: No ( called with pass by value option)
TABLE - Table ID for object
Data type: CUOB-KNTABOptional: No
Call by Reference: No ( called with pass by value option)
ECM_NUMBER - Change Number
Data type: CUOB-AENNROptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CP_BD_EDIT_KNOWLEDGE
ALLOCATION_NUMBER - Number of Object with Assigned Dependencies
Data type: CUOB-KNOBJOptional: No
Call by Reference: No ( called with pass by value option)
UPDATE - Generic Type
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CP_BD_EDIT_KNOWLEDGE
KNOWL_ALLOC_DI_TAB - API Structure for Allocations for Object Dependencies
Data type: RCUOB1Optional: No
Call by Reference: No ( called with pass by value option)
KNOWL_BASIC_DI_TAB - API Structure for Basic Data of Dependency
Data type: RCUKB1Optional: Yes
Call by Reference: No ( called with pass by value option)
KNOWL_NAMES_DI_TAB - API Structure for Lang-Dependent Dependency Descriptions
Data type: RCUKBT1Optional: Yes
Call by Reference: No ( called with pass by value option)
KNOWL_DOCUS_DI_TAB - API Structure for Dependency Documentation
Data type: RCUKDOC1Optional: Yes
Call by Reference: No ( called with pass by value option)
KNOWL_SOURCE_DI_TAB - API Structure for Sources of Dependency
Data type: RCUKN1Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERRORS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CP_BD_EDIT_KNOWLEDGE 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_errors | TYPE STRING, " | |||
| lv_display | TYPE STRING, " SPACE | |||
| lv_allocation_number | TYPE CUOB-KNOBJ, " | |||
| lt_knowl_alloc_di_tab | TYPE STANDARD TABLE OF RCUOB1, " | |||
| lv_update | TYPE C, " | |||
| lv_allocation_number | TYPE CUOB-KNOBJ, " | |||
| lt_knowl_basic_di_tab | TYPE STANDARD TABLE OF RCUKB1, " | |||
| lv_table | TYPE CUOB-KNTAB, " | |||
| lt_knowl_names_di_tab | TYPE STANDARD TABLE OF RCUKBT1, " | |||
| lv_ecm_number | TYPE CUOB-AENNR, " | |||
| lt_knowl_docus_di_tab | TYPE STANDARD TABLE OF RCUKDOC1, " | |||
| lt_knowl_source_di_tab | TYPE STANDARD TABLE OF RCUKN1. " |
|   CALL FUNCTION 'CP_BD_EDIT_KNOWLEDGE' "NOTRANSL: Beziehungswissen-Zuordnungen zu Planobjekten speichern (DIRECT I |
| EXPORTING | ||
| DISPLAY | = lv_display | |
| ALLOCATION_NUMBER | = lv_allocation_number | |
| TABLE | = lv_table | |
| ECM_NUMBER | = lv_ecm_number | |
| IMPORTING | ||
| ALLOCATION_NUMBER | = lv_allocation_number | |
| UPDATE | = lv_update | |
| TABLES | ||
| KNOWL_ALLOC_DI_TAB | = lt_knowl_alloc_di_tab | |
| KNOWL_BASIC_DI_TAB | = lt_knowl_basic_di_tab | |
| KNOWL_NAMES_DI_TAB | = lt_knowl_names_di_tab | |
| KNOWL_DOCUS_DI_TAB | = lt_knowl_docus_di_tab | |
| KNOWL_SOURCE_DI_TAB | = lt_knowl_source_di_tab | |
| EXCEPTIONS | ||
| ERRORS = 1 | ||
| . " CP_BD_EDIT_KNOWLEDGE | ||
ABAP code using 7.40 inline data declarations to call FM CP_BD_EDIT_KNOWLEDGE
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_display) | = ' '. | |||
| "SELECT single KNOBJ FROM CUOB INTO @DATA(ld_allocation_number). | ||||
| "SELECT single KNOBJ FROM CUOB INTO @DATA(ld_allocation_number). | ||||
| "SELECT single KNTAB FROM CUOB INTO @DATA(ld_table). | ||||
| "SELECT single AENNR FROM CUOB INTO @DATA(ld_ecm_number). | ||||
Search for further information about these or an SAP related objects