Results for “distribution_amt”

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

Overview

JAI_FBT_REPOSITORY is a transactional table owned by the JA (Asia/Pacific Localizations) schema in Oracle EBS 12.1.1 and 12.2.2. It stores all transactions that attract Fringe Benefit Tax (FBT), supporting statutory reporting obligations for Asia/Pacific legislation, particularly Australia. The table captures the tax-relevant attributes of each qualifying transaction, including taxable basis, computed tax and surcharge amounts, cess amounts, and the accounting distribution used for settlement. It is a VALID dictionary object with a documented physical schema of 39 columns in ETRM 12.2.2.

From a Data Vault modeling perspective, the mined FK structure suggests classification as a link. The table sits at the intersection of multiple business entities — legal entities, accounting flexfield combinations, invoice distributions, and general ledger journals — rather than representing a single durable business concept. A hub-and-link interpretation would treat each FBT transaction as a relationship event connecting a legal entity, a distribution account, and a period, with satellite attributes such as tax amounts and settlement status attached to that event.

Key Information Stored

The primary key is JAI_FBT_REPOSITORY_PK, defined on FBT_TRANSACTION_ID, which serves as the system-generated surrogate identifier for each FBT transaction record. A unique index, JAI_FBT_REPOSITORY_U1, is also documented on FBT_TRANSACTION_ID, making it the sole documented business-key candidate.

The most significant columns include:

• FBT_TRANSACTION_ID — surrogate primary key uniquely identifying each qualifying transaction.
• LEGAL_ENTITY_ID — the legal entity (organization) to which the FBT obligation belongs; references HR_ALL_ORGANIZATION_UNITS.
• PERIOD_START_DATE / PERIOD_END_DATE — the reporting period boundaries for the FBT calculation.
• INVOICE_DISTRIBUTION_ID / INVOICE_DATE / INVOICE_CURRENCY_CODE / DISTRIBUTION_AMT — source invoice distribution details and amount.
• FRINGE_BENEFIT_TYPE_CODE — classification of the fringe benefit driving the tax treatment.
• TAXABLE_BASIS / FBT_TAXABLE_AMOUNT — the basis of assessment and resulting taxable amount.
• FBT_TAX_AMOUNT, FBT_SURCHARGE_AMOUNT, FBT_EDU_CESS_AMOUNT, FBT_SH_CESS_AMOUNT — the computed tax, surcharge, and cess components.
• DIST_CODE_COMBINATION_ID — the accounting flexfield combination used for the distribution; references GL_CODE_COMBINATIONS.
• SETTLEMENT_ID, JE_HEADER_ID, JE_NAME, JE_LINE_NUM, PERIOD_NAME — identifiers linking the record to its settlement and journal entry posting.
• MANUAL_FLAG / MODIFIED_FLAG — indicators of user intervention or post-processing changes.

Common Use Cases and Queries

Typical usage centers on FBT liability reporting, reconciliation of FBT amounts to the general ledger, and audit trails for statutory submissions. A common query pattern retrieves all FBT transactions for a legal entity within a period:

• SELECT fbt_transaction_id, legal_entity_id, period_start_date, fbt_taxable_amount, fbt_tax_amount, fbt_surcharge_amount FROM jai_fbt_repository WHERE legal_entity_id = :p_legal_entity AND period_name = :p_period;
• Reconciliation: joining DIST_CODE_COMBINATION_ID to GL_CODE_COMBINATIONS to validate that posted FBT amounts agree with the distribution account balances.
• Journal audit: filtering on JE_HEADER_ID or JE_NAME to trace how FBT records were posted through subledger accounting to the GL.
• Exception review: filtering on MANUAL_FLAG = 'Y' or MODIFIED_FLAG = 'Y' to isolate records altered after initial calculation.

Related Objects

The following objects are most significant to JAI_FBT_REPOSITORY:

• GL_CODE_COMBINATIONS — referenced twice via DIST_CODE_COMBINATION_ID, supplying the accounting flexfield for distributions.
• HR_ALL_ORGANIZATION_UNITS — referenced via LEGAL_ENTITY_ID, identifying the responsible legal entity.
• JAI_FBT_REPOSITORY_PK / JAI_FBT_REPOSITORY_U1 — primary key constraint and unique index enforcing record uniqueness.
• GL_JE_HEADERS / GL_JE_LINES — related through JE_HEADER_ID and JE_LINE_NUM for journal entry traceability, where the localization posts FBT liabilities.
• AP invoice distribution tables — related through INVOICE_DISTRIBUTION_ID, the upstream source of qualifying transactions.