Search Results transaction_class




Overview
Explore in AI Chat

Overview

The view APPS.JL_ZZ_AR_TX_ATT_CLS_LOOKUP_V is a reporting and integration object within the Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2 environment, delivered as part of the ETRM (E-Business Tax / Tax Reporting) product family. It presents a curated, filtered subset of Oracle's general-purpose lookup infrastructure — specifically the seeded and user-defined lookup values associated with organization, contributor, and transaction classification. Rather than exposing the entire FND_LOOKUP_VALUES table, the view constrains its result set to three lookup types: ORGANIZATION_CLASS, CONTRIBUTOR_CLASS, and TRANSACTION_CLASS. This makes it the canonical reference source for the "transaction class" concept sought by users searching on that term.

Because it resolves user-facing meaning and descriptions alongside codes and date-range validity, the view is well suited to LOV (List of Values) population, validation logic, concurrent-program extraction, and BI Publisher or Discoverer reporting against tax and receivable transaction classifications. It respects Oracle's language and multi-org security conventions, so the values returned are automatically scoped to the session's language and operating unit security group.

Underlying Base Objects

The view is defined over a single documented base object: FND_LOOKUP_VALUES, accessed through the APPS synonym. FND_LOOKUP_VALUES is the standard Oracle Application Object Library table that stores every lookup code and its translation, active status, and descriptive attributes across all applications. The view does not join additional tables; instead, it filters and projects the columns of the base table.

Three predicates define the view's behavior. First, B.LANGUAGE = USERENV('LANG') restricts output to the lookup rows whose language matches the current session, guaranteeing correctly translated MEANING and DESCRIPTION values. Second, LOOKUP_TYPE IN ('ORGANIZATION_CLASS', 'CONTRIBUTOR_CLASS', 'TRANSACTION_CLASS') limits the result set to these three classification regimes. Third, VIEW_APPLICATION_ID = 0 and a SECURITY_GROUP_ID computed from SUBSTRB(USERENV('CLIENT_INFO'), 55, ...) enforce multi-org security group isolation, matching the client information passed at session initialization. A ROW_ID pseudo-column is also projected to enable row-level addressing.

Key Columns

  • ROW_ID — the underlying row identifier from FND_LOOKUP_VALUES, useful for update or reference operations.
  • LOOKUP_TYPE — distinguishes the three classes: ORGANIZATION_CLASS, CONTRIBUTOR_CLASS, or TRANSACTION_CLASS.
  • LOOKUP_CODE — the stored code value used by tax and receivable processing logic.
  • MEANING and DESCRIPTION — the language-specific display text and detail.
  • ENABLED_FLAG, START_DATE_ACTIVE, END_DATE_ACTIVE — control whether and when a classification is valid for selection.
  • TERRITORY_CODE — optional territory restriction for country-specific classifications.
  • VIEW_APPLICATION_ID, TAG, ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield and extensibility attributes.
  • SECURITY_GROUP_ID, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — audit and security columns.

Common Use Cases and Queries

Typical scenarios include populating a transaction-class LOV, validating a classification passed by an interface, and reporting on active classifications. The following returns all active transaction classes in the current language and security group:

SELECT lookup_code, meaning, description FROM apps.jl_zz_ar_tx_att_cls_lookup_v WHERE lookup_type = 'TRANSACTION_CLASS' AND enabled_flag = 'Y' AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE) ORDER BY meaning;

To retrieve all three classification families for a configuration report, the same view is queried with an IN ('ORGANIZATION_CLASS','CONTRIBUTOR_CLASS','TRANSACTION_CLASS') predicate and grouped by lookup_type. Because the view already enforces language and security-group filtering, callers should avoid appending redundant language or ORG_ID predicates, which can conflict with the session context set by the EBS application layer.