Search Results source_distribution_id_num_1

Overview

The PA_GL_COST_XFER_AUDIT_V view in the APPS schema of Oracle E-Business Suite (validated across 12.1.1 and 12.2.2) provides a reconciliation-style audit trail for project cost transfers into Oracle General Ledger. It presents project Cost Distribution Lines alongside their corresponding accounting entries created through Subledger Accounting (XLA) and ultimately posted to the General Ledger. The view answers a recurring audit question: for a given project expenditure item, what General Ledger journal line was generated, in which accounting period, for what amount, and against which account combination.

Because Oracle Projects and Oracle General Ledger are separate ledgers bridged by the SLA transfer process, this view is a critical diagnostic and reporting object. It is primarily used within the Projects module for cost audit by GL account, remediation of transfer failures, and downstream reconciliation reporting. The view is exposed as read-only metadata and is intended for query and reporting rather than transactional processing.

Underlying Base Objects

The view selects from a broad set of base objects spanning Projects, Subledger Accounting, Human Resources, and the General Ledger. Documented referenced objects include PA_PROJECTS_ALL, PA_TASKS, PA_EXPENDITURES, PA_EXPENDITURE_ITEMS_ALL, PA_COST_DISTRIBUTION_LINES_ALL, and PA_IMPLEMENTATIONS_ALL. The Subledger Accounting side is represented by XLA_AE_HEADERS, XLA_AE_LINES, XLA_DISTRIBUTION_LINKS, XLA_ACCT_CLASS_ASSGNS, XLA_ASSIGNMENT_DEFNS_B, and XLA_POST_ACCT_PROGS_B. General Ledger objects referenced include GL_JE_HEADERS, GL_JE_LINES, and GL_IMPORT_REFERENCES. Party and organization information is drawn from PER_PEOPLE_F, HR_ORGANIZATION_UNITS, and supporting packages such as HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY. Linkages and system configuration are referenced through PA_SYSTEM_LINKAGES. The view joins expenditure items to cost distribution lines on EXPENDITURE_ITEM_ID, then links to XLA accounting events and their GL journal entries through the SLA distribution links and code combinations.

Key Columns

• EXPENDITURE_ITEM_ID — the unique identifier linking the audit row to the source project expenditure.
• CDL_LINE_NUM — the Cost Distribution Line sequence in the project cost transfer.
• CODE_COMBINATION_ID — the GL account combination charged by the debit side of the accounting entry.
• CR_CODE_COMBINATION_ID — the corresponding credit-side account combination, resolved dynamically from the SLA distribution links and post-accounting program logic.
• PROJECT_ID / PROJECT_NUMBER — the project identifier and its user-visible number.
• TASK_ID / TASK_NUMBER — the task associated with the expenditure item.
• EXPENDITURE_TYPE, EXPENDITURE_ITEM_DATE — classification and transaction date of the expenditure.
• EMP_OR_ORG_NAME — the entered-by employee or organization name, resolved via HR packages.
• PERIOD_NAME — the accounting period in which the entry resides.
• JE_LINE_NUMBER — the SLA accounting entry line number (AE_LINE_NUM).
• GL_DATE, TRANSFERRED_DATE — the GL accounting date and the date the transfer was processed.
• GL_DR_AMOUNT / GL_CR_AMOUNT — unrounded accounted debit and credit amounts from the SLA distribution links.
• ORG_ID — the operating unit, supporting multi-org security.

Common Use Cases and Queries

A primary use case is reconciling transferred cost distribution lines to their GL journal entries for a given project or period. Because the view filters on CDL.TRANSFER_STATUS_CODE||'' = 'A', only fully transferred (approved/posted) cost lines are returned. A typical query isolates discrepancies between project and GL amounts for a period:

SELECT project_number, task_number, expenditure_item_date,
       period_name, gl_date, gl_dr_amount, gl_cr_amount,
       code_combination_id, cr_code_combination_id
FROM   pa_gl_cost_xfer_audit_v
WHERE  project_number = 'PROJ-1001'
AND    period_name    = 'OCT-2024'
ORDER  BY expenditure_item_date, cdl_line_num;

Auditors frequently join this view to GL_CODE_COMBINATIONS on CODE_COMBINATION_ID to translate the numeric account combination into readable segment values, supporting cost-by-GL-account reporting. Project accountants also use it to investigate transfer failures or duplicate postings by comparing GL_DR_AMOUNT and GL_CR_AMOUNT against the expected distribution. Because the view spans the full chain — Projects, SLA, and GL — it remains a foundational object for cost transfer and GL reconciliation reporting in both EBS 12.1.1 and 12.2.2.