Results for “okc_folders_tl”

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

Overview

APPS.OKC_FOLDERS_VL is a multi-language (ML) validation view in the Oracle E-Business Suite Contracts (OKC) module. It exposes folder definitions maintained by the Contract Terms and Conditions (T&C) and folder management infrastructure, presenting the translatable attributes of folder records alongside their language-independent columns. Like other _VL views in EBS, it is designed so that consumers see only the row translation matching the session language, thereby simplifying application logic and reporting that must display folder names and descriptions in the runtime locale rather than in every installed language.

The view is owned by APPS and is documented in ETRM for both 12.1.1 and 12.2.2. It plays a supporting role in contracts authoring, folder administration, and any integration or report that needs to resolve folder identifiers to their user-facing labels. Because _VL views typically combine the base (_B) and translation (_TL) tables with a language predicate, this view functions as the canonical read interface for folder metadata.

Underlying Base Objects

The ETRM metadata documents two referenced base objects, both exposed through APPS synonyms:

• OKC_FOLDERS_B — the base table holding language-independent folder attributes, joined as the driving table FOLD.
• OKC_FOLDERS_TL — the translation table holding the language-dependent columns, joined as FOLDT.

The join condition is FOLD.FOLDER_ID = FOLDT.FOLDER_ID AND FOLDT.LANGUAGE = USERENV('LANG'). The language predicate restricts output to the single translation row matching the current session language, as returned by the USERENV('LANG') call. Consequently, exactly one row per folder is surfaced wherever a translation exists for that language. These base tables and the view all sit under the OKC schema and are exposed to APPS via synonyms, in keeping with standard EBS object publishing conventions.

Key Columns

The view selects all principal columns from OKC_FOLDERS_B and adds the translatable columns from OKC_FOLDERS_TL:

• FOLDER_ID — primary identifier of the folder; the join key between the base and translation tables.
• OBJECT_VERSION_NUMBER — used for optimistic locking and concurrency control.
• ORG_ID — the operating unit (multi-org) identifier, supporting organization-specific access and reporting.
• SAT_CODE — the folder structure / setup code associating the folder with its contract terms configuration.
• CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS auditing (WHO) columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard DFF/flexfield columns available for descriptive information.
• LANGUAGE, SOURCE_LANG — the language of the returned translation and its source language.
• FOLDER_NAME, DESCRIPTION — the translated, user-facing folder name and description.

Common Use Cases and Queries

Typical scenarios include resolving folder names for contract terms setup reports, validating folder configuration during integration, and driving LOVs that present folder choices in the session language. Because the language predicate is embedded in the view, consumers do not need to add LANGUAGE filtering manually.

List all folders with names and descriptions:

• SELECT folder_id, sat_code, folder_name, description FROM apps.okc_folders_vl ORDER BY folder_name;

Filter to a specific operating unit and structure code:

• SELECT folder_id, folder_name FROM apps.okc_folders_vl WHERE org_id = :p_org_id AND sat_code = :p_sat_code;

Join to contract terms data by folder identifier:

• SELECT v.folder_name, t.* FROM apps.okc_folders_vl v, apps.okc_terms_tl t WHERE v.folder_id = t.folder_id ...

These patterns make OKC_FOLDERS_VL the preferred read source for folder metadata, while OKC_FOLDERS_TL should be queried directly only when all language translations are required.