Results for “duty_code”

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

Overview

JAI_CMN_BOE_DTLS is a transactional detail table within the JA (Asia/Pacific Localizations) product family of Oracle E-Business Suite, holding the line-level breakdown of Bills of Entry (BOE) invoices used for customs and import duty processing. In EBS 12.1.1 and 12.2.2 the table resides in the JA schema and is documented as VALID with 45 columns. Its parent is JAI_CMN_BOE_HDRS, which stores the BOE invoice header, so JAI_CMN_BOE_DTLS functions as a child entity that captures the itemized customs lines belonging to each BOE invoice.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is satellite-leaning. This is appropriate because the table is dependent on JAI_CMN_BOE_HDRS through BOE_ID and carries descriptive and quantitative attributes rather than defining independent business relationships. The primary key, JAI_CMN_BOE_DTLS_PK, is a composite of BOE_ID and LINE_NUMBER.

Key Information Stored

The table stores both line identification and detailed duty computation attributes. The most significant columns include:

• BOE_ID — Foreign key to JAI_CMN_BOE_HDRS; part of the surrogate primary key.
• LINE_NUMBER — Line sequence within the BOE; the second component of JAI_CMN_BOE_DTLS_PK.
• PKG_NUMBER, PKG_DESCRIPTION, SERIAL_NUMBER — Package and serial identifiers for the imported goods.
• ITEM_NUMBER, QUANTITY, UOM_CODE — Item identity and quantity information for the line.
• BASIC_DUTY_RATE, BASIC_DUTY_AMOUNT, TOTAL_VALUE — Core customs valuation and basic duty results.
• ADDL_DUTY_RATE, ADDL_DUTY_AMOUNT, CUMM_DUTY_AMOUNT, TOTAL_DUTY_AMOUNT — Cumulative and additional duty figures.
• CUSTOMS_TARIFF, DUTY_CODE, ACCESSIBLE_VALUE, EXEMPTION_NUM — Tariff classification, duty codes, and exemption references.
• EDU_CESS_CVD_RATE/AMOUNT/BASIS and EDU_CESS_CUSTOMS_RATE/AMOUNT/BASIS — Education cess computation basis, rate, and amount.
• SH_CUSTOMS_CESS_*, SH_CVD_CESS_*, SH_EDU_CESS_* — Secondary and higher education cess fields for each duty category.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — Standard EBS audit and optimistic-locking columns.

The primary key JAI_CMN_BOE_DTLS_PK (BOE_ID, LINE_NUMBER) is the only unique index documented and is the business-key candidate; it distinguishes the surrogate line identity from the descriptive attributes listed above.

Common Use Cases and Queries

Typical usage centers on customs duty reconciliation, tariff reporting, and BOE line inquiry. A frequent pattern joins the detail table to its parent header to retrieve complete BOE invoice context:

• SELECT h.boe_number, d.line_number, d.item_number, d.quantity, d.total_duty_amount FROM jai_cmn_boe_hdrs h, jai_cmn_boe_dtls d WHERE h.boe_id = d.boe_id ORDER BY h.boe_number, d.line_number;
• Aggregating duty components per BOE for statutory reporting, summing BASIC_DUTY_AMOUNT, ADDL_DUTY_AMOUNT, and the education cess columns grouped by BOE_ID.
• Auditing lines changed since a given date using LAST_UPDATE_DATE and LAST_UPDATED_BY.
• Reconciling ACCESSIBLE_VALUE against TOTAL_VALUE to validate assessable customs value.

These queries support duty drawback analysis, import cost tracking, and reconciliation against customs documents.

Related Objects

The principal related object is the parent header table. The documented foreign key establishes the following join:

• JAI_CMN_BOE_HDRS — referenced via JAI_CMN_BOE_DTLS.BOE_ID = JAI_CMN_BOE_HDRS.BOE_ID. This is the mandatory parent relationship and the primary join path for any reporting query.

Additional dependent objects — such as duty calculation APIs, BOE inquiry forms, and localization reports that consume JAI_CMN_BOE_DTLS line data — operate through the BOE_ID and LINE_NUMBER combination. Because the documented metadata identifies only one foreign key, JAI_CMN_BOE_HDRS should be treated as the definitive related object, with all other dependencies inferred through the BOE_ID key rather than through explicitly documented constraints.