Results for “wsh_report_sets”

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

Overview

WSH_REPORT_SETS is a Shipping Execution (WSH) table that stores the definition of shipping report sets — named groupings of shipping-related reports that can be submitted together as a single unit. In Oracle EBS Release 12.1.1 and 12.2.2, the table serves as the header record for report set configuration, allowing organizations to bundle multiple reports and control how and when they are launched. Each row represents one report set, identified by a surrogate primary key and qualified by a unique business key, and the table carries the usual Oracle EBS descriptive flexfield and WHO audit columns.

From a Data Vault modeling perspective, the mined metadata classifies WSH_REPORT_SETS as hub-leaning. This is a reasonable heuristic: the table holds a stable, uniquely identified business concept (the report set) with a small number of descriptive attributes, and it is referenced by a single child table via a foreign key. In practice it functions as a hub candidate, with the descriptive and audit columns behaving like satellite attributes.

Key Information Stored

The documented physical schema contains 32 columns. The most significant are summarized below.

• REPORT_SET_ID — the surrogate primary key, backed by the unique index WSH_REPORT_SETS_U1 and the primary key constraint WSH_REPORT_SETS_PK. This is the column referenced by child tables.
• NAME — the user-visible name of the report set, the primary business identifier used in setup and submission screens.
• USAGE_CODE — indicates the purpose or context in which the report set applies, distinguishing report sets by shipping usage.
• SUBMISSION_METHOD — governs how the report set is invoked or run, such as through concurrent processing.
• DESCRIPTION — free-text description of the report set for administrative reference.
• START_DATE_ACTIVE and END_DATE_ACTIVE — the effective-dating window that determines when the report set is valid and selectable.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield segments, allowing customers to capture additional site-specific information.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns recording row provenance.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context columns that record which request last modified the row.

Common Use Cases and Queries

Typical usage centers on setup validation and reporting on configured report sets. A common query retrieves active report sets and their associated lines:

• Listing active report sets: SELECT report_set_id, name, usage_code, submission_method FROM wsh_report_sets WHERE SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);
• Joining to the child table to enumerate the reports contained in each set: SELECT s.name, l.* FROM wsh_report_sets s, wsh_report_set_lines l WHERE s.report_set_id = l.report_set_id;
• Auditing recent configuration changes using LAST_UPDATE_DATE and LAST_UPDATED_BY.
• Identifying stale or expired report sets through the effective-dating columns.

Related Objects

The most significant dependent object is WSH_REPORT_SET_LINES, which references this table through WSH_REPORT_SET_LINES.REPORT_SET_ID. Because the metadata documents only this single incoming foreign key, the report set header is a relatively self-contained configuration entity. In practice, the report set is populated and maintained through the Shipping Execution setup and concurrent report submission flows, and the REFERENCE_ID relationship data confirms the hub-leaning classification, with WSH_REPORT_SET_LINES acting as the dependent detail.