Search Results parameter_num

Overview

The SO_REPORT_PARAMETERS table is a core data object within the Oracle E-Business Suite (EBS) Order Entry (OE) module, specifically for versions 12.1.1 and 12.2.2. It functions as a repository for the configuration parameters associated with various reports in the Order Management system. This table is essential for the runtime execution and customization of standard reports, as it stores the metadata that defines the input prompts, data types, default values, and validation rules for report parameters. Its role is to provide a structured, database-driven method for managing report behavior, separating the report logic from its configurable inputs, thereby enhancing maintainability and flexibility.

Key Information Stored

Based on the provided ETRM metadata, the table's structure is defined by its primary key and its relationship to the parent reports table. The critical columns include:

• REPORT_ID: A foreign key column that links each parameter record to its parent report definition in the SO_REPORTS table. This establishes which report the parameter belongs to.
• PARAMETER_NUM: A numeric identifier that, combined with REPORT_ID, forms the primary key (SO_REPORT_PARAMETERS_PK). This sequence number dictates the order of parameters and ensures uniqueness for a given report.

While the explicit column list is not detailed in the excerpt, typical parameter tables in this context would also store columns for the parameter's internal name, prompt text displayed to the user, data type (e.g., VARCHAR2, NUMBER, DATE), default value, list of values (LOV) definitions, and whether the parameter is mandatory or optional.

Common Use Cases and Queries

A primary use case is the administrative setup and troubleshooting of Order Management reports. Developers and functional consultants query this table to understand or modify the parameterization of a specific report. For instance, to list all parameters for a known report, one would join to the SO_REPORTS table using the documented foreign key relationship.

Sample Query: To retrieve the parameter sequence and names for a report titled 'Order Summary':

SELECT rp.parameter_num, rp.parameter_name, rp.prompt
FROM oe.so_report_parameters rp
JOIN oe.so_reports r ON r.report_id = rp.report_id
WHERE r.report_name = 'ORDER_SUMMARY'
ORDER BY rp.parameter_num;

Another common scenario involves data validation or impact analysis before migrating custom report configurations between environments, ensuring parameter consistency.

Related Objects

The ETRM documentation explicitly defines one critical foreign key relationship for this table:

• Parent Table: SO_REPORTS
• Relationship: The column SO_REPORT_PARAMETERS.REPORT_ID is a foreign key referencing the SO_REPORTS table. This enforces referential integrity, ensuring every parameter is associated with a valid, existing report definition.

This relationship is fundamental. The SO_REPORTS table acts as the master definition for reports, while SO_REPORT_PARAMETERS stores the detailed, child configuration for each. Any process or interface that generates or executes an Order Management report will likely traverse this relationship to gather the necessary runtime parameters.