ores.refdata.purpose_type
Table of Contents
Reference data table defining valid purpose type values. Examples: 'Hedging', 'Trading', 'Investment'.
Purpose types are managed by the system tenant and are used to classify the intent of portfolio records.
1. Flags
2. Columns
2.1. code
Unique purpose type code.
Examples: 'Hedging', 'Trading', 'Investment'.
std::string("PurposeType")
2.2. name
Human-readable name for the purpose type.
std::string(faker::word::adjective()) + " Purpose"
2.3. description
Detailed description of the purpose type.
std::string(faker::lorem::sentence())
2.4. display_order
Order for UI display purposes.
faker::number::integer(1, 100)
3. SQL
3.1. Flags
3.2. Extra drops
drop function if exists ores_refdata_validate_purpose_type_fn;
4. Validation function
5. Insert trigger
5.1. Validations
| column | validation_function |
|---|---|
| change_reason_code | ores_dq_validate_change_reason_fn |
6. C++
6.1. Flags
6.2. Repository
6.3. Domain includes
#include <string>
6.4. Entity includes
#include <string>
6.5. Conventions
6.6. Table display
| column | header |
|---|---|
| code | Code |
| name | Name |
| description | Description |
| display_order | Display Order |
| modified_by | Modified By |
| version | Version |
6.7. Presentation
6.7.1. Columns
| enum_name | field | header | type | width | is_badge | badge_key |
|---|---|---|---|---|---|---|
| Code | code | Code | string | auto | true | purpose_type |
| Name | name | Name | string | auto | ||
| Description | description | Description | string | auto | ||
| DisplayOrder | display_order | Display Order | int | 70 | ||
| Version | version | Version | int | 70 | ||
| ModifiedBy | modified_by | Modified By | string | auto | ||
| RecordedAt | recorded_at | Recorded At | timestamp | auto |
6.8. Custom repository methods
7. See also
- ores.refdata — component group overview.