Search Results bis_pmv_approval_types

Overview

The view APPS.BIS_APPR_MSGTYPE is a lightweight lookup-driven view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments. It exposes the set of valid approval type codes and their corresponding display values that are consumed by the Oracle Business Intelligence (BI) / Daily Business Intelligence (DBI) approval messaging components. In EBS reporting and integration terms, this view acts as a semantic bridge between the underlying Oracle Application Object Library (FND) lookup repository and the application code or reports that require a clean, two-column representation of approval type identifiers and their user-facing meanings.

The view is commonly surfaced when users search for the identifier bis_pmv_approval_types, since that is the lookup type it filters on. Rather than binding reports directly to FND_LOOKUP_VALUES_VL, this view standardizes the output columns as ID and VALUE, making it a convenient source for LOVs, parameter validations, and reference data joins across the BI product family.

Underlying Base Objects

According to the documented view text, BIS_APPR_MSGTYPE is defined exclusively over FND_LOOKUP_VALUES_VL. No additional base tables or objects are documented for this view. The definition is a straightforward projection with a hard-coded predicate:

SELECT lookup_code id, meaning value
  FROM fnd_lookup_values_vl
 WHERE lookup_type = 'BIS_PMV_APPROVAL_TYPES'

Because it selects from the _VL (view of lookups) variant, the view returns only values whose translations exist for the current language, ensuring that display meanings are localized. The dependency is entirely on the lookup framework, so the view inherits the standard FND lookup security and multi-language behavior without additional joins.

Key Columns

• ID — Derived from LOOKUP_CODE. This is the machine-readable code that identifies the approval type (for example, internal codes used by the BI approval messaging engine).
• VALUE — Derived from MEANING. This is the translated, user-facing description associated with the approval type, suitable for display in reports and LOVs.

Because the view exposes only these two aliased columns, consumers should not expect attributes such as enabled flags, effective dates, or descriptions. All filtering is already applied internally via the lookup type predicate, so the view returns only the approval types relevant to BI approval messaging.

Common Use Cases and Queries

Typical scenarios include populating a parameter LOV with approval types, translating stored lookup codes into readable labels in a custom report, and validating inbound integration payloads. A simple retrieval of all approval types is:

SELECT id, value
  FROM apps.bis_appr_msgttype;

A more practical query that resolves a stored approval code to its display meaning is:

SELECT b.value
  FROM apps.bis_appr_msgtype b
 WHERE b.id = :approval_code;

For integration or diagnostic purposes, developers often compare the view output against the underlying lookup to confirm both the code and meaning lists are synchronized:

SELECT l.lookup_code, l.meaning
  FROM fnd_lookup_values_vl l
 WHERE l.lookup_type = 'BIS_PMV_APPROVAL_TYPES'
   AND l.lookup_code NOT IN (SELECT id FROM apps.bis_appr_msgtype);

These queries illustrate the view's role as a focused, reusable reference source for approval type data within Oracle EBS BI reporting and integration workflows.