Oracle Fusion · Data dictionary
PJF_EXP_TYPES_B
ProjectsUsed in 2 subject areas9 reporting columns
Projects Foundation (PJF), type / category reference.
Likely primary key: EXP_TYPE_CODE (inferred from Oracle naming conventions, verify against Tables & Views)
Joins (inferred from key columns): EXP_TYPE_CODE → PJF_EXP_TYPES_VL
Columns
| Column | Key | In reports | Description (inferred) |
|---|---|---|---|
| COST_RATE_FLAG | ● | Indicator (Y/N) for the cost rate. | |
| CREATED_BY | ● | User who created the row. | |
| CREATION_DATE | ● | Date and time the row was created. | |
| END_DATE_ACTIVE | ● | End date active. | |
| EXP_TYPE_CODE | PK? | ○ | Code identifying the exp type. |
| LAST_UPDATED_BY | ● | User who last updated the row. | |
| LAST_UPDATE_DATE | ● | Date and time the row was last updated (the incremental-extract key). | |
| PROCEEDS_FLAG | ● | Indicator (Y/N) for the proceeds. | |
| REVENUE_CATEGORY_CODE | ● | Code identifying the revenue category. | |
| START_DATE_ACTIVE | ● | Start date active. |
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 PJF_EXP_TYPES_B?
We ship parameterized SQL, BICC config, and dbt models you own.
Problems that run through this table