ores.compute.batch
Table of Contents
Tracks the lifecycle of a collection of workunits that together constitute a financial computation (e.g., a risk report run). The Assimilator monitors batch completion to trigger downstream report generation.
1. Flags
2. Columns
2.1. id
UUID primary key for the batch.
2.2. party_id
The party that submitted the batch, copied from the session when the batch is created. NULL for work that predates the party scope.
2.3. external_ref
External reference linking this batch to the originating finance system or project.
2.4. status
Lifecycle status: open, dispatched, processing, assimilating, or closed. The dispatch command writes dispatched when it has created the batch's workunits.
3. SQL
3.1. Flags
4. Indexes
A page of batches reads newest first, so the tenant's current batches are indexed by their recording time.
4.1. recorded_at
5. C++
5.1. Flags
5.2. Repository
5.3. Domain includes
#include <string>
5.4. Conventions
5.5. Table display
| column | header |
|---|---|
| id | ID |
| external_ref | External Ref |
| status | Status |
| modified_by | Modified By |
| recorded_at | Recorded At |
5.6. Custom repository methods
6. See also
- ores.compute — component group overview.