Search Results iex_repos_objects




Overview

IEX_REPOS_OBJECTS is a Collections module table in the Oracle E-Business Suite (EBS) IEX schema. It stores information about assets that are undergoing repossession, providing the granular detail behind each repossession activity. Where the parent table IEX_REPOSSESSIONS captures the repossession event, IEX_REPOS_OBJECTS records the individual objects (assets) linked to that event. The table is marked VALID and is present in both EBS 12.1.1 and 12.2.2, with the documented 12.2.2 physical schema comprising 35 columns owned by IEX.

From a Data Vault modeling perspective, the mined FK structure classifies this object as standalone — a heuristic suggestion that it behaves more like a satellite or an independent detail entity rather than a pure junction/link hub. This classification reflects that the table carries descriptive asset attributes (ASSET_ID, RNA_ID, ART_ID) tied to a single parent repossession record rather than defining many-to-many relationships among independent hubs.

Key Information Stored

The surrogate primary key is REPOS_OBJECT_ID (constraint IEX_REP_PK), which uniquely identifies each repossession object row. The principal parent link is REPOSSESSION_ID, a foreign key to IEX_REPOSSESSIONS, tying each object to its repossession event. Additional business-identifying attributes include:

No separate unique business index is documented in the metadata beyond the surrogate primary key; business-key candidacy rests on the combination of REPOSSESSION_ID and ASSET_ID.

Common Use Cases and Queries

Typical usage centers on reporting and reconciliation of repossessed collateral. Common scenarios include listing all assets for a given repossession, identifying active repossessions by operating unit, and joining to asset master tables to enrich descriptions.

  • List objects for a repossession: SELECT * FROM iex_repos_objects WHERE repossession_id = :p_id AND active_yn = 'Y';
  • Multi-org filter: SELECT repos_object_id, asset_id FROM iex_repos_objects WHERE org_id = :org_id;
  • Detail query joining parent: SELECT r.repossession_id, o.asset_id FROM iex_repossessions r, iex_repos_objects o WHERE r.repossession_id = o.repossession_id;
  • Audit/change tracking via OBJECT_VERSION_NUMBER and LAST_UPDATE_DATE.

Because attribute columns form a DFF, reporting on ATTRIBUTE1–15 yields custom classifications configured by the implementation.

Related Objects

The most significant related objects derive from the documented FK relationships and IEX Collections context:

  • IEX_REPOSSESSIONS — Parent table; join on REPOSSESSION_ID = REPOSSESSION_ID. This is the primary dependency.
  • FND_SECURITY_GROUPS — Join on SECURITY_GROUP_ID; governs row visibility.
  • FA_ASSETS (or the corresponding asset master) — Linked via ASSET_ID for asset detail.
  • IEX_RNA / receivable-related tables — Linked via RNA_ID and RNA_SITE_ID.
  • ART (AR transactions) — Linked via ART_ID for transaction context.
  • FND_CONCURRENT_REQUESTS — Join on REQUEST_ID for concurrent process traceability.

Together these relationships position IEX_REPOS_OBJECTS as the asset-level detail layer within the IEX Collections repossession subsystem.