Search Results mfg_related

Overview

The PA_PROJ_COST_SUBLEDGER_V view in the APPS schema provides a consolidated, project-centric presentation of cost subledger activity across Oracle Projects. It exposes project cost distribution lines together with the descriptive attributes of the expenditure item, project, task, expenditure type, and GL account that gave rise to each cost. The view is documented under the PA - Projects product family in ETRM for both Oracle EBS 12.1.1 and 12.2.2, and its stated purpose is to present project costs including manufacturing costs, reflected in the MFG_RELATED column drawn from PA_SYSTEM_LINKAGES.PROJECT_MANUFACTURING_FLAG.

For reporting and integration purposes the view is significant because it joins transactional cost data held in PA_COST_DISTRIBUTION_LINES_ALL to the descriptive master data required to render meaningful cost reports without requiring downstream consumers to reconstruct a complex join chain. It surfaces the raw cost, burdened cost, and derived burden cost per distribution line, along with the GL date and the accounting code combination, making it a useful source for reconciliation of project costs against Oracle Subledger Accounting and General Ledger postings.

Underlying Base Objects

The view is defined over both Oracle Projects and Oracle Subledger Accounting base objects. The documented referenced base objects in ETRM 12.2.2 are:

• GL_CODE_COMBINATIONS, GL_LEDGERS — account description and ledger context.
• PA_COST_DISTRIBUTION_LINES_ALL — the core cost distribution lines, including raw and burdened cost amounts, GL date, and transfer status.
• PA_EXPENDITURE_ITEMS_ALL — the expenditure items (the source transaction lines) linked to each distribution line.
• PA_EXPENDITURE_TYPES — expenditure category and expenditure type.
• PA_IMPLEMENTATIONS_ALL — implementation/business group context.
• PA_PROJECTS_ALL, PA_TASKS — project number, name, type, and task attributes.
• PA_SYSTEM_LINKAGES — system linkage function and manufacturing flag.
• PA_TRANSACTION_SOURCES — transaction source attributes, notably the predefined flag.
• XLA_AE_HEADERS, XLA_AE_LINES, XLA_ACCT_CLASS_ASSGNS, XLA_ASSIGNMENT_DEFNS_B, XLA_DISTRIBUTION_LINKS, XLA_POST_ACCT_PROGS_B — Subledger Accounting tables that supply the accounting header, line, and assignment information used to identify and value the accounting events for the cost lines.

Per the documented view text, distribution lines are restricted to those with LINE_TYPE = 'R' and TRANSFER_STATUS_CODE in ('A','V') where the accounting event ID is null, i.e. lines that have been transferred or are eligible for transfer but not yet accounted. A UNION ALL combines the project system-linkage branch with an SLA-driven branch that retrieves the code combination via XLA_ACCT_LINES (referenced as AEL), so the view resolves both pre-SLA and SLA-derived cost lines.

Key Columns

• EXPENDITURE_ITEM_ID — foreign key to the expenditure item that produced the cost.
• COST_DISTRIBUTION_LINE_NUM — the line number of the cost distribution line.
• CODE_COMBINATION_ID — the accounting flexfield combination for the debit side.
• ACCOUNT_DESCRIPTION — descriptive text of the code combination from GL_CODE_COMBINATIONS.
• GL_DATE — the GL date assigned to the distribution line.
• MFG_RELATED — flag indicating whether the cost is related to project manufacturing.
• SYSTEM_LINKAGE_FUNCTION — the meaning of the system linkage function, describing the source system that originated the cost.
• EXPENDITURE_CATEGORY, EXPENDITURE_TYPE — classification of the cost.
• ORGANIZATION_ID — the operating unit (ORG_ID) for the distribution line.
• PROJECT_ID, PROJECT_NUMBER, PROJECT_NAME, PROJECT_TYPE — project identification and classification.
• TASK_ID, TASK_NUMBER, TASK_NAME — task identification.
• TOTAL_COST, RAW_COST, BURDEN_COST — computed cost amount columns; TOTAL_COST returns burdened cost where present, otherwise raw cost; BURDEN_COST is the difference between the two.

Common Use Cases and Queries

Typical uses include project cost reporting, burden analysis, and reconciliation between Oracle Projects cost distributions and GL balances. A common query is to aggregate costs by project, task, and expenditure type:

• SELECT project_number, task_number, expenditure_type, SUM(raw_cost), SUM(total_cost), SUM(burden_cost) FROM pa_proj_cost_subl edger_v GROUP BY project_number, task_number, expenditure_type;
• Filtering by MFG_RELATED = 'Y' isolates manufacturing-related costs, supporting the view's documented emphasis on manufacturing costs.
• Filtering on GL_DATE and ORGANIZATION_ID supports period-end reconciliation against subledger accounting entries.

Because the view is defined over large transactional tables such as PA_COST_DISTRIBUTION_LINES_ALL and the XLA tables, queries should be constrained by project, organization, or GL date range and avoid unbounded full scans. All object names referenced here are in the APPS schema and are exposed as synonyms per the documented metadata for Oracle EBS 12.2.2.