Oracle Fusion · Data dictionary
OKC_CONTRACT_TYPES_VL
SharedUsed in 31 subject areas1 reporting columns
Contracts (OKC), view layer, joins the base table with translations for the current language.
Likely primary key: CONTRACT_TYPE_CODE (inferred from Oracle naming conventions, verify against Tables & Views)
Joins (inferred from key columns): CONTRACT_TYPE_CODE → OKC_CONTRACT_TYPES_B
Columns
| Column | Key | In reports | Description (inferred) |
|---|---|---|---|
| CONTRACT_TYPE_CODE | PK? | ○ | Code identifying the contract type. |
| NAME | ● | Name. |
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.
- Costing - Cost Accounting Real Time
- Costing - Receipt Accounting Real Time
- Costing - Work Order Costs Real Time
- Distributed Order Orchestration - Fulfillment Lines Real Time
- Inventory - Inventory Transactions Real Time
- Inventory - Inventory Transfer Order Real Time
- Maintenance Management - Material Usage Real Time
- Maintenance Management - Purchased Item Usage Real Time
- Maintenance Management - Resource Usage Real Time
- Maintenance Management - Work Order Performance Real Time
- Manufacturing - Actual Production Real Time
- Manufacturing - Material Usage Real Time
- Manufacturing - Purchased Item Usage Real Time
- Manufacturing - Resource Usage Real Time
- Manufacturing - Work Order Performance Real Time
- Procurement - Procure To Pay Real Time
- Procurement - Purchasing Real Time
- Procurement - Requisitions Real Time
- Project Billing - Funding Real Time
- Project Billing - Invoices Real Time
Need the extract + dbt staging for OKC_CONTRACT_TYPES_VL?
We ship parameterized SQL, BICC config, and dbt models you own.
Problems that run through this table