SAP ABAP Data Element PK_REUSEHZ (Reuse Horizon for Planned Orders)
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 | PK_REUSEHZ |
| Short Description | Reuse Horizon for Planned Orders |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | DEC03 | |
| Data Type | DEC | Counter or amount field with comma and sign |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 4 | |
| 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 | Horizon |
| Medium | 15 | Reuse Horizon |
| Long | 35 | Production Plan Reuse Horizon |
| Heading | 35 | Reuse Horizon |
Documentation
Definition
Horizon for use of MRP planned orders in Kanban.
Use
Enter in this field the working days (according to plant calendar) within which a planned order can be assigned to an empty kanban container.
You must have previously set up the system in such a way that planned orders generated in MRP can be used for Kanban. The system then attempts to use a planned order created by MRP for Kanban when a kanban container is set to empty, instead of creating a new planned order. Assignment is possible only if the planned order has the same lot size as the kanban container.
Dependencies
Example
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in | 700 |