Clone
A clone operation is always carried out from a reference plant to a target plant. The target plant can be identical or different when activated.
Additional view
If a reference plant is set, only target plants according to this setting and target plant = source plant is allowed. Else all defined plants in the system can be used. In order to copy a group or plant BOM, input reference plant = empty is required for the target plant.
Parameter | Parameter Description |
---|---|
Reference Plant | Reference plant |
Plant | Target plant, for which the reference plant is possible. |
Plant views | Defines which of the existing views in the reference plant shall be created for the new plant. Without input, all existing plant views will be copied. |
...
Defines which routings have to be copied. Without entry, all will be ignored. Without target plant (group BOM) the entry will be ignored, too.
Parameter | Parameter Description |
---|---|
Clone Control Reference Plant Plant | According superior view |
Routing Type | Relevant routing type. Valid for routing and test plan |
Usage | Relevant usage.- * allowed, empty = * |
Routings to copy / Status | Status for the new routing. If empty, the current status of the reference routing will be used. |
Use change number | If activated, the routing will be created in relation to the change number. |
...
When copying from one plant to another, certain fields in the new plant view (or routing) must have a different value, because the fields have plant specific contents.
These settings allows the definition of this relation and the storage views which shall be copied.
Parameter | Parameter Description |
---|---|
Field | See table below |
FROM | Value „FROM", always in relation to the reference plant. * allowed |
TO | Value "TO" in relation to target plant |
Values in Field | Function |
---|---|
Storage place | Only valid for clone, not view expansion |
BOM usage | Defines which from which usages to which alternative usages the BOM can be cloned. |
Dispo profile | For a dispo profile all missing and mandatory fields of the corresponding dispo profile will be used and always a dispo view will be created (D). The values will be determined as follows:
|
All other values | Defines how the relevant value will be replace with a new one. If no template value can be found, the source value will be copied identically. |
...