SAP ABAP Data Element PLWRK (Planning Plant)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ MD01 (Package) Appl. dev. R/3 consumption driven gen. requirements planning
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ MD01 (Package) Appl. dev. R/3 consumption driven gen. requirements planning
Basic Data
Data Element | PLWRK |
Short Description | Planning Plant |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | WERKS | |
Data Type | CHAR | Character String |
Length | 4 | |
Decimal Places | 0 | |
Output Length | 4 | |
Value Table | T001W |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | WRK | |
Default Component name | PLAN_PLANT | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Plng plant |
Medium | 15 | Planning plant |
Long | 20 | Planning plant |
Heading | 4 | PlPl |
Documentation
Definition
Number which clearly identifies the plant where the forecast, MRP or long-term planning is carried out.
Supplementary Documentation - PLWRK 0001
Use
In Sales & Operations (SOP), this entry allows you to perform resource leveling in two situations:
- The rough-cut planning profile is based on an information structure which does not contain the characteristic "plant".
- The rough-cut planning profile is based on an information structure which does contain the characteristic "plant", but the characteristic values combination being planned includes more than one plant. For example, you plan all the materials in division TOYS and these materials are manufactured in several different plants.
SOP determines the plant for resource leveling as follows:
- Is "plant" one of the characteristics that was specified when the planning table was called up? If so, this is the plant via which the selection ID is determined. If not, the system continues with step 2.
- Has a plant been set in this field? If so, this is the plant via which the selection ID is determined. If not, the system continues with step 3.
- Has a universal SOP plant been set in the new Customizing step "Set planning plant for SOP"? If so, this is the plant via which the selection ID is determined. If not, no resource requirements can be read and resource leveling cannot be carried out.
Procedure
Examples
Dependencies
History
Last changed by/on | SAP | 19981111 |
SAP Release Created in |