Search Results baisc_ed




Overview

APPS.JAI_CMN_PLA_REGISTER_V is a reporting view in the Oracle E-Business Suite Asia/Pacific (JA) Localizations module, owned by the APPS schema and validated against release 12.1.1 and 12.2.2. It presents a consolidated, business-friendly projection of the Plant, Machinery, and Localization Accounting (PLA) transaction register maintained by the Asia/Pacific localization layer. Its principal role is to expose the register in a format suitable for statutory reporting, register printing, reconciliation, and downstream integration, rather than for direct transactional entry.

The view joins the transaction base table JAI_CMN_RG_PLA_TRXS to organization and location master data, resolving internal foreign keys into descriptive names and codes. It additionally enforces the operating unit security context through the ORG_ID profile option, making it a session-aware reporting object. The view is a key component of ETRM-documented metadata and is frequently targeted by report queries that need register line detail without directly navigating the underlying PLA tables.

Underlying Base Objects

The view is defined over the following documented base objects:

  • JAI_CMN_RG_PLA_TRXS (synonym) — the primary transaction register table, aliased A, supplying transaction dates, debit/credit economic development amounts, opening and closing balances, invoice references, financial year, and register identifiers.
  • ORG_ORGANIZATION_DEFINITIONS (view) — aliased HR_ORG, supplying organization name, organization code, and operating unit; joined on ORGANIZATION_ID.
  • HR_LOCATIONS (view) — aliased HR_LOC, supplying location code and description; joined on LOCATION_ID.
  • JAI_CMN_INVENTORY_ORGS (synonym) — used in a subquery to restrict results to inventory-relevant organizations.
  • FND_PROFILE (package) — invoked as FND_PROFILE.VALUE('ORG_ID') to enforce operating unit security.
  • HR_GENERAL and HR_SECURITY (packages) — leveraged indirectly through the HR organizational and location views for security and name resolution.

The joins are standard equijoins on ORGANIZATION_ID and LOCATION_ID, with an additional filter that restricts organization IDs to those present in JAI_CMN_INVENTORY_ORGS and matches the current operating unit.

Key Columns

Common Use Cases and Queries

The view is typically queried for statutory register extracts and period reconciliation. A representative query for additional economic development amounts by organization and period is:

  • SELECT organization_code, name, transaction_date, additional_ed, other_ed, opening_balance, closing_balance FROM apps.jai_cmn_pla_register_v WHERE fin_year = :p_year AND register_id = :p_register ORDER BY transaction_date, slno;
  • Because the view enforces ORG_ID, the query returns only the rows for the operating unit set in the session context, which is essential for multi-org compliance.
  • Drill-back to the base register row is possible using ROW_ID against JAI_CMN_RG_PLA_TRXS.

Typical consumers include the Asia/Pacific localization reports, extract programs, and reconciliation queries that compare register balances against GL postings for economic development compliance.