MNT_FORECAST_LINES

SharedUsed in 1 subject areas20 reporting columns

Maintenance (MNT) — line table — one row per line item under the header.

Likely primary key: FORECAST_HEADER_ID, FORECAST_LINE_ID (inferred from Oracle naming conventions — verify against Tables & Views)

Columns

Column	Key	In reports	Description (inferred)
ASSET_ID		●	Identifier for the asset.
CONDITION_EVENT_CODE_ID		●	Identifier for the condition event code.
CYCLE_INTERVAL		●	Cycle interval.
DAY_INTERVAL_VALUE		●	Day interval value.
FORECAST_DATE		●	Forecast date.
FORECAST_HEADER_ID	PK?	○	Identifier for the forecast header.
FORECAST_ID		●	Identifier for the forecast.
FORECAST_LINE_ID	PK?	●	Identifier for the forecast line.
FORECAST_MTR_READING_VALUE		●	Forecast mtr reading value.
FORECAST_SEQUENCE		●	Forecast sequence.
METER_DEFINITION_ID		●	Identifier for the meter definition.
METER_ID		●	Identifier for the meter.
METER_INTERVAL_VALUE		●	Meter interval value.
METER_UTILIZATION_RATE		●	Meter utilization rate.
NEXT_WORK_ORDER_ONLY_FLAG		●	Indicator (Y/N) for the next work order only.
ORGANIZATION_ID		●	Identifier for the organization.
REQUIREMENT_ID		●	Identifier for the requirement.
SCHEDULE_PATTERN_ID		●	Identifier for the schedule pattern.
SUPPRESSED_FLAG		●	Indicator (Y/N) for the suppressed.
WORK_DEFINITION_ID		●	Identifier for the work definition.
WORK_DEFINITION_VERSION_ID		●	Identifier for the work definition version.

No cataloged report reads from this table yet — it's part of the broader Fusion dictionary.

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 MNT_FORECAST_LINES?

We ship parameterized SQL, BICC config, and dbt models you own.