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

FUN_ALL_BUSINESS_UNITS_V

IntercompanyUsed in 132 subject areas18 reporting columns

Federation (FUN), business unit master across the enterprise.

Primary key: BU_ID
Joins (inferred from key columns): LEGAL_ENTITY_ID → XLE_ENTITY_PROFILES

Columns

ColumnKeyIn reportsDescription (inferred)
BUSINESS_GROUP_ID●Identifier for the business group.
BU_IDPK●Identifier for the business unit.
BU_NAME●Name of the business unit.
CREATED_BY●User who created the row.
CREATION_DATE●Date and time the row was created.
DATE_FROM●Date from.
DATE_TO●Date to.
DEFAULT_CURRENCY_CODE●Currency code for the default.
DEFAULT_SET_ID●Identifier for the default set.
ENABLED_FOR_HR_FLAG●Indicator (Y/N) for the enabled for hr.
FIN_BUSINESS_UNIT_ID●Identifier for the fin business unit.
LAST_UPDATE_DATE●Date and time the row was last updated (the incremental-extract key).
LEGAL_ENTITY_ID●Identifier of the legal entity.
LOCATION_ID●Identifier for the location.
MANAGER_ID●Identifier for the manager.
PRIMARY_LEDGER_ID●Identifier for the primary ledger.
SHORT_CODE●Code identifying the short.
STATUS●Status.

5 reports read from this table

Change a column here and these are the reports that move with it, the blast radius for any change to FUN_ALL_BUSINESS_UNITS_V.

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 FUN_ALL_BUSINESS_UNITS_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