Results for “okc_folders_vl”

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

Overview

OKC_FOLDERS_VL is an Oracle E-Business Suite (EBS) views defined in the APPS schema and owned by the OKC – Contracts Core product. It is classified as an "Org striped Folders View," meaning it presents folder information for the Contracts Core module, exposing translated (language-specific) folder names and descriptions alongside the base folder attributes. The "VL" suffix follows the standard EBS naming convention for a "View with Language" — a view that joins a base table with its translation table and filters the translated rows by the current session language.

In both EBS 12.1.1 and 12.2.2, this view serves as the primary read interface for Contracts folder data for reporting, integration, and forms that need to display folder names and descriptions in the user's language. Folders in OKC are used to organize and categorize contract documents and related artifacts. Because the view resolves the translation internally via USERENV('LANG'), it abstracts away the underlying _B/_TL table split, allowing developers and report writers to query a single object and receive language-appropriate folder names without writing translation-aware SQL.

Underlying Base Objects

The documented ETRM metadata identifies the referenced base objects as OKC_FOLDERS_B (SYNONYM) and OKC_FOLDERS_TL (SYNONYM). The view text confirms this: it selects from OKC_FOLDERS_B (aliased FOLD) joined to OKC_FOLDERS_TL (aliased FOLDT) on FOLDER_ID, with the restriction FOLDT.LANGUAGE = USERENV('LANG').

• OKC_FOLDERS_B — the base (non-translated) table holding FOLDER_ID, ORG_ID, SAT_CODE, object version, WHO columns, and the 15 descriptive flexfield (DFF) attributes.
• OKC_FOLDERS_TL — the translation table containing LANGUAGE, SOURCE_LANG, FOLDER_NAME, and DESCRIPTION for each folder.

Because the join key is FOLDER_ID and LANGUAGE is constrained to the current environment language, the view returns exactly one row per folder for the active language, provided a translation exists.

Key Columns

• FOLDER_ID — Primary identifier of the folder; the join key between the _B and _TL tables.
• OBJECT_VERSION_NUMBER — Used for optimistic locking in the OAF/forms layer.
• ORG_ID — Multi-org operating unit identifier; the "org striped" nature of the view means folders are partitioned by organization.
• SAT_CODE — Code identifying the folder's status/type classification within Contracts Core.
• CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield context and segment values for folder-level DFF data.
• LANGUAGE, SOURCE_LANG — From the _TL table; LANGUAGE is filtered to the session language, SOURCE_LANG indicates the original language of the translated text.
• FOLDER_NAME, DESCRIPTION — The user-facing, translated name and description of the folder.

Common Use Cases and Queries

Typical uses include: enumerating folders for a given operating unit; joining folder data to contract documents or deliverable records; building custom reports or OBIEE extracts; and integration interfaces that fetch folder names in the user's language. Because the view automatically filters by USERENV('LANG'), the query results depend on the language of the database session issuing the call.

Example: retrieve all folders for the current organization with translated names.

• SELECT folder_id, org_id, sat_code, folder_name, description FROM apps.okc_folders_vl WHERE org_id = :p_org_id ORDER BY folder_name;
• SELECT v.folder_id, v.folder_name, v.language FROM apps.okc_folders_vl v WHERE v.folder_id = :p_folder_id;

When embedding this view in reports, note that it is org-striped; callers should pass or apply the correct ORG_ID (or rely on MOAC/CLIENT_INFO security) to restrict results to the appropriate operating unit. For translations in a language other than the session default, the session's NLS_LANG or USERENV('LANG') must be set accordingly, since the view does not expose all languages simultaneously.