Results for “so_report_set_lines_v”

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

Overview

SO_REPORT_SET_LINES_V is a validity-checked view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the Order Entry (OE) product family and is documented in the E-Business Suite Technical Reference Manual (ETRM) with the description "10SC Only," indicating that the object is restricted to specific Oracle internal or country-specific reporting configurations rather than the general order management flow. The view exposes the individual lines that make up a report set used by the concurrent manager. Each row represents one concurrent program assigned to a report set, together with its execution order. In practice, the view provides a denormalized, human-readable projection of report set membership by joining the low-level intersection table SO_REPORT_SET_LINES to the program definition and the report definition. Because it surfaces the REPORT_SEQUENCE attribute directly, it is the canonical reference for determining and validating the order in which programs execute within an EBS report set, which is the concept frequently referenced by the search term "report_sequence."

Underlying Base Objects

The view is defined over three documented base objects:

• SO_REPORT_SET_LINES (SYNONYM) — the primary driving table, holding the association between a report set, a report, and the sequence in which the report executes.
• SO_REPORTS (SYNONYM) — supplies the REPORT_ID primary key and a descriptive attribute used to link each line to its program.
• FND_CONCURRENT_PROGRAMS_VL (VIEW) — the concurrent programs repository, providing the translated user-facing program name.

The join is expressed as RSL.REPORT_ID = R.REPORT_ID and R.NAME = F.CONCURRENT_PROGRAM_NAME, so each report set line is resolved to its underlying concurrent program by matching the report name against the concurrent program name. The view also carries the standard EBS WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) inherited from SO_REPORT_SET_LINES, and exposes RSL.ROWID as ROW_ID for row-level identification.

Key Columns

• REPORT_SET_LINE_ID — primary key of the report set line; uniquely identifies one program assignment within a set.
• REPORT_SET_ID — foreign key to the parent report set; groups all lines that belong to the same set.
• REPORT_ID — identifier of the individual report participating in the set.
• REPORT_SEQUENCE — the ordinal position of the program within the set; this is the column that governs execution order and is the object of the "report_sequence" search.
• NAME — the concurrent program name from FND_CONCURRENT_PROGRAMS_VL, aliased from USER_CONCURRENT_PROGRAM_NAME.
• DESCRIPTION — descriptive text drawn from SO_REPORTS.
• ROW_ID — the ROWID of the underlying SO_REPORT_SET_LINES row, useful for direct row addressing and updates.
• WHO columns — standard audit attributes for creation and last-update tracking.

Common Use Cases and Queries

Typical scenarios include listing the contents of a report set in execution order, verifying the PROGRAM_NAME assigned to a given Report, and auditing when a report set definition was last changed. A representative query to list all lines of a set in sequence is:

SELECT report_set_id, report_sequence, name, description, last_update_date FROM apps.so_report_set_lines_v WHERE report_set_id = :p_report_set_id ORDER BY report_sequence;

To locate the set membership of a specific concurrent program:

SELECT report_set_id, report_sequence, name FROM apps.so_report_set_lines_v WHERE name = :p_program_name ORDER BY report_set_id, report_sequence;

To audit recent changes:

SELECT report_set_id, report_sequence, name, last_updated_by, last_update_date FROM apps.so_report_set_lines_v WHERE last_update_date >= SYSDATE - 30 ORDER BY last_update_date DESC;

Because the view is read-oriented and exposes no security predicates beyond standard APPS access, it should be queried through a read-only responsibility-supplied account or a custom synonym, and any correction of sequence values must be performed against the SO_REPORT_SET_LINES base table rather than the view.