Results for “default_value”

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

Overview

PON_AUC_DOCTYPE_RULES is a table in the PON (Sourcing) module of Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. It stores the business rules that are applicable to a negotiation document type. In practical terms, the table acts as a junction or association between individual sourcing business rules and the negotiation document types to which they apply. It defines not only which rules are associated with a given document type, but also controls presentation and behavior attributes such as whether the rule is displayed, whether it is required, whether its value is fixed or defaulted, and whether restricted values apply. This makes it central to the configurable behavior of the Oracle Sourcing negotiation interface, since buyers configure negotiation styles and document types with rule sets that drive mandatory data entry and enforced value restrictions.

The heuristic Data Vault classification mined from the foreign key structure is a link. In Data Vault modeling terms, this table resolves a many-to-many relationship between business rules (PON_AUC_BIZRULES) and negotiation document types (PON_AUC_DOCTYPES). The suggestion is that PON_AUC_DOCTYPE_RULES should be modeled as a link table; researchers should treat the classification as a modeling heuristic rather than a definitive data warehouse design directive.

Key Information Stored

The most significant columns are:

• BIZRULE_ID — Identifier of the business rule; part of the composite primary key and a foreign key to PON_AUC_BIZRULES. This is the column most commonly referenced by the search term "bizrule_id."
• DOCTYPE_ID — Identifier of the negotiation document type; part of the composite primary key and a foreign key to PON_AUC_DOCTYPES.
• DISPLAY_FLAG — Indicates whether the rule is displayed for the document type.
• REQUIRED_FLAG — Indicates whether the rule value is mandatory.
• FIXED_VALUE — Holds a value that is fixed and therefore not user-modifiable.
• DEFAULT_VALUE — The value used when the user does not explicitly supply one.
• RESTRICTED_VALUES_FLAG — Indicates whether the acceptable values for the rule are restricted to a defined list.
• VALIDITY_FLAG — Indicates whether the rule association is currently valid/active.
• TEMPLATE_DISPLAY_FLAG — Controls display behavior in the context of templates.
• ZD_EDITION_NAME — Editioning column used in the 12.2 online patching (edition-based redefinition) architecture.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard EBS audit columns.

The documented primary key is PON_AUC_DOCTYPE_RULES_PK over (BIZRULE_ID, DOCTYPE_ID). A documented unique index, PON_AUC_DOCTYPES_RULES_U1, is defined over (DOCTYPE_ID, BIZRULE_ID, ZD_EDITION_NAME), which is the business-key candidate that also accommodates the editioning column.

Common Use Cases and Queries

Typical use cases include inspecting or reporting which business rules apply to a given negotiation document type, troubleshooting why a negotiation field is required or locked, and analyzing defaulted versus fixed values. A representative query joins the junction to its parent tables:

SELECT r.DOCTYPE_ID, r.BIZRULE_ID, r.DISPLAY_FLAG, r.REQUIRED_FLAG, r.FIXED_VALUE, r.DEFAULT_VALUE, r.RESTRICTED_VALUES_FLAG, b.* FROM PON_AUC_DOCTYPE_RULES r, PON_AUC_BIZRULES b WHERE r.BIZRULE_ID = b.BIZRULE_ID AND r.DOCTYPE_ID = :doctype_id;

Because the primary key is composite, lookups by BIZRULE_ID alone must be filtered by ZD_EDITION_NAME in a 12.2 multi-edition environment; in 12.1.1 the editioning column is not present and queries simply omit it. Reporting typically pivots on DOCTYPE_ID to summarize the rule set applied to a negotiation style.

Related Objects

• PON_AUC_BIZRULES — parent of the BIZRULE_ID foreign key; provides rule definitions. Join on BIZRULE_ID.
• PON_AUC_DOCTYPES — parent of the DOCTYPE_ID foreign key; provides negotiation document types. Join on DOCTYPE_ID.
• PON_AUC_DOCTYPE_RULES_PK — primary key constraint enforcing uniqueness of the rule-to-doctype pairing.
• PON_AUC_DOCTYPES_RULES_U1 — unique index over (DOCTYPE_ID, BIZRULE_ID, ZD_EDITION_NAME), the business-key candidate.
• PON_AUC_* rule set tables — companion rule configuration tables in the PON schema that define available behavior for negotiation styles.

Oracle Sourcing configuration and negotiation-style APIs ultimately resolve rules through these two parent tables, so any integration or custom report that needs to know which rules govern a document type must traverse PON_AUC_DOCTYPE_RULES.