Results for “parameter_num”

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

Overview

SO_REPORT_PARAMETERS is a transactional configuration table owned by the OE (Order Entry) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store report parameters — the individual input fields that the order management reporting framework requires or accepts when a report or concurrent program is submitted. Each row describes one parameter belonging to one report, giving the OE reporting layer a declarative definition of what a report needs before it can execute.

The table is registered as VALID in the ETRM metadata, and its physical definition comprises eight documented columns. Structurally, its primary key SO_REPORT_PARAMETERS_PK is a composite of REPORT_ID and PARAMETER_NUM, and it carries a single documented foreign key, SO_REPORT_PARAMETERS.REPORT_ID referencing SO_REPORTS. Because that foreign key is the only outbound reference and it points to a parent report definition, the heuristic Data Vault classification mined from the FK structure is satellite-leaning — that is, the table is best modeled as descriptive satellite data attached to the SO_REPORTS parent rather than as an independent hub or a many-to-many link. This classification is a modeling suggestion only, inferred from relationship topology.

Key Information Stored

The composite primary key supplies the two most important columns. REPORT_ID identifies the parent report or concurrent program to which the parameter belongs; it is both the leading component of SO_REPORT_PARAMETERS_PK and the foreign key column joining to SO_REPORTS. PARAMETER_NUM is the sequence or ordinal of the parameter within that report, completing the primary key and establishing the parameter's position in the report's input order. Together these two columns are the business-key candidates — they are the only documented unique identifier for a parameter, so an application query for "parameter_num" is normally issued alongside REPORT_ID.

The remaining documented columns fall into two functional groups. NAME carries the parameter's label or prompt as presented to the user, and is the attribute most commonly displayed in reporting and enquiry screens. The standard Oracle EBS audit and concurrency columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — record who created and last modified the parameter definition and when, following the conventional WHO-column pattern used throughout the OE schema.

Common Use Cases and Queries

The principal use case is introspection of the report parameter catalog: determining which parameters a given order management report exposes, in what sequence, and under what names. A typical query filters on the business keys defined by the primary key:

• Retrieve all parameters for a report and order them: SELECT parameter_num, name FROM oe.so_report_parameters WHERE report_id = :p_report_id ORDER BY parameter_num;
• Locate a specific parameter by its ordinal: SELECT report_id, name FROM oe.so_report_parameters WHERE parameter_num = :p_parameter_num;
• Join to the parent report to build a full catalog: SELECT r.report_id, p.parameter_num, p.name FROM oe.so_reports r, oe.so_report_parameters p WHERE r.report_id = p.report_id ORDER BY r.report_id, p.parameter_num;
• Audit recently changed parameter definitions using the WHO columns: filter on LAST_UPDATE_DATE against a cutoff and inspect LAST_UPDATED_BY.

Reporting teams use these patterns to document report interfaces, to validate that a custom or cloned report exposes the expected prompts, and to drive migration scripts that compare parameter definitions between environments. Because the table is small and configuration-oriented, queries are inexpensive and are generally safe to run against production, though the underlying objects should still be accessed read-only.

Related Objects

The most significant related object is SO_REPORTS, the parent table referenced by the documented foreign key SO_REPORT_PARAMETERS.REPORT_ID. This is the only outbound relationship documented in the ETRM metadata and is the primary join path. Beyond it, the order entry reporting layer typically includes companion configuration and run-time tables such as SO_REPORT_PARAMETERS dependencies, report group and report assignment objects, and the concurrent program definitions in FND_CONCURRENT_PROGRAMS that ultimately launch the report. Custom views or PL/SQL packages in the OE schema that present or consume parameter definitions also depend on this table. When extending or troubleshooting order management reporting, SO_REPORTS and SO_REPORT_PARAMETERS should be treated as a single parent-child unit, joined on REPORT_ID and ordered by PARAMETER_NUM.