Search Results param_data

Overview

BIS.BIS_PMF_POPULATE_PORTLET is a transient staging table owned by the BIS (Business Intelligence System / Daily Business Intelligence) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. The ETRM metadata classifies it explicitly as a "temporary Table for demo of portlet content," indicating that its rows are populated at runtime to drive the display of Dashboard and Daily Business Intelligence portlets, then purged or overwritten as the portlet context changes. The table resides in the APPS_TS_TX_DATA tablespace, is marked VALID, and carries an FND Design Data reference of BIS.BIS_PMF_POPULATE_PORTLET, confirming it is a registered application schema object rather than a customer extension.

Because it holds no persistent business state and only references one parent object, the heuristic Data Vault classification is standalone. From a modeling perspective, it is best treated as neither a durable hub, link, nor satellite; it is a transient operational staging structure whose lifecycle is bound to a single portlet rendering cycle. Analysts performing ETL or warehouse modeling should therefore not treat this as a warehouse source of record.

Key Information Stored

The physical shape is defined by nine columns and a single unique index, BIS_PMF_POPULATE_PORTLET_U1 on (PLUG_ID, SEQ_ID). The surrogate identifier in practice is the composite of these two indexed columns; they form the business-key candidate and are the mandatory access path.

• PLUG_ID (NUMBER) — Foreign key to BSC_USER_KPILIST_PLUGS, identifying the specific portlet plug to which the staged row belongs.
• SEQ_ID (NUMBER) — Ordering discriminator within a plug, establishing the sequence in which staged content rows are presented.
• LABEL (VARCHAR2(40)) — Display label shown for the portlet line or attribute.
• PARAM_DATA (VARCHAR2(2000)) — The parameter payload associated with the staged portlet row; this is the column most commonly targeted when users search for parameter-driven portlet content, and it is the largest free-form field in the table.
• CREATION_DATE, CREATED_BY — Standard WHO columns recording row creation timestamp and the FND_USER.USER_ID of the creator.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns capturing the last modification timestamp, user, and FND_LOGINS.LOGIN_ID of the updating session.

Common Use Cases and Queries

The predominant use case is diagnostic: confirming what content the Dashboard/PMF portlet framework staged for a given plug at a given moment, particularly when a portlet renders blank, truncates, or displays unexpected parameters. A representative query for a specific plug, ordered as the portlet would render it, is:

• SELECT PLUG_ID, SEQ_ID, LABEL, PARAM_DATA FROM BIS.BIS_PMF_POPULATE_PORTLET WHERE PLUG_ID = :plug_id ORDER BY SEQ_ID;
• Auditing freshness: SELECT MAX(CREATION_DATE) FROM BIS.BIS_PMF_POPULATE_PORTLET;
• Inspecting parameter payloads by label: SELECT LABEL, PARAM_DATA FROM BIS.BIS_PMF_POPULATE_PORTLET WHERE LABEL = :label;
• WHO audit trail: SELECT CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN FROM BIS.BIS_PMF_POPULATE_PORTLET WHERE PLUG_ID = :plug_id;

Note that because the table is transient, row counts and contents fluctuate with user sessions and are not suitable for historical reporting.

Related Objects

The documented relationship set is narrow. The most significant dependency is the foreign key from PLUG_ID to BSC_USER_KPILIST_PLUGS, which supplies the portlet plug definition that this staging table populates. The APPS synonym BIS_PMF_POPULATE_PORTLET provides the application-layer access point used by run-time code and by DBAs querying through the APPS schema. Standard WHO columns implicitly reference FND_USER via CREATED_BY and LAST_UPDATED_BY, and FND_LOGINS via LAST_UPDATE_LOGIN. Broader BIS Dashboard objects such as the PMF portlet configuration and KPI list definitions are functionally coupled to this table through the same plug framework, though ETRM does not enumerate them as hard database dependencies.