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 | RFENT |
| Short Description | Kanban Calculation: Unlocking Sequence |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | RFENT | |
| 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 | Unlock |
| Medium | 15 | Unlock Sequence |
| Long | 20 | Unlocking Sequence |
| Heading | 2 | Sq |
Documentation
Definition
Specifies the sequence in which the system is to unlock locked kanban containers.
Use
If further kanban containers are to be added to a control cycle during the checking of the kanban calculation proposal and this control cycle has locked kanbans, the latter are first unlocked before the system creates new containers.
You can specify which kanbans are to be unlocked first. This is relevant in the case that not all kanbans are unlocked. Those that remain locked may subsequently be deleted preferentially.
You have the following options:
- First unlock kanbans with a low status
If you choose this option, the system first unlocks kanbans with a low status. In this way, the remaining kanbans acquire the status WAITING more quickly. As a result, kanbans that are not needed are removed from circulation as quickly as possible.
- First unlock kanbans with a low kanban item number
If you choose this option, kanbans with a low item number are unlocked first. In this way, the preference is that kanbans with a high number remain locked and may thus be deleted before others. This setting contributes toward achieving a cohesive number range.
Dependencies
Example
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in |
