Search Results so_report_sets_pk




Overview

The SO_REPORT_SETS table is a core configuration table within the Order Entry (OE) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It serves as a master repository for defining document sets, which are logical groupings of shipping documents (such as packing slips, bills of lading, or commercial invoices) that can be printed as a batch. Its primary role is to support the shipping execution process, specifically enabling users to select and print pre-defined sets of documents from the Ship Confirm Delivery and Ship Confirm Departure windows. This functionality streamlines the shipping documentation process by eliminating the need to select individual reports during confirmation.

Key Information Stored

The table stores the essential metadata for each document set definition. The primary and unique key columns are the most critical for understanding its structure. The REPORT_SET_ID column serves as the system-generated primary key (SO_REPORT_SETS_PK) that uniquely identifies each document set within the database. The NAME column is a unique key (SO_REPORT_SETS_UK1) that stores the user-defined, descriptive name for the report set as it appears in the application's list of values. While the provided metadata does not list all columns, typical supporting columns would include creation and last update dates, and the user who created the set, aligning with Oracle's standard audit trail conventions.

Common Use Cases and Queries

The primary use case is the configuration and execution of batch document printing during shipping operations. An administrator defines report sets via the application, which creates records in this table. During ship confirm, a user selects a set from a list, and the system prints all associated reports defined in the related SO_REPORT_SET_LINES table. Common queries involve listing available sets for reporting or troubleshooting. For example, to retrieve all configured report sets, a basic SQL query would be: SELECT report_set_id, name FROM oe.so_report_sets ORDER BY name;. To investigate which set is assigned to a specific delivery, one would join with the WSH_DELIVERIES table: SELECT d.delivery_id, s.name FROM wsh_deliveries d, oe.so_report_sets s WHERE d.report_set_id = s.report_set_id;.

Related Objects

SO_REPORT_SETS is a central object with several key dependencies, as indicated by its foreign key relationships. The SO_REPORT_SET_LINES table is a direct child, containing the specific reports (e.g., packing slip, invoice) that belong to each set defined in the parent SO_REPORT_SETS table. Two tables from the Shipping Execution (WSH) module reference it: WSH_DELIVERIES and WSH_DEPARTURES. These foreign keys (on REPORT_SET_ID) store the document set selected for a particular delivery or departure, linking the configuration to the transactional shipping data. This structure clearly separates the reusable configuration (SO_REPORT_SETS) from the transactional assignment (WSH_DELIVERIES/WSH_DEPARTURES) and the detailed report composition (SO_REPORT_SET_LINES).

  • Table: SO_REPORT_SETS 12.1.1

    owner:OE,  object_type:TABLE,  fnd_design_data:OE.SO_REPORT_SETS,  object_name:SO_REPORT_SETS,  status:VALID,  product: OE - Order Entrydescription: Document sets to be printed from Ship Confirm Delivery and Ship Confirm Departure windows ,  implementation_dba_data: OE.SO_REPORT_SETS

  • Table: SO_REPORT_SETS 12.2.2

    owner:OE,  object_type:TABLE,  fnd_design_data:OE.SO_REPORT_SETS,  object_name:SO_REPORT_SETS,  status:VALID,  product: OE - Order Entrydescription: Document sets to be printed from Ship Confirm Delivery and Ship Confirm Departure windows ,  implementation_dba_data: OE.SO_REPORT_SETS