Results for “jai_boe_details”

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

Overview

JAI_BOE_DETAILS is a table owned by the JA schema within the Oracle E-Business Suite Asia/Pacific Localizations module (JA). It stores line-level information related to a Bill of Entry (BOE) document. In Indian and other Asia/Pacific customs localization flows, a Bill of Entry is the statutory document filed with customs authorities for imported goods, and this table captures the detail associated with each specific BOE document line, including quantity, goods identity, customs duty, and package information. It operates as the operational detail layer beneath a BOE document header, allowing the localization to track per-line customs valuation, duty computation, and matching against receipts or shipments.

From a modeling perspective, the metadata's heuristic Data Vault classification is satellite-leaning. This suggests the table is best understood as a descriptive detail structure that hangs off a parent business entity (the BOE header), carrying attributes that describe the state of each line rather than acting as an independent hub or a pure association link. The primary key JAI_BOE_DETAILS_PK is defined on BOE_DETAIL_ID.

Key Information Stored

The table contains 44 documented columns. The most significant are summarized below, distinguishing the surrogate key from business keys and descriptive attributes.

• BOE_DETAIL_ID — the surrogate primary key (JAI_BOE_DETAILS_PK), uniquely identifying each detail line.
• BOE_ID — foreign key to JAI_CMN_BOE_HDRS, linking the detail to its parent BOE header.
• BOE_DOC_ID, DETAIL_LINE_NUM — together with BOE_ID, these form the unique index JAI_BOE_DETAILS_U2, a business-key candidate identifying the document line.
• BOE_DOC_LINE_ID, BOE_DOC_LINE_NUM, SHIPMENT_LINE_NUM — references tying the detail to source document and shipment lines.
• QUANTITY, APPLIED_QTY, UOM_CODE — the transacted quantity, the quantity already applied or matched, and its unit of measure.
• INVENTORY_ITEM_ID, DESCRIPTION — the item identity and textual description of the goods.
• UNIT_PRICE, LINE_AMOUNT, ASSESSABLE_VALUE — valuation amounts used to compute customs duty.
• CUSTOMS_TARIFF_CODE, CUSTOMS_TARIFF_HEADING, DUTY_CODE, TAX_CATEGORY_ID, TAX_AMOUNT — customs tariff classification and computed duty/tax amounts.
• PKG_MARKS_NUM, PKG_SERIAL_NUMBER — package and serialization references for the goods.
• ATTRIBUTE1–15, ATTRIBUTE_CATEGORY — the standard EBS descriptive-flexfield columns.
• OBJECT_VERSION_NUMBER, CREATION_DATE, LAST_UPDATE_DATE and audit columns — standard concurrency and auditing fields.

Common Use Cases and Queries

Typical usage centers on customs duty reconciliation and BOE line reporting. A common pattern joins detail lines to the header to report full BOE content:

• Report duty and assessable value per BOE line for a given BOE header by joining on BOE_ID.
• Reconcile applied quantities (APPLIED_QTY versus QUANTITY) to gauge how much of a BOE line has been matched to receipts.
• Extract tariff classification and tax amounts for statutory reporting against CUSTOMS_TARIFF_CODE and TAX_CATEGORY_ID.
• Trace a detail line to its downstream tax and matching records through the child keys BOE_DETAIL_ID.

A representative query selects line identifiers, item, quantity, and duty values filtered by BOE_ID, aggregating TAX_AMOUNT for duty summaries.

Related Objects

The most significant dependent and referenced objects are:

• JAI_CMN_BOE_HDRS — the parent BOE header, referenced via BOE_ID.
• JAI_BOE_DETAIL_TAXES — child table holding tax lines per detail, referenced by BOE_DETAIL_ID.
• JAI_CMN_BOE_MATCHINGS — matching records that reference this table through BOE_DETAIL_ID.
• Inventory and item master tables referenced indirectly through INVENTORY_ITEM_ID for item validation and description lookup.

Together these objects form the BOE localization data model, with JAI_BOE_DETAILS acting as the central detail satellite linking headers, taxes, and matching records.