Results for “jeit_clause_ref”

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

Overview

The view APPS.JE_IT_EXEMPT_LETTERS_V is a reporting and inquiry construct within the Oracle E-Business Suite (EBS) Financials/Subledger environment, spanning both release 12.1.1 and 12.2.2. Its purpose is to expose exemption letters associated with Italian tax reporting, presenting the stored data alongside decoded, user-facing lookup meanings. Rather than requiring callers to resolve lookup codes independently, the view joins the underlying exemption letter records to the FND_LOOKUPS table so that descriptive values for the clause reference and the letter type are returned in the same result set. This design makes the view suitable for concurrent program report sources, OAF-based inquiry pages, and integration extracts where human-readable output is expected. The view remains owned by the APPS schema and is defined as a non-updatable projection over a synonym and lookup metadata.

Underlying Base Objects

According to the documented ETRM metadata for release 12.2.2, the view references three objects:

• JE_IT_EXEMPT_LETTERS (SYNONYM) — the primary base object holding the exemption letter records. Column prefixes in the view text (EL.) map directly to this object.
• FND_LOOKUPS (VIEW) — joined twice, aliased LU1 and LU2, to resolve lookup codes into meanings.
• FND_GLOBAL (PACKAGE) — the standard EBS session context package, referenced by such views to establish ORG_ID and other runtime context.

The join conditions restrict LU1 to lookup type JEIT_CLAUSE_REF and LU2 to lookup type JEIT_EXEMPT_LETTER, ensuring that only the correct code sets are matched. Because both lookup joins are inner joins, a record whose CLause_REF or LETTER_TYPE does not exist in the corresponding lookup type will be filtered out of the view result.

Key Columns

The view exposes the full set of columns from the base letter table plus two derived descriptive columns:

• ROW_ID — the physical row identifier from the base table, useful for direct row addressing.
• EXEMPTION_LETTER_ID — primary key of the exemption letter record.
• LEGAL_ENTITY_ID, VENDOR_ID, SET_OF_BOOKS_ID — the operating context identifying the legal entity, supplier, and ledger.
• EFFECTIVE_FROM, EFFECTIVE_TO, YEAR — validity window and reporting year of the letter.
• CLAUSE_REF and CLAUSE_REF_DSP — the raw lookup code (the value the user searched for, jeit_clause_ref) and its decoded meaning drawn from lookup type JEIT_CLAUSE_REF.
• LETTER_TYPE and LETTER_TYPE_DSP — the raw letter type code and its decoded meaning from lookup type JEIT_EXEMPT_LETTER.
• LIMIT_AMOUNT — the monetary threshold associated with the letter.
• PRINT_FLAG, CUSTOM_FLAG, ISSUE_FLAG, ISSUE_DATE — control and status attributes governing printing, customization, issuance, and the issue timestamp.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

Typical usage centers on listing active exemption letters for a supplier or legal entity, filtering by lookup meaning rather than raw code, and exporting decoded values for reporting. A representative query follows:

• SELECT exemption_letter_id, vendor_id, legal_entity_id, clause_ref_dsp, letter_type_dsp, effective_from, effective_to, limit_amount FROM apps.je_it_exempt_letters_v WHERE clause_ref = '&clause_ref' AND year = :year;
• SELECT vendor_id, COUNT(*) FROM apps.je_it_exempt_letters_v WHERE effective_from <= SYSDATE AND NVL(effective_to, SYSDATE) >= SYSDATE GROUP BY vendor_id;
• SELECT clause_ref, clause_ref_dsp, letter_type_dsp FROM apps.je_it_exempt_letters_v WHERE issue_flag = 'Y';

Because the view is a projection, it should be treated as read-only; inserts, updates, and deletes must target JE_IT_EXEMPT_LETTERS directly. When extending reports, developers should also be aware that the inner joins to FND_LOOKUPS suppress records with unmapped lookup codes, a behavior that is significant when auditing incomplete configuration.