Search Results jai_po_osp_hdrs




Overview
Explore in AI Chat

Overview

The JAI_PO_OSP_HDRS table is a core data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the JA - Asia/Pacific Localizations product. Its primary function is to store 57F4 header information for Purchase Orders (POs) of the Outside Processing (OSP) type. This table is essential for regulatory compliance in specific Asia/Pacific jurisdictions, capturing the formal documentation details required for OSP transactions. It acts as a central repository linking localized form data to standard EBS purchasing entities, ensuring that localized legal requirements are integrated with the core procurement workflow.

Key Information Stored

The table's structure is defined by its primary and unique keys, which indicate its critical data elements. The primary key is FORM_ID, a unique identifier for each 57F4 form record. A composite unique key (JAI_PO_OSP_HDRS_UK1) enforces business rule integrity across the columns ORGANIZATION_ID, LOCATION_ID, FORM_NUMBER, PO_HEADER_ID, and OTH_DOC_ID. Key stored information includes identifiers for the associated purchasing organization (ORGANIZATION_ID), ship-to location (LOCATION_ID), the vendor and vendor site (VENDOR_ID, VENDOR_SITE_ID), and the core EBS purchase order or release (PO_HEADER_ID, OTH_DOC_ID). The FORM_NUMBER column stores the specific identifier for the 57F4 form, while PRIMARY_FORM_ID supports hierarchical relationships between form records via a self-referencing foreign key.

Common Use Cases and Queries

This table is primarily accessed for generating compliant 57F4 reports, auditing OSP transactions for local tax or regulatory purposes, and troubleshooting data integrity issues between localized forms and standard PO documents. A common reporting query involves joining the table to core EBS tables to retrieve a complete view of an OSP order. For example, to list all 57F4 forms for a specific vendor:

  • SELECT h.FORM_NUMBER, h.PO_HEADER_ID, p.SEGMENT1 PO_NUM, p.VENDOR_NAME FROM JAI_PO_OSP_HDRS h JOIN PO_HEADERS_ALL p ON h.PO_HEADER_ID = p.PO_HEADER_ID WHERE h.VENDOR_ID = :vendor_id;

Another critical use case is validating the lineage of amended forms by querying the self-referential relationship: SELECT child.FORM_ID, parent.FORM_ID AS PRIMARY_FORM_ID FROM JAI_PO_OSP_HDRS child LEFT JOIN JAI_PO_OSP_HDRS parent ON child.PRIMARY_FORM_ID = parent.FORM_ID.

Related Objects

The JAI_PO_OSP_HDRS table has extensive integration within the EBS data model, as evidenced by its foreign key relationships. It references several foundational tables: HZ_PARTIES and HZ_PARTY_SITES for trading community data; HR_ALL_ORGANIZATION_UNITS and HR_LOCATIONS_ALL for organizational structure; and PO_HEADERS_ALL and PO_RELEASES_ALL for core purchasing documents. It also maintains a recursive relationship with itself via the PRIMARY_FORM_ID column. Crucially, this table is the parent to detail tables within the localization, specifically JAI_PO_OSP_LINES and JAI_PO_OSP_LINE_DTLS, which store line-level information for the 57F4 form, linked via the FORM_ID column. This hierarchy ensures a complete audit trail from the header form down to individual item details.