Results for “ap_inv”

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

Overview

APPS.PA_PROJ_COST_SUBLEDGER_V is a reporting and integration view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that presents project cost subledger accounting information at the expenditure item and cost distribution line level. It consolidates project, task, expenditure, and general ledger accounting data into a single denormalized structure, enabling users to reconcile project costs against their corresponding subledger accounting entries without navigating multiple base tables.

The view plays a central role in Oracle Subledger Accounting (SLA) reporting for Projects. It exposes the linkage between project expenditure items, their cost distribution lines, and the XLA accounting engine outputs, making it suitable for reconciliation reports, cost auditing, and downstream integration extracts. The presence of the XLA base objects (XLA_AE_HEADERS, XLA_AE_LINES, XLA_DISTRIBUTION_LINKS, and others) confirms that the view is designed to surface accounted cost data as processed by the SLA architecture introduced in Release 12.

Although the user search term "ap_prepay" does not directly map to a column or object in this view, prepayment-related transactions can flow into project costs when prepayments are applied and subsequently distributed to projects. The view would surface those costs once they are accounted and linked to project expenditure items, though the prepayment application logic itself resides in the Payables module.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, the view is defined over the following documented base objects (all accessed via synonyms in the APPS schema):

• PA_COST_DISTRIBUTION_LINES_ALL — the core cost distribution lines carrying debit code combinations, GL dates, raw and burdened costs, and transfer status.
• PA_EXPENDITURE_ITEMS_ALL — expenditure item details, including transaction source, expenditure type, task, and system linkage function.
• PA_EXPENDITURE_TYPES — expenditure type and category definitions.
• PA_PROJECTS_ALL and PA_TASKS — project number, name, type, and task identifiers.
• PA_SYSTEM_LINKAGES — system linkage function meanings and manufacturing flags.
• PA_TRANSACTION_SOURCES — source definitions used to determine historical flag treatment.
• PA_IMPLEMENTATIONS_ALL — implementation context.
• GL_CODE_COMBINATIONS and GL_LEDGERS — accounting flexfield and ledger information.
• XLA_ACCT_CLASS_ASSGNS, XLA_AE_HEADERS, XLA_AE_LINES, XLA_ASSIGNMENT_DEFNS_B, XLA_DISTRIBUTION_LINKS, and XLA_POST_ACCT_PROGS_B — Subledger Accounting engine tables linking distribution lines to journal entries and accounting programs.

The view text shows a UNION ALL structure combining distribution lines by debit code combination with a second branch that draws account code combinations through the XLA tables, ensuring both directly accounted and SLA-derived cost lines are captured.

Key Columns

• EXPENDITURE_ITEM_ID — Unique identifier for the project expenditure item.
• COST_DISTRIBUTION_LINE_NUM — Line number on the cost distribution.
• CODE_COMBINATION_ID / ACCOUNT_DESCRIPTION — Accounting flexfield and its description for the debit account.
• GL_DATE — Accounting date of the distribution line.
• PROJECT_ID, PROJECT_NUMBER, PROJECT_NAME, PROJECT_TYPE — Project identification attributes.
• TASK_ID, TASK_NUMBER, TASK_NAME — Task identification attributes.
• EXPENDITURE_CATEGORY, EXPENDITURE_TYPE — Cost classification.
• TOTAL_COST, RAW_COST, BURDEN_COST — Derived cost measures; TOTAL_COST defaults to burdened cost when present, otherwise raw cost.
• SYSTEM_LINKAGE_FUNCTION — Meaning of the source system linkage.
• MFG_RELATED — Project manufacturing flag.
• ORGANIZATION_ID — Organization context for the distribution line.

Common Use Cases and Queries

The view supports project cost reconciliation, subledger-to-GL tie-outs, and cost audit reporting. A typical query retrieves all accounted cost lines for a project within a date range:

• SELECT project_number, task_number, expenditure_type, gl_date, raw_cost, burden_cost, total_cost FROM apps.pa_proj_cost_subl edger_v WHERE project_number = :project AND gl_date BETWEEN :start_date AND :end_date ORDER BY gl_date, expenditure_item_id;

Analysts also use it to total burdened cost by expenditure category, or to join to XLA_AE_LINES for journal drill-down. Its UNION ALL structure makes it reliable for both pre-SLA and SLA-processed cost lines, which is valuable during migration and parallel-run activities.