Results for “warning_code”

50+ results




Overview
Explore in AI Chat

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

Overview

PA_GL_INTERFACE is a Projects (PA) module interface table that serves as the staging and hand-off mechanism between Oracle Projects and the Oracle General Ledger Journal Import process. It is owned by the PA schema and is classified as VALID in the EBS 12.1.1 / 12.2.2 data dictionary. Its functional purpose is to hold Labor Cost records that must be transferred to General Ledger, and it is referenced both by the GL Journal Import concurrent program and by the PA Tieback process, which reconciles and updates transferred records after GL processing completes.

From a dimensional modeling perspective, the heuristic Data Vault classification for PA_GL_INTERFACE is standalone, based on its foreign key structure. This suggests that the table is not normative as a hub, link, or satellite in a Data Vault sense; rather, it behaves as an operational staging or transaction table whose relationships are expressed through denormalized accounting flexfield segments and GL identifiers rather than through a normalized parent-child key hierarchy. Modelers should treat it as a transient interface entity rather than a durable master or reference dataset.

Key Information Stored

PA_GL_INTERFACE contains 128 documented columns (12.2.2 schema). The most operationally significant columns fall into several groups:

The ETRM metadata does not document a surrogate primary key for this table, and no unique index is listed. Business-key candidates would typically be the combination of GROUP_ID, REQUEST_ID, JE_HEADER_ID, and JE_LINE_NUM, but these are not formally declared as unique constraints in the provided metadata. Foreign key relationships exist to GL_ENCUMBRANCE_TYPES via ENCUMBRANCE_TYPE_ID and to GL_MGT_SEG_UPGRADE_H via CHART_OF_ACCOUNTS_ID.

Common Use Cases and Queries

The primary use case is diagnostic and reconciliation reporting around the Projects-to-GL labor cost transfer. Common scenarios include verifying that all labor cost rows reached GL, investigating rows that remain unposted, and analyzing conversion or warning conditions.

A typical reconciliation query filters by status and period:

  • SELECT STATUS, STATUS_DESCRIPTION, COUNT(*), SUM(ACCOUNTED_DR), SUM(ACCOUNTED_CR) FROM PA_GL_INTERFACE WHERE PERIOD_NAME = :period AND SET_OF_BOOKS_ID = :sob GROUP BY STATUS, STATUS_DESCRIPTION;
  • SELECT JE_HEADER_ID, JE_LINE_NUM, STATUS, WARNING_CODE, DATE_CREATED_IN_GL FROM PA_GL_INTERFACE WHERE GROUP_ID = :group_id;
  • SELECT SEGMENT1, SEGMENT2, SEGMENT3, CODE_COMBINATION_ID, ENTERED_DR, ENTERED_CR FROM PA_GL_INTERFACE WHERE REQUEST_ID = :request_id;

These queries are useful during period close, when Project Accounting and GL accountants must confirm that labor distribution has been fully accounted and posted before the period is closed.

Related Objects

PA_GL_INTERFACE sits within a defined set of related EBS objects:

  • GL_ENCUMBRANCE_TYPES — joined via ENCUMBRANCE_TYPE_ID to classify encumbrance entries.
  • GL_MGT_SEG_UPGRADE_H — joined via CHART_OF_ACCOUNTS_ID to resolve chart of accounts context.
  • GL_JE_BATCHES / GL_JE_HEADERS / GL_JE_LINES — populated through GL Journal Import using JE_BATCH_ID, JE_HEADER_ID, and JE_LINE_NUM as linkage keys.
  • GL_CODE_COMBINATIONS — referenced through CODE_COMBINATION_ID for the validated account combination.
  • PA_GL_INTERFACE controls — the PA Tieback process and the GL Journal Import concurrent program are the principal consumers that update STATUS, WARNING_CODE, and DATE_CREATED_IN_GL.

Together these relationships explain how PA_GL_INTERFACE functions as a controlled staging table that bridges Projects labor cost processing and General Ledger posting.