Results for “excise_register_id”

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

Overview

The JAI_PA_DRAFT_INVOICES table is a core transactional data object within the JA (Asia/Pacific Localizations) product family of Oracle E-Business Suite. It resides in the JA schema and stores draft invoice header attributes that support India localization requirements. Specifically, the table captures the excise and VAT (value-added tax) header-level details that must accompany draft invoices generated from Oracle Projects before they are finalized into the statutory invoice documents mandated under Indian indirect tax law.

In Releases 12.1.1 and 12.2.2, this table acts as the localization extension to the standard Oracle Projects draft invoice model. It stores fields that are not present on the base PA_DRAFT_INVOICES_ALL table, including excise invoice registration details, cess amounts, and inter-state tax flags. Based on the heuristic Data Vault classification mined from its foreign key structure, this object leans toward a satellite pattern: it extends and enriches a parent business entity (the draft invoice) rather than representing an independent business key or acting purely as an associative link. Modelers should treat it as a localized descriptive extension to the Projects draft invoice hub.

Key Information Stored

The table is defined with 25 columns in the documented 12.2.2 physical schema. The most significant columns are grouped as follows:

• DRAFT_INVOICE_ID — The surrogate primary key, enforced by the JAI_PA_DRAFT_INVOICES_PK constraint. This is the unique identifier for each draft invoice header record.
• PROJECT_ID — The Project identifier, forming part of the business-key candidate.
• DRAFT_INVOICE_NUM — The draft invoice number; together with PROJECT_ID, this forms the unique business-key candidate indexed by JAI_PA_DRAFT_INVOICES_U2.
• ORGANIZATION_ID — The operating unit or organization responsible for the invoice, referencing HR_ALL_ORGANIZATION_UNITS.
• LOCATION_ID — The delivery or tax location associated with the invoice, referencing HZ_LOCATIONS.
• EXCISE_INVOICE_NO / EXCISE_INVOICE_DATE — The statutory excise invoice number and its date.
• VAT_INVOICE_NO / VAT_INVOICE_DATE — The VAT invoice number and date.
• EXCISE_REGISTER_TYPE / EXCISE_REGISTER_ID — The excise register classification and its identifier, referencing JAI_CMN_RG_23AC_II_TRXS.
• BASIC_EXCISE_AMT, ADDITIONAL_EXCISE_AMT, OTHER_EXCISE_AMT, EXCISE_CESS_AMT, EXCISE_SH_CESS_AMT — The itemized excise duty and cess components.
• PROCESS_EXCISE_FLAG / PROCESS_VAT_FLAG — Flags controlling whether excise and VAT processing applies.
• PARENT_DRAFT_INVOICE_ID — Self-referencing foreign key supporting invoice hierarchies or adjustments.
• OBJECT_VERSION_NUMBER — The standard Oracle EBS optimistic locking column, alongside the standard WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN).

Common Use Cases and Queries

The primary reporting use cases center on India excise and VAT compliance reporting, where localization teams must reconcile draft invoice headers against the excise registers. A typical pattern joins the header to its parent project draft invoice and to the excise register:

SELECT j.DRAFT_INVOICE_ID, j.DRAFT_INVOICE_NUM, j.PROJECT_ID,
  j.EXCISE_INVOICE_NO, j.VAT_INVOICE_NO,
  j.BASIC_EXCISE_AMT + j.ADDITIONAL_EXCISE_AMT + j.OTHER_EXCISE_AMT + j.EXCISE_CESS_AMT AS TOTAL_EXCISE
FROM JA.JAI_PA_DRAFT_INVOICES j
WHERE j.PROJECT_ID = :project_id
  AND j.PROCESS_EXCISE_FLAG = 'Y';

Other scenarios include validating that every draft invoice header has a matching excise register entry (EXCISE_REGISTER_ID), auditing VAT invoice sequences, and detecting self-referencing parent-child invoice relationships via PARENT_DRAFT_INVOICE_ID. Reporting on organization and location-level tax liabilities across operating units is also common, joining to HR_ALL_ORGANIZATION_UNITS and HZ_LOCATIONS.

Related Objects

The table participates in a well-defined foreign key network. The significant related objects are:

• JAI_PA_DRAFT_INVOICE_LINES — Child table; its DRAFT_INVOICE_ID and PARENT_DRAFT_INVOICE_ID columns reference this table, providing line-level tax detail.
• PA_DRAFT_INVOICES_ALL — The parent Oracle Projects draft invoice table, joined on PROJECT_ID.
• HR_ALL_ORGANIZATION_UNITS — Joined via ORGANIZATION_ID to attribute the invoice to an operating unit.
• HZ_LOCATIONS — Joined via LOCATION_ID for tax and delivery addresses.
• JAI_CMN_RG_23AC_II_TRXS — Joined via EXCISE_REGISTER_ID, linking to the RG-23AC Part II excise register transactions.
• JAI_PA_DRAFT_INVOICES — Self-referenced through PARENT_DRAFT_INVOICE_ID for hierarchical or corrective invoice structures.

Collectively, these relationships establish the table as the header-level localization anchor for India draft invoice processing in Oracle Projects.