Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ CP (Package) R/3 Application development: PP Task Lists
Basic Data
Data Element | PLNNR |
Short Description | Key for Task List Group |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | PLNNR | |
Data Type | CHAR | Character String |
Length | 8 | |
Decimal Places | 0 | |
Output Length | 8 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | PLN | |
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Group |
Medium | 15 | Group |
Long | 20 | Group |
Heading | 8 | Group |
Documentation
Definition
Key identifying a group.
Use
You can use groups, for instance, to identify two routings that have different production steps for one material.
Procedure
Enter the group to which you want to restrict the selection.
Supplementary Documentation - PLNNR 0001
Procedure
To search for a PS text, enter the number of a standard network and press F16.
Supplementary Documentation - PLNNR 0002
Use
If you are maintaining relationships, this field specifies the number of the standard network containing the activity for which you maintain the relationship.
Supplementary Documentation - PLNNR 0003
Procedure
Enter the key of the standard network that you want to transfer from the project management system into an MPX file.
Supplementary Documentation - PLNNR 0004
Dependencies
You can set the key alphanumerically for the group when you create a task list.
If you do not specify a key, a numeric key will be assigned internally by the system.
In the case of external number assignment, you must make sure that the number you specify is within the number range defined for the task list type you are creating.
Supplementary Documentation - PLNNR 0005
Use
Procedure
If you want to limit the selection, enter a group.
Examples
Dependencies
Supplementary Documentation - PLNNR 0033
Procedure
To search for PS texts used in a library network, enter the key for the library network here and press Enter.
Supplementary Documentation - PLNNR 0060
Procedure
Enter the routing/plan group of the routing/plan that you want to change using this change number.
Supplementary Documentation - PLNNR 0660
Use
Enter the task list group of a reference operation set.
Supplementary Documentation - PLNNR 0700
Use
Procedure
Assign a numeric or alphanumeric key here if you want to combine several task lists into one group.
You can assign a numeric key (external assignment) or let the system assign one for you (internal assignment).
If you assign a number externally, make sure it is within the number range for external number assignment. Number ranges are dependent on task list type.
Examples
Dependencies
If you do not enter a group when creating a routing, the system assigns a group from the internal number range. You see the group number on the status line when you save your routing. You can use the group number to change and display the routing. Later you can allocate a material to a task list which you created in this way.
Supplementary Documentation - PLNNR 1000
Definition
Key indicating a library network.
Procedure
To search for PS texts in library network, type in the key for a library network and press Enter.
Supplementary Documentation - PLNNR 2000
Definition
Key indicating a library network.
Supplementary Documentation - PLNNR 3000
Use
For maintenance plans with the maintenance call object notification, you do not, as a rule, have to assign a task list to a maintenance item.
You should only specify a task list if you later want to combine the generated notifications in an order using the list editing function for notifications ("Worklist for planned maintenance").
If you generate an order using the worklist, the system copies the operations of the task list to the order.
Dependencies
Example
History
Last changed by/on | SAP | 19991124 |
SAP Release Created in |