Search Results bis_appr_msgtype

Overview

BIS_APPR_MSGTYPE is a lightweight database view registered under the FND — Application Object Library product within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 code lines. Rather than representing a physical or materialized reporting entity, the view functions as a lookup-driven decoding layer. It exposes the approval message-type values maintained in the Oracle Application Object Library (AOL) lookup framework and presents them as a two-column identifier/value pair suitable for direct use by forms, concurrent programs, and integration code.

The view exists specifically to service the approval workflow associated with the BIS product family (associated with Oracle Business Intelligence / Daily Business Intelligence pages and their publishing and approval model). It abstracts the underlying AOL lookup table so that developer and reporting code can resolve the approval type code stored on a transaction or message record into a user-visible, translated meaning without embedding a hard-coded join to FND_LOOKUP_VALUES_VL.

Per the ETRM 12.2.2 metadata, the view is documented but is marked as "Not implemented in this database" in the instance surveyed. This is a meaningful caveat: the view definition ships with the application, but in environments where the BIS approval feature set is not licensed or seeded, no object is created. The structure is nonetheless preserved in the data model so that dependent code fails predictably rather than silently.

Underlying Base Objects

The ETRM documentation records no separately documented base objects for this view. That is consistent with its definition, which is a single-table projection rather than a join. The view text is:

• Source table: FND_LOOKUP_VALUES_VL — the translated (VL, "view language") AOL lookup values table. This is the same object exposed by the standard FND_LOOKUPS view family.
• Filter predicate: LOOKUP_TYPE = 'BIS_PMV_APPROVAL_TYPES'. Only rows belonging to this lookup type are surfaced.
• Column projection: the internal LOOKUP_CODE is renamed to ID, and the translated MEANING is renamed to VALUE.

Because FND_LOOKUP_VALUES_VL is a language-sensitive view over FND_LOOKUP_VALUES_B and FND_LOOKUP_VALUES_TL, the VALUE column returned honors the session's language setting through the standard AOL language-resolution mechanism. This makes BIS_APPR_MSGTYPE an internationalized representation of the approval types without any additional code on the caller's part.

Key Columns

The view exposes exactly two columns:

• ID (LOOKUP_CODE) — the approval message-type code. This is the stored, language-independent value used as a foreign key by BIS approval records. Values are defined by the BIS_PMV_APPROVAL_TYPES lookup type.
• VALUE (MEANING) — the translated, user-facing description of the approval type. This is what should be displayed in reports, LOVs, and notification text.

There is no effective-dating filter in the view text as documented; callers requiring only currently enabled lookups should join to FND_LOOKUP_VALUES_VL directly or apply an ENABLED_FLAG predicate.

Common Use Cases and Queries

The view is typically used to populate a list of valid approval message types in a parameter LOV, to translate a stored code in a report, or to validate a value supplied by an interface. A basic enumeration follows:

• Populate an approval-type selection list for a concurrent program parameter.
• Decode a message-type code on a BIS approval staging table for display.
• Validate inbound integration codes against the seeded set before insert.

Sample query — list all approval types:

SELECT id, value FROM bis_appr_msgtype ORDER BY value;

Sample query — decode a stored code:

SELECT m.appr_type_code, b.value AS appr_type_meaning
FROM my_approval_table m, bis_appr_msgtype b
WHERE m.appr_type_code = b.id;

Because the view is not created in every instance, integration code should guard calls with a metadata check against ALL_VIEWS before relying on it, and fall back to a direct FND_LOOKUP_VALUES_VL query on the BIS_PMV_APPROVAL_TYPES lookup type where the object is absent.