Results for “so_report_sets”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
SO_REPORT_SETS is an Order Entry (OE) configuration table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores document set definitions used when printing shipping documents. Specifically, the table holds the named report sets that the Ship Confirm Delivery and Ship Confirm Departure windows present to users, allowing a single selection to trigger the printing of an ordered group of documents (for example, packing slip, bill of lading, and commercial invoice) at the moment a delivery is confirmed or a departure is recorded.
The object resides in the OE schema and is documented as VALID in the ETRM repository. Because it functions as the parent of the individual report assignments (SO_REPORT_SET_LINES) and is itself referenced by delivery and departure records, the metadata's heuristic Data Vault classification is hub-leaning. Modeled in Data Vault terms, SO_REPORT_SETS would serve as a hub holding the unique report-set business key, while descriptive columns such as NAME, DESCRIPTION, and the date-activity range would more naturally belong to an attached satellite. This is offered as a modeling suggestion, not as an Oracle-imposed constraint.
Key Information Stored
The table contains 28 documented columns. The surrogate primary key is REPORT_SET_ID, enforced by SO_REPORT_SETS_PK and additionally guaranteed unique by index SO_REPORT_SETS_U1. The business-key candidate is NAME, uniquely enforced by SO_REPORT_SETS_U2, which is how users identify a report set in the Ship Confirm windows. The most significant columns are:
- REPORT_SET_ID — surrogate primary key; the join target for all child and referencing tables.
- NAME — the user-visible, unique name of the document set.
- DESCRIPTION — free-text explanation of the set's purpose.
- USAGE_CODE — indicates the context in which the set may be used (for example, delivery versus departure printing).
- SUBMISSION_METHOD — controls how the set is submitted for printing.
- START_DATE_ACTIVE and END_DATE_ACTIVE — the effective date range that governs whether the set is selectable.
- CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit (WHO) columns maintained automatically by EBS.
- CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — the DFF (descriptive flexfield) segment set, available for customer-specific extension.
Common Use Cases and Queries
The primary operational use is set-up validation: confirming that a report set intended for Ship Confirm Delivery or Ship Confirm Departure exists, is active, and is correctly linked to its constituent reports. A typical lookup joins the header to its lines:
SELECT rs.report_set_id, rs.name, rs.usage_code, rsl.* FROM oe.so_report_sets rs, oe.so_report_set_lines rsl WHERE rs.report_set_id = rsl.report_set_id AND rs.name = :set_name;SELECT * FROM oe.so_report_sets WHERE sysdate BETWEEN start_date_active AND NVL(end_date_active, sysdate + 1);— list currently effective sets.SELECT d.delivery_id, d.report_set_id, rs.name FROM wsh_deliveries d, oe.so_report_sets rs WHERE d.report_set_id = rs.report_set_id;— audit which set each delivery uses.
Reporting use cases include tracing which deliveries or departures reference a given set, and reviewing date-activity windows to troubleshoot sets that no longer appear in the Ship Confirm LOV.
Related Objects
The FK metadata defines the following significant relationships:
- SO_REPORT_SET_LINES — child table; joins on REPORT_SET_ID and holds the ordered individual reports comprising the set.
- WSH_DELIVERIES — references SO_REPORT_SETS via REPORT_SET_ID; records the set chosen for a delivery.
- WSH_DEPARTURES — references SO_REPORT_SETS via REPORT_SET_ID; records the set chosen for a departure.
- OE.SO_REPORT_SETS_PK / SO_REPORT_SETS_U1 / SO_REPORT_SETS_U2 — the primary key and unique indexes enforcing REPORT_SET_ID and NAME integrity.
These relationships confirm SO_REPORT_SETS as a controlled reference hub for shipping document printing in Order Entry and Shipping Execution.
-
Document sets to be printed from Ship Confirm Delivery and Ship Confirm Departure windows
-
Document sets to be printed from Ship Confirm Delivery and Ship Confirm Departure windows
-
SYNONYM: APPS.SO_REPORT_SETS 12.2.2
-
TABLE: OE.SO_REPORT_SETS 12.2.2
-
SYNONYM: APPS.SO_REPORT_SETS 12.1.1
-
TABLE: OE.SO_REPORT_SETS 12.1.1
-
VIEW: OE.SO_REPORT_SETS# 12.2.2
-
View: WSHFV_DEPARTURE 12.1.1
- Retrofitted
APPS.WSHFV_DEPARTURE·↳ MTL_SYSTEM_ITEMS·↳ SO_REPORT_SETS·↳ WSH_DEPARTURES·Explore OE module →
-
VIEW: OE.SO_REPORT_SETS# 12.2.2
-
View: WSHFV_DEPARTURE 12.2.2
- Retrofitted
APPS.WSHFV_DEPARTURE·↳ MTL_SYSTEM_ITEMS·↳ SO_REPORT_SETS·↳ WSH_DEPARTURES·Explore OE module →
-
View: WSH_DEPARTURES_V 12.1.1
Departures for departure planning or ship confirm
APPS.WSH_DEPARTURES_V·↳ FND_GLOBAL·↳ MTL_SYSTEM_ITEMS·↳ SO_LOOKUPS·Explore OE module →
-
View: WSH_DEPARTURES_V 12.2.2
Departures for departure planning or ship confirm
APPS.WSH_DEPARTURES_V·↳ FND_GLOBAL·↳ MTL_SYSTEM_ITEMS·↳ SO_LOOKUPS·Explore OE module →
-
VIEW: APPS.WSHFV_DEPARTURE 12.1.1
-
VIEW: APPS.WSHFV_DEPARTURE 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
VIEW: APPS.WSH_DEPARTURES_V 12.1.1
-
VIEW: APPS.WSH_DEPARTURES_V 12.2.2
-
VIEW: APPS.WSHFV_DEPARTURE 12.2.2
-
VIEW: APPS.WSHFV_DEPARTURE 12.1.1
-
Document set lines
-
Document set lines
-
View: WSHFV_DELIVERY 12.1.1
- Retrofitted
Not implemented in this database·Explore OE module →
-
View: WSHFV_DELIVERY 12.2.2
- Retrofitted
Not implemented in this database·Explore OE module →
-
VIEW: APPS.WSH_DEPARTURES_V 12.2.2
-
View: SO_PICKING_BATCHES_V 12.1.1
10SC ONLY
Not implemented in this database·Explore OE module →
-
View: SO_PICKING_BATCHES_V 12.2.2
10SC ONLY
Not implemented in this database·Explore OE module →
-
VIEW: APPS.WSH_DEPARTURES_V 12.1.1
-
Shipping departures
-
Shipping departures
-
View: WSH_DELIVERIES_V 12.2.2
Deliveries for departure planning or ship confirm
Not implemented in this database·Explore OE module →
-
View: WSH_DELIVERIES_V 12.1.1
Deliveries for departure planning or ship confirm
Not implemented in this database·Explore OE module →
-
Shipping deliveries
-
Shipping deliveries
-
eTRM - OE Tables and Views 12.2.2
Temporary table
-
eTRM - OE Tables and Views 12.1.1
Temporary table
-
eTRM - OE Tables and Views 12.1.1
Temporary table
-
eTRM - OE Tables and Views 12.2.2
Temporary table