Views, Filters & Print
Costs Are Stored in the Base Currency
Costs stored in base currency; view currency is display only
What a planner means
Every cost in the database is stored in one base currency. Default is US dollars. The base exchange rate is always 1.0. The UI marks that row BASE RATE.
A view currency is a user display setting. Displayed cost = stored base × the view currency’s current exchange rate. Oracle example: base USD, view EUR at 0.75 → $10 shows as 7.5 Euros; typing 7.5 Euros stores $10. Entries always show in the user’s view currency.
Admin Superusers / Edit Currency can define more view currencies and edit the base row’s ID, name, and symbol. Install/admin docs: set the base before projects start; you cannot change it once projects begin (script path for an empty database). Do not treat a later UI edit of the BASE RATE label as a stored-cost conversion unless you have a later Oracle page that says so.
This is not a unit of measure and not a cost account.
XER
CURRTYPE (Currency Types):
| Column | Oracle label |
|---|---|
curr_id | Unique ID |
curr_short_name | Currency ID |
curr_type | Currency Name |
curr_symbol | Currency Symbol |
base_exch_rate | Exchange Rate |
decimal_digit_cnt | Number of Digits after Decimal |
decimal_symbol | Decimal Symbol |
digit_group_symbol | Digit Grouping Symbol |
group_digit_cnt | Currency Group Digit Count |
pos_curr_fmt_type | Positive Currency Format |
neg_curr_fmt_type | Negative Currency Format |
There is no “is base” flag on the map. Base is the rate-1.0 row. Format-type stored tokens are unverified.
RSRC.curr_id is labeled Currency Name. No PROJECT currency column on the cited project map. View currency is a user preference, not a project XER table.
Microsoft Project
MSP allows one currency per project (File > Options > Display: symbol, placement, decimal digits). Consolidating files with different currencies means you change each file to a common currency and update costs yourself. There is no base/view pair and no exchange-rate table. Do not map CURRTYPE to MSP Cost.
Don't
- Treat displayed view-currency amounts as the stored numbers.
- Invent a PROJECT currency or a base-currency flag.
- Invent
pos_curr_fmt_type/neg_curr_fmt_typetokens. - Map CURRTYPE to UMEASURE or to MSP Cost.
- Assume MSP can hold two currencies in one file.