--- title: "Sub batch change approval" slug: "sub-batch-change-approval" description: "Manage sub-batch change approvals in Life Sciences Supply Chain Management, ensuring thorough review and compliance before system updates." tags: ["Life Sciences", "Supply Chain Management"] updated: 2026-06-26T07:17:00Z published: 2026-06-26T07:17:00Z canonical: "docs.staedean.com/sub-batch-change-approval" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.staedean.com/llms.txt > Use this file to discover all available pages before exploring further. # Sub batch change approval Life Sciences Supply Chain Management enables users to manage the sub batch change approval workflows, thus allowing a review of sub-batch changes before they are applied in the system. Users can enable the workflow by setting the **Enable sub batch change approval** parameter to **Yes** in the **Inventory and warehouse management parameters** form (**Inventory management > Setup >Inventory and warehouse management parameters > Proposed changes** tab > **Sub batch change approval** FastTab). In the list of fields, users can select the **Enable** checkbox for every field that must be approved before the changes can be made. The following fields are available: | **Field** | **Form** | | --- | --- | | **Expiration date** | Sub batches | | **Manufacturing date** | Sub batches | | **Shelf advice date** | Sub batches | | **Best before date** | Sub batches | | **Destroy by date** | Sub batches | | **Desiccant expiration date** | Sub batches | | **Container opening date** | Sub batches | | **Use code** | Sub batches | | **Stopped** | Sub batches | | **Storage condition** | Sub batches | | **Container configuration** | Sub batches | | **Restriction** | Restrictions | | **Restriction type** | Restriction types | Some of the sub-batch properties can be updated using the [copy from batch functionality](/life-sciences/docs/copy-sub-batch-information-from-batch). The following parameters can be enabled/disabled to define if the action of copying information from the parent batch should trigger the change approval workflow: - **Copy dates from batch**: if disabled, the change approval workflow is not triggered when copying the dates from the parent batch to the selected sub-batches. - **Copy storage condition**: if disabled, the change approval workflow is not triggered when copying the storage condition from the parent batch to the selected sub-batches. - **Copy restrictions**: if disabled, the change approval workflow is not triggered when copying the restrictions from the parent batch to the selected sub-batches. - **Copy restriction types**: if disabled, the change approval workflow is not triggered when copying the restriction types from the parent batch to the selected sub-batches. - **Copy use code**: if disabled, the change approval workflow is not triggered when copying the use code from the parent batch to the selected sub-batches. - **Copy container configuration**: if disabled, the change approval workflow is not triggered when copying the container configuration from the parent batch to the selected sub-batches. > [!NOTE] > Note > > If the parameters above are enabled and multiple sub-batches are selected when copying the properties of the parent batch, the change approval workflow must be processed for each of the modified sub-batches to confirm the proposed changes. In the **Data entity behavior** field, users can select the action that should be used when data is imported: - **Allow changes without approval** – The data entity can update the sub-batch without processing it through the workflow. - **Reject changes** – Changes cannot be made to the sub-batch. The import will fail for the fields that are enabled for the workflow. - **Create change proposals** – All fields will be changed except the fields that are enabled for the workflow. The new values for those fields will be added to the sub-batch as proposed changes. The data entity will not automatically start the workflow, and users must submit the proposed changes as required. The workflow name is **Proposed sub batch changes workflow**. The workflow template can be setup in the **Inventory management workflows** form (**Inventory management > Setup >Inventory management workflows**). STAEDEAN Life Sciences workflow templates leverages D365 F&SCM workflow engines and standards. Please refer to the Microsoft Dynamics 365 Finance & Supply Chain Management training material for information on how to configure a workflow instance. Users can set up the workflow according to the required approval process. The **Workflow approval for proposed sub batch change** workflow approval element applies the changes to the sub-batch. When a field that is enabled for the workflow is changed: - The **Proposed changes** page appears, showing the original and new values of the field. - The changed field is reverted to its original value. - A status message informs that the changes have been logged but have not yet been submitted to the workflow. All changed fields (unless they are not enabled for the workflow) are added to the list on the **Proposed changes** page. To discard the proposed value for a field, use the **Discard** button next to the field in the list. To discard all changes, use the [**Discard all changes**](/life-sciences/docs/change-approval-workflows-setup) button, if enabled, at the bottom of the page. Select **OK** to close the page. When there is at least one proposed change, two additional buttons are displayed in the Action Pane: - The **Proposed changes** button opens the **Proposed changes** page, thus allowing the user to review the changes. - The **Workflow > Submit** button allows to submit the changes to workflow. The **Workflow status of proposed change** field is changed from **Changes not submitted** to **Changes pending approval**. The workflow follows the standard workflow process. The approver is directed to the **Released product details** page, where they can review the changes on the **Proposed changes** page and then select **Workflow > Approve** to approve or **Workflow > Reject** to reject them. A [reason code](/life-sciences/docs/change-approval-workflows-setup) and a comment must be entered. After all approvals are completed, the fields are updated with the proposed values. ## Related - [Copy sub-batch information from batch](/copy-sub-batch-information-from-batch.md) - [Change approval workflows setup](/change-approval-workflows-setup.md)