Search Results plug_id

Overview

ICX_PAGE_PLUGS is a table owned by the ICX schema, the product family that hosts Oracle iProcurement and related self-service applications. Per the ETRM metadata, the object is VALID and its documented purpose is to "define plugs of a page." In practical terms, a "plug" is a configurable attachment point on an iProcurement or self-service page — a slot through which an administrator binds a menu, a responsibility, a region, or a display label onto a given page. The table therefore functions as a page-configuration and content-assembly map rather than a transactional store.

The heuristic Data Vault classification derived from the foreign-key structure is standalone — that is, it does not behave as a classic hub or a pure link in a modeled Data Vault sense. In a Data Vault modeling suggestion, it is best treated as its own configuration entity, with its parent references to FND_MENUS and FND_SECURITY_GROUPS handled as optional descriptive links rather than as conformed hub keys. The table carries no downstream dependents within the documented schema, which reinforces the standalone interpretation.

Key Information Stored

The documented physical schema for 12.2.2 exposes 15 columns. The composite primary key, ICX_PAGE_PLUGS_PK1, is composed of PAGE_ID and PLUG_ID, and the unique business-key candidate, ICX_PAGE_PLUGS_U1, is identically defined on (PAGE_ID, PLUG_ID). PAGE_ID identifies the host page, while PLUG_ID identifies the individual plug instance within that page.

• PAGE_ID — the page to which the plug belongs; part of the composite key.
• PLUG_ID — the plug identifier; part of the composite key.
• DISPLAY_SEQUENCE and ENTRY_SEQUENCE — control the ordering in which the plug and its entries render on the page.
• DISPLAY_NAME — the label presented to the user for the plug.
• REGION_ID — the page region into which the plug is placed.
• RESPONSIBILITY_APPLICATION_ID and RESPONSIBILITY_ID — scope the plug to a specific application and responsibility, enabling responsibility-driven content.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, applying the multi-org security group context.
• MENU_ID — foreign key to FND_MENUS, binding an Oracle EBS menu (and therefore its function hierarchy) to the plug.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns used for change tracking and concurrency.

Common Use Cases and Queries

Typical uses center on diagnosing why a page renders a particular menu, responsibility, or region, and on auditing page configuration after a patch or upgrade. A frequently used pattern lists all plugs for a page in render order:

• SELECT plug_id, display_name, region_id, display_sequence, menu_id, responsibility_id FROM icx.icx_page_plugs WHERE page_id = :page_id ORDER BY display_sequence, entry_sequence;
• Joining to FND_MENUS on menu_id reveals which function hierarchy each plug exposes.
• Filtering by responsibility_id and responsibility_application_id isolates responsibility-specific page behavior.
• Reporting on LAST_UPDATE_DATE and LAST_UPDATED_BY identifies recent configuration changes for change-control review.

Related Objects

The documented foreign keys and key relationships point to the following significant objects:

• FND_MENUS — joined via ICX_PAGE_PLUGS.MENU_ID = FND_MENUS.MENU_ID.
• FND_SECURITY_GROUPS — joined via ICX_PAGE_PLUGS.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID.
• FND_RESPONSIBILITY — matched through RESPONSIBILITY_ID and RESPONSIBILITY_APPLICATION_ID.
• ICX_PAGES — the parent page definition referenced by PAGE_ID.
• ICX_PAGE_PLUG_ENTRIES — child entries sequenced by ENTRY_SEQUENCE.
• FND_APPLICATION — resolves RESPONSIBILITY_APPLICATION_ID to an application short name.
• FND_REGIONS (where present) — resolves REGION_ID for region-level reporting.