Results for “pa_postaccounting_debit”

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

Overview

APPS.PA_GL_COST_XFER_AUDIT_V is a reporting view in Oracle E-Business Suite Projects (PA) that exposes the audit trail linking project expenditure items to their corresponding subledger accounting entries and General Ledger postings. It is defined over the Project Costing tables (PA_EXPENDITURE_ITEMS_ALL, PA_COST_DISTRIBUTION_LINES_ALL), the Subledger Accounting (XLA) tables, and selected Projects and HR reference objects. The view's primary function is to reconcile what was distributed on a project cost distribution line against the accounting events generated by the Subledger Accounting engine.

The view is particularly relevant to the accounting program PA_POSTACCOUNTING_DEBIT and its counterpart PA_POSTACCOUNTING_CREDIT, which are referenced directly in the view SQL through XLA_POST_ACCT_PROGS_B. For debit postings, the view derives a corresponding credit code combination by joining back to XLA_AE_LINES and XLA_DISTRIBUTION_LINKS to locate the paired line. This makes the view a convenient single source for examining both sides of a post-accounting transfer without manually joining the XLA tables.

Underlying Base Objects

The documented base objects fall into four groups:

• Project Costing: PA_EXPENDITURE_ITEMS_ALL, PA_COST_DISTRIBUTION_LINES_ALL, PA_EXPENDITURES, PA_PROJECTS_ALL, PA_TASKS, PA_IMPLEMENTATIONS.
• Subledger Accounting: XLA_AE_HEADERS, XLA_AE_LINES, XLA_DISTRIBUTION_LINKS, XLA_POST_ACCT_PROGS_B, XLA_ASSIGNMENT_DEFNS_B, XLA_ACCT_CLASS_ASSGNS.
• Human Resources: HR_ORGANIZATION_UNITS, PER_PEOPLE_F, HR_GENERAL, HR_PERSON_NAME, HR_SECURITY.
• General Ledger: GL_JE_HEADERS, GL_JE_LINES, GL_IMPORT_REFERENCES.

The join logic anchors on expenditure item and cost distribution line, then fans out to XLA distribution links using application_id 275 (Projects) and the distribution identifiers. Only cost distribution lines with a transfer status of 'A' and a populated accounting event are included, ensuring that only posted or transferred cost lines appear in the result set.

Key Columns

• EXPENDITURE_ITEM_ID / CDL_LINE_NUM: Identifiers for the expenditure item and its cost distribution line.
• PROJECT_ID, PROJECT_NUMBER, TASK_ID, TASK_NUMBER: Project and task context for the transaction.
• EXPENDITURE_TYPE, EXPENDITURE_ITEM_DATE: Classification and date of the underlying expenditure.
• EMP_OR_ORG_NAME: Resolved from PER_PEOPLE_F with a fallback to the HR organization name.
• PERIOD_NAME, GL_DATE, TRANSFERRED_DATE: Accounting period, GL date, and the date the line was transferred.
• JE_LINE_NUMBER, CODE_COMBINATION_ID: The accounting entry line and its account combination.
• GL_DR_AMOUNT / GL_CR_AMOUNT: Unrounded accounted debit and credit amounts from XLA_DISTRIBUTION_LINKS.
• CR_CODE_COMBINATION_ID: For PA_POSTACCOUNTING_DEBIT rows, the derived credit account combination looked up from the paired XLA line; for PA_POSTACCOUNTING_CREDIT rows, the credit account itself.
• ORG_ID: Operating unit associated with the expenditure.

Common Use Cases and Queries

SELECT project_number, task_number, expenditure_type,
       period_name, gl_date, je_line_number,
       code_combination_id, cr_code_combination_id,
       gl_dr_amount, gl_cr_amount
FROM   apps.pa_gl_cost_xfer_audit_v
WHERE  period_name = :period
AND    gl_dr_amount IS NOT NULL;

The view is widely used in audit and reconciliation extracts where users need to see both the expenditure item detail and the XLA/GL posting in one row. Because the definition relies on XLA tables, it reflects the subledger accounting model introduced with R12 and is consistent across Oracle EBS 12.1.1 and 12.2.2, subject to standard XLA schema stability.