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

FND_TERRITORIES_B

Common / FoundationUsed in 20 subject areas18 reporting columnsBICC incremental-ready

Foundation / Setup (FND), base table, language-neutral data (paired with _TL labels and the _VL view).

Primary key: not yet catalogued for FND_TERRITORIES_B, reference Oracle Tables & Views guide. · Incremental key: LAST_UPDATE_DATE

Columns

ColumnKeyIn reportsDescription (inferred)
ADDRESS_STYLEAddress style.
ADDRESS_VALIDATIONAddress validation.
ALTERNATE_TERRITORY_CODECode identifying the alternate territory.
BANK_INFO_STYLEBank info style.
BANK_INFO_VALIDATIONBank info validation.
CREATED_BYUser who created the row.
CREATION_DATEDate and time the row was created.
CURRENCY_CODECode identifying the currency.
ENABLED_FLAGIndicator (Y/N) for the enabled.
EU_CODECode identifying the eu.
ISO_NUMERIC_CODECode identifying the iso numeric.
ISO_TERRITORY_CODECode identifying the iso territory.
LAST_UPDATED_BYUser who last updated the row.
LAST_UPDATE_DATEINCRDate and time the row was last updated (the incremental-extract key).
LAST_UPDATE_LOGINSession login of the user who last updated the row.
NLS_TERRITORYNls territory.
OBSOLETE_FLAGIndicator (Y/N) for the obsolete.
TERRITORY_CODECode identifying the territory.

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