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

CSE_AS_BUILT_STRUCTURES_V

SharedUsed in 2 subject areas14 reporting columns

denormalized view.

Primary key: not yet catalogued for CSE_AS_BUILT_STRUCTURES_V, reference Oracle Tables & Views guide.
Joins (inferred from key columns): RELATIONSHIP_TYPE_CODE → HZ_RELATIONSHIP_TYPES

Columns

ColumnKeyIn reportsDescription (inferred)
ACTIVE_END_DATE●Active end date.
ACTIVE_START_DATE●Active start date.
CHILD_ASSET_ID●Identifier for the child asset.
CHILD_ASSET_LOT_NUMBER●Child asset lot number.
CHILD_ASSET_NUMBER●Child asset number.
CHILD_ASSET_SERIAL_NUMBER●Child asset serial number.
CHILD_LEVEL●Child level.
PARENT_ASSET_ID●Identifier for the parent asset.
PARENT_ASSET_LOT_NUMBER●Parent asset lot number.
PARENT_ASSET_NUMBER●Parent asset number.
PARENT_ASSET_SERIAL_NUMBER●Parent asset serial number.
RELATIONSHIP_TYPE_CODE●Code identifying the relationship type.
ROOT_ASSET_ID●Identifier for the root asset.
ROOT_ASSET_NUMBER●Root asset number.

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