Results for “start_caching_timemilli”
8 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The ICX.PORTLET_CUSTOMIZATIONS table is an Oracle E-Business Suite base table that stores per-user and per-tenant customization settings for dashboard portlets, most notably within the Oracle iProcurement (ICX) module and the broader self-service framework. Each row defines how a specific portlet plug-in should be rendered, cached, titled, and secured for a given user, responsibility, page, or security group. The table therefore acts as the configuration backbone behind the personalized portal and KPI content that end users see when they log in.
The heuristic Data Vault classification mined from the foreign-key structure is standalone. Because the table holds descriptive attributes tied to configuration keys rather than participating in multi-source integration links, it is most naturally modeled as a satellite-like configuration entity. In a Data Vault context it could be treated as a hub for portlet customization identity, but the documentation does not suggest it functions as a true hub, link, or satellite, so the label should be regarded as a modeling suggestion only.
Key Information Stored
The table contains 13 documented columns. The most significant include:
- PLUG_ID — Foreign key to
BSC_USER_KPILIST_PLUGS; identifies the portlet or KPI plug-in being customized. - APPLICATION_ID — The application context to which the customization applies.
- RESPONSIBILITY_ID — The responsibility under which the customization is active.
- SECURITY_GROUP_ID — Foreign key to
FND_SECURITY_GROUPS, governing access scope. - USER_ID — The specific user who owns the customization, when applicable.
- PAGE_ID — The portal page to which the portlet is assigned.
- TITLE — The display title of the portlet.
- REFERENCE_PATH — The path reference used to resolve the portlet content.
- CACHING_KEY and CACHING_PERIOD — Parameters controlling caching behavior.
- START_CACHING_TIMEMILLI — The millisecond offset at which caching begins.
- FUNCTION_ID — Links the portlet to a registered function for security and navigation.
- USER_AGENT — Captures the browser or client agent associated with the customization.
No explicit surrogate primary key is documented in the provided metadata; uniqueness is effectively enforced through the combination of plug, user, responsibility, page, and security-group keys.
Common Use Cases and Queries
Administrators and developers query this table to diagnose why a portlet appears, disappears, or renders with stale content. A typical pattern joins the plug definition to identify the owning component:
- Retrieve all customizations for a specific plug:
SELECT * FROM ICX.PORTLET_CUSTOMIZATIONS WHERE PLUG_ID = :plug_id; - Identify per-user overrides:
SELECT USER_ID, PAGE_ID, TITLE FROM ICX.PORTLET_CUSTOMIZATIONS WHERE USER_ID IS NOT NULL; - Audit caching configuration:
SELECT CACHING_KEY, CACHING_PERIOD, START_CACHING_TIMEMILLI FROM ICX.PORTLET_CUSTOMIZATIONS;
Reporting use cases include auditing which responsibilities expose which portlets, verifying security-group alignment, and troubleshooting performance issues related to caching periods.
Related Objects
- BSC_USER_KPILIST_PLUGS — joined on
PLUG_ID. - FND_SECURITY_GROUPS — joined on
SECURITY_GROUP_ID. - FND_APPLICATION — resolved via
APPLICATION_ID. - FND_RESPONSIBILITY — resolved via
RESPONSIBILITY_ID. - FND_USER — resolved via
USER_ID. - FND_FORM_FUNCTIONS — referenced through
FUNCTION_ID.
These relationships make the table a central reference point for portal personalization and access-control analysis.