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 | PKGZDT |
| Short Description | Date of Next Planned Receipt |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | DATUM | |
| Data Type | DATS | Date field (YYYYMMDD) stored as char(8) |
| Length | 8 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| 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 | Receipt |
| Medium | 15 | Planned Receipt |
| Long | 20 | Planned Receipt |
| Heading | 15 | Planned Receipt |
Documentation
Definition
Use
By entering the date and time (from/to), you can restrict selection of the affected kanban containers. The system converts the start date/time and end date/time entered into timestamps. The latter facilitate the selection of planned receipts (purchase order proposals). The system stores the planned delivery date/time or availability date/time of an order proposal as a timestamp.
This timestamp is determined when the kanban is set to "Empty". Setting the kanban to "Empty" leads to the creation of a purchase order proposal, which is forward-scheduled in accordance with the master data. The result of the forward scheduling is noted in the kanban item as a "planned receipt" (timestamp). The timestamps of the kanban item are checked at the time of selection.
Dependencies
Example
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in |
