Search Results jai_cmn_inventory_orgs




Overview
Explore in AI Chat

Overview

The JAI_CMN_INVENTORY_ORGS table is a core setup entity within the Oracle E-Business Suite Asia/Pacific Localizations module, specifically designed for implementations in India. Its primary role is to serve as a central repository linking inventory organizations and their physical locations to the specific accounting and regulatory information mandated by Indian tax and excise laws. This table acts as a critical junction point, extending the standard Oracle Inventory and HR organizational structures by appending localization-specific attributes. It is essential for the accurate processing of transactions, calculation of taxes like MODVAT (now CENVAT), and generation of statutory reports such as RG registers. The table's validity in both EBS 12.1.1 and 12.2.2 underscores its continued importance in the localized financial and logistics architecture.

Key Information Stored

The table stores a combination of organizational identifiers and dedicated general ledger account mappings. The primary organizational data includes the ORGANIZATION_ID (linking to HR_ALL_ORGANIZATION_UNITS), LOCATION_ID (linking to HR_LOCATIONS_ALL), and MASTER_ORGANIZATION_ID. A critical regulatory field is the EC Code (Excisable Commodity Code), which identifies the product category for excise purposes. The table's defining feature is its extensive set of foreign keys to GL_CODE_COMBINATIONS, which store the specific account IDs for various localized transactions. These accounts include, but are not limited to, the RTV Expense Account, MODVAT Reverse Account, Scrap Cost Account, and accounts for MODVAT on Raw Materials (RM), Capital Goods (CG), and PLA (Personal Ledger Account). It also holds accounts for BOE (Bill of Entry), RG Rounding, and CESS Paid/Payable.

Common Use Cases and Queries

This table is primarily accessed during transaction posting (e.g., goods receipt, invoice creation) to determine the correct excise and accounting treatment based on the involved organization and location. It is also central to statutory reporting for excise. A common reporting query involves joining the table to HR and GL tables to list the complete setup for all inventory organizations. For troubleshooting or validation, one might query for organizations missing critical account assignments. Sample SQL to retrieve the basic setup with account codes often follows this pattern:

  • SELECT jcio.organization_id, haou.name org_name, jcio.location_id, hl.location_code, jcio.ec_code, gcc_rv.segment1 AS rtv_expense_acc
  • FROM jai_cmn_inventory_orgs jcio,
  • hr_all_organization_units haou,
  • hr_locations_all hl,
  • gl_code_combinations gcc_rv
  • WHERE jcio.organization_id = haou.organization_id
  • AND jcio.location_id = hl.location_id
  • AND jcio.rtv_expense_account_id = gcc_rv.code_combination_id(+);

Related Objects

JAI_CMN_INVENTORY_ORGS maintains extensive relationships with both core and localized tables, as documented by its foreign key constraints. It is a parent table to several key localization transaction tables, including JAI_CMN_RG_BALANCES and JAI_CMN_RG_OTH_BALANCES (via ORG_UNIT_ID), and JAI_OM_OE_BOND_REG_HDRS and JAI_OM_WSH_LINES_ALL (via the composite ORGANIZATION_ID and LOCATION_ID). As a child table, it references core EBS entities to ensure data integrity: HR_ALL_ORGANIZATION_UNITS (for ORGANIZATION_ID and MASTER_ORGANIZATION_ID), HR_LOCATIONS_ALL (for LOCATION_ID), and GL_CODE_COMBINATIONS for its numerous accounting fields (e.g., RTV_EXPENSE_ACCOUNT_ID, MODVAT_REVERSE_ACCOUNT_ID). This web of relationships positions it as a fundamental hub between standard Oracle functionality and India-specific compliance logic.