Search Results bis_pmf_populate_portlet

Overview

BIS.BIS_PMF_POPULATE_PORTLET is a standalone configuration table within the Oracle EBS Applications BIS (Business Intelligence System) product family. It belongs to the historical Oracle Balanced Scorecard / Daily Business Intelligence reporting stack, where it served as a metadata repository describing how individual portlets retrieve and display data on an Oracle EBS dashboard page. Each row defines a portlet instance and the parameter payload used to drive its underlying query or view.

In the ETRM 12.1.1 documentation the object is classified as VALID, with a physical schema owned by the BIS schema consisting of nine columns and a single unique index. The heuristic Data Vault classification mined from the foreign-key structure is standalone, which suggests that this table behaves primarily as a stand-alone reference or configuration object rather than as a core hub, link, or satellite in a modeled warehouse. In practice it is best treated as a satellite-style attribute store attached to the portlet plug-in definition referenced by PLUG_ID.

Key Information Stored

The table holds nine documented columns. The most consequential are:

• PLUG_ID — Foreign key to BSC_USER_KPILIST_PLUGS. Identifies the parent portlet plug-in definition to which the populate record belongs.
• SEQ_ID — Sequence identifier used to order multiple populate records under the same plug-in.
• LABEL — Display or logical label associated with the populate instruction.
• PARAM_DATA — The parameter payload passed into the portlet query or view at runtime.
• CREATION_DATE, CREATED_BY — Standard WHO audit columns capturing row insert metadata.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns capturing the most recent modification.

The unique index BIS_PMF_POPULATE_PORTLET_U1 is defined on the composite key (PLUG_ID, SEQ_ID). This composite is the documented business-key candidate; there is no separately documented surrogate primary key column in the metadata, so PLUG_ID plus SEQ_ID together act as the effective row identity.

Common Use Cases and Queries

Typical usage centres on diagnosing why a portlet renders with incorrect parameters, or on auditing which parameters a given plug-in supplies. A representative join enumerates all populate records for a plug-in:

• SELECT p.plug_id, p.seq_id, p.label, p.param_data FROM bis.bis_pmf_populate_portlet p WHERE p.plug_id = :plug_id ORDER BY p.seq_id;
• SELECT p.*, u.plug_name FROM bis.bis_pmf_populate_portlet p, bis.bsc_user_kpilist_plugs u WHERE p.plug_id = u.plug_id;
• Audit query: SELECT * FROM bis.bis_pmf_populate_portlet WHERE last_update_date > SYSDATE - 30;

Report authors can use the table to document which portlets expose parameters and how those parameters are sequenced, supporting change-control and post-clone validation checks.

Related Objects

• BIS.BSC_USER_KPILIST_PLUGS — parent plug-in definition table, joined on PLUG_ID.
• BIS.BSC_USER_KPILIST — KPI list header that the plug-ins extend.
• BIS.BSC_USER_KPILIST_ITEMS — KPI list line items.
• BIS.BSC_PMF_PAGES — dashboard page definitions that host portlets.
• BIS.BSC_PMF_PORTLETS — portlet instance definitions.
• BIS.BSC_PMF_DATASOURCES — data source metadata consumed by portlet queries.
• Oracle Daily Business Intelligence / Scorecard concurrent programs that populate or refresh portlet parameters.

Because the table is classified as standalone with a single documented foreign key, its dependency footprint is narrow; integrating it with the surrounding BSC/BIS configuration tables through PLUG_ID remains the most reliable access pattern.