Search Results jmf_shikyu_adjustments




Overview
Explore in AI Chat

Overview

The JMF_SHIKYU_ADJUSTMENTS table is a component of the Oracle E-Business Suite Supply Chain Localizations module (JMF), a product family that delivers country-specific extensions to core Oracle manufacturing and procurement flows, most notably for Japanese subcontracting and pay-on-receipt (shikyu) processing. The table records adjustment entries applied against shikyu payment components associated with subcontract purchase order shipments. Each row captures a discrete monetary or quantity adjustment, its unit of measure, the reason for the adjustment, and the standard Oracle concurrent program audit context that identifies who created or last modified the record and through which request or program.

Because the table is documented as having no child tables referencing it and only a single foreign key pointing outward, the ETRM heuristic classifies it as a standalone object within the Data Vault model. In Data Vault terms this suggests it behaves most like a satellite attached to a parent subcontract order hub, carrying descriptive adjustment attributes rather than defining new business keys or many-to-many relationships. Practitioners modeling the JMF domain should treat ADJUSTMENT_ID as the row-level identifier and SUBCONTRACT_PO_SHIPMENT_ID as the effective parent join.

Key Information Stored

The table contains 16 documented columns. The most significant are:

Common Use Cases and Queries

Typical usage centers on reconciliation of shikyu payments against subcontract receipts, audit of adjustment activity by reason code, and reporting of net payable positions after adjustments. A representative query joins adjustments to their parent subcontract order:

  • List all adjustments for a shipment: SELECT a.ADJUSTMENT_ID, a.ADJUSTMENT, a.UOM, a.REASON FROM JMF.JMF_SHIKYU_ADJUSTMENTS a WHERE a.SUBCONTRACT_PO_SHIPMENT_ID = :shipment_id;
  • Aggregate adjustments by reason: SELECT REASON, SUM(ADJUSTMENT) FROM JMF.JMF_SHIKYU_ADJUSTMENTS GROUP BY REASON;
  • Audit trail lookup by concurrent request: SELECT * FROM JMF.JMF_SHIKYU_ADJUSTMENTS WHERE REQUEST_ID = :request_id;

Because the table is standalone, reporting should always resolve the SUBCONTRACT_PO_SHIPMENT_ID to obtain meaningful supplier and order context.

Related Objects

  • JMF_SUBCONTRACT_ORDERS — Parent object via SUBCONTRACT_PO_SHIPMENT_ID; the primary reference from JMF_SHIKYU_ADJUSTMENTS.
  • JMF_SHIKYU_ADJUSTMENTS_PK / _U1 — Primary key constraint and unique index on ADJUSTMENT_ID.
  • JMF shikyu component tables — Reference SHIKYU_COMPONENT_ID for the adjusted payment element.
  • FND_CONCURRENT_REQUESTS — Join on REQUEST_ID for concurrent program execution context.
  • FND_USER — Join on CREATED_BY and LAST_UPDATED_BY for user attribution.