Changing Master Data with Dependencies
Purpose
In variant configuration, you can use reference characteristics with dependencies to change field values in bills of material (BOMs), task lists, and master recipes.
Caution
Do not use object dependencies to change control fields, such as internal counters, node numbers, and item categories of BOM items.
For example, you can change the following fields in BOMs, task lists, and master recipes:
STPO (BOM) |
Item text (POTX1 and POTX2) |
Variable-size item sizes 1–3 (ROMS1–3) |
|
Number of variable-size items (ROANZ) |
|
Variable-size item quantity (ROMEN) |
|
Component quantity (MENGE) |
PLPOD (task list and master recipe) |
Activity types (LAR01–06) |
Standard values (VGW01–06) |
|
Unit of measure (VGE01–06) |
|
Work center (ARBPL) |
|
Operation description (LTXA1, LTXA2) |
PLFLD (sequence of operations) |
Lot size from (LOSVN) |
Lot size to (LOSBS) |
PLFHD (production resources/tools) |
Quantity (MGVGW) |
Quantity formula (MGFORM) |
|
Required quantity (EWVGW) |
|
Required quantity formula (EWFORM) |
Process Flow
In characteristics maintenance, create a characteristic with a reference to the table field you require.
Assign the reference characteristic to the variant class. In characteristics maintenance, you can define the reference characteristic as hidden.
Create an action or procedure that uses the reference characteristic to refer to the table.
Note
We recommend that you always use procedures to change master data, not actions.
Allocate the object dependency to a BOM item, an operation, an operation sequence, or a production resource/tool (PRT).
Result
When the action or procedure is triggered, it changes the field value referred to in the reference characteristic.
See also:
Creating a Reference Characteristic
PP Routings
Creating Global Dependencies for an Operation
Creating Local Dependencies for an Operation
PPPI Master recipes