Hierarchy
BBPCRM (Software Component) BBPCRM⤷
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 | PLNAL |
| Short Description | Group Counter |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ALTNR | |
| Data Type | CHAR | Character String |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | PAL | |
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Grp.Countr |
| Medium | 15 | Group Counter |
| Long | 20 | Group Counter |
| Heading | 3 | GrC |
Documentation
Definition
This key and the task list group uniquely identify a task list.
Use
In Production Planning and Control, for example, it serves to identify alternative production processes in task lists and is used to make a distinction between similar task lists.
Examples
The group counter can be used to identify different lot-size ranges, for example.
Supplementary Documentation - PLNAL 0001
Procedure
The routing/plan group counter can be assigned manually or automatically by the system.
If you enter the routing/plan group counter when calling a routing/plan, only the data of the corresponding routing/plan is called up from the data base.
Supplementary Documentation - PLNAL 0002
Use
In standard networks, the group counter identifies an alternative of an existing standard network.
Supplementary Documentation - PLNAL 2200
Definition
Key indicating alternatives to a library network.
Use
There can be several alternatives to a library network.
Supplementary Documentation - PLNAL 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 | 19981210 |
| SAP Release Created in |
