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_REUSEST |
| Short Description | Reuse Strategy for Planned Orders |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | PK_REUSEST | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| 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 | PrPl. Use |
| Medium | 15 | Prodn Plan Use |
| Long | 30 | Use of Production Plan |
| Heading | 36 | Use of Production Plan for Kanban |
Documentation
Definition
Use of MRP planned orders for Kanban.
Use
Through this setting, you can specify that planned orders generated in the MRP run are to be used in Kanban. This makes sense, for example, if you have already specified the sequence of your planned orders using the sequencing functionality and do not want a new planned order to be scheduled within this sequence.
Instead of creating a new planned order, the system will attempt to use a planned order created by MRP when a kanban container is set to empty. With this setting, you specify the preconditions under which the planned orders are taken into account in this process.
You have the following options:
- No planned orders are used. Instead, a new planned order is generated when a kanban is set to empty.
- Only planned orders that have the same production version as that of the control cycle are used.
- Both planned orders that have the same production version as that of the control cycle and planned orders without a production version are used.
- All planned orders with or without a production version are taken into account.
In order that a planned order generated by MRP can be assigned to a kanban container, however, irrespective of this setting, the lot size of the planned order must match up with the kanban quantity. If this is not the case, a new planned order is generated when the kanban is set to empty.
Dependencies
You have chosen an in-house-production strategy with the control type Processing with Planned Orders and Cost Collector or Processing with Planned Orders/Preplanning with MRP.
Example
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in | 700 |
