Results for “doctype_id”

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

Overview

PON_AUC_BIZRULE_VALUES is a transactional configuration table in the PON (Sourcing) product schema of Oracle E-Business Suite, valid in both release 12.1.1 and 12.2.2. It stores the individual values assigned to negotiation business rules, acting as the associative layer that binds a specific rule definition to a specific negotiation document type and a specific lookup value. In practice, this table answers the question: "For this document type, which value applies to this business rule?" The table is central to how Oracle Sourcing enforces auction and negotiation behavior, since business rules drive validation, defaulting, and processing logic within the negotiation authoring and execution flow.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is link. The table does not function as an independent hub of business entities; rather, it resolves a many-to-many relationship between rule definitions and document types, with the lookup code qualifying the assignment.

Key Information Stored

The documented physical schema contains nine columns. The most significant are:

• LOOKUP_CODE — Part of the composite primary key; identifies the specific business rule value or rule parameter being assigned.
• BIZRULE_ID — Foreign key to PON_AUC_BIZRULES, identifying the parent business rule definition.
• DOCTYPE_ID — Foreign key to PON_AUC_DOCTYPES, identifying the negotiation document type to which the rule value applies.
• ZD_EDITION_NAME — The editioning column introduced in 12.2 multi-tenant and online patching architecture; participates in the unique index PON_AUC_BIZRULE_VALUES_U1.
• ORDER_BY — Controls display or processing sequence of rule values where multiple values exist.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard EBS WHO columns providing audit lineage for inserts and updates.

The primary key, PON_AUC_BIZRULE_VALUES_PK, is the composite of LOOKUP_CODE, BIZRULE_ID, and DOCTYPE_ID. The unique index PON_AUC_BIZRULE_VALUES_U1 covers DOCTYPE_ID, BIZRULE_ID, LOOKUP_CODE, and ZD_EDITION_NAME, making it the business-key candidate and simultaneously supporting the primary key access path.

Common Use Cases and Queries

Typical scenarios include auditing which business rules apply to a given negotiation type, diagnosing unexpected negotiation behavior caused by rule configuration, and migrating rule values between environments. A representative join returns rule definitions, document types, and assigned values:

• SELECT br.RULE_NAME, dt.DOCTYPE_NAME, v.LOOKUP_CODE, v.ORDER_BY FROM PON_AUC_BIZRULE_VALUES v, PON_AUC_BIZRULES br, PON_AUC_DOCTYPES dt WHERE v.BIZRULE_ID = br.BIZRULE_ID AND v.DOCTYPE_ID = dt.DOCTYPE_ID ORDER BY dt.DOCTYPE_NAME, br.RULE_NAME, v.ORDER_BY;
• Filtering by a specific document type to enumerate all rule values affecting that negotiation template.
• Reporting on rule value coverage to detect gaps where a document type has no configured value for an expected rule.

Because configuration is edition-aware in 12.2, queries should account for ZD_EDITION_NAME when reconciling pre- and post-patch data.

Related Objects

The most significant related objects, drawn from the documented foreign key relationships, are:

• PON_AUC_BIZRULES — Parent rule definition table; joined via BIZRULE_ID.
• PON_AUC_DOCTYPES — Negotiation document type table; joined via DOCTYPE_ID.
• The unique index PON_AUC_BIZRULE_VALUES_U1 — Enforces business-key uniqueness and supports lookup performance.
• Oracle Sourcing negotiation authoring logic, which reads these values to default and validate rule behavior at runtime.
• Standard EBS WHO audit columns, referenced for change tracking and data lineage reporting.

Together these objects form the configuration backbone for negotiation rule assignment in Oracle Sourcing across EBS 12.1.1 and 12.2.2.