Search Results detail_line_id




Overview
Explore in AI Chat

Overview

JAI_PO_OSP_LINE_DTLS is a localization table owned by the JA (Asia/Pacific Localizations) schema in Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It stores the line-level detail associated with the 57F4 statutory report format, a purchasing-related reporting structure used within the Oracle Payables/Purchasing localization for certain Asia/Pacific countries. The table captures dispatch quantities and official register (DR Register) information tied to purchase order shipment lines, enabling localized statutory reporting that is not satisfied by the standard purchasing schema alone.

From a Data Vault modeling perspective, the documented foreign key structure suggests this object is best classified heuristically as a link table. It records relationships and transactional associations between a form/format record (FORM_ID) and a purchase order line (LINE_ID), with additional descriptive attributes carried on the link. This classification is a mining-derived suggestion and should be validated against the physical model during any integration or warehouse design effort.

Key Information Stored

The table contains 14 documented columns in the 12.2.2 schema. The most significant are summarized below:

  • DETAIL_LINE_ID — Surrogate primary key, enforced by JAI_PO_OSP_LINE_DTLS_PK. This is a system-generated identifier and carries no business meaning.
  • LINE_ID — Foreign key referencing the associated purchase order line; the principal business-key candidate linking the detail record to its source transaction.
  • FORM_ID — Foreign key identifying the parent form/format record to which the line detail belongs.
  • DISPATCH_QTY — The dispatched quantity recorded for the line, central to the 57F4 reporting requirement.
  • DR_REGISTER — Indicator or value describing the DR (dispatch register) entry classification for the line.
  • DR_REG_REGISTER_ID — Identifier of the corresponding register record against which the detail is recorded.
  • DR_REG_SLNO — Serial number of the register entry, providing ordering or sequencing within the register.
  • DR_REG_ENTRY_DATE — Date on which the register entry was made, used in period-based statutory reporting.
  • CREATION_DATE, CREATED_BY — Standard audit columns recording when and by whom the row was created.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit trail columns for the most recent modification.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Application Framework (OAF) and concurrent update protection.

Common Use Cases and Queries

Typical usage centers on statutory reporting for dispatch/register information. A representative query joining the detail to its parent purchase order line is:

  • Retrieving all dispatch details for a given form: SELECT LINE_ID, DISPATCH_QTY, DR_REG_SLNO FROM JA.JAI_PO_OSP_LINE_DTLS WHERE FORM_ID = :form_id;
  • Reporting register entry volumes over a date range using DR_REG_ENTRY_DATE.
  • Reconciling DISPATCH_QTY totals against standard purchasing shipment quantities.
  • Auditing row-level change history via CREATION_DATE and LAST_UPDATE_DATE.

Related Objects

The following objects are most significant to this table, based on the documented FK and PK relationships:

  • JAI_PO_OSP_LINE_DTLS (self-referencing) — via FORM_ID and LINE_ID.
  • Form/header parent object — referenced through FORM_ID.
  • Purchase order line object — referenced through LINE_ID.
  • JAI_PO_OSP_LINE_DTLS_PK — the primary key constraint governing DETAIL_LINE_ID.

Because the ETRM metadata lists the foreign tables as placeholders, the precise parent object names should be confirmed against the JA schema data dictionary before relying on them in production joins.