Search Results sts_code_meadning

Overview

OKR_TMP_RGTS_TXN_DV is a database view belonging to the OKR — Contracts for Rights product family in Oracle E-Business Suite. The OKR module governed the management of intellectual property rights, licensing agreements, and royalty-bearing contracts; it is designated as obsolete in current EBS releases and is retained only for backward compatibility with historical data. The "_DV" suffix conventionally denotes a "detail view" or derived view used internally by ETRM (Enterprise Territory and Rights Management) form and reporting logic rather than one exposed through a standard end-user concurrent program.

The view consolidates transaction-level rights data — restrictions, exclusivity, sellability, active date ranges, and descriptive text — with denormalized attributes resolved through the OKR_UTIL_PUB utility package. Because it joins template and rights transaction data, it is intended for read-only reporting and integration scenarios that surface rights transaction details in a flat, presentation-ready form. The metadata records the view as "Not implemented in this database," meaning it exists in the delivered object library but is not deployed in every installation; its presence depends on whether the obsolete OKR schema components were installed or subsequently removed.

Underlying Base Objects

The ETRM documentation lists no referenced base objects, but the view text establishes its dependencies directly. It selects primarily from an alias RTXB, joined to a secondary source TMPRB and a text table aliased RTXT.

• RTXB — the principal rights transaction base table, supplying the transaction identifiers, object references, flags (EXCLUSIVE_YN, RESTRICTED_YN, SELLABLE_YN), currency/legal entity keys (CHR_ID, CLE_ID), and active dates.
• TMPRB — a template rights table supplying VAL_PTRT_ID and IP_ID, used to resolve intellectual property name and type.
• RTXT — a text/detail table providing NAME, DESCRIPTION, RESTRICTION_TEXT, KEYWORD_TEXT, and SFWT_FLAG.
• OKR_UTIL_PUB — the OKR utility package, invoked through several PL/SQL functions to derive contract number, version number, status, intent, and IP attributes.

The join keys are expressed through OBJECT1_ID1 and OBJECT1_ID2 and the JTOT_OBJECT1_CODE discriminator, which controls whether the contract-derived columns are populated.

Key Columns

Columns prefixed STS_CODE relate directly to the user's search term "sts_code_meadning."

• STS_CODE — the contract status code, derived via OKR_UTIL_PUB.GET_CONTRACT_STATUS; populated only when JTOT_OBJECT1_CODE equals 'OKR_TEMPLATE_CONTRACT', otherwise NULL.
• STS_CODE_MEADNING — the decoded, user-facing status meaning returned by OKR_UTIL_PUB.GET_K_STATUS_MEANING. The misspelling is intentional and hard-coded in the delivered view; queries must reference the column exactly as spelled.
• CONTRACT_NUMBER / VERSION_NUMBER — contract identification resolved through GET_CONTRACT_NUMBER and GET_VERSION_NUMBER.
• BUY_OR_SELL — contract intent, from GET_CONTRACT_INTENT.
• IP_NAME, IP_TYPE, IP_TYPE_MEANING — intellectual property attributes resolved through GET_IP_NAME, GET_IP_TYPE, and GET_IP_TYP_MEANING.
• DURATION — computed period length between START_DATE_ACTIVE and END_DATE_ACTIVE via GET_PERIOD_DURATION.
• TXN_ID, IP_RIGHTS_ID, DNZ_RGTP_ID, VAL_PTRT_ID — surrogate keys linking to rights transactions and template definitions.
• EXCLUSIVE_YN, RESTRICTED_YN, SELLABLE_YN — Y/N flags governing rights usage terms.

Common Use Cases and Queries

The view supports rights transaction reporting, particularly for retrieving human-readable status labels alongside contract metadata. A typical query filtering on the populated status meaning:

• SELECT TXN_ID, CONTRACT_NUMBER, VERSION_NUMBER, STS_CODE, STS_CODE_MEADNING FROM OKR_TMP_RGTS_TXN_DV WHERE JTOT_OBJECT1_CODE = 'OKR_TEMPLATE_CONTRACT';
• SELECT CONTRACT_NUMBER, IP_NAME, IP_TYPE_MEANING, BUY_OR_SELL, DURATION FROM OKR_TMP_RGTS_TXN_DV WHERE RESTRICTED_YN = 'Y';
• SELECT CHR_ID, EXCLUSIVE_YN, SELLABLE_YN, START_DATE_ACTIVE, END_DATE_ACTIVE FROM OKR_TMP_RGTS_TXN_DV ORDER BY START_DATE_ACTIVE DESC;

Because the view is not implemented in every database, DBAs should verify existence against DBA_VIEWS before building dependent reports. Queries against STS_CODE_MEADNING must preserve the delivered spelling, and consumers should note that several columns remain NULL for rows not flagged as template contracts.