Results for “crt_type”

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

Overview

OKC_CHANGE_REQUESTS_V is a bilingual reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKC – Contracts Core module. It exposes change request data stored in the change request base and translation tables, presenting a denormalized, translation-resolved result set suitable for concurrent programs, Forms LOVs, Oracle Reports, OBIEE/BI Publisher extractions, and interface/integration queries. Because the view performs the language join internally, consumers receive the change request name and short description already rendered in the session language without needing to know the underlying translation mechanics.

The view is documented as VALID in both the 12.1.1 and 12.2.2 releases, and its structure is stable across those versions. It functions strictly as a read layer over the base tables; all inserts and updates should target the underlying base tables (or the corresponding Forms/APIs) rather than the view itself, since it includes a join to a translation table that is not inherently updatable without an INSTEAD-OF trigger.

Underlying Base Objects

The view is defined over two referenced base objects, both presented through public synonyms:

• OKC_CHANGE_REQUESTS_B — the base ("B") table holding the non-translatable attributes of a change request, including identifiers, dates, authority, signature and extended flags, contract version references, and the standard 15 attribute columns plus the attribute category and WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN).
• OKC_CHANGE_REQUESTS_TL — the translation ("TL") table storing the language-dependent descriptive columns (NAME and SHORT_DESCRIPTION), keyed by ID and LANGUAGE.

The two are joined on CRTB.ID = CRTT.ID, with the translation side further filtered by CRTT.LANGUAGE = USERENV('LANG') so each row is returned in the language of the current session.

Key Columns

The view exposes the following significant columns, drawn from the DBA/ETRM column listing:

• ROW_ID — the ROWID of the base table row (CRTB.ROWID), useful for identifying/locking base records.
• ID — primary identifier of the change request, joining B and TL.
• OBJECT_VERSION_NUMBER — optimistic locking value used by the AOL/contracts framework.
• SFWT_FLAG — the "Secure Forward" / translation flag sourced from the TL table.
• CHR_ID, CRS_CODE, USER_ID — foreign references to the change request source, contract, and requesting user.
• NAME, SHORT_DESCRIPTION — translated descriptive text from OKC_CHANGE_REQUESTS_TL.
• DATETIME_REQUEST and the lifecycle timestamps DATETIME_APPROVED, DATETIME_REJECTED, DATETIME_EFFECTIVE, DATETIME_INEFFECTIVE, DATETIME_APPLIED — track the change request workflow.
• EXTENDED_YN, AUTHORITY, SIGNATURE_REQUIRED_YN, CRT_TYPE — change request characteristics and classification.
• VERSION_CONTRACT, APPLIED_CONTRACT_VERSION — the contract version requested versus the version to which it was applied.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the DFF (descriptive flexfield) columns for extensions.
• WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical usage includes listing change requests for a contract version, tracking approval/rejection status, extracting DFF data, and driving BI reports. Because it joins the translation table, it is best used for display and reporting rather than bulk data migration, where the base table may be preferred.

Sample query listing open change requests with translated names:

• SELECT id, name, short_description, datetme_request, authority FROM okc_change_requests_v WHERE crs_code = :p_crs_code ORDER BY datetme_request;
• SELECT id, version_contract, applied_contract_version, datetime_approved, datetime_applied FROM okc_change_requests_v WHERE chr_id = :p_chr_id AND datetime_applied IS NULL;
• SELECT id, name, attribute_category, attribute1, attribute2 FROM okc_change_requests_v WHERE crt_type = :p_type;

In all cases, apply the appropriate MO: Operating Unit and data-access security via the underlying contract context, since the view itself imposes no row-level security beyond language.