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 | NLOCK |
| Short Description | Kanban Calculation: Locking of New Kanbans |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | NLOCK | |
| 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 | Lock New |
| Medium | 16 | Lock New Kanbans |
| Long | 20 | Lock New Kanbans |
| Heading | 14 | Lock New Kanb. |
Documentation
Definition
Use
Specifies how the system is to proceed with new kanban containers:
- Do Not Lock New Kanbans
This option is set as standard. If the number of kanban containers has to be increased on the basis of the kanban calculation, the system automatically unlocks the existing locked kanbans in the first step and only creates new kanban containers if the total number of containers is insufficient. All new kanban containers are created with the status WAITING and are not locked but can be used immediately.
This option has the disadvantage that the containers may not be prepared for their use, i.e. that they are not yet labeled or no kanban cards have been printed.
- Locking of New Kanbans from Kanban Calculation
With this setting, you ensure that, as a basic rule, every extension of the control cycle as a result of the automatic kanban calculation leads to locked kanbans.
If you choose this setting, the system determines the existing locked kanbans in the first step of the automatic kanban calculation. These are flagged for unlocking. The flags are set in dependence on the unlocking sequence specified by you.
If the total number of kanbans is insufficient, the system then creates new kanban containers with the status WAITING. The kanban containers are locked. They are flagged for unlocking.
With this setting, the kanban containers added manually in control cycle maintenance are not locked, but can be used immediately.
- Always Lock New Kanbans
With this setting, the system locks all newly added kanban containers irrespective of whether they were added automatically through the kanban calculation or manually by a user in control cycle maintenance. The new kanban containers are created with the status WAITING and are locked. They are flagged for unlocking.
Dependencies
In a second step, you must unlock the locked kanban containers in order to use them. You can do this in the following ways:
- You can unlock the locked kanbans using the transaction Unlock Kanbans.
- You invoke the transaction Collective Kanban Print and check the Unlock Kanbans Automatically After Printout box on the initial screen.
- You can also unlock the kanbans in Control Cycle Maintenance.
Example
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in | 605 |
