ores.refdata.party_counterparty
Table of Contents
Junction table controlling which counterparties are visible to which parties. Counterparty identity is shared at tenant level; this junction controls party-level visibility.
1. Flags
2. Left
ID of the party.
References ores_refdata_parties_tbl.id (soft FK).
ctx.generate_uuid()
3. Right
ID of the counterparty visible to this party.
References ores_refdata_counterparties_tbl.id (soft FK).
A counterparty-side read answers which parties may trade with a counterparty, which journey 5 needs and the party-side read cannot answer without scanning the whole junction.
ctx.generate_uuid()
4. Artefact columns
The dataset is scoped to the party a publish names, so it stages the counterparty only, by LEI, because a counterparty id differs from tenant to tenant. A counterparty no LEI of the tenant names is skipped.
4.1. counterparty_lei
4.2. version
5. Columns
6. SQL
6.1. Flags
7. Repository
8. C++
8.1. Flags
8.2. Domain includes
#include <string> #include <boost/uuid/uuid.hpp>
8.3. Entity includes
#include <string>
8.4. Conventions
8.5. Table display
| column | header |
|---|---|
| party_id | Party |
| counterparty_id | Counterparty |
| modified_by | Modified By |
| version | Version |
9. See also
- ores.refdata — component group overview.