Results for “xdp_fe_generic_config”

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

Overview

The XDP_FE_GENERIC_CONFIG table resides in the XDP schema, which underpins the Provisioning module of Oracle E-Business Suite. It stores the configuration definition for Fulfillment Element (FE) Generic Config records. Fulfillment elements represent discrete provisioning activities executed by the provisioning engine, and this table supplies the metadata required to drive their software-driven execution, including start and exit processing routines and lookup-driven classification.

From a dimensional modeling perspective, the FK topology (references to XDP_FES, XDP_FE_SW_GEN_LOOKUP, XDP_PROC_BODY, and FND_SECURITY_GROUPS) suggests the table behaves as a satellite-leaning structure — that is, descriptive configuration attributes hanging off parent fulfillment-element and lookup hubs. This is a heuristic Data Vault classification rather than a normative statement; in an EBS-native sense, it is simply a configuration master table keyed by a surrogate identifier.

Key Information Stored

The table carries 14 documented columns. The most significant are:

• FE_GENERIC_CONFIG_ID — the surrogate primary key (XDP_FE_GENERIC_CONFIG_PK) that uniquely identifies each configuration row.
• FE_ID — foreign key to XDP_FES, identifying the parent fulfillment element to which this configuration belongs.
• FE_SW_GEN_LOOKUP_ID — foreign key to XDP_FE_SW_GEN_LOOKUP, selecting the software-generic lookup variant applicable to the element.
• START_DATE and END_DATE — the effective-dating window controlling when a configuration version is active.
• SW_START_PROC and SW_EXIT_PROC — foreign keys to XDP_PROC_BODY, naming the stored procedures invoked at entry and exit of the software element execution.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org/security-group data isolation.
• ZD_EDITION_NAME — the editioning discriminator supporting online patching (ADOP) in 12.2.x.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Three unique indexes define business-key candidates: U1 (FE_GENERIC_CONFIG_ID, ZD_EDITION_NAME), U2 (FE_ID, FE_SW_GEN_LOOKUP_ID, ZD_EDITION_NAME), and U3 (FE_ID, START_DATE, ZD_EDITION_NAME). These U-indexes confirm that a fulfillment element may have multiple configuration rows, differentiated by lookup and by the effective start date — a classic effective-dated pattern.

Common Use Cases and Queries

Provisioning engineers and support analysts query this table to trace how a given fulfillment element is wired for software execution. A representative join retrieves the current effective configuration for an element:

• SELECT c.FE_GENERIC_CONFIG_ID, c.FE_ID, c.FE_SW_GEN_LOOKUP_ID, c.SW_START_PROC, c.SW_EXIT_PROC FROM XDP_FE_GENERIC_CONFIG c WHERE c.FE_ID = :fe_id AND SYSDATE BETWEEN c.START_DATE AND NVL(c.END_DATE, SYSDATE) AND c.ZD_EDITION_NAME = 'ORA$BASE';
• Joins to XDP_PROC_BODY resolve the actual PL/SQL bodies invoked at start and exit, useful for runtime diagnostics.
• Joins to XDP_FE_ATTRIBUTE_VAL enumerate attribute values attached to each configuration row.
• Reconciliation queries against XDP_FES verify that every active fulfillment element has a corresponding generic configuration.

Related Objects

• XDP_FES — parent fulfillment element master; joined via FE_ID.
• XDP_FE_SW_GEN_LOOKUP — lookup definitions; joined via FE_SW_GEN_LOOKUP_ID.
• XDP_PROC_BODY — PL/SQL procedure bodies invoked at start and exit; joined via SW_START_PROC and SW_EXIT_PROC.
• XDP_FE_ATTRIBUTE_VAL — child attribute-value table; joined via FE_GENERIC_CONFIG_ID.
• FND_SECURITY_GROUPS — security-group master; joined via SECURITY_GROUP_ID.