Results for “save_location”

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

Overview

IA_REQUEST_HEADERS is the master header table in the Oracle E-Business Suite iAssets (IA) module. It stores information about the asset requests created by users during the asset requisition and fulfillment process, in which one party prepares a request for assets and another approves and fulfills it. Each row represents a single asset request and captures the administrative metadata surrounding that request: who prepared it, who requested it, when it was raised, its purpose and type, the approval chain, and the associated asset book. The table functions as the parent of the request line structure held in IA_REQUEST_DETAILS, so all downstream line-level processing is anchored to a REQUEST_ID value in this table.

From a Data Vault modeling perspective, the mined FK topology classifies IA_REQUEST_HEADERS as satellite-leaning. It carries descriptive, request-specific context that changes over the request lifecycle (status, approvers, dates) and points outward to the FA_BOOK_CONTROLS reference dimension via BOOK_TYPE_CODE, while child details attach to it. It is not a pure hub because it holds substantial descriptive attributes rather than only business keys.

Key Information Stored

The surrogate primary key is REQUEST_ID, enforced by the constraint IA_REQUEST_HEADERS_PK and also backed by the unique index IA_REQUEST_HEADERS_U1. Among the 33 documented columns, the most significant are:

• REQUEST_ID — the internally generated identifier that uniquely identifies each request and links to detail lines.
• STATUS — the current lifecycle state of the request (for example, prepared, approved, or fulfilled).
• PREPARER_ID — the user who created and submitted the request.
• REQUESTER_ID — the party on whose behalf the assets are requested.
• REQUEST_DATE — the date the request was raised.
• PURPOSE — free-text justification for the request.
• REQUEST_TYPE — the classification of the request.
• SAVE_LOCATION — the destination or storage location associated with the request.
• RELEASING_APPROVER_ID and RECEIVING_APPROVER_ID — the approving parties on either side of the transfer.
• RESPONSIBILITY_ID — the responsibility under which the request was created.
• BOOK_TYPE_CODE — the foreign key to FA_BOOK_CONTROLS identifying the asset book.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.
• ATTRIBUTE_CATEGORY_CODE and ATTRIBUTE1–15 — the standard descriptive flexfield (DFF) columns for customer-defined extensions.

Common Use Cases and Queries

Typical reporting scenarios include tracking open requests by status, auditing approver activity, and reconciling requests against the asset book. A simple status summary:

• SELECT STATUS, COUNT(*) FROM IA.IA_REQUEST_HEADERS GROUP BY STATUS;
• SELECT h.REQUEST_ID, h.STATUS, h.REQUEST_DATE, h.PURPOSE, h.BOOK_TYPE_CODE FROM IA.IA_REQUEST_HEADERS h WHERE h.REQUESTER_ID = :p_requester_id ORDER BY h.REQUEST_DATE DESC;
• SELECT h.REQUEST_ID, d.LINE_ID FROM IA.IA_REQUEST_HEADERS h JOIN IA.IA_REQUEST_DETAILS d ON d.REQUEST_ID = h.REQUEST_ID WHERE h.STATUS = 'APPROVED';

Because the table is DFF-enabled, queries that expose ATTRIBUTE_CATEGORY_CODE and the ATTRIBUTE1–15 columns are common in client-specific extracts and BI Publisher reports.

Related Objects

• IA_REQUEST_DETAILS — the child line table; joins on IA_REQUEST_DETAILS.REQUEST_ID = IA_REQUEST_HEADERS.REQUEST_ID. This is the dominant relationship.
• FA_BOOK_CONTROLS — referenced by IA_REQUEST_HEADERS.BOOK_TYPE_CODE to identify the asset book.
• FA_ADDITIONS — assets ultimately created or transferred as a result of fulfilled requests, correlated through the book.
• PER_ALL_PEOPLE_F — resolves PREPARER_ID, REQUESTER_ID, RELEASING_APPROVER_ID, and RECEIVING_APPROVER_ID to person names.
• FND_RESPONSIBILITY — resolves RESPONSIBILITY_ID.
• FND_USER — resolves CREATED_BY and LAST_UPDATED_BY.

These relationships make IA_REQUEST_HEADERS the central anchor for iAssets request reporting and for any extract that must trace a request from preparation through approval to fulfillment.