Search Results persistent_flag




Overview
Explore in AI Chat

Overview

BNE_PARAM_LISTS_VL is a standard Oracle E-Business Suite translation (MLS) view owned by the APPS schema and delivered as part of the BNE – Web Applications Desktop Integrator product. It is defined over the BNE_PARAM_LISTS entity and follows Oracle's established convention for multilingual seed and setup data, in which a "_B" (base) table stores language-independent attributes and a "_TL" (translation) table stores the language-dependent prompt and description columns. The "_VL" suffix indicates that the view joins the two and filters the translation rows to the session's current language by restricting the TL row to LANGUAGE = USERENV('LANG').

In EBS 12.1.1 and 12.2.2 the object is documented as VALID in the ETRM repository. Functionally, the view presents parameter-list definitions used by the BNE/Web ADI parameter framework—the mechanism that determines which submission parameters are collected, how they are prompted, and how list-of-values content is resolved for a given integrator or layout. Reporting and integration code should query the _VL view rather than the underlying base and translation tables so that prompt text is returned in the user's own language without manual language joins.

Underlying Base Objects

The view text joins two documented synonyms:

The join is on the composite key APPLICATION_ID plus PARAM_LIST_CODE. Because the row identifier exposed is the base table's ROWID, the view remains updatable for the B (_B) columns in the conventional Oracle MLS pattern, while the translation columns are sourced from the TL table. Both synonyms resolve to APPS-owned objects, so grants on APPS.BNE_PARAM_LISTS_VL control access for custom schemas.

Key Columns

  • APPLICATION_ID / PARAM_LIST_CODE – the composite business key identifying a parameter list within its owning application.
  • LIST_RESOLVER – identifies the resolver used to populate the list of values; central to how BNE renders and validates parameter choices.
  • PERSISTENT_FLAG – indicates whether the parameter list definition is retained persistently.
  • ATTRIBUTE_APP_ID / ATTRIBUTE_CODE – the application and attribute context to which the parameter list applies.
  • COMMENTS – developer/functional remarks stored on the base row.
  • USER_NAME – the translated name of the parameter list.
  • PROMPT_LEFT / PROMPT_ABOVE – translated prompt text positioned to the left of or above the parameter field.
  • USER_TIP – translated tooltip or hint text.
  • OBJECT_VERSION_NUMBER – optimistic locking column used by the underlying framework.
  • ROW_ID – ROWID of the base table row, useful for diagnostics and deletion scripts.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE – standard WHO audit columns.

Common Use Cases and Queries

Typical uses include auditing which parameter lists exist for a given application, verifying prompt text in a target language, and tracing which resolver backs a given list before debugging Web ADI parameter behaviour.

List parameter lists for an application:

SELECT application_id, param_list_code, user_name, list_resolver, persistent_flag
FROM apps.bne_param_lists_vl
WHERE application_id = :app_id
ORDER BY param_list_code;

Locate prompt text for a specific list:

SELECT param_list_code, user_name, prompt_left, prompt_above, user_tip
FROM apps.bne_param_lists_vl
WHERE param_list_code = :code;

Because the view applies USERENV('LANG'), prompt columns reflect the language of the connected session; administrators auditing translations across all languages must query BNE_PARAM_LISTS_TL directly. Where a _VL query returns no rows for a known PARAM_LIST_CODE, the likely cause is a missing TL row for the session language rather than a missing base definition.