Results for “gl_dss_program_type”

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

Overview

APPS.RG_DSS_REQUESTS_V is a reporting and integration view within the Oracle E-Business Suite General Ledger data summarization (DSS) subsystem. It presents the operational state of balance extraction and load requests managed by the RG_DSS_REQUESTS table, enriched with descriptive attributes resolved through outer joins to ledgers, chart of accounts, hierarchies, budget versions, encumbrance types, and summary templates. Rather than returning raw coded identifiers, the view decodes lookup values into human-readable meanings, making it directly usable by concurrent programs, reporting tools, and integration interfaces that monitor or consume GL summarization activity. The view is owned by APPS and is available in both 12.1.1 and 12.2.2; the documented metadata is aligned to the 12.2.2 ETRM repository.

Underlying Base Objects

The view is defined primarily over RG_DSS_REQUESTS (aliased RR), which supplies the transactional request records. Each foreign key is resolved through an outer join so that requests remain visible even when their referenced definition is absent or unassigned. The documented base objects are:

• FND_ID_FLEX_STRUCTURES_TL (SYNONYM) — resolves CHART_OF_ACCOUNTS_ID to the key flexfield structure name, restricted to APPLICATION_ID = 101 and ID_FLEX_CODE = 'GL#', with LANGUAGE set to USERENV('LANG').
• GL_LEDGERS (SYNONYM) — resolves LEDGER_ID to the ledger NAME.
• GL_BUDGET_VERSIONS (SYNONYM) — resolves BUDGET_VERSION_ID to the budget name.
• GL_ENCUMBRANCE_TYPES (SYNONYM) — resolves ENCUMBRANCE_TYPE_ID to the encumbrance type.
• GL_SUMMARY_TEMPLATES (SYNONYM) — resolves TEMPLATE_ID to the template name.
• RG_DSS_HIERARCHIES (SYNONYM) — resolves HIERARCHY_ID to the hierarchy name.
• GL_LOOKUPS (VIEW) — joined twice; LK1 decodes PROGRAM_TYPE using lookup type GL_DSS_PROGRAM_TYPE, and LK2 decodes BALANCE_TYPE using lookup type GL_DSS_BALANCE_TYPE.

Key Columns

The view exposes request identifiers, status, and diagnostic columns alongside decoded descriptive attributes. PROGRAM_TYPE and its derived PROGRAM_NAME indicate the summarization program that generated the request. REQUEST_ID and CONCURRENT_REQUEST_ID link the record to the originating concurrent request. STATUS_FLAG reports processing state, while FILE_SPEC, EXTRACTION_START_DATE, EXTRACTION_END_DATE, LOAD_START_DATE, and LOAD_END_DATE describe the extraction and load window. CHART_OF_ACCOUNTS_ID / CHART_OF_ACCOUNTS_NAME, LEDGER_ID / LEDGER_NAME, HIERARCHY_ID / HIERARCHY_NAME, and TEMPLATE_ID / TEMPLATE_NAME provide the accounting context. FROM_PERIOD and TO_PERIOD define the summarized range. BALANCE_TYPE is the critical discriminator decoded by GL_DSS_BALANCE_TYPE into BALANCE_MEANING; the derived BUDGET_ENC_NAME returns the budget name for balance types 'B' and 'C' and the encumbrance type for 'E'. BUDGET_VERSION_ID and ENCUMBRANCE_TYPE_ID carry the underlying identifiers. PERIOD_YEAR, DAY_OF_PERIOD, and standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) complete the record.

Common Use Cases and Queries

Typical consumers use this view to audit or trigger GL balance summarization runs, verify completed loads, and reconcile balance types. A query filtered by the GL_DSS_BALANCE_TYPE lookup is common:

• SELECT request_id, ledger_name, balance_type, balance_meaning, from_period, to_period FROM apps.rg_dss_requests_v WHERE balance_type = 'B';
• SELECT request_id, ledger_name, balance_meaning, budget_enc_name, status_flag FROM apps.rg_dss_requests_v WHERE status_flag = 'C';
• SELECT request_id, program_name, hierarchy_name, template_name, period_year FROM apps.rg_dss_requests_v WHERE ledger_id = :p_ledger_id ORDER BY creation_date DESC;

Because the lookup joins use outer joins, records with an unassigned balance type still appear, but BALANCE_MEANING will be null; queries should therefore not rely on the decoded column to filter out incomplete rows.