Search Results link_to_data_source_id




Overview

The view AR_BPA_DATA_SOURCES_VL is a public, language-validated (VL) reporting object owned by the APPS schema in Oracle E-Business Suite Receivables. It exposes the configuration of Receivables Business Process Automation (BPA) data sources—the metadata that defines which source views feed the BPA engine, how those sources are sequenced and confirmed, and how they relate to one another. Because it is a VL view, it joins the base and translation tables and filters to the session language via USERENV('LANG'), returning descriptive text in the user's current language while resolving the base identifiers from the single base table.

In EBS 12.1.1 and 12.2.2 the object is documented as VALID and is registered against the AR – Receivables product. Its role is primarily diagnostic and integration-oriented: it provides a queryable, denormalized representation of BPA data-source setup without requiring direct joins against the underlying synonym objects. The presence of the DISPLAY_LEVEL column makes the view especially relevant to users investigating how data sources are presented hierarchically in the BPA setup and processing UI.

Underlying Base Objects

The view is defined over two base objects, both referenced through synonyms in the APPS schema:

The view joins the two on DATA_SOURCE_ID and restricts LANGUAGE to the session language. This is the standard VL pattern: base identifiers from the _B table, translated text from the _TL table. The view text also exposes ROWID from the base table as ROW_ID, an artifact of the view definition that identifies the underlying base row.

Key Columns

  • DATA_SOURCE_ID — primary identifier linking the base and translation records.
  • APPLICATION_ID — owning application of the data source.
  • OBJECT_TYPE / OBJECT_NAME — the database object type and name of the underlying source (for example, a view supplied by a product).
  • VO_USAGE_NAME / VO_USAGE_FULL_NAME — the value-object usage name and its fully qualified equivalent, used by the BPA framework to resolve the source at runtime.
  • VO_INIT_SEQUENCE — initialisation sequence controlling processing or display order.
  • DISPLAY_LEVEL — the hierarchy/indentation level at which the data source is shown, determining nesting in the BPA presentation structure. This is the column most frequently queried by users troubleshooting how sources appear in the UI.
  • LINK_TO_DATA_SOURCE_ID — self-referencing link to a parent data source, establishing source-to-source relationships.
  • INVOICED_LINE_ACCTG_LEVEL — accounting level applicable to invoiced lines for this source.
  • TAX_SOURCE_FLAG — indicates whether the source supplies tax-relevant data.
  • SOURCE_LINE_TYPE — classification of the line type produced by the source.
  • ENABLED_FLAG / SEEDED_FLAG — whether the source is active and whether it was delivered as seed data by Oracle.
  • DATASRC_VIEW_NAME / DATASRC_VIEW_DESC — translated name and description of the data-source view.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical scenarios include auditing BPA source configuration, tracing hierarchical relationships between sources, and verifying which sources are enabled and seeded. A common query filters on display level:

SELECT data_source_id,
       datasrc_view_name,
       object_name,
       vo_usage_name,
       display_level,
       link_to_data_source_id,
       enabled_flag,
       seeded_flag
FROM   apps.ar_bpa_data_sources_vl
WHERE  display_level IS NOT NULL
ORDER  BY display_level, vo_init_sequence;

To locate all child sources beneath a given parent:

SELECT data_source_id, datasrc_view_name, display_level
FROM   apps.ar_bpa_data_sources_vl
WHERE  link_to_data_source_id = :parent_id;

To review only active, seeded sources:

SELECT data_source_id, datasrc_view_name, object_name
FROM   apps.ar_bpa_data_sources_vl
WHERE  enabled_flag = 'Y'
AND    seeded_flag = 'Y';

Because the view applies language filtering, results are returned in the session language; joins to other BPA configuration objects should be made on DATA_SOURCE_ID where possible, rather than on descriptive text, to avoid language-dependent mismatches.