Results for “wsh_report_temp”

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

Overview

The WSH_REPORT_TEMP table is a temporary staging table owned by the OE (Order Entry) schema in Oracle E-Business Suite. It is classified as a temporary table in the ETRM data dictionary and is primarily used by the shipping and order-entry reporting engine to assemble denormalized rows prior to generating a report output, such as a shipper or packing slip report. The table does not persist transactional data permanently; instead, it acts as a scratchpad during the run of a shipping report concurrent program, allowing for efficient aggregation of delivery, line, and item information before the final report layout is produced.

In Data Vault modeling terms, the heuristic classification for this table is standalone. It does not reference other tables via foreign keys; rather, it is populated by the report program and consumed directly by the reporting engine. This suggests it may be treated as a standalone entity or a transient staging area rather than a durable hub, link, or satellite.

Key Information Stored

The table contains 37 columns, reflecting a composite view of shipping and order data. The most significant columns include:

• REPORT_TEMP_ID — Surrogate primary key for the temporary row.
• DEPARTURE_ID — Foreign key to WSH_DEPARTURES, identifying the shipment departure associated with the report row.
• DELIVERY_ID — Identifier for the delivery grouping.
• LINE_ID — Order line identifier.
• ORGANIZATION_ID — Inventory organization context.
• INVENTORY_ITEM_ID and CUSTOMER_ITEM_ID — Item and customer-item cross-reference; the latter is a FK to MTL_CUSTOMER_ITEMS.
• ORDER_NUMBER and PURCHASE_ORDER_NUM — Business document references.
• SHIPPED_QUANTITY, ORDERED_QUANTITY, QUANTITY_TO_INVOICE, TOTAL_SHIPPED_TODATE — Quantitative measures used in shipping and invoicing reconciliation.
• SHIPPED_FLAG, CHILD_RFR_FLAG, REQUIRED_FOR_REVENUE_FLAG, CONFIGURATION_ITEM_FLAG, INCLUDE_ON_SHIP_DOCS — Flags controlling report inclusion and revenue recognition.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, REQUEST_ID, PROGRAM_ID — Standard Who columns and concurrent program context.

The primary key is REPORT_TEMP_ID. Business-key candidates are not documented, as the table is transient.

Common Use Cases and Queries

WSH_REPORT_TEMP is typically queried during debugging of shipping report output or when customizing report logic. Sample query:

SELECT r.REPORT_TEMP_ID, r.ORDER_NUMBER, r.SHIPPED_QUANTITY, r.SHIPPED_FLAG
FROM   OE.WSH_REPORT_TEMP r
WHERE  r.DEPARTURE_ID = :departure_id
AND    r.REQUEST_ID = :request_id;

Because rows are tied to a REQUEST_ID, concurrent program instances can be isolated. Reporting use cases include packing slip generation, shipper confirmation, and revenue shipment reconciliation.

Related Objects

• WSH_DEPARTURES — joined via DEPARTURE_ID.
• MTL_CUSTOMER_ITEMS — joined via CUSTOMER_ITEM_ID.
• WSH_DELIVERY_DETAILS — delivery line details.
• OE_ORDER_HEADERS_ALL / OE_ORDER_LINES_ALL — order context.
• MTL_SYSTEM_ITEMS_B — item master.
• WSH_SHIPPING_REPORT_PUB — PL/SQL API populating this table.