CRM_KNB5 SAP (Business Partner Dunning Data - Only for Mobile) Structure details
Description: Business Partner Dunning Data - Only for Mobile
Structure field list including key, data, relationships and ABAP select examples
CRM_KNB5 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 "Business Partner Dunning Data - Only for Mobile" 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_CRM_KNB5 TYPE CRM_KNB5.
The CRM_KNB5 table consists of various fields, each holding specific information or linking keys about Business Partner Dunning Data - Only for Mobile data available in SAP. These include KUNNR (Customer Numbers), BUKRS (Company Code), MABER (Dunning Area), MAHNA (Dunning Procedure).. 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)
SAP CRM_KNB5 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 |
| BUPA_GUID | CHAR32 data element for SYST | SYCHAR32 | CHAR | 32 | SYCHAR32 | ||||
| KUNNR | Customer Numbers | KUNNR | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | KUN | C_KUNNR |
| BUKRS | Company Code | BUKRS | CHAR | 4 | Assigned to domain | BUKRS | BUK | C_T001 | |
| MABER | Dunning Area | MABER | CHAR | 2 | Assigned to domain | MABER | |||
| MAHNA | Dunning Procedure | MAHNA | CHAR | 4 | Assigned to domain | MAHNA | |||
| MANSP | Dunning block | MANSP | CHAR | 1 | Assigned to domain | MANSP | |||
| MADAT | Last dunned on | MADAT | DATS | 8 | DATUM | ||||
| MAHNS | Dunning level | MAHNS_D | NUMC | 1 | MAHNS | ||||
| KNRMA | Account number of the dunning recipient | KNRMA | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | KUN | |
| GMVDT | Date of the legal dunning proceedings | GMVDT | DATS | 8 | DATUM | ||||
| BUSAB | Dunning clerk | BUSAB_MA | CHAR | 2 | Assigned to domain | BUSAB | |||
| TASK | Com. Interface: Change Indicator | GC_TASK | CHAR | 1 | CHAR1 |
| Key field | Non-key field |
How do I retrieve data from SAP structure CRM_KNB5 using ABAP code?
As CRM_KNB5 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 CRM_KNB5 as there is no data to select.How to access SAP table CRM_KNB5
Within an ECC or HANA version of SAP you can also view further information about CRM_KNB5 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