Results for “so_report_usages”

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

Overview

SO_REPORT_USAGES is a child configuration table in the Oracle Order Entry (OE) module that records the usage assignments of document sets defined in the SO_REPORTS table. Document sets in Oracle EBS Order Management control which reports, pick slips, packing slips, and confirmation documents are printed or transmitted for a given transactional context, and SO_REPORT_USAGES determines the specific usage categories (such as invoice, order acknowledgement, or shipping document) under which each document set is valid. The table is owned by the OE schema and is marked VALID in ETRM 12.1.1 and 12.2.2.

From a dimensional modeling perspective, the heuristic Data Vault classification supplied in the metadata is satellite-leaning. This reflects the table's role as an attribute-bearing extension of the SO_REPORTS reference set: SO_REPORT_USAGES does not introduce a new business entity of its own beyond the usage assignment; instead it qualifies the parent report record. A satellite classification is therefore suggested, with SO_REPORTS acting as the effective hub or reference parent and REPORT_ID serving as the linking foreign key.

Key Information Stored

The table contains eight documented columns. The most significant are:

• REPORT_USAGE_ID — the surrogate primary key, enforced by SO_REPORT_USAGES_PK. This is the value most users search for when the term "report_usage_id" is queried, and it also appears in the unique index SO_REPORT_USAGES_U1.
• REPORT_ID — foreign key to SO_REPORTS.REPORT_ID, identifying the parent document set that the usage applies to. Participates in the composite unique index SO_REPORT_USAGES_U2.
• USAGE_CODE — the business-meaningful usage classification (e.g., invoice, acknowledgement, shipping) assigned to the document set. Combined with REPORT_ID in SO_REPORT_USAGES_U2, it forms the natural business-key candidate.
• CREATION_DATE, CREATED_BY — standard audit columns capturing the row's creation context.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns tracking the most recent modification.

The distinction between the surrogate key (REPORT_USAGE_ID) and the business-key composite (REPORT_ID, USAGE_CODE) is important: the surrogate enforces physical uniqueness, while the composite prevents duplicate usage assignments for the same document set.

Common Use Cases and Queries

Typical scenarios include diagnostic lookups of a specific usage assignment by its primary key, enumeration of all usages for a given document set, and joining to SO_REPORTS to resolve document set names and descriptions.

• Lookup by primary key: SELECT * FROM OE.SO_REPORT_USAGES WHERE REPORT_USAGE_ID = :id;
• Usages for a document set: SELECT r.REPORT_NAME, u.USAGE_CODE FROM OE.SO_REPORT_USAGES u, OE.SO_REPORTS r WHERE u.REPORT_ID = r.REPORT_ID;
• Duplicate or orphan detection around REPORT_ID, given the U2 uniqueness constraint.

Because the table is a configuration object, change audit reporting on CREATED_BY / LAST_UPDATED_BY is also common during Order Management setup reviews.

Related Objects

• SO_REPORTS — parent table joined via SO_REPORT_USAGES.REPORT_ID = SO_REPORTS.REPORT_ID.
• SO_REPORT_USAGES_PK — primary key index on REPORT_USAGE_ID.
• SO_REPORT_USAGES_U1 — unique index on REPORT_USAGE_ID.
• SO_REPORT_USAGES_U2 — composite unique index on REPORT_ID, USAGE_CODE.
• OE Order Management Setup APIs — document set definition and printing flows that read these usages.