Results for “dangling_gl_rate_flag”

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

Overview

PJI_FM_DNGL_ACT is a table owned by the PJI schema within Oracle E-Business Suite, associated with the Project Intelligence product module, which is documented as obsolete in release 12.1.1 and 12.2.2. The ETRM metadata describes the object simply as an intermediate summarization table, indicating that it serves as a staging or aggregation layer rather than as a transactional or master data entity. Its purpose is to consolidate project-related financial measurements from Project Accounting, General Ledger, and Receivables into a denormalized reporting structure, supporting the analytical calculations performed by Project Intelligence. The table is populated and refreshed by PJI concurrent programs and is not intended for direct end-user maintenance.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is standalone. PJI_FM_DNGL_ACT does not participate in a classic hub, link, or satellite pattern in the documented relationships; no dependent tables reference it, and its single documented foreign key acts only as a lookup to a temporary systems table. The table is therefore best modeled as an independent summarization satellite whose natural grain is the combination of project, task, worker, and period identifiers.

Key Information Stored

The documented physical schema contains 151 columns. The most significant include:

• ROW_ID — the surrogate identifier for each row, documented as a foreign key referencing CS_SYSTEMS_ALL_B_TEMP; it functions as the primary key candidate in the intermediate structure.
• PROJECT_ID, TASK_ID, PROJECT_ORG_ID, PROJECT_ORGANIZATION_ID — business-key candidates establishing the project, task, and organization context of each summary row.
• WORKER_ID — identifies the resource or personnel associated with the summarized amounts.
• GL_PERIOD_NAME, PA_PERIOD_NAME, GL_CALENDAR_ID, PA_CALENDAR_ID, GL_TIME_ID, PA_TIME_ID — period and calendar identifiers aligning General Ledger and Project Accounting time dimensions.
• TXN_CURRENCY_CODE with TXN_REVENUE, TXN_FUNDING, and TXN_AR_INVOICE_AMOUNT — transaction-currency measures retained alongside the project-currency figures.
• PRJ_REVENUE, PRJ_FUNDING, PRJ_UNBILLED_RECEIVABLES, PRJ_UNEARNED_REVENUE — project-currency revenue, funding, and receivables balances.
• POU_REVENUE, POU_FUNDING, GG_REVENUE, GG_FUNDING, GP_REVENUE, GP_FUNDING (with corresponding GG2 and GP2 variants) — parallel measure sets representing different summarization or grouping levels.
• DANGLING_GL_RATE_FLAG, DANGLING_PA_RATE_FLAG, DANGLING_EN_TIME_FLAG, DANGLING_GL_TIME_FLAG, DANGLING_PA_TIME_FLAG — exception flags identifying rows lacking valid exchange rates or time dimension mappings.
• AR_INVOICE_COUNT, INITIAL_FUNDING_COUNT, ADDITIONAL_FUNDING_COUNT, CANCELLED_FUNDING_COUNT — count measures supporting frequency analysis.

Common Use Cases and Queries

Because the table is an intermediate summarization artifact, its principal use is troubleshooting Project Intelligence data quality and reconciling project financial balances. A typical diagnostic query isolates rows flagged with missing exchange rates:

• SELECT PROJECT_ID, TASK_ID, GL_PERIOD_NAME, DANGLING_GL_RATE_FLAG, DANGLING_PA_RATE_FLAG FROM PJI.PJI_FM_DNGL_ACT WHERE DANGLING_GL_RATE_FLAG = 'Y' OR DANGLING_PA_RATE_FLAG = 'Y';
• SELECT PROJECT_ID, GL_PERIOD_NAME, PRJ_REVENUE, PRJ_FUNDING, POU_REVENUE, GG_REVENUE FROM PJI.PJI_FM_DNGL_ACT WHERE PROJECT_ID = :project_id ORDER BY GL_PERIOD_NAME;
• SELECT TXN_CURRENCY_CODE, COUNT(*), SUM(TXN_REVENUE) FROM PJI.PJI_FM_DNGL_ACT GROUP BY TXN_CURRENCY_CODE;

These patterns support reconciliation between the summarized PJI figures and the underlying PA and AR transactions, validation of multi-currency summarization, and auditing of period-mapping completeness before reports are generated.

Related Objects

The documented relationship data identifies one FK target, with additional dependencies implied by the column lineage:

• CS_SYSTEMS_ALL_B_TEMP — referenced by PJI_FM_DNGL_ACT.ROW_ID.
• PA_PROJECTS_ALL / PA_TASKS — source of PROJECT_ID and TASK_ID business keys.
• GL_PERIODS / PA_PERIODS — source of GL_PERIOD_NAME and PA_PERIOD_NAME values.
• RA_CUSTOMER_TRX_ALL — origin of the AR invoice, credit memo, and cash application amounts.
• GL_DAILY_RATES — exchange rate source implicated by the DANGLING_GL_RATE and DANGLING_PA_RATE flags.
• PJI_FM_ACT_SUMMARY and related PJI summarization tables — sibling intermediate structures in the same reporting flow.
• PJI_FM_* concurrent programs — the processes that populate and refresh this table.