Results for “bis_months_v”
25 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
BIS_MONTHS_V is a VALID Oracle E-Business Suite view owned by the APPS schema within the BIS (Applications BIS) product family. It presents a consolidated listing of accounting periods drawn from the General Ledger period calendar, cross-referenced against the various organizational and legal constructs that are associated with a set of books or ledger. Rather than exposing periods in isolation, the view unions together several distinct "context" identifiers — set of books, organization, legal entity, operating unit, and OPM company — so that each accounting period appears once per applicable reporting context.
This makes BIS_MONTHS_V a central reference point for reporting and integration logic in which a flat, denormalized period list keyed by context is required. The view is commonly used in BIS analytical and reporting flows where period-level data must be joined to an owning organization, ledger, or legal entity. It is a read-only, query-oriented object; no DML is supported against it.
Underlying Base Objects
The view text shows that BIS_MONTHS_V is defined as a UNION of several SELECT statements. The base objects referenced are:
- GL_PERIODS — supplies the period name, period type, period set name, start and end dates, and period year. It is the anchor table for all branches of the union.
- GL_SETS_OF_BOOKS — used in the set of books and organization branches, providing the accounted period type, period set name, and SET_OF_BOOKS_ID used to join to organizations.
- ORG_ORGANIZATION_DEFINITIONS — supplies ORGANIZATION_ID for the organization-context branch, joined via SET_OF_BOOKS_ID.
- GL_LEDGER_LE_V — supplies LEGAL_ENTITY_ID and LEDGER_ID for the legal entity and operating unit branches. This is a key tie-in to the ledger/legal entity model introduced in Release 12.
- HR_OPERATING_UNITS — provides the operating unit (SET_OF_BOOKS_ID) linkage used in the operating unit branch.
- XLE_FIRSTPARTY_INFORMATION_V — supplies the legal entity identifier associated with the first party for operating units.
The joins consistently constrain GL_PERIODS.PERIOD_TYPE to the accounted period type of the set of books or ledger and match PERIOD_SET_NAME across objects, ensuring only valid period/context combinations are returned.
Key Columns
- ID — concatenation of PERIOD_SET_NAME, the '+' delimiter, and PERIOD_NAME. Serves as a unique composite key for each period/context row.
- VALUE — the period name (GL_PERIOD_NAME), suitable for display in list-of-values or reporting.
- PERIOD_SET_NAME — the accounting calendar/period set to which the period belongs.
- PERIOD_NAME — the accounting period (for example, a month such as JAN-24).
- START_DATE / END_DATE — the effective start and end dates of the accounting period.
- PERIOD_YEAR — the fiscal/period year of the period.
- Derived context column — the eighth column returns a TO_CHAR identifier (SET_OF_BOOKS_ID, ORGANIZATION_ID, LEGAL_ENTITY_ID, or a ledger/legal-entity combination), and the ninth column is a literal label indicating the context: 'SET OF BOOKS', 'ORGANIZATION', 'LEGAL ENTITY', 'OPERATING UNIT', or 'OPM COMPANY'.
Common Use Cases and Queries
The view is typically used to populate period selection lists scoped to a given ledger, legal entity, or operating unit, and to align period metadata during data-extract and reporting routines.
- Retrieving all periods for a specific calendar:
SELECT period_name, start_date, end_date, period_year FROM bis_months_v WHERE period_set_name = :p_set AND id LIKE :p_set||'+%'; - Listing periods applicable to a legal entity context:
SELECT period_name FROM bis_months_v WHERE 'LEGAL ENTITY' = ... ;filtered on the eighth context column. - Joining period keys to fact tables that store the composite period identifier.
Because the view folds multiple contexts into a single result set, queries should always filter on the context label column or the PERIOD_SET_NAME to avoid returning duplicate period rows. In Oracle EBS 12.1.1 and 12.2.2 the underlying GL_LEDGER_LE_V and XLE_FIRSTPARTY_INFORMATION_V objects reflect the Release 12 ledger and legal entity architecture, so the view behaves consistently across both releases.
-
View: BIS_MONTHS_V 12.1.1
APPS.BIS_MONTHS_V·↳ FND_PROFILE·↳ GL_LEDGER_LE_V·↳ GL_PERIODS·Explore BIS module →
-
VIEW: APPS.BIS_MONTHS_V 12.1.1
-
View: BIS_MONTHS_V 12.2.2
Not implemented in this database·Explore BIS module →
-
12.1.1 FND Design Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
SYNONYM: APPS.GL_PLCY_MST 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
VIEW: APPS.GL_LEDGER_LE_V 12.1.1
-
SYNONYM: APPS.SY_ORGN_MST 12.1.1
-
SYNONYM: APPS.GL_PERIODS 12.1.1
-
eTRM - XLE Tables and Views 12.1.1
XLE_UNQ_PROFILES stores information about an Unqualified Legal Construct
-
VIEW: APPS.GL_SETS_OF_BOOKS 12.1.1
-
eTRM - XLE Tables and Views 12.1.1
XLE_UNQ_PROFILES stores information about an Unqualified Legal Construct
-
USSGL transaction codes
-
eTRM - BIS Tables and Views 12.1.1
-
12.1.1 DBA Data 12.1.1
-
eTRM - INV Tables and Views 12.1.1
-
USSGL transaction codes
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person
-
eTRM - BIS Tables and Views 12.1.1
-
eTRM - INV Tables and Views 12.1.1
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person