Results for “primary_form_id”

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

Overview

JAI_PO_OSP_HDRS is a table in the JA (Asia/Pacific Localizations) product schema within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores 57F4 header information for Purchase Orders of the OSP (Outside Processing) type. The "57F4" designation refers to the statutory reporting form used in jurisdictions such as Thailand, where OSP purchase orders require specific header-level records for tax and regulatory reporting. The table sits at the intersection of Oracle Purchasing and the regional localization layer, allowing the standard procurement flow to be enriched with localization-specific attributes that are not present in PO_HEADERS_ALL.

From a dimensional modeling perspective, the heuristic Data Vault classification suggested by the foreign-key topology is satellite-leaning. The table is anchored to the Purchasing hub (PO_HEADERS_ALL via PO_HEADER_ID) and to organizational and party hubs (HR_ALL_ORGANIZATION_UNITS, HZ_PARTIES), while carrying descriptive and transactional attributes that describe the localization context of an existing order. It can therefore be modeled as a satellite attached to the purchase-order hub, with an ancillary link to the vendor and location dimensions.

Key Information Stored

The surrogate primary key is FORM_ID, enforced by the JAI_PO_OSP_HDRS_PK unique index. A secondary unique key, JAI_PO_OSP_HDRS_UK1, is defined over ORGANIZATION_ID, LOCATION_ID, FORM_NUMBER, PO_HEADER_ID, and OTH_DOC_ID, making these the business-key candidates and the natural lookup path for the localization form record.

The most significant columns are:

• FORM_ID – Surrogate primary key and internal identifier for the 57F4 header record.
• PO_HEADER_ID – Foreign key to PO_HEADERS_ALL, tying the localization record to its purchase order.
• OTH_DOC_ID – Foreign key to PO_RELEASES_ALL, used when the record maps to a release rather than a header.
• FORM_NUMBER – The reported form number, part of the business unique key.
• ORGANIZATION_ID – Foreign key to HR_ALL_ORGANIZATION_UNITS identifying the operating unit or legal entity.
• LOCATION_ID – Foreign key to HR_LOCATIONS_ALL providing the ship-to or registration location.
• VENDOR_ID and VENDOR_SITE_ID – Foreign keys to HZ_PARTIES and HZ_PARTY_SITES identifying the supplier and supplier site.
• ISSUE_APPROVED / ISSUE_DATE – Controls and timestamps for form issuance.
• RECEIPT_APPROVED / RECEIPT_DATE – Controls and timestamps for receipt of the returned form.
• DR_REGISTER / CR_REGISTER – Debit and credit register markers, with associated register IDs, serial numbers, and entry dates (DR_REG_*, CR_REG_*).
• PRIMARY_FLAG / PRIMARY_FORM_ID – Self-referencing structure marking a record as primary and linking replacements to their originating form.
• FIN_YEAR, PRINT_ORIGINAL, PRINT_DUPLICATE, PRINT_CNT – Fiscal year and print-tracking attributes for statutory output.
• CANCEL_FLAG, SOURCE, OSP_SI – Status and source indicators controlling downstream processing.

Common Use Cases and Queries

Typical usage centers on reporting and reconciliation of 57F4 records against purchasing transactions. A standard join confirms which OSP purchase orders have completed localization header records:

• Joining JAI_PO_OSP_HDRS to PO_HEADERS_ALL on PO_HEADER_ID to retrieve segment1 (PO number) and vendor for a reporting extract.
• Filtering by FIN_YEAR and ORGANIZATION_ID to produce the periodic statutory submission.
• Querying CANCEL_FLAG and PRIMARY_FLAG to isolate active versus superseded forms, and using PRIMARY_FORM_ID to trace a replacement chain.
• Comparing ISSUE_DATE against RECEIPT_DATE to measure unreturned or overdue forms.
• Driving the register side by selecting DR_REGISTER, CR_REGISTER, and the associated register IDs and serial numbers for accounting reconciliation.
• Line-level drill-down by joining to JAI_PO_OSP_LINES and JAI_PO_OSP_LINE_DTLS on FORM_ID.

Related Objects

The following objects are the most significant dependencies based on the documented foreign-key relationships:

• PO_HEADERS_ALL – joined on PO_HEADER_ID; the parent purchase order header.
• PO_RELEASES_ALL – joined on OTH_DOC_ID; the parent release where applicable.
• HZ_PARTIES – joined on VENDOR_ID; the supplier party.
• HZ_PARTY_SITES – joined on VENDOR_SITE_ID; the supplier site.
• HR_ALL_ORGANIZATION_UNITS – joined on ORGANIZATION_ID; the operating unit or legal entity.
• HR_LOCATIONS_ALL – joined on LOCATION_ID; the location context.
• JAI_PO_OSP_HDRS (self) – joined on PRIMARY_FORM_ID; links replacement forms to their primary.
• JAI_PO_OSP_LINES – joined on FORM_ID; child localization line records.
• JAI_PO_OSP_LINE_DTLS – joined on FORM_ID; child localization line detail records.