# About Batch Disposition Checks

_Batch Disposition Checks_ are a logical unit of work that needs to be completed before a usage decision is made for a _Batch Disposition_. _Batch Disposition Checks_ group similar _Batch Disposition Items_ together that support the decision, such as batch documents, test results, and _Quality Events_.

## Check Batch Genealogy {#genealogy-check}

Admins can configure _Batch Disposition Check Requirements_ to use _Include Genealogy_, which ensures that Vault monitors the _Quality Events_, _Documents_, and _Batch Dispositions_ related to any batch used to make a dispositioned batch. This allows users to discover and address any latent deviations in the manufacturing process, check _Quality Events_ for any automatically dispositioned batches that may have been skipped, and check the status of any manually dispositioned batches.

Users can run the _Genealogy_ check by selecting **Full**, **By Exception**, or **No** from the _Include Genealogy_ picklist. When a _Batch Disposition_ is created, _Full Genealogy Check Batch Disposition Items_ are created for genealogy batches when the _Include Genealogy_ value is **Full**; an error message is displayed if no _Genealogy_ records are found. Vault displays the _Batch Disposition Items_ in the _Check_ section and includes the related record, material, batch, title, and state. Any changes to the batch genealogy need to be assessed for new or canceled _Batch Disposition Check Items_.

## Check By Exception {#by-exception}

The _By Exception Genealogy_ check ensures that _Batch Disposition Items_ in a batch's genealogy are not rechecked if the item already has been checked for a previously closed and approved _Batch Disposition_. While the standard _Genealogy Batch_ check allows users to review all _Quality Events_ associated with the batches used to create a batch, setting _Include Genealogy?_ to _By Exception_ avoids rechecking any of these types of items that have already been checked and released. The _By Exception Genealogy_ check surfaces only latent _Deviations_ or _Quality Events_ associated with batches that were automatically dispositioned and not checked.

Users can run the _By Exception Genealogy_ check by selecting **By Exception** from the _Include Genealogy_ picklist.

### Genealogy Check Configuration {#check-configuration}

Complete the following steps to configure the _Include Genealogy Batch Disposition Check_:

1. Configure the _Include Genealogy_ (`batch_disposition_check_requirement__v.include_genealogy__v`) picklist field, and add the values of **Full**, **By Exception**, and **No** to the picklist.
2. Add the _Include Genealogy_ field to the standard layout for all _Batch Disposition Check_ types.
3. Configure the _Materials_ (`disposition_check_item__v.material__v`) lookup field to display _Batch Disposition Check Items_ in the _Check_ section.

#### Release Exception Decisions

When _Include Genealogy?_ is set to _By Exception_, users can select _Release Exception Decisions_. When a disposition decision matches the _Release Exception Decision_, Vault does not create a related _Batch Disposition Item_, preventing users from needing to review items that were previously reviewed and accepted.

## Include Genealogy Source Data {#source-data}

Using _Include Genealogy_ when you perform a _Batch Disposition Check_ requires using the batch's as-built or as-designed bill of materials (BOM), with the as-designed BOM being used when the as-built BOM is not available. The as-built BOM is managed using _Related Batch_ records, and the as-designed BOM is managed using _Related Material_ records. Using the as-designed BOM is valuable when you are monitoring _Change Controls_ that are related to _Materials_, without requiring the _Full Batch Genealogy_. Using _Include Genealogy By Exception_ is not supported when you are using the as-designed BOM. When you use the as-built BOM, set the _Relationship Type_ field on the _Related Material_ record to **BOM**.

When you execute the _Generate Material Genealogy_ action on _Material_ records, Vault also automatically creates _Material Genealogy_ records, which establishes a relationship between the _Material_ record and all of the materials used to make it. Any time a _Related Material_ is updated, the _Material Genealogy_ record is updated as well.

### Material Genealogy Configuration {#material-genealogy-configuration}
Admins can configure the **Generate Material Genealogy** action on the _Material_ (`material__v`) object lifecycle.

## Bill of Materials Check

You can check a batch's as-built genealogy against its as-designed BOM to ensure that they match. This ensures that manufacturers produce a product to specification, such as ensuring that the correct and latest artwork, labels, packaging, and instructions are included. If you add a _Bill of Materials_ check to a _Batch Disposition Plan_, the system creates _Batch Disposition Items_ for any discrepancies between the batch genealogy and the BOM, such as a _Material_ missing from either, in the _Batch Disposition_. A trigger on the _Related Material_ record and the _Batch Genealogy_ record will create and close the _Batch Disposition Items_ when the discrepancies are discovered or resolved due to BOM changes.

### Bill of Materials Check Configuration

To configure the _Bills of Materials_ check, add the _Bill of Materials Check_ (`bill_of_materials_check__v`) object type to the _Batch Disposition Check Requirement_ and _Batch Disposition Check_ objects.

## Change Control Check {#change-control}

The _Change Control Check_ monitors approved and implemented _Change Controls_ related to a batch or its material for an impacted organization. This ensures that all changes related to a batch's materials and its batch genealogy are reviewed before users make a disposition decision for the batch.

By default, this check creates _Batch Disposition Check Items_ for all _Change Controls_ in the _Approved_ state type related to a batch's material, including the materials in the batch genealogy when appropriate. To configure which states should be monitored instead of the default, select the state types in the _Change Control Check Requirement Change Control State_ field. If impacted organizations are selected on the _Change Control_, Vault monitors the impacted organization only if the batch was manufactured by the organization. If no impacted organizations are associated with the _Change Control_, Vault then monitors batches manufactured at any organization. A trigger on the _Change Control Check_ updates open _Batch Dispositions_ when records are created or updated. The standard _Change Control Batch Disposition Check_ will continue to monitor _Change Controls_ related to batches.

### Change Control Check - Materials Configuration {#change-control-configuration}

To configure the _Change Control - Material Batch Disposition Check_, configure the _Material_ (`disposition_check_item__v.material`) object relationship field to store the related material.

## Batch Disposition Check Status {#check-status}

To help improve reporting on _Batch Dispositions_ and _Batch Disposition Checks_, the following boolean fields are available:

- **Item State Roll-up:** This field is set **True** when all items on a _Batch Disposition Check_ are _Closed_.
- **Check Decision Roll-up:** This field is set to **True** when all check decisions on a _Batch Disposition_ are _Compliant_.
- **Check State Roll-up:** This field is set to **True** when all _Batch Decision Checks_ on a _Batch Disposition_ are _Complete_.

These fields provide visibility to the _Batch Disposition Check_ status when users run a _Batch Disposition Report_ or review the _Batch Disposition Checks_ in the _Batch Disposition_ list view.