Results for “unit_of_measure_id”

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

Overview

RG_REPORT_SET_REQUESTS is a transaction-tracking table within the Oracle E-Business Suite Application Report Generator (RG) product, owned by the RG schema. Its documented purpose is to track submissions of report sets. Each row captures which report set was submitted, when the submission occurred, and the user who initiated it. The table additionally records whether the submission originated from the Multiple Report Sets tab in the Run Financial Statements page, a distinction relevant to Financial Statement Generator (FSG) batch reporting workflows.

Because the table records the occurrence of a submission event—linking a report set definition to a point-in-time execution—it functions as an event or association record rather than a pure descriptive entity. Under the heuristic Data Vault classification mined from its foreign-key structure, RG_REPORT_SET_REQUESTS is assessed as satellite-leaning. In a Data Vault model this would suggest positioning it as a satellite attached to a report-set hub, retaining the descriptive submission attributes (dates, period, submitter) while inheriting its identity through the report set reference. This is a modeling suggestion only; the physical implementation is a conventional relational table with a single-column surrogate primary key.

Key Information Stored

The documented physical schema for 12.2.2 contains 10 columns. The most significant are:

• REPORT_SET_REQUEST_ID — the surrogate primary key, enforced by RG_REPORT_SET_REQUESTS_PK and also by the unique index RG_REPORT_SET_REQUESTS_U1. It provides the durable identifier propagated to child detail rows.
• REPORT_SET_ID — identifies the specific report set definition that was submitted. This is the principal business reference and the natural candidate for resolving a submission back to its FSG report set.
• PERIOD_NAME — the accounting period associated with the submission, typically an FSG period such as a month or quarter name.
• ACCOUNTING_DATE — the accounting date used for the reporting run.
• UNIT_OF_MEASURE_ID — a foreign key to FND_CURRENCIES, documented as the only outbound foreign key from this table. It identifies the currency context (unit of measure) applied to the submitted report set.
• Who columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN record the submitting user and the audit trail of the row itself. These support the documented statement that the table stores "who it was submitted by."

The surrogate key is distinct from any business-key candidate: although RG_REPORT_SET_REQUESTS_U1 is a unique index on REPORT_SET_REQUEST_ID, that column remains a system-generated surrogate rather than a user-meaningful natural key. A more semantically meaningful identifier for reporting purposes is the combination of REPORT_SET_ID with PERIOD_NAME and ACCOUNTING_DATE.

Common Use Cases and Queries

The table is primarily queried for audit and reconciliation of report set submissions: identifying which report sets ran in a given period, which users submitted them, and whether a submission came through the Multiple Report Sets batch path.

• Submission audit by period: select REPORT_SET_ID, PERIOD_NAME, CREATED_BY, CREATION_DATE from RG_REPORT_SET_REQUESTS where PERIOD_NAME = :period order by CREATION_DATE desc.
• User activity analysis: aggregate submissions by CREATED_BY to determine report set usage across a financial close cycle.
• Detail expansion: join to RG_REPORT_SET_REQ_DETAILS on REPORT_SET_REQUEST_ID to enumerate the individual reports produced by each submission.
• Currency-context reporting: join UNIT_OF_MEASURE_ID to FND_CURRENCIES to display the currency associated with each submitted report set.
• Duplicate or missed submission checks: compare expected report set submissions against actual rows for a period to detect gaps before period close.

Related Objects

• RG_REPORT_SET_REQ_DETAILS — the primary child table. It references RG_REPORT_SET_REQUESTS via REPORT_SET_REQUEST_ID, carrying the line-level detail of each submission.
• FND_CURRENCIES — referenced through RG_REPORT_SET_REQUESTS.UNIT_OF_MEASURE_ID, supplying the currency or unit-of-measure context.
• RG_REPORT_SET_REQUESTS_PK — the primary key constraint enforcing uniqueness of REPORT_SET_REQUEST_ID.
• RG_REPORT_SET_REQUESTS_U1 — the unique index on REPORT_SET_REQUEST_ID.
• FSG report set definitions — the parent report set identified by REPORT_SET_ID, which governs the content of each tracked submission.

Together these objects support end-to-end traceability from a submitted report set down to its individual generated reports.