Results for “tr_ec_code”

28 results




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

Overview

JAI_CMN_INVENTORY_ORGS is a configuration and setup table owned by the JA (Asia/Pacific Localizations) schema in Oracle E-Business Suite, supporting the India Localization module. It stores organization- and location-level statutory and accounting information, including excise registrations, VAT and Central Sales Tax details, EC (Excise Control) codes, and inventory valuation account mappings. Each row represents a configured India inventory organization and location pair, along with the default accounts and tax parameters used by India Localization processes such as excise register maintenance, MODVAT/CENVAT accounting, and RG register balancing.

The table is central to India Localization because it links Oracle Inventory organizations to the General Ledger accounts that India statutory transaction flows must post to, and it identifies master organizations and master-location relationships. From a Data Vault modeling perspective, the heuristic classification is satellite-leaning: the table primarily describes the descriptive, time-variant attributes (registrations, account defaults, flags) attached to an inventory organization/location business key, rather than acting as a pure hub or associative link.

Key Information Stored

The table contains 104 columns. Its surrogate primary key is ORG_UNIT_ID (index JAI_CMN_INVENTORY_ORGS_PK). A unique, business-key candidate is defined by JAI_CMN_INVENTORY_ORGS_UK1 over ORGANIZATION_ID and LOCATION_ID, which enforces one configuration row per organization/location combination.

Common Use Cases and Queries

The table is queried to resolve the accounting flexfield accounts that India Localization processes must use, and to validate that an organization/location is correctly configured before excise or VAT transactions are processed. A typical reporting query joins JAI_CMN_INVENTORY_ORGS to GL_CODE_COMBINATIONS to obtain the concatenated account strings for each MODVAT and excise account.

  • Organization setup listing: SELECT organization_id, location_id, ec_code, st_reg_no FROM ja.jai_cmn_inventory_orgs;
  • Resolve MODVAT RM account to GL code combination: join MODVAT_RM_ACCOUNT_ID to GL_CODE_COMBINATIONS.CODE_COMBINATION_ID and select CONCATENATED_SEGMENTS.
  • Master/location mapping: filter MASTER_ORG_FLAG = 'Y' to identify master organizations, then join to dependent register tables on ORG_UNIT_ID.
  • Registration audit: report all organizations with optional or missing ST_REG_NO, CST_REG_NO, or VAT_REG_NO for compliance review.
  • Account default verification: compare the account IDs stored here with those actually used in India excise distributions.

Related Objects

The following objects are the most significant dependents and references, based on the documented FK relationships.

  • GL_CODE_COMBINATIONS — referenced through RTV_EXPENSE_ACCOUNT_ID, SCRAP_COST_ACCOUNT_ID, MODVAT_RM_ACCOUNT_ID, MODVAT_CG_ACCOUNT_ID, MODVAT_PLA_ACCOUNT_ID, MODVAT_REVERSE_ACCOUNT_ID, BOE_ACCOUNT_ID, RG_ROUNDING_ACCOUNT_ID, and CESS_PAID_PAYABLE_ACCOUNT_ID.
  • HR_ALL_ORGANIZATION_UNITS — referenced by ORGANIZATION_ID and MASTER_ORGANIZATION_ID.
  • HR_LOCATIONS_ALL — referenced by LOCATION_ID.
  • JAI_CMN_RG_BALANCES — references this table via ORG_UNIT_ID.
  • JAI_CMN_RG_OTH_BALANCES — references this table via ORG_UNIT_ID.
  • JAI_OM_OE_BOND_REG_HDRS — references this table via ORGANIZATION_ID and LOCATION_ID.
  • JAI_OM_WSH_LINES_ALL — references this table via ORGANIZATION_ID and LOCATION_ID.