Results for “fin_year”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The JAI_CMN_FIN_YEARS table, owned by the JA schema, is a foundational reference table within the Oracle E-Business Suite Asia/Pacific Localizations module. It stores the financial year definitions maintained per organization and serves as the validity master against which a broad set of statutory reporting and localization transaction tables are reconciled. Each row represents the combination of an operating unit (organization) and a specific financial year, together with the start date, end date, and active status of that year. In the 12.1.1 and 12.2.2 releases, this object remains a VALID dictionary table and is central to India and Asia/Pacific statutory reporting features.
Heuristically mined from its foreign key structure, the table exhibits a hub-leaning Data Vault classification. It carries a stable, well-defined business key (ORGANIZATION_ID and FIN_YEAR) and acts as the anchor around which multiple dependent reporting tables cluster. This suggests it is best modeled as a hub, with the reporting tables functioning as satellites or links referencing it.
Key Information Stored
The documented physical schema contains eleven columns. The most operationally significant are:
- ORGANIZATION_ID — Operating unit identifier; the leading component of the composite primary key and the join to HR_ALL_ORGANIZATION_UNITS.
- FIN_YEAR — The financial year label (e.g., 2013-2014); the second component of the primary key.
- FIN_YEAR_START_DATE — Beginning date of the financial year.
- FIN_YEAR_END_DATE — Closing date of the financial year.
- FIN_ACTIVE_FLAG — Indicates whether the financial year is currently active for the organization.
- OBJECT_VERSION_NUMBER — Optimistic locking column used by the concurrent/OLTP layer.
- CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns maintained by the EBS framework.
The surrogate/compound primary key is JAI_CMN_FIN_YEARS_PK, defined on (ORGANIZATION_ID, FIN_YEAR). Because the unique index is built on those two business columns, ORGANIZATION_ID and FIN_YEAR together constitute the business-key candidate; there is no separate single-column surrogate identifier. Uniqueness is therefore enforced at the organization-and-year grain.
Common Use Cases and Queries
Typical usage centers on validating whether a financial year is open for a given operating unit before posting statutory data, and on resolving year start/end dates for period-based reporting. The following patterns are representative:
- Listing all active financial years for an organization:
SELECT fin_year, fin_year_start_date, fin_year_end_date FROM ja.jai_cmn_fin_years WHERE organization_id = :org AND fin_active_flag = 'Y'; - Resolving the fiscal window for a specific year:
SELECT * FROM ja.jai_cmn_fin_years WHERE organization_id = :org AND fin_year = :yr; - Joining statutory transaction data back to the year master to filter by date range or active status across the JAI_CMN_RG_* family of tables.
- Reporting on organizations lacking a defined year, useful during localization setup verification.
Related Objects
The table is referenced extensively by India localization reporting tables. The most significant relationships are:
- HR_ALL_ORGANIZATION_UNITS — referenced via JAI_CMN_FIN_YEARS.ORGANIZATION_ID; supplies the operating unit definition.
- JAI_CMN_RG_23AC_I_TRXS and JAI_CMN_RG_23AC_II_TRXS — excise/CENVAT register transactions joined on ORGANIZATION_ID and FIN_YEAR.
- JAI_CMN_RG_23D_TRXS — Part II register transactions for the same key pair.
- JAI_CMN_RG_COMP_DTLS and JAI_CMN_RG_PLA_CMP_DTLS — compensation detail tables linked by organization and year.
- JAI_CMN_RG_PERIOD_BALS — period balance records for reporting reconciliations.
- JAI_CMN_RG_I_TRXS, JAI_CMN_RG_SLNOS (via CURRENT_FIN_YEAR), and JAI_CMN_RG_EXC_INV_NOS — invoice serial, exception, and transaction sources.
Together these dependencies confirm JAI_CMN_FIN_YEARS as the central fiscal-period reference hub for Asia/Pacific statutory reporting in Oracle EBS.
-
Stores information financial year information of organizations
-
Stores information pertaining to the ST Forms
-
This table holds setup information of Financial Periods.
-
Holds unique combination of OrganizationID, LocationID, Fin_Year as 57F4 Form No
-
Stores setup information to generate excise invoice numbers
-
Stores information pertaining to the ST Forms
-
Stores information financial year information of organizations
-
Holds unique combination of OrganizationID, LocationID, Fin_Year as 57F4 Form No
-
View: JAI_RCV_RG_AMOUNT_V 12.2.2
APPS.JAI_RCV_RG_AMOUNT_V·↳ JAI_CMN_RG_23AC_II_TRXS·↳ JAI_CMN_RG_PLA_TRXS·Explore JA module →
-
View: JAI_RCV_RG_QUANTITY_V 12.2.2
APPS.JAI_RCV_RG_QUANTITY_V·↳ JAI_CMN_RG_23AC_I_TRXS·↳ JAI_CMN_RG_23D_TRXS·↳ JAI_CMN_RG_I_TRXS·Explore JA module →
-
This table holds setup information of Financial Periods.
-
Stores regimeidentifier, party_id and party_site_id info for Document Seq Setup
-
This table is used for storing the information of GST tax calendar
-
This table stores threshold amount for ORG_TAN_NUM ,PARTY_PAN_NUM and FIN_YEAR
-
This table stores threshold amount for ORG_TAN_NUM ,PARTY_PAN_NUM and FIN_YEAR
-
View: JAI_CMN_RG_23_II_V 12.1.1
APPS.JAI_CMN_RG_23_II_V·↳ HR_ALL_ORGANIZATION_UNITS·↳ HR_LOCATIONS_ALL·↳ JAI_CMN_RG_23AC_II_TRXS·Explore JA module →
-
View: JAI_RCV_RG_QUANTITY_V 12.1.1
APPS.JAI_RCV_RG_QUANTITY_V·↳ JAI_CMN_RG_23AC_I_TRXS·↳ JAI_CMN_RG_23D_TRXS·↳ JAI_CMN_RG_I_TRXS·Explore JA module →
-
Stores the details of TDS challan for payments to TDS authority.
-
View: JAI_RCV_RG_AMOUNT_V 12.1.1
APPS.JAI_RCV_RG_AMOUNT_V·↳ JAI_CMN_RG_23AC_II_TRXS·↳ JAI_CMN_RG_PLA_TRXS·Explore JA module →
-
Stores setup information to generate excise invoice numbers
-
Stores regimeidentifier, party_id and party_site_id info for Document Seq Setup
-
View: JAI_CMN_PLA_REGISTER_V 12.2.2
APPS.JAI_CMN_PLA_REGISTER_V·↳ FND_PROFILE·↳ HR_GENERAL·↳ HR_LOCATIONS·Explore JA module →
-
View: JAI_CMN_PLA_REGISTER_V 12.1.1
APPS.JAI_CMN_PLA_REGISTER_V·↳ FND_PROFILE·↳ HR_GENERAL·↳ HR_LOCATIONS·Explore JA module →
-
Stores the details current threshold position for a threshold group.
-
This table stores the certificate information of Customers.
-
View: JAI_CMN_RG_23_II_V 12.2.2
APPS.JAI_CMN_RG_23_II_V·↳ HR_ALL_ORGANIZATION_UNITS·↳ HR_LOCATIONS_ALL·↳ JAI_CMN_RG_23AC_II_TRXS·Explore JA module →
-
Stores the details current threshold position for a threshold group.
-
This will have the details of all TDS invoices which has been paid
-
Stores the details of TDS challan for payments to TDS authority.
-
Stores detailed balances of each excise component for every PLA record
-
Stores detailed balances of each excise component for every PLA record
-
This table stores the certificate information of Customers.
-
Stores detailed balances of each excise component for every RG23A/C record
-
Stores detailed balances of each excise component for every RG23A/C record
-
This is the header table for storing OSP information
-
Stores Information of RG23A/C Part II Details. Also known as Amount Register
-
View: JAI_WCT_CERT_DTLS_V 12.2.2
APPS.JAI_WCT_CERT_DTLS_V·↳ JAI_AP_TDS_INV_PAYMENTS·↳ JAI_CMN_TAXES_ALL·Explore JA module →
-
This table stores transactions with TCS type of Tax. This is a TCS repository
-
Stores 57F4 Header Information for Purchase Orders of type OSP.
-
Stores RG Balances for each period, for different types of RegisterS
-
Quantity register for Trading Organizations
-
This is the header table for storing OSP information
-
This table stores transactions with TCS type of Tax. This is a TCS repository
-
Stores RG Balances for each period, for different types of RegisterS
-
Stores 57F4 Header Information for Purchase Orders of type OSP.
-
Stores the Transaction Information of PLA Register.
-
This will have the details of all TDS invoices which has been paid
-
Stores Information of RG23A/C Part II Details. Also known as Amount Register