SAP ABAP Data Element NKNUM (Kanban Calculation: Number Assignment for New Kanbans)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM (Application Component) Customer Relationship Management
⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷
MD05 (Package) Development class KANBAN
⤷
⤷
⤷
Basic Data
| Data Element | NKNUM |
| Short Description | Kanban Calculation: Number Assignment for New Kanbans |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | NKNUM | |
| Data Type | NUMC | Character string with only digits |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | No. Assgt |
| Medium | 15 | Number Assgt |
| Long | 20 | Kanban Number Assgt |
| Heading | 2 | NA |
Documentation
Definition
Specifies the nature of the number assignment for new kanban containers.
Use
If new kanbans are to be added to a control cycle during the checking of the kanban calculation proposal, the system must assign numbers to these new kanbans.
You can choose between the following options:
- Whether new item numbers assigned are always to be higher than the highest existing item number
- Whether any existing gaps in the numbers are to be closed
Dependencies
Example
Assume that you have a control cycle with the kanbans 001, 002, and 003, and you have in the meantime deleted kanban 002. A new kanban is now to be added to the control cycle. Depending on the chosen setting, this can have either the number 004 or the number 002.
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in |