Results for “ia_request_details”

44 results




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

Overview

IA_REQUEST_DETAILS is a transaction table within the iAssets (IA) product of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It stores the line-level detail information entered for asset transfer and asset request transactions processed through the iAssets module. Where IA_REQUEST_HEADERS captures the parent request, IA_REQUEST_DETAILS holds the individual asset lines belonging to that request, including the source and destination distribution references, target location or employee, and the accounting information required to complete the transfer. The table resides in the IA schema and is documented as VALID in the ETRM 12.2.2 physical schema, containing 35 columns.

From a dimensional modeling perspective, the FK structure of this table—multiple foreign keys pointing outward to independent parent entities such as request headers, asset master records, book controls, distributions, locations, and GL accounts—suggests classifying it heuristically as a link table. This is a modeling suggestion only; in the operational EBS schema, IA_REQUEST_DETAILS functions as a conventional transactional child table.

Key Information Stored

The table is anchored by the surrogate primary key REQUEST_DETAIL_ID, enforced through the IA_REQUEST_DETAILS_PK constraint and the IA_REQUEST_DETAILS_U1 unique index. A second unique index, IA_REQUEST_DETAILS_U2, covers the composite of REQUEST_ID and REQUEST_DETAIL_ID, identifying the business-key candidate that ties each detail line to its parent request. The most significant columns include:

Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) provide audit tracking.

Common Use Cases and Queries

Typical reporting scenarios include tracking pending asset transfers, reconciling distributions released versus received, and auditing approvals. A common pattern joins the header and detail tables:

SELECT h.request_id, d.request_detail_id, d.asset_id, d.status
FROM ia_request_headers h, ia_request_details d
WHERE h.request_id = d.request_id;

To identify transfers awaiting approval, filter on RELEASING_APPROVER_ID or RECEIVING_APPROVER_ID being null alongside STATUS. Location-based reporting joins FA_LOCATIONS on TO_LOCATION_ID, while expense-account analysis joins GL_CODE_COMBINATIONS on TO_EXPENSE_CCID.

Related Objects

The principal related objects, derived from the documented foreign keys, are:

  • IA_REQUEST_HEADERS — joined on REQUEST_ID; provides the parent request context.
  • FA_ADDITIONS_B — joined on ASSET_ID; the asset master record.
  • FA_BOOK_CONTROLS — joined on BOOK_TYPE_CODE; asset book definition.
  • FA_DISTRIBUTION_HISTORY — joined twice on FROM_DISTRIBUTION_ID and TO_DISTRIBUTION_ID; source and destination distributions.
  • FA_LOCATIONS — joined on TO_LOCATION_ID; destination location.
  • GL_CODE_COMBINATIONS — joined on TO_EXPENSE_CCID; destination expense account.