Oracle Fusion · Data dictionary
CST_SCENARIO_EVENT_MESSAGES
CostingUsed in 1 subject areas16 reporting columns
Cost Management (CST).
Likely primary key: SCENARIO_EVENT_MESSAGE_ID (inferred from Oracle naming conventions — verify against Tables & Views)
Columns
| Column | Key | In reports | Description (inferred) |
|---|---|---|---|
| MESSAGE_NAME | ● | Name of the message. | |
| MESSAGE_TEXT | ● | Message text. | |
| MESSAGE_TYPE | ● | Type of message. | |
| SCENARIO_EVENT_MESSAGE_ID | PK? | ● | Identifier for the scenario event message. |
| TOKEN1_NAME | ● | Name of the token1. | |
| TOKEN1_VALUE | ● | Token1 value. | |
| TOKEN2_NAME | ● | Name of the token2. | |
| TOKEN2_VALUE | ● | Token2 value. | |
| TOKEN3_NAME | ● | Name of the token3. | |
| TOKEN3_VALUE | ● | Token3 value. | |
| TOKEN4_NAME | ● | Name of the token4. | |
| TOKEN4_VALUE | ● | Token4 value. | |
| TOKEN5_NAME | ● | Name of the token5. | |
| TOKEN5_VALUE | ● | Token5 value. | |
| TOKEN6_NAME | ● | Name of the token6. | |
| TOKEN6_VALUE | ● | Token6 value. |
Used by reports
No cataloged report reads from this table yet — it's part of the broader Fusion dictionary.
- —
Where this surfaces in OTBI
The OTBI subject areas that expose this table. You can't join across them in OTBI — the owned conformed model joins them on shared keys.
Need the extract + dbt staging for CST_SCENARIO_EVENT_MESSAGES?
We ship parameterized SQL, BICC config, and dbt models you own.