Results for “addl_duty_amount”

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

Overview

JAI_CMN_RG_PLA_DTLS is a table owned by the JA schema (Oracle Applications) and delivered as part of the JA — Asia/Pacific Localizations product family. Its documented purpose is to store PLA (Post Landing Adjustment) detail information generated when a PLA invoice is created in the Payables (AP) module. PLA functionality is used in Asia/Pacific localizations to reconcile import-related landed costs, customs duties, and cess/excise components against the original purchase or import invoice, and this table holds the line-level breakdown of those duty components. In Oracle EBS 12.1.1 and 12.2.2 the table is delivered with status VALID and is a standard, supported localization object.

Heuristic Data Vault classification (mined from the foreign key structure) places this object as satellite-leaning: it carries descriptive, transactional attributes describing the duty details of a PLA record, keyed back to its parent header via PLA_ID. This classification is offered as a modeling suggestion only; in EBS terms the table is simply the child/detail entity of the PLA header.

Key Information Stored

• PLA_ID — the surrogate/foreign key linking each detail line to its parent PLA header record in JAI_CMN_RG_PLA_HDRS. Together with LINE_NUMBER it constitutes the composite primary key.
• LINE_NUMBER — sequential line identifier within a given PLA header.
• ITEM_TARIFF and ITEM_SUB_HEADING — customs tariff classification and sub-heading applied to the line item, used to derive the applicable duty rates.
• BASIC_DUTY_AMOUNT — the base customs duty computed for the line.
• ADDL_DUTY_AMOUNT — additional duty (countervailing/auxiliary) component.
• OTHER_DUTY_AMOUNT — any residual or miscellaneous duty element.
• TOTAL_DUTY_AMOUNT — the aggregated duty amount for the detail line.
• EDU_CESS_EXCISE_AMOUNT and SH_CESS_EXCISE_AMOUNT — education cess and secondary/higher education cess (excise) components, reflecting India-specific localization duty structures.
• Standard audit/WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER (used for optimistic locking / OAF row versioning).

The unique index JAI_CMN_RG_PLA_DTLS_PK on (PLA_ID, LINE_NUMBER) is the documented business-key candidate. There is no independent surrogate column beyond this composite key. The table carries 16 columns in the 12.2.2 physical schema.

Common Use Cases and Queries

Typical reporting needs center on reconciling duty components by PLA header, tariff heading, or period. A common join pattern retrieves header and detail in one query:

SELECT d.pla_id, d.line_number, d.item_tariff,
       d.basic_duty_amount, d.addl_duty_amount,
       d.total_duty_amount, d.edu_cess_excise_amount,
       d.sh_cess_excise_amount
FROM   jai_cmn_rg_pla_dtls d,
       jai_cmn_rg_pla_hdrs h
WHERE  d.pla_id = h.pla_id
AND    h.org_id = :org_id;

Custom localized duty reports and audit extracts frequently aggregate TOTAL_DUTY_AMOUNT by ITEM_TARIFF to validate customs declarations. Reconciliation routines compare detail duty lines against the AP invoice distributions created when the PLA invoice was posted.

Related Objects

• JAI_CMN_RG_PLA_HDRS — the parent header table; joined on JAI_CMN_RG_PLA_DTLS.PLA_ID = JAI_CMN_RG_PLA_HDRS.PLA_ID. This is the documented foreign key dependency.
• AP_INVOICES_ALL / AP_INVOICE_DISTRIBUTIONS_ALL — the Payables objects that trigger PLA invoice creation and receive the resulting accounting.
• JA_PLA_* / Regime localization APIs and concurrent programs — PL/SQL packages in the JA schema process header/detail rows during PLA invoice generation.
• PO_HEADERS_ALL / PO_LINES_ALL — source purchase/import documents whose landed cost drives the duty computation.
• MTL_SYSTEM_ITEMS_B — item master referenced for tariff and sub-heading derivation.

Because the table is a localization satellite, changes should be effected through the delivered JA concurrent programs and APIs rather than direct DML.