Search Results okc_report_tag_b




Overview
Explore in AI Chat

Overview

The OKC_REPORT_TAG_B table is a Contracts Core (OKC) foundation table that stores the published XML tags used by the Oracle E-Business Suite Contract Printing feature. Each row defines a tag name (CODE) that is made available to the contract printing engine, allowing XML-based contract templates to reference contract attributes, merge fields, and structured content at print time. The table resides in the OKC schema and is identified by the primary key constraint OKC_REPORT_TAG_B_PK, defined on the ID column.

The object is documented as VALID within the ETRM 12.2.2 physical schema, with a documented column count of 11. The metadata notes that prior to release 11.5.9, published tags were surfaced through the Help tab rather than through a dedicated setup interface, which confirms the table's role as the runtime source of truth for tag availability in later releases.

Under a heuristic Data Vault classification mined from the foreign key structure, this object is assessed as standalone. That classification is a modeling suggestion only: because the table has no inbound foreign keys from other OKC tables and only a single outbound reference to FND_SECURITY_GROUPS, it behaves as an independent reference/configuration set rather than as a hub, link, or satellite within a normalized Data Vault model.

Key Information Stored

The table holds the tag definitions that drive contract printing. The most significant columns are:

  • ID — Surrogate primary key of the table, enforced by OKC_REPORT_TAG_B_PK. It is also the leading column of the unique index OKC_REPORT_TAG_B_U0.
  • XSL_ID — Identifier linking the tag to its associated XSL (stylesheet) definition used during contract rendering.
  • CODE — The published XML tag name exposed to contract templates. Together with XSL_ID it forms the business-key candidate enforced by the unique index OKC_REPORT_TAG_B_U1 (XSL_ID, CODE).
  • ENABLED_FLAG — Controls whether the tag is active and therefore available for use in contract printing.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Application Framework (OAF) and concurrent update handling.
  • SECURITY_GROUP_ID — Foreign key referencing FND_SECURITY_GROUPS, providing multi-organization and security-group isolation for the tag definition.
  • CREATED_BY, CREATION_DATE — Standard audit columns recording who created the tag and when.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns capturing the most recent change to the row, including the login that performed the update.

The distinction between the surrogate key (ID) and the business-key candidate (XSL_ID plus CODE) is important: integrations and lookups should generally resolve tags by XSL_ID and CODE, while foreign key relationships and technical joins use ID.

Common Use Cases and Queries

Typical uses include auditing which tags are published for a given XSL, validating that template tags resolve to enabled definitions, troubleshooting contract printing failures, and migrating tag definitions between environments.

  • Listing all enabled tags for a stylesheet:
  • SELECT CODE, XSL_ID, ENABLED_FLAG FROM OKC.OKC_REPORT_TAG_B WHERE XSL_ID = :xsl_id AND ENABLED_FLAG = 'Y' ORDER BY CODE;
  • Resolving a tag name used in a template:
  • SELECT ID, XSL_ID, ENABLED_FLAG FROM OKC.OKC_REPORT_TAG_B WHERE CODE = :code;
  • Auditing recent changes to tag definitions:
  • SELECT ID, CODE, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM OKC.OKC_REPORT_TAG_B WHERE LAST_UPDATE_DATE >= :from_date ORDER BY LAST_UPDATE_DATE DESC;
  • Detecting duplicates or conflicts across stylesheets by grouping on XSL_ID and CODE.
  • Joining to FND_SECURITY_GROUPS on SECURITY_GROUP_ID to report tag availability by security group.

Related Objects

The following objects are most significant in relation to OKC_REPORT_TAG_B:

  • FND_SECURITY_GROUPS — Referenced through OKC_REPORT_TAG_B.SECURITY_GROUP_ID, providing the security grouping for each tag definition.
  • OKC_REPORT_TAG_B_PK — The primary key constraint on ID, defining row uniqueness.
  • OKC_REPORT_TAG_B_U0 — The unique index on ID.
  • OKC_REPORT_TAG_B_U1 — The unique index on (XSL_ID, CODE), the business-key candidate.
  • OKC_XSL_DEFINITIONS / XSL-related tables — The XSL_ID column associates each tag with its rendering stylesheet definition.
  • Contract Printing / XML Publisher (XDO) components — Consume the published tags during contract document generation.
  • OKC_CONTRACTS and OKC-related setup tables — Provide the surrounding Contracts Core configuration context in which tags are published and used.