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 | PKSFG |
| Short Description | Status Sequence Kanban |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | PKSFG | |
| Data Type | CHAR | Character String |
| Length | 4 | |
| Decimal Places | 0 | |
| Output Length | 4 | |
| Value Table | TPKSF |
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 | Stat. Seq. |
| Medium | 15 | Status Sequence |
| Long | 20 | Status Seq. Kanban |
| Heading | 5 | Seq. |
Documentation
Definition
The status sequence defines which kanban statuses must, should, can, or must not be used in Kanban processing. The status sequence is assigned in the control cycle.
If no status sequence is defined in the control cycle, the statuses "Full" and "Empty" must be used. All other statuses are optional. If the control cycle is defined with an independent supply source, the status "Waiting" is additionally a mandatory status.
Note
If a status sequence is defined in the control cycle and if a kanban signal (kanban status change) is triggered with no specification of the follow-on status, the system searches for the next mandatory or optional status in the status sequence. If you specify the follow-on status, the system can skip recommended statuses and you can also use optional statuses.
For individual status changes within the status sequence, you can also specify whether activities defined by yourself (such as goods receipt, kanban print, user exit) are to be executed. In this case, you must maintain these own activities for the the status sequence in Customizing for Kanban.
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in |
