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
IMG Activity
| ID | SIMG_CFMENUOM00OM26 | Automatically Delete Event-Driven Kanbans |
| Transaction Code | S_KA5_12000514 | (empty) |
| Created on | 20000127 | |
| Customizing Attributes | SIMG_CFMENUOM00OM26 | Automatically Delete Event-Driven Kanbans |
| Customizing Activity | SIMG_CFMENUOM00OM26 | Automatically Delete Event-Driven Kanbans |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUOM00OM26 |
In this IMG activity you can define the conditions under which event-driven kanbans can be automatically deleted from the system. If event-driven kanbans were previously only deleted when you set them from status FULL to status EMPTY, then with automatic deletion, it is always setting the status FULL for one or more kanbans that triggers the deletion.
An entry always refers to all control cycles in a plant. To activate the deletion, enter the maximum number of kanbans, that cannot be deleted, the minimum age in days from which kanbans can be deleted and set the indicator for automatic flow. The conditions for both fields must be fulfilled, so that the automatic deletion can take place. If you do not set the indicator for automatic flow, you can call up the report SAPMKLK. This takes data from Customizing as a proposal and you can trigger the deletion of kanbans manually.
Example
In plant 0001 you have set the maximum number of kanbans to 4 and the maximum age to 1. There are still 4 kanbans from the previous day in the system and 4 new kanbans are set to status FULL.
The system checks in the following way:
The system recognizes that from the 8 kanbans available in the system, 4 could be deleted and it checks their age. As 4 kanbans are older than 1 day, they are deleted.
If, in this example, 2 lots of 4 kanbans are set to FULL on the same day, then all 8 remain in the system as they do not fulfill the prerequisite of being older than a day.
Requirements
Standard settings
Recommendation
Activities
- In Customizing for KANBAN choose Status -> Automatic deletion of event-driven kanbans.
- This takes you to the screen Automatic deletion of event-driven kanbans.
- If you want to define the conditions for automatically deleting event-driven kanbans for all control cycles in a plant, choose New entries.
- Enter the plant, for which you want to define the deletion of event- driven kanbans and maintain the remaining data. If the deletion is to take place automatically, set the indicator for automatic flow.
- Save your entries.
If you do not want to delete automatically, choose System -> Services -> Reporting.
Enter the report SAPMPKLK in Programm and select Execute.
This takes you to the screen Delete event-driven kanbans. Enter the necessary data and choose Execute.
All event-driven kanbans, that correspond to the conditions, are deleted.
Further notes
Business Attributes
| ASAP Roadmap ID | 105 | Define functions and processes |
| Mandatory / Optional | 3 | Nonrequired activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_CFMENUOM00OM26 | 0 | HLA0006760 | KANBAN |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| V_TPKALEK | V - View | SM30 |
History
| Last changed by/on | SAP | 20000209 |
| SAP Release Created in |
