Results for “show_status”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The GL_LOOKUPS_PERIOD_STATUSES_V view is a General Ledger (GL) dictionary object owned by the APPS schema and carries a VALID status in Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is narrow and highly specific: it exposes the set of lookup codes that describe accounting period closing statuses, presented as a reporting-friendly projection of the underlying lookup data. The view text confirms this role, selecting a lookup code aliased as STATUS_FLAG together with its descriptive meaning aliased as SHOW_STATUS.
The ETRM metadata explicitly flags this object as "10SC ONLY," indicating that it is a specialized dictionary object rather than a general-purpose GL interface view. Despite that limitation, it functions as a lightweight decode aid for developers and report authors who need to translate stored period status codes into human-readable labels without hard-coding lookup values. Because the view resolves the CLOSING_STATUS lookup type directly, it keeps status descriptions synchronized with the application's own lookup maintenance, which is valuable in reporting and integration contexts where period status is validated, displayed, or reconciled.
Underlying Base Objects
The view is defined over a single documented referenced base object: GL_LOOKUPS, itself a view in the APPS schema. The relationship is a simple filtered projection. The defining query joins no additional tables and applies a single predicate restricting the result set to rows where LOOKUP_TYPE = 'CLOSING_STATUS'.
Consequently, GL_LOOKUPS_PERIOD_STATUSES_V inherits all of the filtering, enabled/disabled behavior, and language handling implemented within GL_LOOKUPS. Any change to the CLOSING_STATUS lookup type — adding, disabling, or re-meaning a code — is reflected automatically in this view. This one-to-one dependency means the view adds no storage of its own and imposes no materialized copy; it is a pure query-time construct over the lookup definition.
Key Columns
STATUS_FLAG— Sourced fromGL_LOOKUPS.LOOKUP_CODE. This is the stored code value used to represent a period closing status. It is the column most relevant to the user search term "status_flag," acting as the discriminator for period state.SHOW_STATUS— Sourced fromGL_LOOKUPS.MEANING. Provides the descriptive, user-facing label corresponding to eachSTATUS_FLAG, suitable for display on reports and forms.
No other columns are exposed by the documented view text, so consumers should treat the object as a two-column code/description pair rather than a comprehensive lookup extract.
Common Use Cases and Queries
Typical usage centers on decoding or validating a stored period status value. A reporting query might join the view to a status-bearing column to obtain a readable label, while integration code may validate an incoming STATUS_FLAG against the valid set. A representative query is:
SELECT status_flag, show_status FROM apps.gl_lookups_period_statuses_v ORDER BY status_flag;— enumerates all valid period closing status codes and their meanings.SELECT show_status FROM apps.gl_lookups_period_statuses_v WHERE status_flag = :p_status;— resolves a single status code to its descriptive label.SELECT COUNT(*) FROM apps.gl_lookups_period_statuses_v WHERE status_flag = :p_status;— validates that a supplied status value is a defined closing status.
Because the view is documented as "10SC ONLY," its applicability should be confirmed against the specific EBS configuration before it is adopted in general production reporting.
-
10SC ONLY
APPS.GL_LOOKUPS_PERIOD_STATUSES_V·↳ GL_LOOKUPS·Explore GL module →
-
10SC ONLY
APPS.GL_LOOKUPS_BUDGET_STATUSES_V·↳ GL_LOOKUPS·Explore GL module →
-
Based on GL_LOOKUP_PERIOD_STATUSES_V and GL_PERIOD_STATUSES
APPS.IGI_GL_PERIOD_STATUSES_V·↳ GL_LOOKUPS_PERIOD_STATUSES_V·↳ GL_PERIOD_STATUSES·Explore IGI module →
-
10SC ONLY
APPS.GL_LOOKUPS_PERIOD_STATUSES_V·↳ GL_LOOKUPS·Explore GL module →
-
10SC ONLY
APPS.GL_LOOKUPS_BUDGET_STATUSES_V·↳ GL_LOOKUPS·Explore GL module →
-
View: OKL_PERIOD_STATUSES_UV 12.2.2
APPS.OKL_PERIOD_STATUSES_UV·↳ GL_PERIOD_STATUSES·↳ OKL_ACCOUNTING_UTIL·Explore OKL module →
-
View: GL_PERIOD_STATUSES_V 12.2.2
10SC ONLY
APPS.GL_PERIOD_STATUSES_V·↳ GL_LOOKUPS_PERIOD_STATUSES_V·↳ GL_PERIOD_STATUSES·Explore GL module →
-
View: GL_PERIOD_STATUSES_V 12.1.1
10SC ONLY
APPS.GL_PERIOD_STATUSES_V·↳ GL_LOOKUPS_PERIOD_STATUSES_V·↳ GL_PERIOD_STATUSES·Explore GL module →
-
View: GL_JE_BATCHES_V 12.1.1
APPS.GL_JE_BATCHES_V·↳ FND_USER·↳ GL_JE_BATCHES·↳ GL_LOOKUPS·Explore GL module →
-
View: GL_JE_BATCHES_V 12.2.2
APPS.GL_JE_BATCHES_V·↳ FND_USER·↳ GL_JE_BATCHES·↳ GL_LOOKUPS·Explore GL module →
-
View: GL_BUDGETS_V 12.1.1
10SC ONLY
APPS.GL_BUDGETS_V·↳ GL_BUDGETS·↳ GL_BUDGET_VERSIONS·↳ GL_LEDGERS·Explore GL module →
-
View: GL_BUDGETS_V 12.2.2
10SC ONLY
APPS.GL_BUDGETS_V·↳ GL_BUDGETS·↳ GL_BUDGET_VERSIONS·↳ GL_LEDGERS·Explore GL module →
-
10SC ONLY
APPS.GL_BUDGET_ASSIGNMENT_RANGES_V·↳ GL_BUDGET_ASSIGNMENT_RANGES·↳ GL_LOOKUPS·Explore GL module →
-
View: OKL_PERIOD_STATUSES_UV 12.1.1
APPS.OKL_PERIOD_STATUSES_UV·↳ GL_PERIOD_STATUSES·↳ OKL_ACCOUNTING_UTIL·Explore OKL module →
-
Based on GL_LOOKUP_PERIOD_STATUSES_V and GL_PERIOD_STATUSES
APPS.IGI_GL_PERIOD_STATUSES_V·↳ GL_LOOKUPS_PERIOD_STATUSES_V·↳ GL_PERIOD_STATUSES·Explore IGI module →
-
10SC ONLY
APPS.GL_BUDGET_ASSIGNMENT_RANGES_V·↳ GL_BUDGET_ASSIGNMENT_RANGES·↳ GL_LOOKUPS·Explore GL module →
-
VIEW: APPS.GL_BUDGETS_V 12.2.2
-
VIEW: APPS.GL_BUDGETS_V 12.1.1
-
VIEW: APPS.GL_BUDGETS_V 12.2.2
-
VIEW: APPS.GL_BUDGETS_V 12.1.1
-
VIEW: APPS.GL_JE_BATCHES_V 12.2.2
-
VIEW: APPS.GL_JE_BATCHES_V 12.1.1
-
VIEW: APPS.GL_JE_BATCHES_V 12.1.1
-
VIEW: APPS.GL_JE_BATCHES_V 12.2.2