Oracle Fusion · Data dictionary
VCS_PLANNING_SCH_DETAILS
SharedUsed in 1 subject areas12 reporting columns
detail-level data.
Primary key: not yet catalogued for VCS_PLANNING_SCH_DETAILS, reference Oracle Tables & Views guide.
Columns
| Column | Key | In reports | Description (inferred) |
|---|---|---|---|
| COMMITTED_BY_PARTY | ● | Committed by party. | |
| COMMIT_DATE | ● | Commit date. | |
| COMMIT_DETAIL_VERSION | ● | Commit detail version. | |
| COMMIT_REASON_CODE | ● | Code identifying the commit reason. | |
| FORECAST_DETAIL_VERSION | ● | Forecast detail version. | |
| LAST_UPDATED_BY | ● | User who last updated the row. | |
| LAST_UPDATE_DATE | ● | Date and time the row was last updated (the incremental-extract key). | |
| PUBLISHED_BY | ● | Published by. | |
| PUBLISHED_BY_PARTY | ● | Published by party. | |
| PUBLISHED_DATE | ● | Published date. | |
| QUANTITY | ● | Quantity. | |
| RESPONSE_QUANTITY | ● | Response quantity. |
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 VCS_PLANNING_SCH_DETAILS?
We ship parameterized SQL, BICC config, and dbt models you own.
Problems that run through this table