Search Results jmf_subcontract_orders_temp

Overview

JMF.JMF_SUBCONTRACT_ORDERS_TEMP is a temporary (staging) table within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environment, belonging to the JMF product family, Supply Chain Localizations. As its name implies, the table functions as an intermediate holding area used during the creation, import, or generation of subcontract order data before that data is committed to the permanent transactional table JMF_SUBCONTRACT_ORDERS. It enables programs to validate, enrich, or batch-process subcontract order records — including purchase order shipment references, need-by dates, vendor details, and pricing — without immediately affecting live production records.

Under a heuristic Data Vault classification mined from its foreign key structure, the table is modelled as standalone, meaning it does not itself act as a central hub or hub-referencing link in the surrounding model. This suggestion reflects that the table primarily stores a denormalized, transient snapshot of subcontract order attributes rather than participating in a normalized hub-and-link topology. Its single documented foreign key — SUBCONTRACT_PO_SHIPMENT_ID → JMF_SUBCONTRACT_ORDERS — anchors the temporary rows to the permanent subcontract order they will ultimately populate.

Key Information Stored

The table exposes fifteen documented columns, several of which are the most significant for understanding its role:

• SUBCONTRACT_PO_SHIPMENT_ID — the foreign key linking the temporary row to the corresponding shipment record in JMF_SUBCONTRACT_ORDERS; this is the primary relational anchor.
• SUBCONTRACT_PO_HEADER_ID and SUBCONTRACT_PO_LINE_ID — business-key references to the subcontract purchase order header and line, carrying the purchasing document context.
• OEM_ORGANIZATION_ID — the original equipment manufacturer (outsourcing) organization for which the subcontract is created.
• TP_ORGANIZATION_ID — the trading partner (supplier/third-party) organization performing the subcontract work.
• VENDOR_ID and VENDOR_SITE_ID — the supplier and supplier site supplying the subcontracted service or material.
• NEED_BY_DATE — the required delivery/completion date, a key scheduling attribute.
• UOM, QUANTITY, CURRENCY, and OSA_ITEM_PRICE — the transacted unit of measure, ordered quantity, currency, and item price used for costing and validation.
• OSA_ITEM_ID, PROJECT_ID, and TASK_ID — item and project/task references supporting project-driven subcontracting.

No separate surrogate primary key or unique business-key index is documented in the ETRM metadata; SUBCONTRACT_PO_SHIPMENT_ID functions as the practical relational key, while the PO header/line identifiers are the strongest business-key candidates.

Common Use Cases and Queries

Typical usage centers on pre-staging and validating subcontract orders ahead of commit. Report developers and integration specialists query this table to reconcile staged rows against their target subcontract orders, to detect orphans, or to pre-validate costing and scheduling before data propagation. Sample patterns include:

• Reviewing all staged rows awaiting commit: SELECT * FROM JMF.JMF_SUBCONTRACT_ORDERS_TEMP;
• Matching staged rows to their permanent parent: SELECT t.*, o.* FROM JMF.JMF_SUBCONTRACT_ORDERS_TEMP t JOIN JMF.JMF_SUBCONTRACT_ORDERS o ON t.SUBCONTRACT_PO_SHIPMENT_ID = o.SUBCONTRACT_PO_SHIPMENT_ID;
• Grouping staged quantity and value by vendor and organization for forecasting or audit: SELECT VENDOR_ID, OEM_ORGANIZATION_ID, SUM(QUANTITY), CURRENCY FROM JMF.JMF_SUBCONTRACT_ORDERS_TEMP GROUP BY VENDOR_ID, OEM_ORGANIZATION_ID, CURRENCY;
• Filtering by NEED_BY_DATE to identify near-term subcontract commitments.

Related Objects

The most significant related object is JMF_SUBCONTRACT_ORDERS, the permanent table referenced by the documented foreign key on SUBCONTRACT_PO_SHIPMENT_ID. This relationship is the primary dependency: temporary rows are transformed into or reconciled against the permanent subcontract orders. Because the ETRM metadata documents only this single foreign key and classifies the table as standalone, the object's dependency footprint is narrow. Practically, surrounding objects likely include the JMF subcontract order concurrent programs and the purchasing tables (PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL) whose identifiers are carried in the SUBCONTRACT_PO_HEADER_ID and SUBCONTRACT_PO_LINE_ID columns, as well as supplier tables (PO_VENDORS / AP_SUPPLIERS) for the VENDOR_ID and VENDOR_SITE_ID attributes.