Results for “party_site”

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

Overview

JAI_INV_RG23_AEL_V is an APPS-owned, valid database view shipped with the Oracle E-Business Suite Asia/Pacific Localizations (JA) product. It is documented as the "Base view of RG23 Register" and serves as the primary reconciliation bridge between Indian excise RG23 register entries and the Oracle General Ledger accounting engine. Specifically, the view exposes RG23 Part I and Part II transaction register data already linked to GL journal headers and lines, enabling subledger-to-GL (AEL, or Accounting Events Line) style reporting without requiring custom joins across the inventory and GL schemas.

The view is primarily consumed by statutory excise reporting programs, reconciliation reports, and diagnostic queries that need to validate that RG23 register entries have been accounted correctly. Because it combines inventory transaction attributes (organization, item, quantity, UOM, excise invoice details) with full GL accounting attributes (ledger, journal category, source, debit/credit amounts, currency conversion information), it acts as a single source of truth for excise-to-GL tie-out in EBS 12.1.1 and 12.2.2 environments where JA localizations are installed.

Underlying Base Objects

The view's schema is defined over a documented set of base synonyms, views, and packages. The two RG23 register tables, JAI_CMN_RG_23AC_I_TRXS and JAI_CMN_RG_23AC_II_TRXS, supply the excise register entry lines. These are joined to GL_JE_HEADERS, GL_JE_LINES, GL_JE_CATEGORIES, GL_JE_SOURCES, GL_DAILY_CONVERSION_TYPES, and GL_IMPORT_REFERENCES to obtain the accounting distribution and conversion metadata.

Organization context is derived from ORG_ORGANIZATION_DEFINITIONS and HR_LOCATIONS; party context is resolved through HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES_ALL, AP_SUPPLIER_SITES_ALL, and PO_VENDORS. Access control and descriptive lookups are supplied by the HR_SECURITY and HR_GENERAL packages. The presence of both PO and HZ synonyms confirms that the view resolves supplier and customer identities for determining the counterparty on RG23 movements.

Key Columns

• EVENT_TYPE / TRX_CLASS / TRX_CLASS_NAME — Literal constants ('RG23 ENTRY', 'JAI INV RG23', 'RG23 REGISTER ENTRY') identifying the row source.
• REGISTER_TYPE — The specific RG23 register (Part I or Part II) that the row belongs to; this is the attribute most commonly searched for filtering reports.
• SET_OF_BOOK_ID / LEDGER_ID — Ledger identifier from the GL journal header, used for ledger-level reconciliation.
• INV_ORG_ID / INV_ORG_CODE / LOCATION_ID — Inventory organization and location context of the excise transaction.
• JE_HEADER_ID / JE_LINE_NUM — Link to the underlying GL journal header and line, allowing drill-down to the accounting entry.
• ENTERED_DEBIT/CREDIT and ACCOUNT_DEBIT/CREDIT — Entered and accounted amounts for the journal line.
• ACCOUNT_ID / CODE_COMBINATION_ID — The accounting flexfield combination receiving the entry.
• ACCOUNTING_DATE / EFFECTIVE_DATE — GL accounting date of the journal line.
• ITEM_ID / SERIAL_NUMBER / UOM / QUANTITY — Item and quantity detail; QUANTITY is decoded from TRANSACTION_TYPE so receipts report received quantity and issues report issued quantity.
• PARTY_TYPE / PARTY_ID — Counterparty classification (VENDOR, CUSTOMER, ORGANIZATION) resolved from the RG23 register transaction type.
• INVOICE_NUMBER / INVOICE_DATE — Excise invoice reference captured on the register entry.

Common Use Cases and Queries

Typical usage includes excise reconciliation reports, RG23 register-to-GL tie-out, and audit queries validating that every RG23 entry produced a corresponding journal line. A representative query filtering by register type is:

• SELECT register_type, je_header_id, je_line_num, entered_debit, entered_credit, account_debit, account_credit, accounting_date FROM apps.jai_inv_rg23_ael_v WHERE register_type = :p_register_type AND accounting_date BETWEEN :p_from AND :p_to;
• Reconciling RG23 movement by organization and party: SELECT inv_org_code, party_type, party_id, SUM(entered_debit), SUM(entered_credit) FROM apps.jai_inv_rg23_ael_v GROUP BY inv_org_code, party_type, party_id;
• Drill-down from a GL journal line back to its RG23 source: SELECT * FROM apps.jai_inv_rg23_ael_v WHERE je_header_id = :p_je_header_id AND je_line_num = :p_je_line_num;

Because the view joins multiple heavy GL and register tables, queries should always be constrained by ledger, accounting date, or register type to avoid full scans on production instances.