Results for “osp_header_id”

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

Overview

JA.JAI_PO_OSP_CENVAT_HDRS is a transaction header table within the Oracle E-Business Suite Asia/Pacific Localizations (JA) product family. It stores header-level CENVAT (Central Value Added Tax) information for outside processing (OSP) transactions originating from Oracle Purchasing and Oracle Manufacturing. In the Indian localization context, outside processing refers to the practice of sending components to a supplier for further processing and receiving them back as finished or semi-finished goods. This table captures the fiscal and statutory header details that govern how CENVAT, excise, and VAT amounts are claimed, paid, and reconciled for such transactions.

The object is registered in the JA schema with VALID status in both Oracle EBS 12.1.1 and 12.2.2. It contains 27 documented columns and is keyed by the JAI_PO_OSP_CENVAT_HDRS_PK primary key on OSP_HEADER_ID. Based on the mined foreign-key topology, the table leans toward a satellite classification in a Data Vault modelling sense: it carries descriptive, transaction-specific attributes tied to a primary vendor, a transaction type, an inventory organization, and a concurrent request context, rather than acting as a pure business hub or a pure link between two independent hubs. It does, however, exhibit a self-referencing hierarchy through PARENT_HEADER_ID, which allows CENVAT header records to be chained or grouped.

Key Information Stored

The primary surrogate key is OSP_HEADER_ID, uniquely generated per CENVAT header row. A secondary unique index, JAI_PO_OSP_CENVAT_HDRS_U1, is defined on the composite (OSP_HEADER_ID, TRANSACTION_TYPE_ID, USER_REFERENCE), effectively forming the business-key candidate for OSP CENVAT identification.

The most operationally significant columns include:

• OSP_HEADER_ID – surrogate primary key and parent reference for detail lines.
• OSP_VENDOR_ID – the outside processing supplier, referenced from HZ_PARTIES.
• TRANSACTION_TYPE_ID – the inventory transaction type driving the CENVAT movement, from MTL_TRANSACTION_TYPES.
• TRANSACTION_DATE – the effective date for the CENVAT header.
• USER_REFERENCE – user-supplied document or registration reference.
• TOT_MODVAT_CLAIMED – total MODVAT/VAT amount claimed against the header.
• TOT_EXCISE_PAID – aggregate excise duty paid on the transaction.
• PAYABLE_EXCISE and RECEIVABLE_EXCISE – excise amounts that must be paid to or recovered from the tax authority.
• FINAL_RECEIPT – flag indicating whether the receipt is the final one for the OSP cycle.
• ORIGINAL_DUE_DATE and EXTENDED_DUE_DATE – statutory due dates, including any extensions.
• REGISTER_SELECTED – indicates whether the record has been pulled into the CENVAT register.
• PARENT_HEADER_ID – self-referencing link for grouped or hierarchical headers.
• ORGANIZATION_ID and LOCATION_ID – the inventory organization and tax location.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_LOGIN_ID, PROGRAM_UPDATE_DATE – standard concurrent program and login audit columns.
• OBJECT_VERSION_NUMBER – optimistic locking control for 12.2.x.

Common Use Cases and Queries

The table is primarily consumed by the Indian CENVAT register and excise reporting processes. Typical scenarios include identifying all OSP headers awaiting final receipt, reconciling claimed MODVAT against paid excise, and tracing headers back to their parent grouping.

• Retrieve open OSP CENVAT headers for a given vendor or organization:

  SELECT osp_header_id, osp_vendor_id, transaction_date, tot_excise_paid
  FROM   ja.jai_po_osp_cenvat_hdrs
  WHERE  osp_vendor_id = :p_vendor_id
  AND    final_receipt = 'N';

• Drill into the hierarchy from parent to child headers:

  SELECT h.osp_header_id, h.parent_header_id, h.user_reference
  FROM   ja.jai_po_osp_cenvat_hdrs h
  START WITH h.parent_header_id IS NULL
  CONNECT BY PRIOR h.osp_header_id = h.parent_header_id;

• Reporting the cumulative excise claim by transaction type:

  SELECT tt.transaction_type_name,
         SUM(h.tot_modvat_claimed) modvat,
         SUM(h.tot_excise_paid) excise
  FROM   ja.jai_po_osp_cenvat_hdrs h,
         mtl_transaction_types tt
  WHERE  h.transaction_type_id = tt.transaction_type_id
  GROUP BY tt.transaction_type_name;

• Auditing concurrent processing of CENVAT register loads via REQUEST_ID and PROGRAM_ID joined to FND_CONCURRENT_REQUESTS.

Related Objects

• JA.JAI_PO_OSP_CENVAT_DTLS – detail lines linked via OSP_HEADER_ID (logical child).
• HZ_PARTIES – supplier master, joined on OSP_VENDOR_ID.
• MTL_TRANSACTION_TYPES – transaction classification, joined on TRANSACTION_TYPE_ID.
• HR_ALL_ORGANIZATION_UNITS – inventory organization, joined on ORGANIZATION_ID.
• HR_LOCATIONS_ALL – tax location, joined on LOCATION_ID.
• FND_CONCURRENT_REQUESTS – concurrent request context, joined on REQUEST_ID.
• FND_CONCURRENT_PROGRAMS – program definition, joined on PROGRAM_APPLICATION_ID and PROGRAM_ID.
• FND_LOGINS – login audit, joined on PROGRAM_LOGIN_ID.
• JAI_PO_OSP_CENVAT_HDRS – self-referencing via PARENT_HEADER_ID for header hierarchies.