Results for “user_status_code”

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

Overview

The OKC_SALES_TEMPLATES_V view is a reporting and integration object within the Oracle Contracts Core (OKC) module of Oracle E-Business Suite. It is owned by the APPS schema and carries a VALID status in both the 12.1.1 and 12.2.2 releases. The view presents a filtered, denormalized list of contract templates that are specifically designated as sales templates. Its purpose is to expose only those contract headers that satisfy a fixed set of business predicates, allowing downstream reports, integrations, and concurrent programs to consume a curated set of template records without repeatedly re-implementing the same filtering logic.

The view is a read-only presentation layer over the contract header, version, status, and subclass data model. Because it embeds temporal and classification filters directly in its definition, callers can rely on the view to return only currently effective sales templates.

Underlying Base Objects

The view is defined over several documented OKC objects. Contract header data is sourced from OKC_K_HEADERS_V, which supplies the core header attributes and the TEMPLATE_YN, BUY_OR_SELL, ISSUE_OR_RECEIVE, and classification codes. Version numbering is obtained from OKC_K_VERS_NUMBERS, joined on CHR_ID, providing the major and minor version values.

Status information is resolved through OKC_STATUSES_V, which maps the header status codes to their user-facing meaning and to the system status code (STE_CODE). Subclass and class validation is enforced through OKC_SUBCLASSES_B and OKC_CLASSES_B, ensuring that only records classified under the SALES class are returned. The OKC_UTIL package is also referenced in the documented object list, reflecting its role in supporting the contract reporting infrastructure. Together these objects form the standard OKC contract header and status model, with the view applying the sales-template filter on top.

Key Columns

• ID – Primary identifier of the contract header record.
• OBJECT_VERSION_NUMBER – Optimistic locking version for the header row.
• CONTRACT_NUMBER / CONTRACT_NUMBER_MODIFIER – The template's contract number and any modifier.
• MAJOR_VERSION / MINOR_VERSION – Version identifiers from OKC_K_VERS_NUMBERS.
• STATUS – The user-facing status meaning derived from OKC_STATUSES_V.
• USER_STATUS_CODE (STS_CODE) – The header's user-defined status code.
• SYSTEM_STATUS_CODE (STE_CODE) – The system status code exposed by the view, mapped from the status definition. This column is the target of the "system_status_code" search term and reflects the internal status classification used by Contracts Core.
• SCS_CODE – The subclass code associated with the template.
• SHORT_DESCRIPTION / DESCRIPTION – Descriptive text for the template.
• START_DATE / END_DATE – Effective date range for the template.
• APPROVAL_DATE, SIGNATURE_DATE, CANCELLATION_DATE, TERMINATION_DATE – Lifecycle milestone dates.
• AUTHORING_ORG_ID – The operating unit that authored the template.

Common Use Cases and Queries

Typical usage includes validating that a sales template exists before creating a contract, populating selection lists in custom forms, and feeding data warehouses. A representative query filtering on system status code follows:

• SELECT id, contract_number, status, system_status_code, start_date, end_date FROM okc_sales_templates_v WHERE system_status_code = :p_ste_code;
• SELECT contract_number, major_version, minor_version FROM okc_sales_templates_v WHERE authoring_org_id = :p_org_id;
• SELECT id, short_description, status FROM okc_sales_templates_v ORDER BY contract_number;

Because the view already restricts results to sales templates that are active as of SYSDATE, no additional effective-date predicates are normally required.