Search Results jebe_line_type

Overview

The view APPS.JE_BE_VAT_REP_RULES_V exposes the VAT reporting rule configuration used by Oracle E-Business Suite's Belgian localizations (the "JE_BE" prefix denotes Belgian ETRM/Global Accounting Engine components). It is a denormalized, human-readable presentation layer defined over the base rule table JE_BE_VAT_REP_RULES, joined to multiple FND_LOOKUPS instances. Each row represents a single VAT reporting rule that determines how a transaction type from a given source subledger (Payables, Receivables, General Ledger, or Cash) is mapped to a VAT transaction type, line type, VAT report box, non-recoverable VAT box, sign, and enabled status.

Its role is primarily operational and diagnostic: finance and localization support staff query it to understand the effective VAT box configuration applied during Belgian VAT return generation, rather than reading cryptic lookup codes from the base table. It is a read-only reference view and is not intended for transactional processing.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, the view is owned by APPS and is defined over the following documented base objects:

• JE_BE_VAT_REP_RULES (synonym) — the primary rules table (jv in the view text), holding the actual rule definitions keyed by set of books.
• FND_LOOKUPS (view) — referenced seven times (aliases s, t, v, l, b, b1, e, g) to translate stored codes into display meanings across lookup types such as JEBE_SOURCE, JEBE_AP_OF_TRANS_TYPE, JEBE_VAT_TRANS_TYPE, JEBE_LINE_TYPE, JEBE_VAT_REPORT_BOXES, JEBE_SIGN_FLAG, and YES_NO.
• FND_GLOBAL (package) — listed as a referenced base object, typically used for session context (e.g., session/org identifiers) within EBS localization logic.

The joins are mostly equijoins on lookup code, with the OF_TRANS_TYPE lookup type selected dynamically via DECODE on SOURCE, and the report-box lookups applied as outer joins ((+)).

Key Columns

• SET_OF_BOOKS_ID — identifies the ledger/set of books to which the rule belongs.
• SOURCE / SOURCE_DSP — the source subledger code (AP, AR, GL, CR) and its display meaning.
• OF_TRANS_TYPE / OF_TRANS_TYPE_DSP — the originating transaction type and its description.
• VAT_TRANS_TYPE / VAT_TRANS_TYPE_DSP / VAT_TRANS_TYPE_DESC — the mapped VAT transaction type code, meaning, and description.
• TAX_NAME — the tax name associated with the rule.
• LINE_TYPE / LINE_TYPE_DSP — the reporting line type.
• VAT_REPORT_BOX / VAT_REPORT_BOX_DSP and NOREC_VAT_REP_BOX / NOREC_VAT_REP_BOX_DSP — the recoverable and non-recoverable VAT report box mappings.
• SIGN_FLAG — the sign applied to the reported amount.
• START_DATE_ACTIVE / END_DATE_ACTIVE and ENABLED_FLAG — effective dating and active status.
• Audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN, and ROW_ID.

Common Use Cases and Queries

Typical scenarios include auditing active VAT rules for a given ledger, troubleshooting an incorrect report box, and validating enabled rules by source. A representative query follows:

• SELECT source_dsp, of_trans_type_dsp, vat_trans_type_dsp, vat_report_box_dsp, sign_flag FROM apps.je_be_vat_rep_rules_v WHERE set_of_books_id = :p_sob AND enabled_flag = 'Y' AND TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);
• Listing non-recoverable box mappings: SELECT * FROM apps.je_be_vat_rep_rules_v WHERE norec_vat_rep_box IS NOT NULL;
• Auditing recent changes: SELECT * FROM apps.je_be_vat_rep_rules_v WHERE last_update_date >= TRUNC(SYSDATE)-30;

Because all descriptive fields resolve through FND_LOOKUPS, results reflect the current lookup meanings, which may change independently of the rule records themselves — a consideration when producing historical reconciliations.