Search Results wsh_report_set_lines_u1

Overview

The WSH_REPORT_SET_LINES table is a core data structure within the Oracle E-Business Suite Shipping (WSH) module, specifically for releases 12.1.1 and 12.2.2. It functions as a junction table that defines the composition of shipping report sets. A report set is a logical grouping of individual shipping reports (concurrent programs) that can be submitted and processed together in a predefined sequence. This table's primary role is to assign specific reports to a report set, thereby enabling batch execution of shipping-related documents such as bills of lading, packing slips, and shipping manifests directly from the shipping transaction interface.

Key Information Stored

The table stores the mapping between a report set and its constituent reports, along with execution metadata. The primary key, REPORT_SET_LINE_ID, uniquely identifies each line in the set. The REPORT_SET_ID is a foreign key linking to the parent WSH_REPORT_SETS table, which defines the report set header. The APPLICATION_ID and CONCURRENT_PROGRAM_ID columns identify the specific Oracle application and concurrent program (report) to be executed. A critical operational column is PROGRAM_SEQUENCE, which dictates the order in which the reports within the set are run. The table includes a full complement of Descriptive Flexfield columns (ATTRIBUTE_CATEGORY through ATTRIBUTE15) for extensibility and standard Oracle "Who" columns (CREATED_BY, LAST_UPDATE_DATE, etc.) for auditing.

Common Use Cases and Queries

The primary use case is the management and execution of predefined shipping document batches. Administrators use this data to configure which reports are included in standard shipping workflows. A common reporting need is to list all reports within a specific set, ordered for execution. For example, to find the reports in a set named 'STANDARD_PACKING_SLIP', a developer might use:

• SELECT wrsl.program_sequence, fcp.user_concurrent_program_name
• FROM wsh_report_set_lines wrsl,
• wsh_report_sets wrs,
• fnd_concurrent_programs_vl fcp
• WHERE wrsl.report_set_id = wrs.report_set_id
• AND wrsl.concurrent_program_id = fcp.concurrent_program_id
• AND wrs.name = 'STANDARD_PACKING_SLIP'
• ORDER BY wrsl.program_sequence;

Another critical scenario involves debugging or auditing report set submissions, where queries join this table with FND_CONCURRENT_REQUESTS using the REQUEST_ID who column to trace execution history.

Related Objects

The WSH_REPORT_SET_LINES table maintains a direct, documented foreign key relationship with the WSH_REPORT_SETS table, which stores the report set definition. The join is performed on the REPORT_SET_ID column. This is the primary relationship. The table is also intrinsically linked to the FND_CONCURRENT_PROGRAMS table (via CONCURRENT_PROGRAM_ID) and the FND_APPLICATION table (via APPLICATION_ID) to resolve the actual executable report and its owning application. The unique index WSH_REPORT_SET_LINES_U1 on REPORT_SET_LINE_ID enforces the primary key constraint, WSH_REPORT_SET_LINES_PK.