Search Results xdo_dgf_tpl_rules_u1

Overview

XDO.XDO_DGF_TPL_RULES is a transactional configuration table in the XDO (eXtensible Data Object / XML Publisher) schema within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores template rule definitions used by the XML Publisher (BI Publisher) engine when processing the Data Generator Framework (DGF). Each row associates a template context with a rule catalog entry and a description of the rule, controlling how report data is filtered or formatted before it is merged with a report template. The table is owned by XDO, resides in the APPS_TS_TX_DATA tablespace, and is designated VALID in the ETRM reference for 12.2.2.

Based on the mined foreign key structure, the table is standalone with respect to other XDO entities; a self-referencing relationship to OKC_XPRT_TEMPLATE_RULES is documented on TEMPLATE_RULE_ID, indicating that the rule identifier is shared with the contract template rule infrastructure. From a Data Vault modeling perspective, XDO_DGF_TPL_RULES is best treated as a hub-like entity keyed by TEMPLATE_RULE_ID, with descriptive rule and filter attributes behaving as satellite content. This is a heuristic suggestion, not a mandatory declaration.

Key Information Stored

The table contains 27 documented columns. The most significant are:

• TEMPLATE_RULE_ID (NUMBER) — the surrogate primary key and the single column of the unique index XDO_DGF_TPL_RULES_U1. It is the business-key candidate and the identifier by which the rule is referenced throughout the DGF processing pipeline.
• TEMPLATE_CONTEXT_ID (NUMBER) — links the rule to the template generation context in which the rule is evaluated.
• RULE_CATALOG_ID (NUMBER) — references the rule catalog entry that defines the behavior of the rule.
• TPL_RULE_DESCRIPTION (VARCHAR2, 2000) — free-text description of the rule, providing human-readable documentation of the rule's purpose and scope.
• FORMAT_FILTER_TYPE (VARCHAR2) — identifies the filter or formatting type applied when the rule executes.
• OBJECT_VERSION_NUMBER (NUMBER) — supports optimistic locking and concurrency control during updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns tracking row creation and modification.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 (VARCHAR2, 30 and 150) — the DFF (Descriptive Flexfield) context and segment columns for extensible attributes. Note that the ETRM metadata lists ATTRIUBTE8 as spelled, a typographical anomaly worth verifying against the actual data dictionary before relying on it in code.

Common Use Cases and Queries

Technical consultants query this table when diagnosing why a template's data filter is or is not applied, when migrating rule configurations between environments, and when auditing template rule lineage. A typical lookup retrieves the rule for a given template context:

SELECT r.TEMPLATE_RULE_ID, r.TEMPLATE_CONTEXT_ID, r.RULE_CATALOG_ID,
       r.TPL_RULE_DESCRIPTION, r.FORMAT_FILTER_TYPE
FROM   XDO.XDO_DGF_TPL_RULES r
WHERE  r.TEMPLATE_CONTEXT_ID = :p_context_id;

Reporting scenarios include enumerating all rules for a template context to validate completeness, joining to the rule catalog to resolve rule semantics, and extracting DFF attribute values for documentation. Because the EBS view APPS.XDO_DGF_TPL_RULES exposes the same structure, use the APPS synonym in concurrent-program SQL rather than the base table to respect EBS security and synonym conventions.

Related Objects

The following objects are most relevant when working with this table:

• APPS.XDO_DGF_TPL_RULES — the application-layer synonym/view that exposes the table to concurrent programs and PL/SQL.
• OKC_XPRT_TEMPLATE_RULES — documented foreign-key partner on TEMPLATE_RULE_ID, tying the rule to the contract template rule definition.
• XDO.DGF_TEMPLATES / XDO.DGF_TEMPLATE_CONTEXTS — parent structures that supply TEMPLATE_CONTEXT_ID values.
• XDO.DGF_RULE_CATALOG / RULE_CATALOG_ID references — the catalog master that defines allowable rule behavior.
• XDO_DGF_TPL_RULES_U1 — the unique index guaranteeing TEMPLATE_RULE_ID uniqueness.

Joins should be driven from TEMPLATE_RULE_ID and TEMPLATE_CONTEXT_ID to preserve referential integrity across the DGF and OKC rule structures.