Batches
Captures batch-level data for manufacturing, clinical, or distribution processes. This includes metadata such as batch IDs, production dates, and associated documentation, enabling traceability and quality control.
Columns
| Name | Type | ReadOnly | Description |
| ID [KEY] | String | True |
Unique system-generated identifier for the batch record. This value is immutable and used for internal reference. |
| Name | String | True |
Descriptive name assigned to the batch, typically reflecting the contents or purpose of the batch process. |
| Status | String | True |
Current status of the batch, such as Active, Inactive, or Archived, which reflects its availability or lifecycle stage. |
| Description | String | False |
Detailed narrative or summary that explains the purpose, scope, or contents of the batch. |
| External ID | String | False |
Identifier assigned to the batch by an external system or integration, enabling cross-system reference and traceability. |
| Created By | String | True |
Username or identifier of the user who initially created the batch record in the system. |
| Created Date | Datetime | True |
Timestamp indicating when the batch record was first created in the Veeva Vault environment. |
| Last Modified By | String | True |
Username or identifier of the user who last modified the batch record. |
| Last Modified Date | Datetime | True |
Timestamp representing the most recent update to the batch record, reflecting changes in metadata or status. |
| Lifecycle | String | True |
Assigned lifecycle that governs the batch's state transitions, validation rules, and business processes. |
| Lifecycle State | String | True |
Current state within the assigned lifecycle, such as Draft, In Review, or Approved, indicating its workflow progress. |
| Global ID | String | True |
Globally unique identifier used internally by Veeva Vault to ensure record consistency across environments and integrations. |
| Link | String | False |
URL or internal reference link that allows direct access to the batch record within the Vault interface. |