Results for “okc_folders_b”

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

Overview

APPS.OKC_ART_SET_NAMES_V is an Oracle E-Business Suite view belonging to the Contracts (OKC) module, part of the Enterprise Contracts / ETRM (Enterprise Contracts and Trade Management) application family. The view exposes the set of "article set" or folder definitions maintained in the contracts repository, presenting them in a translated, user-facing form suitable for reporting, list-of-values population, and integration lookups. In 12.1.1 and 12.2.2 the object resides in the APPS schema and is defined over the contracts folder tables, which store the named groupings used by the Contract Terms Library and related OKC features. Because the view derives its descriptive columns from a translation (TL) table joined on the session language, it returns names and descriptions in the language of the logged-in user rather than the base language, making it appropriate for multilingual deployments where contract terms, article sets, and clause folders must be displayed in the local language.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, OKC_ART_SET_NAMES_V is defined over two documented base objects, both referenced through synonyms: OKC_FOLDERS_ALL_TL and OKC_FOLDERS_B. OKC_FOLDERS_B is the base (non-translated) folder table holding the primary folder identifiers and language-independent attributes such as the folder primary key; it is the driving table in the view definition, aliased FOLD. OKC_FOLDERS_ALL_TL is the translated layer that stores folder name and description per language, aliased FOLDT. The join condition, FOLD.FOLDER_ID = FOLDT.FOLDER_ID, links each base folder row to its translated attributes, and the predicate FOLDT.LANGUAGE = USERENV('LANG') restricts the result to the current session language. The user's search term, "okc_folders_b", corresponds directly to one of these two documented base tables, confirming that this view is the reading layer through which folder definitions anchored in OKC_FOLDERS_B are surfaced together with their language-specific text.

Key Columns

The view exposes three columns, two of which are aliased from the underlying translated attributes:

• SAT_CODE — derived as TO_CHAR(FOLD.FOLDER_ID) from OKC_FOLDERS_B. This is the folder identifier rendered as a character string, serving as the code value used in lookups and downstream references.
• NAME — the FOLDER_NAME from OKC_FOLDERS_ALL_TL, providing the display name of the article set or folder in the session language.
• DESCRIPTION — the DESCRIPTION from OKC_FOLDERS_ALL_TL, supplying the descriptive text for the folder, also in the session language.

Because only the language-filtered translated row is joined, each folder returns exactly one row for the active language, ensuring consistent single-row output per SAT_CODE for reporting and value-set purposes.

Common Use Cases and Queries

The view is typically consumed where a compact, translated list of contract folder or article set names is required. A standard retrieval selects all three columns:

• SELECT sat_code, name, description FROM apps.okc_art_set_names_v ORDER BY name; — produces the full translated list for reporting or validation.
• SELECT name FROM apps.okc_art_set_names_v WHERE sat_code = :folder_id; — resolves a single folder identifier to its display name for integration or drill-down screens.
• SELECT sat_code, name FROM apps.okc_art_set_names_v WHERE UPPER(name) LIKE UPPER(:search_text) || '%'; — supports name-based search and list-of-values filtering.

Typical scenarios include populating contract-terms setup forms, validating folder references during data migration, and building multilingual reports where folder names must reflect the user's language. Because results depend on USERENV('LANG'), the same query returns localized text per session, so consumers should not cache results across languages.