Results for “jmf_shikyu_adjustments_pk”

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

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:

• ADJUSTMENT_ID — Surrogate primary key, enforced by JMF_SHIKYU_ADJUSTMENTS_PK and also exposed as the unique index JMF_SHIKYU_ADJUSTMENTS_U1. This is the definitive business-key candidate for the row.
• SUBCONTRACT_PO_SHIPMENT_ID — Foreign key to JMF_SUBCONTRACT_ORDERS. Identifies the subcontract purchase order shipment against which the adjustment is booked.
• SHIKYU_COMPONENT_ID — Identifies the specific shikyu payment component being adjusted (for example a labor, material, or overhead element).
• ADJUSTMENT and UOM — The adjustment amount or quantity and its unit of measure, capturing the magnitude and dimension of the correction.
• REASON — Free-text or coded explanation for why the adjustment was raised.
• REQUEST_ID and BATCH_ID — Concurrent request and batch identifiers under which the adjustment was generated.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Oracle audit columns recording creation and modification metadata.
• PROGRAM_ID, PROGRAM_UPDATE_DATE, PROGRAM_APPLICATION_ID — Identify the concurrent program and application that last processed the row.

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.