Results for “so_reports”

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

Overview

OE.SO_REPORTS is the Oracle Order Entry/Shipping repository of report definitions registered within the E-Business Suite Order Management module. The table stores the header-level registration of each seeded or user-defined report that participates in Order Entry reporting operations, including the report name, the owning concurrent program application, and descriptive metadata. It functions as the central reference point from which report parameters, report printers, report sets, and report usage attributes are derived, making it the authoritative catalog for Order Entry report configuration in both 12.1.1 and 12.2.2 environments.

Under the heuristic Data Vault classification implied by the foreign key structure of OE.SO_REPORTS (a table originating five distinct foreign key relationships), the table can be modeled as a hub. It carries a single-column surrogate primary key, REPORT_ID, and a documented unique business key, and it is referenced by five dependent tables that supply descriptive context for each report. This makes SO_REPORTS the natural parent entity for any Data Vault or dimensional model built around Order Entry report configuration.

Key Information Stored

The table contains 25 documented columns. The most significant are:

• REPORT_ID — the surrogate primary key (SO_REPORTS_PK), a system-generated identifier that uniquely distinguishes each report definition. It is also the leading column of the unique index SO_REPORTS_U1 and is the column to which all five dependent tables join.
• REPORT_APPLICATION_ID — the application identifier of the concurrent program associated with the report; it participates in the documented foreign key to FND_CONCURRENT_PROGRAMS.
• NAME — the report name. Together with REPORT_APPLICATION_ID, it forms the unique business key documented as SO_REPORTS_U2, ensuring that no two reports may share the same name within the same application.
• DESCRIPTION — free-form descriptive text characterizing the report's purpose.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield (DFF) columns, providing extensible, customer-configurable attributes for each report definition.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard Oracle who-columns recording audit and concurrency information.

Common Use Cases and Queries

The table is most commonly queried to enumerate available Order Entry reports, to resolve a report name to its internal identifier, or to trace how a report's parameters and printers are configured. A typical lookup resolving a report by its business key is:

• SELECT report_id, name, report_application_id
• FROM oe.so_reports WHERE name = :p_report_name;

Joining to the concurrent program master clarifies which application owns each registered report:

• SELECT sr.report_id, sr.name, sr.report_application_id
• FROM oe.so_reports sr, fnd_concurrent_programs fcp
• WHERE sr.report_application_id = fcp.concurrent_program_id;

Reporting and reconciliation queries frequently fan out from REPORT_ID into SO_REPORT_PARAMETERS, SO_REPORT_PRINTERS, and SO_REPORT_SET_LINES to reconstruct the full configuration of a report or report set. The DFF attributes are used in descriptive flexfield queries where customers have stored supplemental classification values.

Related Objects

The FK metadata documents the following significant relationships:

• FND_CONCURRENT_PROGRAMS — the parent application/name reference. SO_REPORTS.REPORT_APPLICATION_ID and SO_REPORTS.NAME map to the corresponding concurrent program columns, linking each report to its runnable definition.
• SO_REPORT_PARAMETERS.REPORT_ID — parameter definitions belonging to each report.
• SO_REPORT_PRINTERS.REPORT_ID — printer assignments per report.
• SO_REPORT_SET_LINES.REPORT_ID — membership of each report within report sets.
• SO_REPORT_USAGES.REPORT_ID — usage records governing where and how each report may be invoked.
• SO_NOTE_USAGE_ATTRIBUTES.REPORT_ID — note-usage attribute configuration tied to each report.

Together these dependencies establish SO_REPORTS as the pivot object for Order Entry report registration, parameterization, and print distribution.