Results for “final_receipt”

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

Overview

JAI_OPM_OSP_HDRS is the header table within the Oracle E-Business Suite Asia/Pacific Localizations (JA) product that stores header-level OSP (Octroi / Sales Tax / excise-related statutory document) information. It resides in the JA schema and is validated in both EBS 12.1.1 and 12.2.2. The table functions as the parent record for statutory OSP documentation used in Indian localizations, where each header row consolidates the fiscal, organizational, and duty-related attributes of a single OSP transaction.

Under the heuristic Data Vault classification mined from its FK structure, JAI_OPM_OSP_HDRS is effectively hub-leaning: it holds a stable surrogate key (OSP_HEADER_ID) that anchors descriptive attributes and is referenced by child detail rows, while itself pointing to a source purchasing document. In Data Vault modeling terms it behaves as a hub with satellite-style descriptive columns, and would typically be modeled as a hub joined to its dependent link and satellites in an analytics warehouse.

Key Information Stored

The table defines 28 documented columns. The surrogate primary key is OSP_HEADER_ID, enforced by the unique index JAI_OPM_OSP_HDRS_PK; this column is the single documented business-key candidate and the join key to all child records. Among the most operationally significant columns are:

• OSP_HEADER_ID — surrogate primary key and unique identifier for each OSP header record.
• PO_ID — foreign key to PO_ORDR_HDR, linking the OSP record to its originating purchase order.
• TRANSACTION_DATE — the date the OSP transaction was recorded.
• USER_REFERENCE — free-form user-supplied reference for the transaction.
• TOT_MODVAT_CLAIMED — total modified VAT amount claimed.
• TOT_EXCISE_PAID — total excise duty paid on the transaction.
• RECEIVABLE_EXCISE and PAYABLE_EXCISE — excise amounts recoverable and owed respectively.
• FINAL_RECEIPT — indicator of final receipt status for the OSP document.
• ORIGINAL_DUE_DATE and EXTENDED_DUE_DATE — statutory due dates and any extension applied.
• BATCH_STATUS and BATCH_CLOSE_DATE — processing status and closure date of the OSP batch.
• ORGN_CODE, WHSE_CODE, and ORGANIZATION_ID — organizational context of the transaction.
• FORM_NUMBER, FORM_NAME, and FIN_YEAR — statutory form identifier and fiscal year.
• Standard WHO audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER for optimistic locking.

Common Use Cases and Queries

Typical scenarios include statutory excise reconciliation, OSP batch monitoring, and reporting on duty claimed and paid against purchase orders. A representative query joining the header to its details follows:

• SELECT h.osp_header_id, h.po_id, h.transaction_date, d.* FROM ja.jai_opm_osp_hdrs h, ja.jai_opm_osp_dtls d WHERE h.osp_header_id = d.osp_header_id AND h.organization_id = :org_id;
• Reconciliation by fiscal year and form: filter on FIN_YEAR, FORM_NUMBER, and BATCH_STATUS to list open or closed statutory submissions.
• Excise exposure reporting: aggregate TOT_EXCISE_PAID, RECEIVABLE_EXCISE, and PAYABLE_EXCISE grouped by ORGN_CODE or WHSE_CODE.
• Purchase-order traceability: join PO_ID to PO_ORDR_HDR to trace OSP documents back to their sourcing PO.
• Overdue monitoring: compare ORIGINAL_DUE_DATE and EXTENDED_DUE_DATE against the current date where BATCH_STATUS indicates an open batch.

Related Objects

The following objects are the most significant dependents and references, based on documented FK relationships:

• JAI_OPM_OSP_DTLS — child detail table joined on JAI_OPM_OSP_DTLS.OSP_HEADER_ID = JAI_OPM_OSP_HDRS.OSP_HEADER_ID; the primary line-level dependency.
• PO_ORDR_HDR — referenced via JAI_OPM_OSP_HDRS.PO_ID, providing the originating purchasing document.
• Oracle Purchasing (PO) and OPM (Process Manufacturing) inquiry and reporting views that surface OSP data inherit from these two core tables.
• Localization batch/statutory reporting programs that read BATCH_STATUS, FIN_YEAR, and FORM_NUMBER from the header for regulatory returns.

Because OSP_HEADER_ID is referenced exclusively by JAI_OPM_OSP_DTLS and the table references PO_ORDR_HDR, integrity is preserved at the header-to-detail boundary, making the header the authoritative record for all OSP statutory transactions in the JA schema.