Results for “as_access_types_active_v”

4 results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The AS_ACCESS_TYPES_ACTIVE_V view is a documented reporting object within the Oracle E-Business Suite Sales Foundation (AS) module. Its stated purpose in the ETRM metadata is to expose active access types, meaning those access-type lookup values that are currently enabled for use. Access types are a controlled classification that governs how a user or responsibility may reach sales-related data, and the view provides a clean, filtered read interface over the underlying lookup definitions so that downstream forms, reports, and integrations do not need to re-implement the enabled-flag and lookup-type filters themselves.

Functionally, the view acts as a convenience layer rather than a stored entity. It presents only rows where the lookup is both enabled and of the ACCESS_TYPE class, making it suited to value-list population, validation logic, and reporting where only currently valid access types should appear. In Oracle EBS 12.1.1 and 12.2.2 this pattern is common: lookup values are stored centrally and filtered views expose subsets appropriate to a module. Because the view is read-only and derived from a single base table, it carries no independent persistence and cannot be maintained directly; any change must be made to the underlying lookup record.

Underlying Base Objects

According to the documented view text, AS_ACCESS_TYPES_ACTIVE_V is defined over a single base object: the AS_LOOKUPS table, aliased within the query as ASLKP. The ETRM metadata records that no referenced base objects are separately documented and that the view is "not implemented in this database," indicating that the object is defined but not instantiated in the reference environment. This is typical of objects that exist conditionally, depending on which Sales Foundation features or languages are installed.

The relationship to AS_LOOKUPS is direct and one-to-one. The view applies two restrictive predicates to that table:

  • ENABLED_FLAG = 'Y' — excludes disabled or end-dated lookup values.
  • LOOKUP_TYPE = 'ACCESS_TYPE' — restricts output to the single lookup class that defines access types.

No joins are performed, and no other tables, synonyms, or views are documented as contributing to the definition. Consequently, the view inherits the row granularity of AS_LOOKUPS for that lookup type: one row per active access-type lookup value.

Key Columns

The view projects three columns, all sourced from AS_LOOKUPS:

  • LOOKUP_CODE — the internal, typically uppercase code that uniquely identifies the access type within the ACCESS_TYPE lookup class. This is the value stored on transactional or setup records and is the key used in program logic.
  • MEANING — the translatable, user-facing label presented on forms and in value lists. In multilingual environments the meaning may vary by language installation.
  • DESCRIPTION — optional free-text detail providing additional context for the access type, suitable for display or documentation purposes.

Because the view exposes only these three attributes, consumers cannot retrieve audit columns such as creation dates, last-update information, or the disabled rows themselves. Any requirement involving historical or inactive access types must query AS_LOOKUPS directly.

Common Use Cases and Queries

The principal use case is populating selection lists and validating user input against currently valid access types. A report or concurrent program that must present only active access types can select from the view without adding filter conditions:

  • Listing all active access types for display: SELECT LOOKUP_CODE, MEANING, DESCRIPTION FROM AS_ACCESS_TYPES_ACTIVE_V ORDER BY MEANING;
  • Resolving a stored code to its displayed label: SELECT MEANING FROM AS_ACCESS_TYPES_ACTIVE_V WHERE LOOKUP_CODE = :p_access_type;
  • Validating that a supplied code is currently active: SELECT COUNT(*) FROM AS_ACCESS_TYPES_ACTIVE_V WHERE LOOKUP_CODE = :p_access_type;

Integrations that extract reference data for external systems may also use the view as a stable source of the active access-type set, avoiding dependence on the broader lookup table. In every case the semantics remain the same: the view answers the question "which access types are enabled right now," using the Sales Foundation lookup model as authoritative.