Hierarchy

⤷

⤷

Basic Data
Data Element | CS_ALPGR |
Short Description | Alternative Item: Group |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CHAR2 | |
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 | ||
Default Component name | ALT_GROUP | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | AltItemGrp |
Medium | 15 | AltItemGroup |
Long | 20 | AltItemGroup |
Heading | 3 | Grp |
Documentation
Definition
Consolidation of alternative items within a BOM. Every material in the assembly can be included in the alternative item group.
Use
As soon as you enter an alternative item group, you see an additional dialog box with the following data: ranking order, strategy, usage probability.
You can maintain alternative items in the following situations:
- Alternative positions with specific usage probability
These alternative items are incorporated with a specific usage probability. Enter the usage probability for each alternative item in the group, so that:
- dependent requirements are determined in requirements planning
- dependent requirements are changed to a reservation in the production order
- Alternative positions as information
You can enter an alternative item for information purposes. This item would then, for example, only be taken into account in situations involving missing parts.
As there should be neither dependent requirements nor a reservation for this item, enter no usage probability.
Procedure
- Enter the same character string to denote the alternative items of an alternative item group.
Enter the same strategy for all alternative items in the alternative item group.
Examples
Dependencies
Alternative items are valuated in the following way:
- Dependent requirements determination
Requirements planning determines the dependent requirements according to the usage probabilities that have been entered.
If the usage probability is 0%, then no procurement is planned for the item. For information purposes, however, dependent requirements with 0 as quantity are created. - Withdrawal posting
You can control the withdrawal posting for the resevation in the production order in the following way:
- Withdrawal according to usage probability (manual change is possible)
- Withdrawal if there is 100% availability
(Check ranking order and strategy)
Example: See Strategy for alternative position
History
Last changed by/on | SAP | 19991102 |
SAP Release Created in |