Search Results authoring_party_code

Overview

The APPS.OKC_TEMPLATE_USAGES_V view belongs to the Oracle Contracts Core (OKC) module and exposes template usage records maintained by the Oracle E-Business Suite Contracts application. Its role is to present a consolidated, query-friendly representation of how contract templates have been applied to specific documents, capturing the document identity, the authoring party, the contract source, the template referenced, and the numbering scheme used for the resulting document.

Because the view carries the suffix "_V" and is owned by APPS, it is intended primarily for reporting, inquiry, and integration consumption rather than direct DML. Applications and custom reports query the view to determine which templates are in active use, how governed documents were numbered, and whether a template usage is tied to a valid configuration. The view was noted under doc_numbering_scheme search intent, meaning it surfaces the DOC_NUMBERING_SCHEME column, allowing implementers to trace which numbering scheme governed a given contract document generated from a template.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, the view is defined over a single referenced base object: the synonym OKC_TEMPLATE_USAGES. The view text is a straight projection of the columns of OKC_TEMPLATE_USAGES with no joins, unions, or aggregation. As a result, it exhibits a strict one-to-one row cardinality with the underlying synonym and effectively presents the base template usages table in a governed APPS-owned read interface.

Because the definition is a direct SELECT over the synonym, all filtering, sorting, and derived logic must be applied by the calling query. No row-level security, organization-based restriction, or multi-org filter is introduced by the view itself. Consumers should therefore apply their own predicates, particularly on DOCUMENT_TYPE and AUTHORING_PARTY_CODE, to narrow result sets.

Key Columns

• DOCUMENT_TYPE — Classifies the document to which the template usage applies; useful for separating contracts, templates, or quotations.
• DOCUMENT_ID — Identifier of the specific document instance using the template.
• AUTHORING_PARTY_CODE — Indicates whether the document was authored internally or by an external party.
• CONTRACT_SOURCE_CODE — Source system or channel through which the contract originated.
• TEMPLATE_ID — Foreign key to the contract template applied.
• DOC_NUMBERING_SCHEME — The numbering scheme assigned to the generated document; central to the user's search.
• DOCUMENT_NUMBER — The actual document number produced under the scheme.
• ARTICLE_EFFECTIVE_DATE — Effective date associated with the template article set.
• CONFIG_HEADER_ID / CONFIG_REVISION_NUMBER — Identify the configuration header and revision, linking usage to configured contract structures.
• VALID_CONFIG_YN — Flag indicating whether the referenced configuration is valid.
• Standard audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER for optimistic locking.

Common Use Cases and Queries

Typical scenarios include auditing template adoption, reconciling document numbering, and validating configuration integrity. Because the view is a plain projection, queries remain simple.

To list all documents using a specific template with their numbering scheme:

• SELECT document_number, doc_numbering_scheme, document_type, creation_date FROM apps.okc_template_usages_v WHERE template_id = :p_template_id ORDER BY creation_date DESC;
• SELECT template_id, COUNT(*) FROM apps.okc_template_usages_v WHERE authoring_party_code = :p_party GROUP BY template_id; to measure template usage by party.
• SELECT document_id, config_header_id, config_revision_number FROM apps.okc_template_usages_v WHERE valid_config_yn = 'Y'; to validate configuration alignment.

Integrations extracting contract metadata commonly filter on DOCUMENT_TYPE and CONTRACT_SOURCE_CODE, then join the returned DOCUMENT_ID back to contract headers. As the view introduces no joins, performance depends directly on indexing and predicates supplied by the calling statement.