Search Results so_report_usages_pk

Overview

The SO_REPORT_USAGES table is a core data object within the Oracle E-Business Suite (EBS) Order Entry (OE) module. It functions as a junction or mapping table that defines the specific business contexts, or "usages," for which a configured document set report is applicable. In Oracle EBS, document sets are used to generate various order-related outputs, such as order acknowledgments, pick slips, packing slips, and invoices. This table's primary role is to associate a specific report definition (from SO_REPORTS) with one or more usage codes, thereby controlling where and when that document set is available for execution within the order management workflow. It is a critical component for ensuring the correct document template is selected based on the business transaction being processed.

Key Information Stored

The table stores the essential linkage between a report and its intended application. The key columns, as indicated by the provided metadata, are:

• REPORT_USAGE_ID: The primary key column (SO_REPORT_USAGES_PK) providing a unique identifier for each report-usage association record.
• REPORT_ID: A foreign key column that references the SO_REPORTS table (SO_REPORTS.REPORT_ID). This identifies the specific document set report being configured.
• USAGE_CODE: A code that defines the business context or transaction type for which the report is valid. This column, combined with REPORT_ID, forms a unique constraint (SO_REPORT_USAGES_UK1). Common usage codes might correspond to document types like 'ORDER_ACKNOWLEDGEMENT', 'PICK_SLIP', or 'COMMERCIAL_INVOICE'.

Common Use Cases and Queries

A primary use case is auditing and validating the setup of document printing. For instance, an implementation consultant may need to verify all reports configured for a specific usage, or identify which usages are assigned to a particular report to troubleshoot missing document options in the UI. Common SQL queries include listing all usages for a known report name, or finding all reports assigned to a specific usage code for compliance checks.

Sample query to find all usage codes for a report named 'MY_ACK_PACK':

SELECT r.report_name, u.usage_code
FROM oe.so_reports r,
     oe.so_report_usages u
WHERE r.report_id = u.report_id
  AND r.report_name = 'MY_ACK_PACK';

Another typical scenario involves joining through to SO_REPORT_DESTINATIONS to get a complete picture of a document set's configuration—its usages and its output destinations (e.g., print, email, XML).

Related Objects

As documented in the provided metadata, SO_REPORT_USAGES has a direct and fundamental relationship with the SO_REPORTS table. The relationship is enforced by a foreign key constraint where SO_REPORT_USAGES.REPORT_ID references SO_REPORTS.REPORT_ID. This means every record in SO_REPORT_USAGES must correspond to a valid, pre-existing report definition in SO_REPORTS. The table is also intrinsically linked to the document set submission logic within the Order Management module, as the application queries this table to determine the valid report(s) for a given document usage during the concurrent request submission process. While not listed in the brief metadata, this table is often queried in conjunction with SO_REPORT_DESTINATIONS and OE_DOCUMENT_SETS to understand the full document generation setup.