Results for “assigned_flag”

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

Overview

IGP_US_PORTFOLIOS is a transactional table owned by the IGS schema within the Oracle E-Business Suite Student System (IGS) product family. Its documented purpose is to store the details of portfolios — structured collections of a student's or constituent's achievements, artifacts, activities, and career-related information maintained through the Oracle iLearning and Student System portfolio functionality. In EBS 12.1.1 and 12.2.2 the table is listed as VALID and exposes seventeen documented columns, with the primary key IGP_US_PORTFOLIOS_PK defined on PORTFOLIO_ID.

Because the table carries a single-column surrogate primary key and a foreign key to IGP_AC_ACCOUNTS, the metadata describes it as hub-leaning under a heuristic Data Vault classification. As a modeling suggestion, it can be treated as a hub entity — a portfolio is a durable business concept keyed by PORTFOLIO_ID — with its descriptive attributes (name, type, dates, status flags, purpose) behaving like satellite columns. It also functions as a parent for downstream dependent objects, which is consistent with the link relationships shown below.

Key Information Stored

The most significant columns describe the portfolio identity, classification, publication window, and ownership context:

• PORTFOLIO_ID — the surrogate primary key from IGP_US_PORTFOLIOS_PK, uniquely identifying each portfolio record.
• ACCOUNT_ID — foreign key to IGP_AC_ACCOUNTS, tying the portfolio to the owning account; part of the unique business key IGP_US_PORTFOLIOS_U1 together with PORTFOLIO_NAME.
• PORTFOLIO_NAME — the user-facing name of this portfolio, the second business-key component.
• PORTFOLIO_TYPE_CODE — classifies the portfolio (for example by purpose or category).
• PUB_START_DATE / PUB_END_DATE — the publication window controlling when the portfolio is visible or active.
• DESCRIPTION, PURPOSE, and CAREER_OBJECTIVE — free-text attributes describing the intent and goals of the portfolio.
• PUB_CAREER_SERVICES_FLAG and ASSIGNED_FLAG — status/eligibility flags for career-services publication and assignment.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — standard EBS WHO-column audit and optimistic-locking fields.

The surrogate key PORTFOLIO_ID should not be confused with the natural business key (ACCOUNT_ID, PORTFOLIO_NAME), enforced by IGP_US_PORTFOLIOS_U1.

Common Use Cases and Queries

Typical reporting and integration scenarios include listing all portfolios for an account, filtering by publication date, or joining portfolio data to registration viewers and activity records.

• Retrieve portfolios for a given account using the business-key columns:
  SELECT PORTFOLIO_ID, PORTFOLIO_NAME, PORTFOLIO_TYPE_CODE FROM IGP_US_PORTFOLIOS WHERE ACCOUNT_ID = :p_account_id AND SYSDATE BETWEEN PUB_START_DATE AND PUB_END_DATE;
• Enrich portfolio records with account context by joining to IGP_AC_ACCOUNTS on ACCOUNT_ID.
• Find active, career-services-enabled portfolios using PUB_CAREER_SERVICES_FLAG = 'Y' and ASSIGNED_FLAG.
• Report only the latest version using OBJECT_VERSION_NUMBER ordering for downstream extract jobs.

Related Objects

The documented relationship metadata identifies the following dependencies and dependents:

• IGP_AC_ACCOUNTS — parent account table; joined via IGP_US_PORTFOLIOS.ACCOUNT_ID = IGP_AC_ACCOUNTS.ACCOUNT_ID.
• IGP_US_REG_VIEWERS — references this table through PORTFOLIO_ID, controlling which viewers may access a portfolio.
• IGP_VW_PORT_ACTIVITIES — references this table through PORTFOLIO_ID, holding portfolio activity entries.

Together these relationships confirm IGP_US_PORTFOLIOS as the central hub for portfolio information, with IGP_AC_ACCOUNTS as its primary parent and IGP_US_REG_VIEWERS and IGP_VW_PORT_ACTIVITIES as dependent children.