Search Results portfolio_id




Overview
Explore in AI Chat

Overview

The IGS.IGP_US_PAGES table is a core data repository within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the IGS (Internet Global Services) product family. Its primary function is to store the definition and content of pages that constitute a portfolio, a logical grouping of related content or functionality. This table serves as the foundational storage layer for managing page-level information within the portfolio management framework of the application, enabling the organization, display, and retrieval of structured page data.

Key Information Stored

The table's columns are designed to capture the identity, classification, and content of each portfolio page. The PAGE_ID serves as the unique, system-generated primary key. A critical column is PORTFOLIO_ID, which links each page to its parent portfolio, establishing the fundamental hierarchical relationship. The PAGE_NAME and PAGE_TITLE columns store the administrative identifier and the display title for the page, respectively. The PAGE_CONTENT column, defined as a CLOB, holds the substantive HTML or formatted content of the page itself. Classification is managed through flags: PRIMARY_FLAG indicates the main page within a portfolio, and EXTERNAL_FLAG distinguishes between pages created via an internal wizard and those uploaded from an external source. Standard EBS "Who" columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and OBJECT_VERSION_NUMBER for data integrity round out the structure.

Common Use Cases and Queries

A primary use case is querying all pages belonging to a specific portfolio, which is essential for rendering a portfolio's navigation or content list. The user's search for "portfolio_id" directly aligns with this fundamental operation. Another common scenario is identifying the primary page for a given portfolio to serve as a default landing page. Administrators may also run queries to audit page creation or modifications. Sample SQL patterns include:

  • Retrieving all pages for a portfolio: SELECT PAGE_NAME, PAGE_TITLE, PRIMARY_FLAG FROM IGS.IGP_US_PAGES WHERE PORTFOLIO_ID = :1 ORDER BY PAGE_NAME;
  • Finding the primary page for a portfolio: SELECT PAGE_ID, PAGE_TITLE, PAGE_CONTENT FROM IGS.IGP_US_PAGES WHERE PORTFOLIO_ID = :1 AND PRIMARY_FLAG = 'Y';
  • Basic reporting on page inventory: SELECT PORTFOLIO_ID, COUNT(*) AS PAGE_COUNT, MAX(CREATION_DATE) AS LAST_PAGE_ADDED FROM IGS.IGP_US_PAGES GROUP BY PORTFOLIO_ID;

Related Objects

Based on the provided metadata, the IGP_US_PAGES table has a defined relationship with a parent table via its PORTFOLIO_ID column. The table's unique index, IGP_US_PAGES_U1, on (PORTFOLIO_ID, PAGE_NAME) enforces uniqueness of page names within a portfolio. The primary relationship is implied by the PORTFOLIO_ID column itself, which functions as a foreign key referencing a parent portfolio table (not fully named in the excerpt, but the notation "TABLE: IGS.IGP_US_PAGES.PORTFOLIO_ID → %" confirms the foreign key constraint exists). The table is referenced by an APPS synonym named IGP_US_PAGES, which is the standard access point for EBS application code. There are no other tables or views documented as referencing IGP_US_PAGES in the provided dependency information.