Results for “so_report_set_lines”

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

Overview

The SO_REPORT_SET_LINES table is a core configuration object within the Oracle Order Entry (OE) module of Oracle E-Business Suite, owned by the OE schema. It holds the individual "document set lines" that define the ordered composition of a document set — that is, the sequence of individual reports (documents) that must be produced when an Order Management document set is processed. Document sets are used heavily in order entry and order fulfillment workflows to control which printable outputs (order acknowledgements, pick slips, packing slips, invoices, etc.) are generated together and in which order.

From a heuristic Data Vault modeling standpoint, the mined foreign-key structure classifies SO_REPORT_SET_LINES as a link entity. This suggestion reflects its role as an associative table connecting a parent document set (SO_REPORT_SETS) to an individual report definition (SO_REPORTS), with the relationship itself (the sequence and its descriptive attributes) carrying meaning.

Key Information Stored

The table contains 26 documented columns. The most significant are the identifying and relational columns and the standard EBS audit columns.

• REPORT_SET_LINE_ID — the surrogate primary key (SO_REPORT_SET_LINES_PK), uniquely identifying each line.
• REPORT_SET_ID — foreign key to SO_REPORT_SETS, identifying the parent document set to which the line belongs.
• REPORT_ID — foreign key to SO_REPORTS, identifying the specific report/document attached to the set.
• REPORT_SEQUENCE — the positional order of the report within the set; this is a business-key column that governs output ordering.
• APPLICATION_ID — identifies the owning application for the report line, supporting multi-application report definitions.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS descriptive flexfield columns, allowing extensible, customer-defined attributes.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard "who/when" audit columns present on nearly every EBS transactional and setup table.

Two unique indexes are documented. The user's search term, so_report_set_lines_uk1, corresponds to the unique key constraint SO_REPORT_SET_LINES_UK1, defined on (REPORT_SET_ID, REPORT_SEQUENCE). This enforces that no two lines within the same document set may share the same sequence number, guaranteeing a deterministic ordering. A second unique index, SO_REPORT_SET_LINES_U1, is defined on the surrogate key REPORT_SET_LINE_ID.

Common Use Cases and Queries

Typical usage centers on documenting and reporting the composition of document sets and diagnosing ordering or output problems.

• Listing all reports in a given set, in sequence: SELECT REPORT_SET_ID, REPORT_ID, REPORT_SEQUENCE FROM OE.SO_REPORT_SET_LINES WHERE REPORT_SET_ID = :set_id ORDER BY REPORT_SEQUENCE;
• Finding which sets contain a particular report: SELECT REPORT_SET_ID FROM OE.SO_REPORT_SET_LINES WHERE REPORT_ID = :report_id;
• Detecting sequence conflicts, which the UK1 constraint prevents: SELECT REPORT_SET_ID, REPORT_SEQUENCE, COUNT(*) FROM OE.SO_REPORT_SET_LINES GROUP BY REPORT_SET_ID, REPORT_SEQUENCE HAVING COUNT(*) > 1;
• Auditing recent configuration changes via the audit columns.

Because the columns are configuration, direct DML is generally discouraged; changes are typically made through Order Management setup or the concurrent/administrative programs that maintain document sets.

Related Objects

• SO_REPORT_SETS — parent table; joined on SO_REPORT_SET_LINES.REPORT_SET_ID = SO_REPORT_SETS.REPORT_SET_ID.
• SO_REPORTS — referenced table; joined on SO_REPORT_SET_LINES.REPORT_ID = SO_REPORTS.REPORT_ID.
• SO_REPORT_SET_LINES_PK — primary key constraint on REPORT_SET_LINE_ID.
• SO_REPORT_SET_LINES_UK1 — unique constraint on (REPORT_SET_ID, REPORT_SEQUENCE).
• Order Management document set generation programs, which read these lines to determine report execution order and content.