Results for “fsc_cls_id”

34 results




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

Overview

JL_ZZ_AR_TX_FSC_CLS_ALL is a table in the JL schema (JL – Latin America Localizations) that stores Latin Tax Fiscal Classification Information. It holds the definitional data that drives fiscal classification of transactions for Latin American tax reporting regimes within Oracle E-Business Suite 12.1.1 and 12.2.2. Because it is an _ALL table containing an ORG_ID column, it is a multi-org (operating unit) enabled object: rows are partitioned logically by operating unit, and the same fiscal classification code may be defined independently per organization.

The object is marked Status: VALID and is documented as a physical table in ETRM 12.2.2 with 30 columns. Its role is to map a fiscal classification code to a tax category, tax code, and base rate, together with effective dating and enabled status. It is a setup/definition table rather than a transactional table, so row volumes are typically low and change frequency is driven by tax configuration maintenance.

From a Data Vault modeling perspective, the mined metadata classifies this object heuristically as standalone. In practice this suggests the table is best modelled as either a hub for the fiscal classification business key (FISCAL_CLASSIFICATION_CODE combined with TAX_CATEGORY_ID and ORG_ID) or, because of its descriptive and effective-dated attributes, as a satellite attached to that hub. No downstream link relationships were mined beyond the reference from JL_BR_AR_TX_FSC_CLS_ALL.

Key Information Stored

The following are the most significant columns documented in the ETRM schema:

  • FSC_CLS_ID — the surrogate primary key, defined by constraint JL_ZZ_AR_TX_FSC_CLS_ALL_PK. It uniquely identifies each fiscal classification record independent of organization.
  • FISCAL_CLASSIFICATION_CODE — the user-facing classification code. This forms the leading column of unique index JL_ZZ_AR_TX_FSC_CLS_U1 together with TAX_CATEGORY_ID, END_DATE_ACTIVE, and ORG_ID, making it the primary business-key candidate.
  • TAX_CATEGORY_ID — identifies the tax category to which the fiscal classification belongs; a core part of both the business key and the tax determination logic.
  • TAX_CODE — the tax code associated with the classification, used to drive tax calculation.
  • BASE_RATE — the base rate applied to the classification.
  • ENABLED_FLAG — indicates whether the record is active for use.
  • START_DATE_ACTIVE and END_DATE_ACTIVE — the effective-dating window. END_DATE_ACTIVE is part of the unique business key, allowing multiple historical versions of the same classification code.
  • ORG_ID — the operating unit qualifier; participates in both U1 and U2 unique indexes.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard EBS WHO columns providing audit traceability.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard DFF (descriptive flexfield) container set, supporting country-specific or implementation-specific extensions without schema change.

The second unique index, JL_ZZ_AR_TX_FSC_CLS_U2 on (FSC_CLS_ID, ORG_ID), enforces that the surrogate key is unique within an operating unit, reinforcing the multi-org nature of the table.

Common Use Cases and Queries

Typical usage centres on validating and reporting fiscal classification setup, and on joining classifications to tax category and tax code for localization reporting in Argentina, Brazil, and other Latin American countries.

  • Setup validation — listing all enabled classifications for an operating unit:

    SELECT FISCAL_CLASSIFICATION_CODE, TAX_CATEGORY_ID, TAX_CODE, BASE_RATE
    FROM JL_ZZ_AR_TX_FSC_CLS_ALL
    WHERE ORG_ID = :org_id AND ENABLED_FLAG = 'Y'
    AND TRUNC(SYSDATE) BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE);

  • Effective-dated lookups — retrieving the classification in force at a transaction date, honouring the START_DATE_ACTIVE/END_DATE_ACTIVE window that forms part of unique index U1.
  • Rate reconciliation — comparing BASE_RATE across classifications and tax codes to detect configuration drift.
  • Audit reporting — using the WHO columns to report recent maintenance (who changed a classification and when).
  • DFF extraction — reporting ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 for country-specific classification attributes.

Related Objects

The FK relationship data identifies the following significant dependencies:

  • JL_BR_AR_TX_FSC_CLS_ALL — references this table via FSC_CLS_ID → JL_ZZ_AR_TX_FSC_CLS_ALL.FSC_CLS_ID. This is the Brazil-specific fiscal classification table, joining on the surrogate key.
  • JL_ZZ_AR_TX_FSC_CLS_ALL_PK — the primary key constraint on FSC_CLS_ID.
  • JL_ZZ_AR_TX_FSC_CLS_U1 — unique index on (FISCAL_CLASSIFICATION_CODE, TAX_CATEGORY_ID, END_DATE_ACTIVE, ORG_ID).
  • JL_ZZ_AR_TX_FSC_CLS_U2 — unique index on (FSC_CLS_ID, ORG_ID).
  • Tax category and tax code reference objects — joined via TAX_CATEGORY_ID and TAX_CODE respectively, providing the tax determination context.
  • Operating unit / organization reference — joined via ORG_ID to resolve the multi-org context.

The metadata describes this object as standalone in the Data Vault sense, with the sole mined dependent being the Brazil localization table; broader integration is achieved through the TAX_CATEGORY_ID, TAX_CODE, and ORG_ID reference columns rather than formal foreign keys.