SAP ABAP Data Element PK_INDREQ (Consideration of Planned Independent Requirements)
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 | PK_INDREQ |
Short Description | Consideration of Planned Independent Requirements |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | REQCONS | |
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 | PlIndRqmts |
Medium | 15 | Pl. Ind. Reqmts |
Long | 20 | Planned Ind. Reqmts |
Heading | 10 | PlIndRqmts |
Documentation
Definition
Use
If you set this indicator, the system also takes the planned independent requirements for the material you have specified into account in the kanban calculation.
Dependencies
- Planned independent requirements are created either plant-wise or for an MRP area. It is easiest to maintain a quota arrangement assignment in this case by specifying the material and plant here in this transaction and setting a generic storage location (*). The entry then has cross-storage-location validity.
- For planned independent requirements assigned to an MRP area, the kanban calculation searches for an existing distribution record with the receiving storage location of the MRP area. You must therefore specify an entry with the receiving storage location of the MRP area in this case.
Example
History
Last changed by/on | SAP | 20110901 |
SAP Release Created in | 605 |