Search Results pon_doctype_styles




Overview
Explore in AI Chat

Overview

PON_DOCTYPE_STYLES is a configuration table in the Oracle E-Business Suite Sourcing module (PON). It records, for each combination of document type and style, whether that style is enabled or disabled for use with the associated document type. In practical terms, the table acts as a control-point matrix: it governs which styles a Sourcing user may apply to a given type of sourcing document, such as an auction, a negotiation, or a related sourcing artifact represented by the PON_AUC_DOCTYPES registry.

The metadata provided classifies this object, heuristically mined from its foreign key structure, as standalone. Under a Data Vault modeling approach this would suggest treating PON_DOCTYPE_STYLES as neither a classic hub nor a pure link, but rather as a low-cardinality configuration entity whose natural business key is the pairing of document type and style. The table is owned by the PON schema and is VALID in the ETRM documentation set for 12.1.1 and 12.2.2.

Key Information Stored

The documented physical schema exposes nine columns. The most significant are the two foreign key columns that together form the substance of the record:

No surrogate primary key column is separately documented. The unique index PON_DOCTYPE_STYLES_U1 on (DOCTYPE_ID, STYLE_ID, ZD_EDITION_NAME) is the business-key candidate: it enforces that a document type may reference a given style only once per edition.

Common Use Cases and Queries

Typical usage centers on validating or reporting which styles are active for a document type. A common pattern joins the style registry to resolve the style name:

  • Listing enabled styles for a specific document type: select from PON_DOCTYPE_STYLES where DOCTYPE_ID = :p_doctype_id and ENABLED_FLAG = 'Y'.
  • Reporting the full configuration matrix by joining to PON_AUC_DOCTYPES on DOCTYPE_ID and to HR_ADE_STYLES on STYLE_ID to display human-readable names alongside the enabled indicator.
  • Troubleshooting missing style options in the Sourcing UI by confirming a row exists and that ENABLED_FLAG is set correctly for the document type in question.

Because the table is small and configuration-oriented, queries are typically low-volume lookups rather than analytical scans.

Related Objects

The two documented foreign keys anchor this table to the wider Sourcing and style data model:

  • PON_AUC_DOCTYPES — joined via DOCTYPE_ID; defines the document types to which styles are mapped.
  • HR_ADE_STYLES — joined via STYLE_ID; the style definitions applied across Oracle applications.

Consumers of this configuration generally sit within the Sourcing module, where document-type setup and style availability are resolved at runtime. The relationship data confirms the object participates primarily as a dependent child of both the document-type and style registries, reinforcing its role as a bridging configuration table rather than a transactional or high-volume entity.