Search Results fnd_tablespaces_p1

Overview

FND_TABLESPACES is a reference table owned by the APPLSYS schema within the FND (Application Object Library) product of Oracle E-Business Suite. Its documented purpose is to map logical tablespace identifiers to their corresponding physical tablespace names. In Oracle EBS 12.1.1 and 12.2.2, this mapping is significant because the application framework, the AutoConfig tooling, and the tablespace migration utilities do not reference physical tablespace names directly; they work against abstract logical tokens that must be resolved at runtime. FND_TABLESPACES provides that resolution layer, decoupling Oracle EBS metadata and migration logic from environment-specific database storage configuration.

From a Data Vault modeling perspective, the heuristic mined from the foreign-key structure classifies FND_TABLESPACES as hub-leaning. This suggests treating TABLESPACE_TYPE as the hub business key, with the surrounding descriptive attributes (TABLESPACE, CUSTOM_FLAG) functioning as satellite attributes dependent on that key. The table carries eight documented columns and is marked VALID and registered in the ETRM repository for release 12.2.2.

Key Information Stored

The documented physical schema contains eight columns, of which the following are most significant:

• TABLESPACE_TYPE — the logical tablespace identifier and the single primary key column (constraint FND_TABLESPACES_P1). It is the business-key candidate that uniquely identifies each row and is the column referenced by all foreign keys to this table.
• TABLESPACE — the physical tablespace name to which the logical TABLESPACE_TYPE resolves. This is the principal payload of the table.
• CUSTOM_FLAG — indicates whether the mapping is a customer-defined (non-seeded) entry, allowing seeded and customized rows to be distinguished during upgrades or patching.
• LAST_UPDATE_DATE — standard FND audit column recording the timestamp of the most recent modification.
• LAST_UPDATED_BY — the application user who performed the last modification.
• CREATION_DATE — the timestamp at which the row was originally inserted.
• CREATED_BY — the application user who created the row.
• LAST_UPDATE_LOGIN — the login identifier associated with the most recent update, part of the standard FND WHO column set.

The surrogate-versus-business distinction is straightforward: FND_TABLESPACES_P1 is defined directly on TABLESPACE_TYPE, which therefore serves as both primary key and business key. The WHO columns together with CUSTOM_FLAG form the attribute set that would populate a satellite in a Data Vault model.

Common Use Cases and Queries

The primary scenario for querying FND_TABLESPACES is resolving logical tablespace types to physical names prior to storage administration, tablespace migration, or sizing analysis. A typical pattern joins this table to FND_OBJECT_TABLESPACES to identify which physical tablespace holds each application object:

• Resolving a single logical type: SELECT TABLESPACE FROM FND_TABLESPACES WHERE TABLESPACE_TYPE = :p_type;
• Reporting all mappings and flagging custom rows: SELECT TABLESPACE_TYPE, TABLESPACE, CUSTOM_FLAG FROM FND_TABLESPACES ORDER BY TABLESPACE_TYPE;
• Joining to dependent objects to plan a migration: SELECT o.OBJECT_NAME, t.TABLESPACE_TYPE, t.TABLESPACE FROM FND_OBJECT_TABLESPACES o, FND_TABLESPACES t WHERE o.TABLESPACE_TYPE = t.TABLESPACE_TYPE;
• Inspecting migration rules: SELECT m.RULE, t.TABLESPACE FROM FND_TS_MIG_RULES m, FND_TABLESPACES t WHERE m.TABLESPACE_TYPE = t.TABLESPACE_TYPE;

Because custom mappings may be seeded by implementation teams, reports frequently filter on CUSTOM_FLAG to distinguish baseline Oracle content from site-specific configuration before comparing environments or planning a clone.

Related Objects

The documented foreign-key metadata identifies two tables that reference FND_TABLESPACES through the shared TABLESPACE_TYPE column:

• FND_OBJECT_TABLESPACES — references FND_TABLESPACES.TABLESPACE_TYPE. This relationship allows application objects to be associated with a logical tablespace type that is then resolved through FND_TABLESPACES.
• FND_TS_MIG_RULES — references FND_TABLESPACES.TABLESPACE_TYPE. These rules govern tablespace migration and resolve their logical types through this parent table.

Both dependents join on TABLESPACE_TYPE, the primary key of FND_TABLESPACES, confirming the hub-leaning classification. When querying either dependent, the join should always include TABLESPACE_TYPE to preserve the logical-to-physical resolution this table exists to provide.