Search Results gl_periods




Overview
Explore in AI Chat

Overview

BIS_QUARTERS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, catalogued under the BIS (Applications BIS) product family. It exposes calendar quarter period definitions drawn from the General Ledger period infrastructure and enriches them with the various organizational entities that are associated with each quarter through the accounting flexfield structures. The view is commonly encountered during reporting and integration work involving period-based hierarchies, because it presents a single, denormalized source that links GL period sets to set of books, organizations, legal entities, operating units, and process manufacturing companies.

The view is especially relevant to users investigating GL_PERIODS, as it is defined directly over that table and filters exclusively on PERIOD_TYPE = 'QUARTER'. Its role is to answer the practical question: "For a given period set and quarter name, which accounting and organizational entities are valid?" This makes it useful as a lookup source for parameter lists, LOVs, and cross-entity reporting.

Underlying Base Objects

Although documented ETRM metadata lists no referenced base objects, the view text reveals its actual dependencies. The primary table is GL_PERIODS, from which the calendar dates, year, period name, and period set name are sourced. This is then joined or combined through UNION operations with several other objects:

The UNION structure is significant: each branch returns the same column shape but a different "entity type" value in the second-to-last column. This allows a single query against the view to surface all entity associations for a quarter, rather than requiring multiple joins.

Key Columns

  • ID — a concatenation of PERIOD_SET_NAME || '+' || PERIOD_NAME, providing a unique surrogate key across the UNION branches.
  • VALUE — the period name, typically used as the display value in flexfield or LOV lookups.
  • PERIOD_SET_NAME — the accounting period set to which the quarter belongs.
  • PERIOD_NAME — the quarter designation (for example, a quarterly period name).
  • START_DATE, END_DATE — the quarter's effective date boundaries.
  • PERIOD_YEAR — the fiscal year to which the quarter is assigned.
  • The entity identifier column (unnamed in the excerpt) — holds a set of books ID, organization ID, legal entity ID, operating unit context, or OPM organization code.
  • The entity type column — one of the literals SET OF BOOKS, ORGANIZATION, LEGAL ENTITY, OPERATING UNIT, or OPM COMPANY, identifying what the preceding column represents.

Common Use Cases and Queries

Typical uses include resolving which entities share a quarter period, driving period-selection LOVs, and validating period-to-entity mappings during data conversion or reconciliation.

To list all quarters for a specific period set:

SELECT DISTINCT period_set_name, period_name, start_date, end_date
FROM   apps.bis_quarters_v
WHERE  period_set_name = :p_period_set
ORDER BY start_date;

To find all entities associated with a given quarter:

SELECT id, value, period_year
FROM   apps.bis_quarters_v
WHERE  period_set_name = :p_period_set
AND    period_name = :p_period_name;

Because the view unions multiple entity sources, queries should account for potential duplicate period rows distinguished only by entity identifier and entity type. Filtering on the entity type literal narrows results to a specific organizational dimension.