--- alias: merge-material description: "The Merge Material operation combines two or more materials into one, requiring specific data and state matches for successful execution" --- # Merge Material :lock: Material.**RecordLossBonus** ## Overview Merges two or more **Materials** into one. Merge is performed primarily for logistical reasons. As a convention, the **Material** to be merged is referred to as Child **Material** and the **Material** to absorb the Child **Material** is referred to as Main **Material**. !!! info The Merge Material operation is relevant for Genealogy. ## Setup No special setup is required other than to meet the preconditions of the transaction. ## Preconditions * Child **Material** and Main **Material** exist and are Active. * Child **Material** and Main **Material** are not On Hold or In Transit. * Child **Material** and Main **Material** have the Split Merge Restriction Type property set to No Split Or Merge Restrictions or Splits Not Allowed. * The Parent of the Main **Material** and the Child **Material** must be the same (can be `null`). * Child **Material** and Main **Material** have the same: * Facility * Type * Product * Step * Logical Step Name * Is In Line Step * Line Flow Version * System State * Form * Is Approved * Experiment * Is In Store * Off-Flow Stack * Last Processed Resource, if **Material** is In Process and Lane. * Lane (can be `null`) * Current BOM Version * Current BOM Assembly Type * If Main **Material** is Top-Most and it is assigned to a **Resource**, the Child **Material** must also be assigned to the same **Resource**. * Since it is assumed that the Child **Material** will reside at the same Container/Position as the Main **Material**, it must be checked that if the Main **Material** is associated with a **Container** with Capacity Validation Mode set as Units, that the **Container** Capacity Per Position can hold the Main **Material** plus the Child **Material** additional units (Primary Units or Secondary Units as defined in the **Container** Capacity Units - if matching). * If Main **Material** or Child **Material** have a **Production Order** associated with it, the **Production Order** must not be Closed. Additionally, if the Child **Material** has a Restricted **Production Order** associated with it, the Main **Material** must be associated with the same **Production Order**. * The Top-Most of Main **Material** and Top-Most of Child **Material** must have the Transfer Material property set to `null`. * Both the Main **Material** and Child **Materials** must have the same Primary and Secondary units. * The Child **Material** required Future Action must be `null`. * The Main **Material** and the **Sub-Materials** must not have any open defects (Open Defect Count is `0`). * The Characteristics Count of the Main **Material** and Child **Material** must be equal (can be `null`). If not `0` (not `null`), the set of Material Characteristics (Name and Value) must be exactly the same for both the Main **Material** and Child **Material**. * If the Main **Material Product** has its Product Type set to Part and the Part Type set to Repairable, the Main **Material** and the Child **Material** cannot be referenced in any active Resource Part. * If **Material** is Top-Most and **Material** Assembly Type is Packing (or the property Packing Step of the **Step** associated to the **Material** is set to `true` and the **Material** currently has its System State as In Process), for the final Parent **Material** the system must ensure that: * Either the **Material** Primary Quantity or the **Sub-Materials** Primary Quantity must be zero (packing is single level). * The **Material** Primary Quantity plus the **Sub-Materials** Primary Quantity must be greater than `0`. * For Packing/Packaging: * If Assembly Type of Top-Most of Main **Material** is Packing: * The Child **Materials** must be Top-Most. * If the Main **Material** Primary Quantity is `0`, the Child **Material** Primary Quantity is also `0`. * If the Main **Material** Primary Quantity of the **Sub-Materials** is `0`, the Child **Material** Primary Quantity of the **Sub-Materials** is also `0`. * The **Child Material** to be merged must have a single level, and the Sub-Material Count of all **Sub-Materials** must be `0`. * If the **Step** of the **Material** From Packing Level is 2, all Packages of the Main **Material** and Child **Material** of Level 1 (if any) must be of the same **Product** and have the same Is Trackable property. * For Material Rework Counter: * **Materials** can only be merged in these conditions: * The **Product** of the **Child Material** must have the following properties set to `false`: * Apply Global Rework Limit * Apply Step Rework Limits * Apply Reason Rework Limits * If the above conditions are not met, the list of Child **Material** Rework Counters must be empty to allow the merging of **Materials**. * For both the Main **Material** and Child **Material**, the In Process Verification Maintenance Plan Instance property must be `null`. * If the Qualification Count of the Child **Material** is greater than `0` and the Parent **Material** meets the preconditions of [[user-guide-special-manage-qualification-materials]], the Parent **Material** is added to the same **MAOs** as the Child **Material**. If the Parent **Material** does not meet those preconditions, the **Merge** operation is completed and the Parent **Material** is not added to those **MAOs**. ## Preconditions for Bulk * In addition to the preconditions mentioned above, all Child **Materials** must: * Be merged to the same Main **Material**. ## Sequence of Steps ### Step 1: Materials This step is used to select the **Materials** that should be merged into the Parent **Material**. 1. Verify the Parent **Material** information. 2. Select the **Materials** to be attached as **Sub-Materials** by selecting their checkbox(es). 3. Any **Sub-Materials** of the **Materials** to be merged can be seen by selecting the **Sub-Material** count in the right-most column, with the **Sub-Material** logo on the header. 4. If the Child **Materials** have **Sub-Materials**, another step is required. Otherwise, select **Merge** to complete the operation. ![Screenshot showing a list of materials, including "De Mere Materials", with various options and fields.](images/merge_material_step_one.png) !!! info If the Step where the Materials will be merged has the Print Material Labels Automatically property set to `true`, that information will be displayed on the bottom section of the wizard. ![Screenshot showing a checkbox setting for "Print Material Labels Automatically" in a step titled "Step 1: Materials".](images/merge_material_label_printing_automatically.png) ### Step 2: Sub-Material Containers !!! info Only shown if the Child Materials have Sub-Materials. This screen provides the possibility to define a new **Container** and Position for each new **Sub-Material**. 1. For each **Sub-Material** of the Child **Material** it is possible to assign a new **Container** and Position (if the **Container** does not auto-generate its Positions). 2. It is possible to copy the future holds of Child **Materials** to the Main **Material** by selecting the Copy Future Holds property in the Options section. 3. It is possible to copy the future holds of Child **Materials** to the Main **Material** by selecting the Copy Future Holds property in the Options section. 4. It is possible to apply the **Container** of the Main **Material** to the Child **Materials** automatically by selecting the corresponding property in the Options section. 5. Select **Merge** to complete the operation. ![Screenshot showing a UI with options for merging materials, including "Merge" and possibly other related settings.](images/merge_material_step_two.png) !!! info If the Main Material is associated to a Lane when dispatched, the Child Material must be in the same Lane and have the same conditions as the Main Material for the Merge operation to be possible.