SAP ABAP Data Element GSBAZ (Number of Locked Kanbans)
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
⤷ 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 | GSBAZ |
Short Description | Number of Locked Kanbans |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | BEHAZ | |
Data Type | NUMC | Character string with only digits |
Length | 3 | |
Decimal Places | 0 | |
Output Length | 3 | |
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 | Locked K. |
Medium | 15 | No. Locked Kbns |
Long | 20 | No. Locked Kanbans |
Heading | 20 | No. Locked Kanbans |
Documentation
Definition
Indicates the number of locked kanban containers in the control cycle.
Use
Dependencies
Kanbans can be locked for the following reasons:
- The kanban container was locked manually by a user in control cycle maintenance.
- The kanban container was locked automatically by the system. The system always locks a container if the control cycle size has been adjusted either manually or as a result of the kanban calculation, provided you have defined this in Customizing.
- You are using the lifecycle for control cycles.
Example
History
Last changed by/on | SAP | 20100310 |
SAP Release Created in | 605 |