Results for “csi_object_dictionary”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The CSI_OBJECT_DICTIONARY table resides in the CSI schema and belongs to the Install Base (CSI) product module of Oracle E-Business Suite, and is documented as VALID in both release 12.1.1 and 12.2.2. Its stated purpose is to hold the names of the objects and the sequence in which those objects are archived during the archival of transaction history data. In practice, it functions as a control and reference table for the Install Base purging and archiving framework: rather than hard-coding the objects that participate in a history-archive run, the framework consults this dictionary to determine which Install Base entities are eligible and the order in which they must be processed. Each row represents a single archivable object definition, keyed by OBJECT_ID.

Under a heuristic Data Vault classification mined from its foreign-key structure, this table is modeled as a standalone object rather than a hub, link, or satellite. This is a modeling suggestion only: the table has no incoming or outgoing child relationships within the documented FK set, so it does not participate in a classic hub-and-satellite topology. Its single documented foreign key to FND_SECURITY_GROUPS is a security/access-control reference rather than a true functional dependency.

Key Information Stored

The documented physical schema contains 29 columns. The most significant for functional use are:

• OBJECT_ID — The surrogate primary key of the table, enforced by the index CSI_OBJECT_DICTIONARY_PK. Every dictionary entry is uniquely identified by this numeric identifier.
• OBJECT_NAME — The name of the Install Base object being catalogued for archival. Together with OBJECT_ID and ZD_EDITION_NAME, this forms the documented business-key candidate in unique index CSI_OBJECT_DICTIONARY_U01.
• ZD_EDITION_NAME — The edition/version qualifier used by the online patching (adop) model introduced in 12.2; it participates in the business key and allows multiple editions of a dictionary entry to coexist.
• ACTIVE_START_DATE and ACTIVE_END_DATE — The effective window during which the object definition is considered active for archival processing.
• LAST_ARCHIVE_DATE — Records the date the object was last archived, supporting restartability and incremental archive runs.
• SECURITY_GROUP_ID — The foreign key to FND_SECURITY_GROUPS, aligning the dictionary entry with a security group partition.
• OBJECT_VERSION_NUMBER — The standard EBS optimistic-locking column used by the underlying framework's update logic.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The standard WHO-column audit set present on nearly all EBS transactional tables.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — The standard descriptive-flexfield columns, available for site-specific extension if the dictionary is customized.

Common Use Cases and Queries

Because the table is a control table for the Install Base archival program, the most frequent interactions are diagnostic: confirming which objects are registered, verifying their active window, and inspecting the last archive date to understand the state of a purge run.

A typical listing query returns all currently active dictionary entries:

• SELECT object_id, object_name, active_start_date, active_end_date, last_archive_date FROM csi.csi_object_dictionary WHERE TRUNC(SYSDATE) BETWEEN NVL(active_start_date, SYSDATE) AND NVL(active_end_date, SYSDATE);

To identify objects that have never been archived, filter on a null or stale LAST_ARCHIVE_DATE:

• SELECT object_name, last_archive_date FROM csi.csi_object_dictionary WHERE last_archive_date IS NULL ORDER BY object_name;

For edition-aware environments, restrict the query to the current edition using ZD_EDITION_NAME and OBJECT_ID as the join/business-key anchors. Reporting uses include archive-audit extracts, readiness checks before a history purge, and reconciliation of object names against the physical Install Base tables. Because the table is small and reference-like, it is safe to query directly; there is no documented maintenance API, so updates for custom objects should follow standard EBS column-audit conventions.

Related Objects

• FND_SECURITY_GROUPS — Joined via CSI_OBJECT_DICTIONARY.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID; the only documented foreign key of this table.
• CSI_OBJECT_DICTIONARY_PK — The primary-key index on OBJECT_ID that guarantees uniqueness of each dictionary entry.
• CSI_OBJECT_DICTIONARY_U01 — The unique business-key index on (OBJECT_ID, OBJECT_NAME, ZD_EDITION_NAME), enforcing edition-aware duplication rules.
• CSI_INSTALLED_BASE — The principal Install Base transactional table whose archival runs are governed by the object and sequence definitions held here.
• CSI_ITEM_INSTANCES — The item-instance history table whose transaction records are eligible for the archive process driven by this dictionary.
• CSI_TXN_HISTORY — The transaction-history store referenced in this table's stated purpose; dictionary entries define which objects and order apply when its data is archived.

These objects share the CSI schema namespace and are the primary consumers of the dictionary's archive sequencing metadata.