KKB_PARTNER_SPLIT SAP (Partner Cst Comp. Split in Company Code/CO Area Currency) Structure details
Description: Partner Cst Comp. Split in Company Code/CO Area Currency
Related tables to KKB_PARTNER_SPLIT
Access table KKB_PARTNER_SPLIT
Structure field list including key, data, relationships and ABAP select examples
KKB_PARTNER_SPLIT is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "Partner Cst Comp. Split in Company Code/CO Area Currency" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_KKB_PARTNER_SPLIT TYPE KKB_PARTNER_SPLIT.
The KKB_PARTNER_SPLIT table consists of various fields, each holding specific information or linking keys about Partner Cst Comp. Split in Company Code/CO Area Currency data available in SAP. These include BUKRS (Company Code), WERK (Plant), PRCTR (Profit Center), GSBER (Business Area).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can be enhanced (character-type or numeric)
SAP KKB_PARTNER_SPLIT structure fields - Full list of fields found in SAP data dictionary
Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
MATNR | Material Number | MATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | S_MAT1 |
BUKRS | Company Code | BUKRS | CHAR | 4 | Assigned to domain | BUKRS | BUK | C_T001 | |
WERK | Plant | WERKS_D | CHAR | 4 | Assigned to domain | WERKS | WRK | H_T001W_C | |
PRCTR | Profit Center | PRCTR | CHAR | 10 | Assigned to domain | ALPHA | PRCTR | PRC | PRCTR_EMPTY |
GSBER | Business Area | GSBER | CHAR | 4 | Assigned to domain | GSBER | GSB | ||
MATNR_T | Description | KLTXT | CHAR | 40 | TEXT40 | ||||
BUKRS_T | Description | KLTXT | CHAR | 40 | TEXT40 | ||||
WERK_T | Description | KLTXT | CHAR | 40 | TEXT40 | ||||
PRCTR_T | Description | KLTXT | CHAR | 40 | TEXT40 | ||||
GSBER_T | Description | KLTXT | CHAR | 40 | TEXT40 | ||||
VALUES_B | 0 | ||||||||
EGROUP1 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP2 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP3 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP4 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP5 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP6 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP7 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP8 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP9 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP10 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP11 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP12 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP13 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP14 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP15 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP16 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP17 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP18 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP19 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP20 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
SUMME_B | Total value | KKB_VALUE_TOTAL | CURR | 15(2) | WERTV8 | ||||
VALUES_K | 0 | ||||||||
EGROUP1 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP2 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP3 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP4 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP5 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP6 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP7 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP8 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP9 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP10 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP11 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP12 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP13 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP14 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP15 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP16 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP17 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP18 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP19 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
EGROUP20 | Total Value of Cost Estimate | CK_WERTV8 | CURR | 15(2) | WERTV8 | ||||
SUMME_K | Total value | KKB_VALUE_TOTAL | CURR | 15(2) | WERTV8 |
Key field | Non-key field |
How do I retrieve data from SAP structure KKB_PARTNER_SPLIT using ABAP code?
As KKB_PARTNER_SPLIT is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on KKB_PARTNER_SPLIT as there is no data to select.How to access SAP table KKB_PARTNER_SPLIT
Within an ECC or HANA version of SAP you can also view further information about KKB_PARTNER_SPLIT and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects