Results for “xdp_fe_types”

50+ results




Overview
Explore in AI Chat

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

Overview

XDP_FE_TYPES is the fulfillment element type definition table owned by the XDP (Provisioning) schema in Oracle E-Business Suite. It functions as a foundational reference entity that enumerates the distinct categories of fulfillment elements the provisioning engine can recognize, validate, and orchestrate during service delivery. Each row represents one element type, providing the named identity against which dependent transactional and configuration data is registered.

From a Data Vault modeling perspective, the mined key structure (a single surrogate primary key with no participating parent references except an optional security group) suggests a hub-leaning classification — a durable business entity against which downstream links and satellites would resolve. This is a heuristic suggestion rather than a documented declaration.

Key Information Stored

  • FETYPE_ID — the surrogate primary key, enforced through XDP_FE_TYPES_PK. All dependent tables join back through this column, so it is the stable technical identifier referenced throughout the XDP schema.
  • FULFILLMENT_ELEMENT_TYPE — the human-readable business name of the element type. It is a business-key candidate, constrained by the unique index XDP_FE_TYPES_U1 (and XDP_FE_TYPES_U2 when editioning is present). This is the column most frequently surfaced in user-facing reports and lookup queries.
  • SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, restricting visibility of a given element type to the appropriate operating unit or security context.
  • ZD_EDITION_NAME — the editioning column introduced for online patching in EBS 12.2.2; it participates in both unique indexes and separates overlapping editions of the same business record.
  • Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN capture the standard Who columns for incremental extraction, auditable change tracking, and data-governance reporting.

The XDP_FE_TYPES_UK1 index identified by the user search corresponds to the alternative unique constraint on the business name, distinguishing it from the surrogate XDP_FE_TYPES_PK.

Common Use Cases and Queries

A frequent requirement is resolving a fulfillment element to its descriptive type name for reporting or troubleshooting. The core pattern joins the transactional table to this reference table on the surrogate key:

  • Lookup by name: SELECT fetery_id, fulfillment_element_type FROM xdp_fe_types WHERE fulfillment_element_type = :p_name — this leverages the UK1 unique index.
  • Dependency listing: SELECT f.fes_id, t.fulfillment_element_type FROM xdp_fes f JOIN xdp_fe_types t ON f.fetype_id = t.fetype_id WHERE f.order_line_id = :id.
  • Translation-aware reporting joins XDP_FE_TYPES_TL on FETYPE_ID and filters by the target language for localized element names.
  • Set-up validation confirms that every configured element in a provisioning path maps to a valid type, exercising the XDP_FE_TYPES_U2 constraint during data conversion or patching.

Related Objects

  • XDP_FES — the fulfillment element instance table, joined on FETYPE_ID.
  • XDP_FE_SW_GEN_LOOKUP — lookup of software-generation behavior per element type, joined on FETYPE_ID.
  • XDP_FE_TYPES_TL — the translated-attributes companion table, joined on FETYPE_ID.
  • FND_SECURITY_GROUPS — the security group reference reached via XDP_FE_TYPES.SECURITY_GROUP_ID.
  • XDP_FE_TYPES_PK, XDP_FE_TYPES_UK1, and XDP_FE_TYPES_U1/U2 — the constraints and indexes that enforce entity and business-key integrity.