Results for “rate_var_code_combination_id”

2 results




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

Overview

JE_NO_INVEST_LINES is a table owned by the AP schema within Oracle E-Business Suite, classified under the JE – European Localizations product. Per the ETRM metadata, it is a structural copy of AP_INVOICE_DISTRIBUTIONS augmented with two additional columns that support investment tax processing. The table therefore carries the full invoice distribution grain—one row per accounted distribution line of an Oracle Payables invoice—while layering European localization attributes on top of the standard Payables distribution model.

Its role is archival and processing-oriented: it stores distribution lines that must be excluded from, or handled separately during, investment tax calculation and accounting. The table participates in the Payables accounting lifecycle through standard distribution columns such as POSTED_FLAG, ACCOUNTING_DATE, and JE_BATCH_ID, and in concurrent processing through its foreign keys to FND_CONCURRENT_PROGRAMS. The physical schema at 12.2.2 documents 117 columns, confirming status VALID in the AP schema.

Under the heuristic Data Vault classification derived from its foreign key structure, the table is satellite-leaning. This is a modeling suggestion only: the table behaves as a descriptive, line-level record attached to parent invoice and distribution hubs, rather than as an independent hub of business entities.

Key Information Stored

The most operationally significant columns include:

Because the table mirrors AP_INVOICE_DISTRIBUTIONS, the surrogate/business-key distinction follows the same convention: INVOICE_DISTRIBUTION_ID is the preferred unique identifier, while INVOICE_ID plus DISTRIBUTION_LINE_NUMBER forms the natural business key.

Common Use Cases and Queries

Typical uses include reconciliation of Payables distributions against investment tax exclusions, audit reporting of which lines were carried into the localization table, and validation that excluded lines were correctly accounted.

  • Invoice-level reconciliation — compare JE_NO_INVEST_LINES to AP_INVOICE_DISTRIBUTIONS for a given invoice to identify excluded lines.
  • Posting status reporting — filter on POSTED_FLAG or PERIOD_NAME for period-close reporting.
  • Tax analysis — aggregate AMOUNT by TAX_CODE_ID or VAT_CODE where TAX_RECOVERABLE_FLAG is set.
  • Award/grant linkage — join to IGF_AW_AWARD_ALL on AWARD_ID to report grant-funded lines.

A representative pattern:

  • SELECT n.INVOICE_ID, n.DISTRIBUTION_LINE_NUMBER, n.AMOUNT, n.POSTED_FLAG
  • FROM AP.JE_NO_INVEST_LINES n
  • WHERE n.PERIOD_NAME = :period AND n.POSTED_FLAG = 'Y';

Related Objects

  • AP_INVOICE_DISTRIBUTIONS — the source table this object copies; joined on INVOICE_DISTRIBUTION_ID and INVOICE_ID.
  • AP_INVOICES_ALL — parent invoice header, joined on INVOICE_ID.
  • AP_INVOICE_LINES_ALL — invoice line detail, joined on INVOICE_ID.
  • FND_CONCURRENT_PROGRAMS — documented foreign key via PROGRAM_APPLICATION_ID and PROGRAM_ID.
  • IGF_AW_AWARD_ALL — documented foreign key via AWARD_ID.
  • AP_JE_HEADERS_ALL / AP_JE_LINES_ALL — journal entry batch and line records referenced through JE_BATCH_ID.
  • GL_CODE_COMBINATIONS — accounting flexfield definitions for DIST_CODE_COMBINATION_ID.

Because the object is proprietary to the JE European Localizations module, joins should always be constrained by SET_OF_BOOKS_ID and period to limit scan volume.