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 | SPLITTUNG |
Short Description | Required splitting |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XFELD | |
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 | Req.spltng |
Medium | 15 | Req. splitting |
Long | 20 | Required splitting |
Heading | 7 | ReqSplt |
Documentation
Definition
You use this indicator to specify that the operation must be split for scheduling.
If you do not set it, the operation is split in reduction, if you entered splitting in the reduction strategey.
Use
The following options exist for splitting operations:
- You can enter a maximum number of splits.
The system distributes the lot procssing or operation processing into partial lots or amongst the individual capacities.
- You can enter a minimum processing time
In this economical splitting the system determines the number of splits by dividing the processing time of the operation by the minimum processing time.
In both cases the system uses at the most the number of individual capacties that are assigned to the capacity that is used for scheduling.
If you have set the required splitting indicator and have not entered either a minimum processing time or a maximum number of splits, the system distributes the lot processing or operation processing amongst the individual capacities used for scheduling.
Dependencies
An operation is only split, if you have specified via its control key that it is to be scheduled.
History
Last changed by/on | SAP | 19981210 |
SAP Release Created in |