Search Results jai_po_line_locations




Overview

JAI_PO_LINE_LOCATIONS is a table owned by the JA schema (JA – Asia/Pacific Localizations) within Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It stores localization-level information at the purchase order line shipment (line location) level. Where the standard Purchasing tables PO_HEADERS_ALL, PO_LINES_ALL, and PO_LINE_LOCATIONS_ALL capture the base transactional document structure, this table extends the shipment record with tax and localization data required by Asia/Pacific regional requirements, including tax amounts, total amounts, tax category assignments, and price override information.

The table is documented with 37 columns and is therefore a narrow, extension-oriented object rather than a standalone transaction table. From a Data Vault modeling perspective, the mined foreign key structure suggests a satellite-leaning classification: the table's primary key is a surrogate identifier (LINE_FOCUS_ID) and its foreign keys point outward to core purchasing hubs and to the localization tax category dimension. Each row keys back to a specific PO shipment, making the table behave as a descriptive satellite attached to the PO line location business key, with additional dependent detail tables (JAI_PO_TAXES, JAI_PO_REQUEST_T) hanging off the same LINE_FOCUS_ID.

Key Information Stored

The primary key is JAI_PO_LINE_LOCATIONS_PK, defined on the surrogate column LINE_FOCUS_ID. A second unique index, JAI_PO_LINE_LOCATIONS_UK1, is defined on the combination of PO_LINE_ID and LINE_LOCATION_ID, making that pair the principal business-key candidate for a given shipment localization record.

  • LINE_FOCUS_ID – Surrogate primary key; also the join key used by dependent tables JAI_PO_TAXES and JAI_PO_REQUEST_T.
  • PO_HEADER_ID – Foreign key to PO_HEADERS_ALL, identifying the owning purchase order.
  • PO_LINE_ID – Foreign key to PO_LINES_ALL; part of the unique business key.
  • LINE_LOCATION_ID – Foreign key to PO_LINE_LOCATIONS_ALL, identifying the specific shipment; part of the unique business key.
  • TAX_CATEGORY_ID – Foreign key to JAI_CMN_TAX_CTGS_ALL, the localization tax category applied to the shipment.
  • TAX_AMOUNT and TOTAL_AMOUNT – Stored tax and total values at the shipment localization level.
  • TAX_MODIFIED_FLAG – Indicates whether the tax treatment was manually altered.
  • PRICE_OVERRIDE, QUANTITY, CURRENCY – Pricing and quantity context for the localized line.
  • ITEM_ID, VENDOR_ID, VENDOR_SITE_ID – Item and supplier identifiers carried for reporting convenience.
  • SERVICE_TYPE_CODE – Service classification for the shipment.
  • OBJECT_VERSION_NUMBER – Optimistic locking column used by the OA Framework.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1ATTRIBUTE15 – Descriptive flexfield storage.

Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) provide audit trail information.

Common Use Cases and Queries

Typical usage involves joining this table to the core Purchasing tables to report on localized tax treatment of PO shipments. A representative query retrieves shipment-level tax detail for a purchase order:

  • SELECT j.po_line_id, j.line_location_id, j.tax_amount, j.total_amount, j.tax_category_id FROM ja.jai_po_line_locations j WHERE j.po_header_id = :p_po_header_id;
  • Join to PO_LINE_LOCATIONS_ALL on LINE_LOCATION_ID to obtain shipment quantities, promised dates, and receipt routing alongside the localized tax figures.
  • Join to JAI_CMN_TAX_CTGS_ALL on TAX_CATEGORY_ID to resolve tax category descriptions for reporting.
  • Aggregate TAX_AMOUNT and TOTAL_AMOUNT by vendor (VENDOR_ID) or currency (CURRENCY) for regional tax reporting.
  • Audit rows where TAX_MODIFIED_FLAG is set to identify manually adjusted tax treatment during PO entry or revision.
  • Feed downstream localization processes through the dependent tables JAI_PO_TAXES and JAI_PO_REQUEST_T, both keyed by LINE_FOCUS_ID.

Related Objects

  • PO_LINE_LOCATIONS_ALL – Joined via JAI_PO_LINE_LOCATIONS.LINE_LOCATION_ID; the parent shipment record.
  • PO_LINES_ALL – Joined via PO_LINE_ID; supplies line-level item and pricing context.
  • PO_HEADERS_ALL – Joined via PO_HEADER_ID; the purchase order header.
  • JAI_CMN_TAX_CTGS_ALL – Joined via TAX_CATEGORY_ID; the localization tax category definition.
  • JAI_PO_TAXES – References this table through LINE_FOCUS_ID; stores the detailed tax lines for each shipment.
  • JAI_PO_REQUEST_T – References this table through LINE_FOCUS_ID; holds related localization request detail.

These relationships confirm that JAI_PO_LINE_LOCATIONS acts as the central localization anchor for Asia/Pacific purchasing tax processing, bridging standard Purchasing entities with the JAI tax structures.