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 | PKLOG |
| Short Description | Logic for Setting Kanban to Empty |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | PKLOG | |
| 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 | Replenish. |
| Medium | 15 | Trigger Replen. |
| Long | 20 | Trigger Replenishmnt |
| Heading | 3 | Lgc |
Documentation
Definition
Usually the replenishment for a kanban is triggered if the kanban is set to the status, "empty".
By selecting another logic, you can instruct the system to trigger replenishment for a kanban B that is set to the inactive status "wait" if a signal is given for another kanban A.
These signals for triggering replenishment include:
- Setting the status to "in use":
Here, the replenishment is triggered for kanban B when kanban A is set to the status "in use".
- Setting the status to "wait"
Here, the replenishment is triggered for kanban B when kanban A is set to the status "wait".
- Arriving at or exceeding the trigger quantity:
Here, the replenishment is triggered for kanban B when the actual quantity of kanban A is reduced to the trigger quantity or falls below the trigger quantity due to the quantity signal. The trigger quantity must also be maintained in the control cycle.
Then kanban A is first set to status "wait". The replenishment for kanban A is triggered when the appropriate signal is given for the subsequent kanban.
The purpose of this special logic is to set up a so-called single-card kanban with with two kanbans in a control cycle. Because a kanban is set to the inactive status, "wait" for certain periods, the stocks at the demand source can be further reduced - which is especially useful if the material is not always required.
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in |
