Hierarchy

⤷

⤷

Basic Data
Data Element | RMPU_ISKANB |
Short Description | Indicator: Kanban part |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XFELD | |
Data Type | CHAR | Character String |
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 | Kanb.part |
Medium | 15 | Kanban part |
Long | 20 | Kanban part |
Heading | 4 | Knbn |
Documentation
Definition
Specifies that components in the storage location are replenished using KANBAN.
Use
Procedure
In the pull list, the system can trigger replenishment using event-driven KANBAN if an appropriate control cycle exists. Requirements which have been assigned this indicator should only be processed using this function.
Avoid mixed cases in the pull list. At a certain storage location, a component is to be provided;
- Only via the pull list using stock transfer
- Only using KANBAN
- Only using storage location MRP
You can easily combine conventional and event-driven KANBAN within a storage location.
Examples
Dependencies
Kanban container quantities are managed in the system as a part of the storage location stock. At storage location level, you cannot differentiate which portion of the storage location stock is part of a kanban control cycle.
Therefore, the missing parts calculation in the pull list may provide incorrent results if kanban control cycles exist in the storage location.
History
Last changed by/on | SAP | 19970923 |
SAP Release Created in |