SAP ABAP Data Element N1POBKLCD (Code for Planning Object Class)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM (Application Component) Customer Relationship Management
⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ NORD (Package) R/3MED: Services processing EDV-G
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
NORD (Package) R/3MED: Services processing EDV-G
Basic Data
| Data Element | N1POBKLCD |
| Short Description | Code for Planning Object Class |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | N1POBKLCD | |
| Data Type | CHAR | Character String |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| Value Table | N1POBKL |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | PLANOBJECT | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | PlnObjClss |
| Medium | 14 | Pln.Obj.Class |
| Long | 20 | Plan. Obj. Class |
| Heading | 10 | Pln.Obj.Cl |
Documentation
Definition
A planning object class groups together several planning objects. Common characteristics that apply to all planning objects in the class can be defined for a class.
Example:
An OR requires prep and clean-up times for the execution of a certain operation. These times can be stored based on service and the planning object class "OR". This then applies for all planning objects of the type "Room" that belong to the planning object class "OR".
History
| Last changed by/on | SAP | 20050409 |
| SAP Release Created in |
