Search Results upload_header

Overview

BNE_INTEGRATORS_VL is a standard Oracle Application Object Library translation (TL) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It sits within the BNE product family — Web Applications Desktop Integrator (Web ADI) — and presents the denormalized, language-specific definition of an "integrator," the metadata construct that drives how Web ADI uploads, downloads, imports, and lays out data into EBS forms. The view performs a left-side join between the base entity table BNE_INTEGRATORS_B and its translation table BNE_INTEGRATORS_TL, exposing translated presentation attributes such as USER_NAME, UPLOAD_TITLE_BAR, and UPLOAD_HEADER alongside the language-independent operational attributes. Its role in reporting and integration is to give developers, administrators, and diagnostic tools a single, language-resolved source of truth for every registered integrator, including the parameter list assignments that govern how a given integrator prompts the end user at runtime. The view is documented as VALID in the ETRM repository and is treated as a read-only reporting and validation object; the underlying entity is maintained through the Web ADI administrator UIs rather than by direct DML against the view.

Underlying Base Objects

The view is defined over two documented base objects, both accessed through public synonyms:

• BNE_INTEGRATORS_B — the base entity table (alias I) holding the canonical, non-translated definition of each integrator.
• BNE_INTEGRATORS_TL — the translation table (alias T) holding the language-dependent descriptive attributes.

These are joined on the composite key APPLICATION_ID and INTEGRATOR_CODE, with the translation row further restricted by T.LANGUAGE = USERENV('LANG'). The B and TL layers are related one-to-many in principle (one base row per language), and the view projects only the row matching the caller's session language, which is why every query against BNE_INTEGRATORS_VL returns exactly one row per integrator regardless of how many translations exist. The view also exposes I.ROWID as ROW_ID, providing a stable identifier for the base row.

Key Columns

• APPLICATION_ID, INTEGRATOR_CODE — composite business key uniquely identifying an integrator within an application.
• ENABLED_FLAG, DISPLAY_FLAG — control whether the integrator is active and visible to end users.
• SESSION_PARAM_LIST_APP_ID, SESSION_PARAM_LIST_CODE — the parameter list governing the integrator's session, i.e. the runtime prompt/parameter set presented when a user launches the integrator. This is the column referenced by the search term "session_param_list_code."
• UPLOAD_PARAM_LIST_APP_ID/CODE, UPLOAD_SERV_PARAM_LIST_APP_ID/CODE, IMPORT_PARAM_LIST_APP_ID/CODE, CREATE_DOC_LIST_APP_ID/CODE — sibling parameter-list assignments for the upload, upload-service, import, and document-creation phases of the integrator lifecycle.
• UPLOADER_CLASS, LAYOUT_RESOLVER_CLASS, LAYOUT_VERIFIER_CLASS, SESSION_CONFIG_CLASS — Java class hooks that implement custom behavior.
• IMPORT_TYPE, DATE_FORMAT, NEW_SESSION_FLAG — behavioral flags controlling import semantics, date rendering, and session handling.
• USER_NAME, UPLOAD_TITLE_BAR, UPLOAD_HEADER — translated (TL) display attributes resolved to the session language.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE, OBJECT_VERSION_NUMBER — standard WHO/audit and optimistic-locking columns.

Common Use Cases and Queries

Typical usage includes auditing integrator configuration, resolving the parameter list applied to a session, and diagnosing why an integrator fails to launch or upload.

• List all enabled integrators and their session and upload parameter lists:

SELECT application_id,
       integrator_code,
       user_name,
       session_param_list_app_id,
       session_param_list_code,
       upload_param_list_code,
       import_param_list_code
  FROM apps.bne_integrators_vl
 WHERE enabled_flag = 'Y'
   AND display_flag = 'Y'
 ORDER BY application_id, integrator_code;

• Find integrators referencing a specific session parameter list (directly addressing the "session_param_list_code" search):

SELECT integrator_code, user_name, session_param_list_app_id
  FROM apps.bne_integrators_vl
 WHERE session_param_list_code = :p_code;

• Inspect translation content for a single integrator to verify the title bar and header text presented to users:

SELECT integrator_code, user_name, upload_title_bar, upload_header
  FROM apps.bne_integrators_vl
 WHERE application_id = :app_id
   AND integrator_code = :code;

Because BNE_INTEGRATORS_VL is a view over B and TL tables, it is safe for read-only reporting and validation but should not be used for DML; integrator definitions must be maintained through the supported Web ADI administrative interfaces.