Results for “application_id”

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

Overview

SO_REPORT_NAMES_V is a reporting-oriented database view owned by the APPS schema within the Oracle E-Business Suite Order Entry (OE) product family. Its documented purpose is to expose "Report names" — a consolidated list of concurrent program names that are available to the Order Entry reporting framework. In Oracle EBS 12.1.1 and 12.2.2, this view functions as a lightweight lookup layer that joins report set definitions against the concurrent program definitions maintained by the concurrent manager. It enables Order Entry forms, report set maintenance screens, and custom extensions to resolve a human-readable report name from a numeric report identifier without querying the underlying concurrent manager tables directly. The view carries a documented status of VALID in the ETRM metadata and is exposed as APPS.SO_REPORT_NAMES_V.

Underlying Base Objects

The view definition is concise and is built on two documented objects:

• FND_CONCURRENT_PROGRAMS_VL (VIEW) — the concurrent manager's language-enabled program definition view, which supplies the user-facing concurrent program name (USER_CONCURRENT_PROGRAM_NAME), application, and program identifier.
• SO_REPORT_SET_LINES (SYNONYM) — the Order Entry report set line table that defines which concurrent programs belong to a given report set.

The join predicate matches R.APPLICATION_ID = F.APPLICATION_ID AND F.CONCURRENT_PROGRAM_ID = R.REPORT_ID, effectively pairing each report set line with its corresponding concurrent program definition. A DISTINCT operator is applied to eliminate duplicate rows that can arise when the same program appears in multiple report sets, producing a de-duplicated list of report identifiers and names per application.

Key Columns

• REPORT_ID — the concurrent program identifier (CONCURRENT_PROGRAM_ID) associated with a report set line; this is the numeric foreign key used throughout Order Entry for report selection.
• REPORT_NAME — the user-facing concurrent program name, aliased from F.USER_CONCURRENT_PROGRAM_NAME; this is the value most commonly displayed to end users.
• APPLICATION_ID — the application owning the concurrent program, used to scope reports to the correct product and to support multi-application environments.

Common Use Cases and Queries

This view is typically referenced when building Order Entry report set maintenance functionality, when validating that a report ID resolves to a known program name, or when constructing custom list-of-values queries in 12.1.1 or 12.2.2.

• Resolve a name for a known report ID: SELECT REPORT_ID, REPORT_NAME, APPLICATION_ID FROM APPS.SO_REPORT_NAMES_V WHERE REPORT_ID = :p_report_id;
• List available reports for an application: SELECT REPORT_ID, REPORT_NAME FROM APPS.SO_REPORT_NAMES_V WHERE APPLICATION_ID = :p_app_id ORDER BY REPORT_NAME;
• Validate that a report belongs to a report set: join SO_REPORT_SET_LINES to SO_REPORT_NAMES_V on REPORT_ID to confirm the set line resolves to a concurrent program name.

Because the view joins language-enabled concurrent program definitions, it should be used with standard EBS language handling expectations. Queries should always filter or join on APPLICATION_ID where possible to guarantee correct scoping, and applications should not rely on the view for update operations, as it is read-only by design.