Results for “return_qty”

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

Overview

JAI_PO_OSP_LINES is a table owned by the JA (Asia/Pacific Localizations) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores line-level information associated with the 57F4 form, a localization document used within the Asia/Pacific regional reporting framework. The table functions as a transactional detail repository that bridges Oracle Purchasing and Oracle Work in Process (WIP) records to support localized excise, tariff, and dispatch reporting requirements.

From a Data Vault modeling perspective, the FK structure suggests JAI_PO_OSP_LINES is best classified as a link table. It records relationships between purchasing documents (PO_LINES_ALL, PO_DISTRIBUTIONS_ALL) and manufacturing entities (WIP_ENTITIES, WIP_LINES, WIP_OPERATIONS, WIP_REPETITIVE_SCHEDULES), while also serving as a parent to its own detail table, JAI_PO_OSP_LINE_DTLS. The header record is held in JAI_PO_OSP_HDRS, linked through FORM_ID, forming a classic header-line-detail hierarchy.

Key Information Stored

The table contains 31 documented columns in the 12.2.2 schema. The unique identifier for each row is LINE_ID, which is also the primary key (JAI_PO_OSP_LINES_PK). No additional unique indexes are documented beyond this surrogate key.

• LINE_ID — Surrogate primary key uniquely identifying each line record.
• FORM_ID — Foreign key to JAI_PO_OSP_HDRS, associating the line with its parent 57F4 form header.
• PO_LINE_ID — Foreign key to PO_LINES_ALL, referencing the purchase order line.
• PO_DISTRIBUTION_ID — Foreign key to PO_DISTRIBUTIONS_ALL, identifying the associated distribution.
• ITEM_ID — Inventory item identifier for the line.
• WIP_ENTITY_ID, WIP_LINE_ID, WIP_REPETITIVE_SCHEDULE_ID, WIP_OPERATION_SEQUENCE_NUM — Work in Process references identifying the manufacturing entity, line, repetitive schedule, and operation sequence.
• ASSEMBLY_ID, PARENT_ITEM_ID — Assembly and parent item references supporting component relationships.
• DESPATCH_QTY, RETURN_QTY, DISPATCHED_QTY, ORIGINAL_QTY, SCRAP_QTY — Quantities tracking dispatch, returns, original amounts, and scrap.
• EXCISE_RATE, TARIFF_CODE — Localization-specific tax and tariff attributes.
• PROCESS_REQD, SOURCE_CODE, IDENTIFICATION — Processing flags, source identification, and descriptive attributes.
• STANDARD WHO COLUMNS — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER.

Common Use Cases and Queries

The most common reporting scenario joins the line table to its header to reconstruct the full 57F4 document. A typical pattern retrieves dispatch and excise information for a given form:

• Reconciling dispatched quantities against purchase order receipts, joining PO_LINE_ID to PO_LINES_ALL.
• Tracking WIP-related component consumption through WIP_ENTITY_ID and WIP_LINE_ID.
• Computing excise liabilities using EXCISE_RATE and ITEM_VALUE across lines.
• Generating tariff reports filtered by TARIFF_CODE for regional compliance.

Sample SQL:

SELECT l.line_id, l.despatch_qty, l.excise_rate, l.tariff_code FROM ja.jai_po_osp_lines l WHERE l.form_id = :form_id AND l.process_reqd = 'Y';

Related Objects

• JAI_PO_OSP_HDRS — Parent header via FORM_ID.
• JAI_PO_OSP_LINE_DTLS — Child detail via LINE_ID.
• PO_LINES_ALL — Purchase order lines via PO_LINE_ID.
• PO_DISTRIBUTIONS_ALL — Distributions via PO_DISTRIBUTION_ID.
• WIP_ENTITIES — Manufacturing entities via WIP_ENTITY_ID.
• WIP_LINES — WIP lines via WIP_LINE_ID.
• WIP_REPETITIVE_SCHEDULES — Repetitive schedules via WIP_REPETITIVE_SCHEDULE_ID.
• WIP_OPERATIONS — Operations via WIP_ENTITY_ID and WIP_OPERATION_SEQUENCE_NUM.