Search Results xtd_periodicity

Overview

BSC.BSC_RPT_KEYS is a global temporary table owned by the BSC schema within Oracle E-Business Suite, registered in the FND Design Data repository as BSC.BSC_RPT_KEYS and confirmed with a status of VALID. It functions as a transient staging structure used during report generation and period-resolution routines in the Oracle Enterprise Trade Management (ETRM) modules running on Oracle EBS 12.1.1 and 12.2.2.

The table is defined as a global temporary table with a data duration of SYS$TRANSACTION. Rows inserted by one session are visible only to that session, and the data is purged automatically at transaction commit or rollback. This behavior makes the table unsuitable for persistent storage and confirms its intended role as an intermediate work area for concurrent, session-scoped report processing.

Under the heuristic Data Vault classification supplied in the metadata, BSC_RPT_KEYS is recorded as standalone. The sole foreign key relationship identified, PERIODICITY_ID → BSC.BSC_SYS_PERIODICITIES, is not sufficient to classify the table as a conventional link. In a Data Vault modeling sense, this object is best treated as a transient or session-scoped satellite-like structure that captures period and periodicity context assembled at run time rather than a persistent hub or link.

Key Information Stored

The table contains thirteen documented columns. The most significant are listed below.

• SESSION_ID — Numeric identifier isolating the rows of a single concurrent session, consistent with the global temporary table semantics.
• REPORT_DATE — The effective date on which the report or period expansion is anchored.
• XTD_PERIOD — The extended period number derived from the reporting date.
• XTD_YEAR — The extended fiscal or calendar year associated with the reporting date.
• XTD_PERIODICITY — The periodicity value resolved in the extended (XTD) context; this is the field most commonly searched when users investigate periodicity handling, and it is distinct from the foreign-key column below.
• PERIOD and YEAR — The base period and year values.
• PERIOD_TYPE_ID — Reference to the period type governing the reporting period.
• PERIODICITY_ID — Foreign key to BSC.BSC_SYS_PERIODICITIES, defining the recurrence interval.
• PERIOD_FLAG — Indicator controlling how the period is interpreted during processing.
• DAY_COUNT — Number of days represented by the resolved period.
• ROLLING_FLAG — VARCHAR2(40) marker indicating whether the period rolls forward.
• LAST_UPDATE_DATE — Standard EBS audit column recording the last modification timestamp.

No surrogate primary key is documented, and no unique index columns are listed in the metadata. The combination of SESSION_ID, REPORT_DATE, and PERIODICITY_ID constitutes the most plausible business-key candidate for row disambiguation within a session.

Common Use Cases and Queries

The primary use case is the derivation of report period keys from a supplied reporting date and periodicity. A query pattern typical of diagnostics for the xtd_periodicity search term is:

• SELECT SESSION_ID, REPORT_DATE, XTD_PERIOD, XTD_YEAR, XTD_PERIODICITY, PERIODICITY_ID FROM BSC.BSC_RPT_KEYS;
• Filtering by session to inspect a single concurrent request: WHERE SESSION_ID = :session_id.
• Joining to BSC_SYS_PERIODICITIES on PERIODICITY_ID to translate the identifier into a descriptive periodicity name.
• Reconciling XTD_PERIODICITY against PERIODICITY_ID to validate that the extended and stored periodicity values agree.

Because the table is transaction-scoped, queries are meaningful only within the originating session; after commit the data is removed.

Related Objects

The documented dependency data identifies one referencing object and one referenced object.

• BSC.BSC_SYS_PERIODICITIES — Referenced through PERIODICITY_ID; provides periodicity definitions.
• APPS.BSC_RPT_KEYS — The APPS-layer synonym pointing to this table, used by report and concurrent program logic.

Additional consumers, such as period-expansion views and ETRM reporting packages, operate indirectly through the APPS synonym. Administrators should verify that any such objects pass a valid SESSION_ID, since cross-session visibility of BSC_RPT_KEYS rows is not supported by the global temporary table design.