Results for “account_debit”

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

Overview

JAI_PO_OSPM_AEL_V is an APPS-owned database view within the JA (Asia/Pacific Localizations) product family, delivered as part of the Oracle E-Business Suite 12.1.1 and 12.2.2 code lines. Its documented description identifies it as the "Base view of OSP manually entered." The view consolidates manually entered Outside Processing (OSP) transactions and exposes them in the column shape expected by the Oracle Subledger Accounting (SLA/XLA) and Accounting Events architecture, specifically the Application Event Log (AEL) model. The hard-coded literal APPLICATION_ID = 7000 and TRX_CLASS = 'JAI INV OSPM' signal that this view is a reporting and accounting-extract source for the JA-localized OSP manual entry process, mapping transactional data onto the standard AEL column contract used by other subledger AEL views.

Underlying Base Objects

Per the documented 12.2.2 metadata, the view is defined over the following base and referenced objects: JAI_PO_OSP_HDRS and JAI_PO_OSP_LINES (the JA-localized OSP manual entry header and line tables), GL_JE_HEADERS, GL_JE_LINES, GL_JE_CATEGORIES, GL_JE_SOURCES, GL_DAILY_CONVERSION_TYPES, GL_IMPORT_REFERENCES (the general ledger journal tables that carry the accounting side of each OSP manual entry), ORG_ORGANIZATION_DEFINITIONS and WIP_ENTITIES (inventory organization and job information), PO_HEADERS_ALL and PO_VENDORS, AP_SUPPLIER_SITES_ALL (procurement supplier and PO context), and the HR_GENERAL and HR_SECURITY packages, which apply organizational security filtering. The join path links each OSP manual entry to its accounting lines through JE_HEADER_ID and JE_LINE_NUM in the GL tables, and back to the originating PO, supplier, and WIP job for full transactional context.

Key Columns

• EVENT_TYPE, APPLICATION_ID, TRX_CLASS, TRX_CLASS_NAME — Literal values ('MANUAL OSP TRANSACTIONS', 7000, 'JAI INV OSPM', 'OSP MANUAL ENTRY') that identify the transaction source for SLA processing and reporting.
• FORM_NUMBER, FORM_DATE, FORM_ID (TRX_HDR_ID) — The user-searched column. FORM_NUMBER carries the manually entered OSP form reference, FORM_DATE is the creation date, and TRX_HDR_ID maps to JAI_PO_OSP_HDRS.FORM_ID. These are the principal business-document identifiers for the manual OSP entry.
• JE_HEADER_ID, JE_LINE_NUM, JE_CATEGORY, JE_SOURCE, ENTERED_DEBIT/CREDIT, ACCOUNT_DEBIT/CREDIT, ACCOUNT_ID, ACCOUNTING_DATE — The GL accounting representation, including entered and accounted amounts, code combination, and journal category/source with user-facing names.
• ENTERED_CURRENCY, CURRENCY_CONVERSION_RATE, CURRENCY_CONVERSION_TYPE, CURRENCY_CONVERSION_DATE — Currency and rate information for the entered transaction amounts.
• DISPATCH_REGISTER, DISPATCH_ENTRY_NUMBER, RECEIPT_REGISTER, RECEIPT_ENTRY_NUMBER, DISPATCH_QUANTITY, RETURN_QUANTITY, ORIGINAL_QUANTITY, UOM — Movement and quantity detail for the dispatched, received, and returned OSP material.
• SUPPLIER_ID, SUPPLIER_NUMBER, SUPPLIER_NAME, SUPPLIER_SITE_ID, SUPPLIER_SITE, PO_HEADER_ID, PO_NUMBER — Supplier and purchase order context.
• JOB_ID, JOB_NAME, ITEM_ID, INV_ORG_ID, INV_ORG_CODE — WIP job, item, and inventory organization identifiers.
• PRIMARY_FORM_ID, PRIMARY_FORM_NUMBER — Reference to a prior or primary OSP form, used for form lineage or resubmission tracking.

Common Use Cases and Queries

The view is typically queried to reconcile manually entered OSP transactions to their GL journals, to extract accounting data feeding SLA, or to report OSP form activity by supplier, PO, or WIP job. A representative query retrieving form-level detail with accounting amounts is:

SELECT FORM_NUMBER, FORM_DATE, SUPPLIER_NAME, PO_NUMBER, JOB_NAME,
  DISPATCH_QUANTITY, RETURN_QUANTITY, ENTERED_CURRENCY,
  ENTERED_DEBIT, ENTERED_CREDIT, JE_CATEGORY, ACCOUNTING_DATE
FROM APPS.JAI_PO_OSPM_AEL_V
WHERE FORM_NUMBER = :form_number
ORDER BY FORM_DATE, JE_LINE_NUM;

Because the view carries HR_SECURITY-based organization filtering, results are automatically restricted to the inventory organizations accessible to the querying responsibility. Analysts commonly join it back to JAI_PO_OSP_HDRS or JAI_PO_OSP_LINES on FORM_ID/TRX_HDR_ID and LINE_ID for additional localized OSP attributes, and to GL_JE_LINES for further journal drill-down.