Results for “gl_period_sets”

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

Overview

GL_PERIOD_SETS is a General Ledger reference table in the GL schema that stores accounting calendar (period set) definitions. Each row describes a named period set — for example, a monthly or weekly calendar — that governs how fiscal periods are organized and named for one or more ledgers. Period sets are foundational configuration data in Oracle EBS: they must exist before periods can be generated in GL_PERIODS and before a ledger can be assigned a calendar in GL_SETS_OF_BOOKS. The table is therefore a prerequisite for journal entry, period close, and any process that depends on period status.

From a dimensional modeling perspective, the mined foreign-key structure suggests classifying GL_PERIOD_SETS as a hub: it holds the durable business key PERIOD_SET_NAME, and the surrounding transactional and reference tables (GL_PERIODS, GL_SETS_OF_BOOKS, PA_SUMM_BALANCES, and others) reference it by name rather than owning it. Analysts building a Data Vault or star-schema layer may treat it as the calendar dimension hub, with GL_PERIODS acting as a dependent satellite or detail.

Key Information Stored

GL_PERIOD_SETS contains 16 documented columns. The most significant are:

• PERIOD_SET_ID — surrogate primary key (GL_PERIOD_SETS_PK). Stable internal identifier used by downstream surrogate-key joins.
• PERIOD_SET_NAME — the business name of the calendar, e.g. "Accounting Calendar" or a custom name. This is the business-key candidate (with ZD_EDITION_NAME in GL_PERIOD_SETS_U1) and the column most commonly joined on across EBS.
• DESCRIPTION — free-text description of the period set for user reference.
• SECURITY_FLAG — indicates whether the period set is secured, influencing which users can open or close periods.
• ZD_EDITION_NAME — editioning support column in 12.2.2, part of both unique indexes (GL_PERIOD_SETS_U1, GL_PERIOD_SETS_U2).
• ATTRIBUTE1 through ATTRIBUTE5 — descriptive flexfield segments for site-specific extensions.
• CONTEXT — the DFF context that determines which attribute segments are meaningful.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, which record who created and last modified the row.

The surrogate PERIOD_SET_ID should be reserved for internal joins, while PERIOD_SET_NAME is the join key exposed in most EBS screens, concurrent programs, and third-party references.

Common Use Cases and Queries

Typical reporting scenarios include identifying the calendar attached to a ledger, listing all defined period sets, and joining period definitions to summarize balances by accounting period.

To join ledgers to their calendars:

• SELECT sob.name ledger, sob.period_set_name, sob.accounted_period_type, ps.description FROM gl_sets_of_books sob, gl_period_sets ps WHERE sob.period_set_name = ps.period_set_name;

To find periods belonging to a given set (using GL_PERIODS, which references GL_PERIOD_SETS by PERIOD_SET_NAME):

• SELECT ps.period_set_name, p.period_name, p.start_date, p.end_date FROM gl_period_sets ps, gl_periods p WHERE ps.period_set_name = p.period_set_name AND ps.period_set_name = :set_name ORDER BY p.start_date;

Because several modules — including Payables (PA_SUMM_BALANCES, PA_PROJ_PERIOD_PROFILES), RG_DSS_SYSTEMS, and GL_DATE_PERIOD_MAP — carry PERIOD_SET_NAME, the table is also used to reconcile date-to-period mapping and concurrent schedule definitions. Queries should filter on ZD_EDITION_NAME when working in multi-edition 12.2.2 environments to avoid cross-edition duplicates.

Related Objects

The following objects are the most significant consumers of GL_PERIOD_SETS, joined by PERIOD_SET_NAME unless noted:

• GL_SETS_OF_BOOKS — each ledger references its calendar via PERIOD_SET_NAME.
• GL_PERIODS — stores the actual period names and date ranges belonging to a period set.
• GL_DATE_PERIOD_MAP — maps transaction dates to periods within a set.
• GL_CONCURRENT_SCHEDULES — period-based concurrent schedules reference the set.
• PA_SUMM_BALANCES — Projects summarized balances keyed by PERIOD_SET_NAME.
• PA_PROJ_PERIOD_PROFILES — project period profiles reference the calendar.
• RG_DSS_SYSTEMS — Reporting/DSS configuration referencing the set.

Surrogate-key joins within GL should use GL_PERIOD_SETS.PERIOD_SET_ID; most cross-table integration instead uses the business key PERIOD_SET_NAME, which reinforces the hub classification identified in the metadata.