Search Results jai_po_osp_lines




Overview
Explore in AI Chat

Overview

The JAI_PO_OSP_LINES table is a core transactional data object within the Oracle E-Business Suite Asia/Pacific Localizations module (product JA). Its primary function is to store detailed line-level information required for generating the 57F4 Form, a statutory document mandated for specific business transactions in certain Asia/Pacific jurisdictions, such as India. This table operates as a child entity to the JAI_PO_OSP_HDRS table, which stores the corresponding header-level data for the form. It serves as a critical integration point between the localization's compliance logic and the standard Purchasing and Work in Process modules, ensuring transactional data is accurately captured for regulatory reporting.

Key Information Stored

The table's structure is defined by its primary and foreign key relationships, which dictate the key data elements it holds. The primary key, LINE_ID, uniquely identifies each record. The most significant columns are the foreign keys that link this localization data to standard EBS transaction lines. The FORM_ID column associates each line with its parent header record in JAI_PO_OSP_HDRS. The PO_LINE_ID and PO_DISTRIBUTION_ID columns link the form line to a specific purchase order line and its distribution in PO_LINES_ALL and PO_DISTRIBUTIONS_ALL, respectively. For manufacturing-related transactions, the table links to Work in Process entities via WIP_ENTITY_ID, WIP_LINE_ID, and WIP_REPETITIVE_SCHEDULE_ID. The relationship with WIP_OPERATIONS is also supported through a composite foreign key involving WIP_ENTITY_ID, WIP_OPERATION_SEQUENCE_NUM, and WIP_REPETITIVE_SCHEDULE_ID.

Common Use Cases and Queries

The primary use case is the generation, inquiry, and audit of the 57F4 Form. This involves querying the table to retrieve all line details for a given form header or to trace the localization data associated with a specific purchase order or work order transaction. Common reporting needs include summarizing declared values or quantities for a period. A typical SQL pattern would join this table to its parent header and the referenced Purchasing or WIP tables to create a complete dataset for the form.

  • Sample Query for Form Lines: SELECT * FROM JAI_PO_OSP_LINES l, JAI_PO_OSP_HDRS h WHERE l.FORM_ID = h.FORM_ID AND h.FORM_NUMBER = '<form_num>';
  • Sample Query for PO Traceability: SELECT * FROM JAI_PO_OSP_LINES WHERE PO_LINE_ID = <line_id>;

Related Objects

JAI_PO_OSP_LINES has extensive dependencies within the EBS schema, as documented by its foreign key constraints. It is a central hub connecting localization data to standard application tables.

  • Parent Table: JAI_PO_OSP_HDRS (via JAI_PO_OSP_LINES.FORM_ID)
  • Referenced Standard Tables:
    • PO_LINES_ALL (via PO_LINE_ID)
    • PO_DISTRIBUTIONS_ALL (via PO_DISTRIBUTION_ID)
    • WIP_ENTITIES (via WIP_ENTITY_ID)
    • WIP_LINES (via WIP_LINE_ID)
    • WIP_REPETITIVE_SCHEDULES (via WIP_REPETITIVE_SCHEDULE_ID)
    • WIP_OPERATIONS (via WIP_ENTITY_ID, WIP_OPERATION_SEQUENCE_NUM, WIP_REPETITIVE_SCHEDULE_ID)
  • Child Table: JAI_PO_OSP_LINE_DTLS (references JAI_PO_OSP_LINES.LINE_ID)