Analytics Catalog/Data dictionary/WIE_WO_OPERATION_RESOURCES
Explore the catalogReportsModulesEnterprise modelOTBI subject areasBICC PVOs
Oracle Fusion · Data dictionary

WIE_WO_OPERATION_RESOURCES

SharedUsed in 3 subject areas14 reporting columns

Work in Process (WIE).

Primary key: not yet catalogued for WIE_WO_OPERATION_RESOURCES, reference Oracle Tables & Views guide.
Joins (inferred from key columns): EQP_QUAL_PROFILE_ID → MNT_EQP_QUAL_PROFILES_B · PROFILE_ID → HRT_PROFILES_B

Columns

ColumnKeyIn reportsDescription (inferred)
ACTUAL_RESOURCE_USAGE●Actual resource usage.
ASSIGNED_UNITS●Assigned units.
BASIS_TYPE●Type of basis.
CHARGE_TYPE●Type of charge.
EQP_QUAL_PROFILE_ID●Identifier for the eqp qual profile.
PLANNED_COMPLETION_DATE●Planned completion date.
PLANNED_START_DATE●Planned start date.
PRINCIPAL_FLAG●Indicator (Y/N) for the principal.
PROFILE_ID●Identifier for the profile.
REQUIRED_USAGE●Required usage.
RESOURCE_ACTIVITY_CODE●Code identifying the resource activity.
RESOURCE_SEQ_NUMBER●Resource seq number.
SCHEDULED_FLAG●Indicator (Y/N) for the scheduled.
USAGE_RATE●Usage rate.

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. In OTBI they combine only through shared dimensions or set operators such as union, inside one application; the owned conformed model joins this table across modules and systems on conformed keys.

Need the extract + dbt staging for WIE_WO_OPERATION_RESOURCES?
We ship parameterized SQL, BICC config, and dbt models you own.
Talk to us
Problems that run through this table
What the extract does not carry · The export ceiling · The extraction pattern