Results for “id_flex_num”

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

Overview

The JE_NO_INVEST_SETUP_B table is a setup table owned by the AP schema and delivered under the JE – European Localizations product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores configuration information that drives the Norwegian Investment Tax (investeringsavgift) localization, allowing the EMEA/European localization features to determine which accounting flexfield segment combinations and tax codes are eligible for investment tax treatment. Because the table holds relatively static configuration rows created during implementation rather than transactional postings, it functions as a reference or control table that downstream Norwegian tax calculations read at runtime.

From a Data Vault modeling perspective, the documentation classifies this object as hub-leaning. That classification reflects the fact that the table's primary key consists entirely of business-meaningful attributes rather than a single surrogate key, and that dependent code descriptions and translations are stored elsewhere. A modeler wishing to apply Data Vault principles would therefore treat JE_NO_INVEST_SETUP_B as the hub, with the companion translation table serving as a satellite carrying descriptive, language-dependent attributes.

Key Information Stored

The table contains 14 documented physical columns. The most significant are:

• SEGMENT_NAME – identifies the accounting flexfield segment to which the setup rule applies.
• FOR_SEGMENT_VALUE – the specific segment value (low or high, depending on configuration) covered by the rule.
• TAX_CODE_ALLOWED – the Norwegian tax code permitted for the referenced segment combination and investment tax processing.
• SET_OF_BOOKS_ID – the ledger for which the setup row is defined, scoping configuration across multiple sets of books.
• APPLICATION_COLUMN_NAME – identifies the application and column context that uses the setup rule.
• ID_FLEX_NUM – the key flexfield structure number associated with the segment.
• INV_CODE_COMBINATION_ID – links to the investment code combination used in the localization calculation.
• TAX_RATE – the investment tax rate applied for the configured combination.
• INACTIVE_DATE – the date on which the setup row ceases to be effective, supporting date-driven rule changes.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN – EBS standard WHO (audit) columns tracking insertion and modification.

Three attributes — SEGMENT_NAME, FOR_SEGMENT_VALUE, and TAX_CODE_ALLOWED — form both the composite primary key JE_NO_INVEST_SETUP_B_PK and the unique business-key index JE_NO_INVEST_SETUP_B_U1. No separate numeric surrogate key is documented, so the business key is the primary identifier in practice.

Common Use Cases and Queries

Implementation and support teams query this table to diagnose why a particular Norwegian investment tax line fails to calculate or produces an unexpected rate. A typical verification query filters on ledger scope and active dates:

SELECT segment_name, for_segment_value, tax_code_allowed, tax_rate
FROM ap.je_no_invest_setup_b
WHERE set_of_books_id = :p_sob_id
  AND NVL(inactive_date, SYSDATE+1) > SYSDATE;

Reporting scenarios include producing a configuration register of allowed tax codes per segment for audit, and joining to the translation table to present the setup in the user's language. Because the table is read during posting, tuning queries to use the unique index on the three business columns avoids full scans.

Related Objects

• JE_NO_INVEST_SETUP_TL – the translation table. Joined on SEGMENT_NAME, FOR_SEGMENT_VALUE, and TAX_CODE_ALLOWED; supplies language-dependent descriptions. The FK relationship runs from the TL child to this base table.
• The Norwegian Investment Tax program units and concurrent programs within the JE European Localizations module that read this setup to compute investment tax.
• FND_ID_FLEX_STRUCTURES and FND_ID_FLEX_SEGMENTS, referenced via ID_FLEX_NUM and SEGMENT_NAME for flexfield metadata.
• GL_CODE_COMBINATIONS, referenced via INV_CODE_COMBINATION_ID for the investment account combination.
• FND_TAX_CODES / AP_TAX_CODES where TAX_CODE_ALLOWED resolves to the tax code definition.
• Standard WHO audit columns are maintained through the standard EBS DML triggers and concurrent request context.