Search Results fnd_ts_mig_rules_u1

Overview

APPLSYS.FND_TS_MIG_RULES is a seed data table in the Oracle E-Business Suite Applications (APPLSYS) schema. Its ETRM title, "TABLE: APPLSYS.FND_TS_MIG_RULES," reflects its role as a repository of classification rules used during tablespace migration and object placement activities. The table stores rule definitions, each expressed as a SQL WHERE clause fragment, that determine how database objects are classified when the migration utilities evaluate them. This classification supports decisions about which tablespace an object should be assigned to, whether during an upgrade, a migration between releases such as 12.1.1 and 12.2.2, or an operational reorganization.

The object holds the status VALID and is owned by APPLSYS, with FND design data recorded as FND.FND_TS_MIG_RULES, indicating it is delivered as part of the Oracle Applications Foundation (FND) product family. Storage is allocated in the APPS_TS_SEED tablespace, which confirms that the contents are seed or reference data rather than transactional data. The table has nine documented columns and one unique index.

From a modeling perspective, the mined relationship data classifies this object as satellite-leaning. In Data Vault terms, this suggests treating FND_TS_MIG_RULES primarily as a satellite carrying descriptive rule attributes, keyed by a hub-style surrogate identifier, rather than as a central hub or an associative link table.

Key Information Stored

• RULE_ID — NUMBER(15), the sequence number and primary key. It is the surrogate identifier for each rule row and is enforced by the unique index FND_TS_MIG_RULES_U1, making it the documented business-key candidate for uniqueness.
• RULE_QUERY — VARCHAR2(4000), the WHERE clause of the rule. This is the core functional payload: a predicate evaluated against candidate objects to determine their classification.
• TABLESPACE_TYPE — VARCHAR2(30), a foreign key to FND_TABLESPACES. It associates the rule with a tablespace category, tying rule outcomes to physical storage destinations.
• OWNER — VARCHAR2(30), the schema name to which the rule applies, allowing rules to be scoped per database user or application schema.
• Standard who columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN provide auditability: when and by whom each rule was created and last modified, and the login context of the update.

The design separates rule identity (RULE_ID) from rule logic (RULE_QUERY) and rule scope (OWNER, TABLESPACE_TYPE). The unique index on RULE_ID is the single documented uniqueness constraint; no separate composite business key is documented.

Common Use Cases and Queries

Administrators and DBAs query this table to audit which classification rules are active, to understand why a given object was assigned to a particular tablespace, and to verify rule coverage across schemas. A standard retrieval of all rules follows the documented query text:

• SELECT RULE_ID, RULE_QUERY, TABLESPACE_TYPE, OWNER, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN FROM APPLSYS.FND_TS_MIG_RULES;
• Filtering by schema: SELECT * FROM APPLSYS.FND_TS_MIG_RULES WHERE OWNER = :schema_name;
• Joining to the tablespace reference table: SELECT r.RULE_ID, r.RULE_QUERY, t.TABLESPACE_NAME FROM APPLSYS.FND_TS_MIG_RULES r, APPLSYS.FND_TABLESPACES t WHERE r.TABLESPACE_TYPE = t.TABLESPACE_TYPE;
• Auditing recent changes: SELECT RULE_ID, OWNER, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM APPLSYS.FND_TS_MIG_RULES ORDER BY LAST_UPDATE_DATE DESC;

Typical reporting uses include migration readiness assessments, validation that each target tablespace type has at least one governing rule, and change-history reviews using the standard who columns.

Related Objects

• APPLSYS.FND_TABLESPACES — referenced through the TABLESPACE_TYPE foreign key; the primary lookup for tablespace categories.
• APPS.FND_TS_MIG_RULES — the APPS synonym or view layer that references this table, providing the standard access path for application code.
• FND.FND_TS_MIG_RULES — the FND design-data registration, which governs the object's delivered definition and patching.
• APPS.FND_TABLESPACES — the corresponding APPS-layer synonym for the tablespace reference data.
• APPLSYS.FND_TS_MIG_RULES_U1 — the unique index on RULE_ID that enforces row uniqueness and supports direct lookups.

No additional referencing objects are documented beyond these; the table is largely self-contained within the FND tablespace migration framework.