Search Results ia_request_details




Overview
Explore in AI Chat

Overview

The IA_REQUEST_DETAILS table is a core data repository within the Oracle E-Business Suite (EBS) iAssets (IA) module. It functions as the detailed transaction line table for asset-related requests. While the IA_REQUEST_HEADERS table stores the overall request metadata, the IA_REQUEST_DETAILS table holds the granular, line-level information for each action specified within a request. This object is essential for tracking the specific changes, transfers, or adjustments proposed for individual assets, serving as the primary transactional detail table that drives the iAssets business process from initiation through to approval and posting.

Key Information Stored

The table's primary key, REQUEST_DETAIL_ID, uniquely identifies each request line. Its most critical foreign key, REQUEST_ID, links each detail line to its parent header in the IA_REQUEST_HEADERS table. The table stores the identifiers for the asset being acted upon (ASSET_ID) and the associated accounting book (BOOK_TYPE_CODE). Crucially, it captures the "from" and "to" states for a transfer or adjustment, including the source and target distribution IDs (FROM_DISTRIBUTION_ID, TO_DISTRIBUTION_ID), the destination location (TO_LOCATION_ID), and the new expense account combination (TO_EXPENSE_CCID). This design allows the system to record both the current state and the intended future state of the asset within a single request line.

Common Use Cases and Queries

This table is central to reporting on pending asset transactions and auditing historical changes. A common use case involves generating a detailed report of all request lines for a specific asset or within a date range to analyze change history. Support personnel often query this table to diagnose issues with specific requests. A typical reporting query would join to the header, asset, and code combination tables:

  • SELECT ird.request_id, ird.asset_id, fa.asset_number, ird.book_type_code, fdh_from.location_id from_loc, fdh_to.location_id to_loc FROM ia_request_details ird JOIN fa_additions_b fa ON ird.asset_id = fa.asset_id LEFT JOIN fa_distribution_history fdh_from ON ird.from_distribution_id = fdh_from.distribution_id LEFT JOIN fa_distribution_history fdh_to ON ird.to_distribution_id = fdh_to.distribution_id WHERE ird.request_id = :p_request_id;

Another critical pattern is validating data integrity by identifying detail lines orphaned from their parent request headers.

Related Objects

IA_REQUEST_DETAILS maintains documented foreign key relationships with several key EBS tables, primarily within the Fixed Assets module, underscoring its integrative role. The relationships are as follows:

  • IA_REQUEST_HEADERS: Via IA_REQUEST_DETAILS.REQUEST_ID. This is the primary parent relationship.
  • FA_ADDITIONS_B: Via IA_REQUEST_DETAILS.ASSET_ID. Links the request line to the master asset record.
  • FA_BOOK_CONTROLS: Via IA_REQUEST_DETAILS.BOOK_TYPE_CODE. Associates the detail with the correct asset book.
  • FA_DISTRIBUTION_HISTORY (Two Relationships): Via IA_REQUEST_DETAILS.FROM_DISTRIBUTION_ID and IA_REQUEST_DETAILS.TO_DISTRIBUTION_ID. These links track the precise historical distribution record being moved from and the new distribution record being created.
  • FA_LOCATIONS: Via IA_REQUEST_DETAILS.TO_LOCATION_ID. Identifies the destination location for a transfer.
  • GL_CODE_COMBINATIONS: Via IA_REQUEST_DETAILS.TO_EXPENSE_CCID. References the new general ledger expense account for the asset.