Search Results pay_gl_interface




Overview
Explore in AI Chat

Overview

PAY_GL_INTERFACE is an Oracle E-Business Suite payroll table owned by the HR schema in the PAY (Payroll) product. As stated in the Oracle ETRM metadata (validated across releases 12.1.1 and 12.2.2), its purpose is to hold "costed details to be passed to the General Ledger." In practice, this table acts as the cost-transfer staging area: after payroll costing is run, the resulting debit and credit amounts associated with assignment-level actions are written here so that the Oracle Payroll Transfer to General Ledger process (or its cost-transfer concurrent programs) can post the accounting entries into Oracle General Ledger via the GL interface (GL_INTERFACE / GL_JE_HEADERS).

From a Data Vault modeling perspective, the mined heuristic classification is standalone. This suggests that PAY_GL_INTERFACE is best modeled as an independent table that carries its own transactional grain (one row per costed payroll action) rather than participating in a strict hub-link-satellite chain enforced purely by the documented foreign keys. Its foreign keys to PAY_ASSIGNMENT_ACTIONS and PAY_COST_ALLOCATION_KEYFLEX do, however, provide natural link points to assignment-action and cost-allocation-keyflex hubs if a formal Data Vault design were applied.

Key Information Stored

The documented physical schema (ETRM 12.2.2) exposes seven columns. The most significant are:

  • ASSIGNMENT_ACTION_ID — Foreign key to PAY_ASSIGNMENT_ACTIONS. Identifies the specific assignment action (e.g., payroll run processing for an employee assignment) that generated the costed entry. This is a principal business-key candidate for joining back to payroll results.
  • RUN_PAYROLL_ACTION_ID — References the parent payroll run action. Ties the costed line to the overall payroll run that produced it, supporting reconciliation of run-to-run cost totals.
  • COST_ALLOCATION_KEYFLEX_ID — Foreign key to PAY_COST_ALLOCATION_KEYFLEX. Points to the cost allocation flexfield combination (the accounting distribution used to charge the cost to the correct GL account, cost center, and so forth).
  • CURRENCY_CODE — The currency in which the entered debit and credit amounts are expressed.
  • ENTERED_DR — The entered debit amount for the costed line.
  • ENTERED_CR — The entered credit amount for the costed line.
  • ACCOUNTING_DATE — The accounting date to which these payroll costs should be posted in the General Ledger period.

Because the ETRM metadata documents no explicit surrogate primary key for this table, the practical business key is the combination of the assignment action, cost allocation keyflex, and accounting date context. Database DBAs should note that the documented schema lists seven columns; additional columns may exist in specific patch levels, so reference the actual DDL of HR.PAY_GL_INTERFACE before building persistent queries.

Common Use Cases and Queries

Typical scenarios for PAY_GL_INTERFACE include auditing the payroll cost transfer, reconciling payroll costs to general ledger balances, and debugging discrepancies between costed payroll and posted GL entries.

A representative join to retrieve costed amounts with their source payroll action:

  • SELECT g.ASSIGNMENT_ACTION_ID, g.RUN_PAYROLL_ACTION_ID, g.COST_ALLOCATION_KEYFLEX_ID, g.CURRENCY_CODE, g.ENTERED_DR, g.ENTERED_CR, g.ACCOUNTING_DATE FROM PAY_GL_INTERFACE g WHERE g.ACCOUNTING_DATE BETWEEN :start_date AND :end_date;

To reconcile the amounts against the originating assignment action, join to PAY_ASSIGNMENT_ACTIONS on ASSIGNMENT_ACTION_ID. To validate that each costed row maps to a valid allocation flexfield, join to PAY_COST_ALLOCATION_KEYFLEX on COST_ALLOCATION_KEYFLEX_ID. Reporting extracts commonly sum ENTERED_DR and ENTERED_CR by COST_ALLOCATION_KEYFLEX_ID and ACCOUNTING_DATE to produce period cost summaries for finance.

Related Objects

The most significant related objects, grounded in the documented foreign keys, are:

  • PAY_ASSIGNMENT_ACTIONS — Referenced through ASSIGNMENT_ACTION_ID; the source of the assignment-level payroll action that produced each costed line.
  • PAY_COST_ALLOCATION_KEYFLEX — Referenced through COST_ALLOCATION_KEYFLEX_ID; supplies the accounting distribution for the costed entry.
  • GL_INTERFACE / GL_JE_HEADERS / GL_JE_LINES — Downstream General Ledger objects that receive the posted cost entries generated from this staging table.
  • PAY_PAYROLL_ACTIONS — Provides the payroll run context associated with RUN_PAYROLL_ACTION_ID.
  • PAY_RUN_RESULTS — The source payroll run results whose costs are ultimately transferred through this interface.

Together, these objects form the payroll costing-to-GL pipeline in Oracle Payroll.