Results for “jlzz_ar_tx_fiscal_class_code”

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

Overview

The view APPS.JL_ZZ_AR_TX_FSC_LOOKUP_V is a localization-specific lookup view used within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, primarily within the context of Latin American (LATAM) tax and fiscal reporting. The view is designed to expose a filtered subset of Oracle Application Object Library (FND) lookup values that correspond to the fiscal class code set used in Accounts Receivable (AR) tax transactions. The lookup type it isolates is JLZZ_AR_TX_FISCAL_CLASS_CODE, which governs the classification of AR tax lines for fiscal and regulatory reporting purposes.

By encapsulating a predefined filter over FND_LOOKUP_VALUES_VL, the view provides a stable, self-documenting interface for reports, concurrent programs, and integrations that require the fiscal classification codes without needing to replicate the filter logic. It is not a transactional view; it is a reference or lookup view. Its role is to centralize the retrieval of a specific lookup class while enforcing security group isolation suitable for multi-org and multi-legal-entity deployments. The inclusion of attributes 1 through 15 indicates that the lookup values may carry supplementary segment data used by downstream LATAM localization logic.

Underlying Base Objects

The view is defined entirely over the single documented base object FND_LOOKUP_VALUES_VL, which is itself a view in the FND lookup framework. According to the ETRM 12.2.2 metadata, no other base tables are referenced. The definition applies a WHERE clause with three predicates: LOOKUP_TYPE = 'JLZZ_AR_TX_FISCAL_CLASS_CODE', VIEW_APPLICATION_ID = 0, and a security group restriction derived from the session client information. The VIEW_APPLICATION_ID = 0 predicate ensures that only values visible across application boundaries (or specifically seeded for the localization) are returned.

The security group predicate uses SUBSTRB(USERENV('CLIENT_INFO'), 55, 1) and SUBSTRB(USERENV('CLIENT_INFO'), 55, 10) to extract the security group identifier from the client info string, with a DECODE defaulting blank or null positions to zero. This mirrors the standard Multi-Org security pattern used throughout EBS. As with all FND lookup-based views, data changes in FND lookup maintenance are immediately reflected, since no materialized or cached copy is maintained.

Key Columns

All columns projected by the view originate from FND_LOOKUP_VALUES_VL. The most significant for consumers are:

• LOOKUP_TYPE — Always JLZZ_AR_TX_FISCAL_CLASS_CODE within this view.
• LOOKUP_CODE — The internal code representing a fiscal class value.
• MEANING and DESCRIPTION — User-facing translated descriptions.
• ENABLED_FLAG — Indicates whether the lookup value is active.
• START_DATE_ACTIVE and END_DATE_ACTIVE — Validity period of the lookup value.
• VIEW_APPLICATION_ID and SECURITY_GROUP_ID — Security and visibility scope identifiers.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield-style attributes that may hold localization-specific metadata.
• TERRITORY_CODE and TAG — Optional localization qualifiers.

Common Use Cases and Queries

Typical usage involves populating value sets in concurrent programs, forms, or OAF pages related to LATAM AR tax reporting. A standard query selecting all active fiscal classes is:

SELECT LOOKUP_CODE, MEANING FROM APPS.JL_ZZ_AR_TX_FSC_LOOKUP_V WHERE ENABLED_FLAG = 'Y' AND TRUNC(SYSDATE) BETWEEN NVL(START_DATE_ACTIVE, SYSDATE) AND NVL(END_DATE_ACTIVE, SYSDATE);

Because the view enforces security group isolation based on CLIENT_INFO, callers must ensure the database session is initialized with the correct multi-org context. Failure to do so may result in the security group predicate defaulting to zero and returning no rows or unintended rows. The view is commonly joined to AR tax line tables or LATAM tax reporting staging tables via LOOKUP_CODE. Its restriction to a single lookup type makes it convenient for reference data integration into external reporting layers without exposing unrelated lookup values.