Results for “jai_boe_documents”

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

Overview

JAI_BOE_DOCUMENTS is a table owned by the JA schema within the Oracle E-Business Suite Asia/Pacific Localizations product (JA). It is classified in the ETRM repository as a VALID table in both Oracle EBS 12.1.1 and 12.2.2. Functionally, the table stores document line information associated with a Bill of Entry (BOE) header, capturing references to procurement and shipment documents such as Purchase Orders, Releases, and Advance Shipment Notices (ASBN) that are tied to a specific BOE. The BOE is a statutory customs document used extensively in Asia/Pacific locales, and this table acts as the bridge that connects each BOE header to its supporting trade documents.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is standalone. In practice, this suggests treating JAI_BOE_DOCUMENTS as a candidate satellite or link-like detail table rather than a pure hub, since it carries descriptive attributes alongside a foreign key to the BOE header. Modelers should validate this suggestion against actual cardinality and historization requirements before adopting a Data Vault design.

Key Information Stored

The table comprises twelve documented columns, of which the following are most significant for understanding and querying the object.

• BOE_DOC_ID — The surrogate primary key of the table, enforced by the constraint JAI_BOE_DOCUMENTS_PK. It also appears in the unique index JAI_BOE_DOCUMENTS_U1, making it the primary identifier returned when a user searches for "boe_doc_id."
• BOE_ID — The foreign key referencing JAI_CMN_BOE_HDRS.BOE_ID, linking each document line to its parent BOE header.
• DOC_SR_NUM — The document serial number that distinguishes individual document lines within a single BOE. Together with BOE_ID, it forms the second business-key candidate captured by the unique index JAI_BOE_DOCUMENTS_U2.
• DOC_ID — The identifier of the referenced source document, such as a PO, release, or ASBN, depending on DOC_TYPE.
• DOC_TYPE — The classification code indicating the category of the referenced document (for example, purchase order or shipment notice).
• DESCRIPTION — Free-form descriptive text associated with the document line.
• CREATION_DATE, CREATED_BY — Standard audit columns recording who created the row and when.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns tracking the most recent modification and the login session responsible for it.
• OBJECT_VERSION_NUMBER — The concurrency-control column used by the Oracle EBS framework to detect conflicting updates.

Common Use Cases and Queries

Typical usage centers on tracing which source documents support a given BOE, and conversely, identifying which BOE references a specific PO, release, or ASBN. A common pattern joins the detail table to the header:

SELECT d.boe_doc_id, d.boe_id, d.doc_sr_num, d.doc_id, d.doc_type
FROM   ja.jai_boe_documents d,
       ja.jai_cmn_boe_hdrs h
WHERE  d.boe_id = h.boe_id
AND    d.doc_id = :p_document_id;

Reporting scenarios include customs reconciliation reports that must list all supporting documents per BOE, audit extracts that verify document completeness, and integration queries that pass BOE document references to downstream customs or trade-compliance systems. The OBJECT_VERSION_NUMBER column should be selected whenever the row is subject to programmatic update through the EBS framework.

Related Objects

• JAI_CMN_BOE_HDRS — The parent header table, joined via JAI_BOE_DOCUMENTS.BOE_ID = JAI_CMN_BOE_HDRS.BOE_ID. This is the primary dependency and the anchor of most BOE reporting.
• JAI_BOE_DOCUMENTS_PK — The primary key constraint on BOE_DOC_ID governing uniqueness of the surrogate key.
• JAI_BOE_DOCUMENTS_U1 — Unique index on BOE_DOC_ID, a business-key candidate.
• JAI_BOE_DOCUMENTS_U2 — Unique index on (BOE_ID, DOC_SR_NUM), enforcing uniqueness of document lines within each BOE.
• PO_HEADERS_ALL / PO_RELEASES_ALL / PO_LINE_LOCATIONS_ALL — Source document tables referenced indirectly through DOC_ID and DOC_TYPE where the document is a purchase order or release.
• ASN-related tables in the shipping schema — Referenced indirectly through DOC_ID when the document type indicates an Advance Shipment Notice.

The metadata documents only the header foreign key and the two unique indexes; additional integration points are inferred from the DOC_TYPE semantics and should be confirmed against the localization's functional documentation before being relied upon in production queries.