Results for “okc_report_tag_b_u0”

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

Overview

OKC.OKC_REPORT_TAG_B is a base table in the Oracle E-Business Suite Contracts (OKC) schema that stores the published XML tags used by the Contract Printing facility. It functions as the repository of tag definitions that map symbolic tag codes to XSL stylesheet definitions, allowing contract output to be rendered with the correct tag substitutions at print time. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and the documented status is VALID across EBS 12.1.1 and 12.2.2.

Historically, prior to release 11.5.9, these tags were published on the help tab of the Contracts form. The migration to a governed table structure provided a controlled, queryable registry of tags that could be versioned and enabled selectively. From a Data Vault modeling perspective, the heuristic classification supplied in the metadata identifies this object as standalone; it can be treated as a reference hub candidate keyed on its surrogate identifier, with descriptive attributes (tag code, enabled flag, audit columns) behaving as satellite-style attributes.

Key Information Stored

The table contains eleven documented columns. The most significant of these are:

• ID — the surrogate primary key column, enforced by the unique index OKC_REPORT_TAG_B_PK. This is the internal identifier used by foreign key references.
• XSL_ID — foreign key to OKC_REPORT_XSL_B, linking each tag to its governing XSL stylesheet definition.
• CODE — a VARCHAR2(150) tag code, the business-facing name of the published tag.
• ENABLED_FLAG — a Y/N indicator controlling whether the tag is active for contract printing.
• OBJECT_VERSION_NUMBER — the optimistic locking column, set to 1 on insert and incremented on update, allowing Oracle APIs to detect stale records.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns tracking record provenance and maintenance history.
• SECURITY_GROUP_ID — used in hosted (multi-tenant) environments and referenced by the FND_SECURITY_GROUPS table.

Two unique indexes are documented: OKC_REPORT_TAG_B_U0 on ID, which is the primary surrogate key, and OKC_REPORT_TAG_B_U1 on the composite (XSL_ID, CODE), which represents the natural business-key candidate ensuring a tag code is unique within its XSL definition.

Common Use Cases and Queries

The principal use case is contract printing and tag validation. Developers and support analysts query the table to confirm which tag codes are enabled and to which XSL definition they belong. A typical pattern enumerates the enabled tags for a stylesheet:

• SELECT CODE FROM OKC.OKC_REPORT_TAG_B WHERE XSL_ID = :p_xsl_id AND ENABLED_FLAG = 'Y';
• A full projection using the documented query text: SELECT ID, XSL_ID, CODE, ENABLED_FLAG, OBJECT_VERSION_NUMBER FROM OKC.OKC_REPORT_TAG_B;
• Audit reporting on tag maintenance often filters on LAST_UPDATE_DATE to identify recently modified tag definitions.

Because the table is a base (non-interface) table, changes are normally performed through Oracle-supplied contract APIs rather than direct DML, given the OBJECT_VERSION_NUMBER concurrency control.

Related Objects

• OKC.OKC_REPORT_XSL_B — referenced by XSL_ID; the parent stylesheet table for each tag.
• OKC.OKC_REPORT_TAG_B# — the documented dependent object generated within the OKC schema.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID for hosted-environment security grouping.
• OKC_REPORT_TAG_B_U0 / OKC_REPORT_TAG_B_U1 — unique indexes enforcing the primary and composite business keys.