Search Results psp_summary_lines_c_v

Overview

PSP_SUMMARY_LINES_C_V is a reporting view within the Oracle E-Business Suite Labor Distribution (PSP) module. Its functional purpose is narrow and well defined: it exposes only those summary lines that represent credit entries. In labor distribution processing, cost allocations and adjustments flow through summary tables where each row is tagged with a debit/credit indicator. This view pre-filters that data so that downstream reporting, reconciliation, and integration processes can retrieve credit-side records without needing to embed the DR_CR_FLAG predicate in every query.

The view's role is primarily informational and integration-oriented. It does not introduce new logic or aggregation; rather, it presents a consistent, credit-only projection of the header-level summary data. Because it carries identifiers such as GL_CODE_COMBINATION_ID, PROJECT_ID, AWARD_ID, and SET_OF_BOOKS_ID, the view is useful for reconciling labor distribution results against General Ledger, Projects, and Grants accounting. In the 12.1.1 and 12.2.2 releases it behaves as a standard documented ETRM object; per the ETRM metadata it is not implemented as a physical object in the reference database, meaning it is delivered as a view definition only and is created where the Labor Distribution product is installed.

Underlying Base Objects

The view is defined over a single base object: PSP_SUMMARY_LINES, aliased as A in the view text. No additional base tables, joins, or sub-queries are documented. The defining SELECT statement is:

• SELECT SUMMARY_LINE_ID, PERSON_ID, ASSIGNMENT_ID, SOURCE_CODE, SOURCE_TYPE, TIME_PERIOD_ID, INTERFACE_BATCH_NAME BATCH_NAME, SUMMARY_AMOUNT, GL_CODE_COMBINATION_ID, PROJECT_ID, EXPENDITURE_ORGANIZATION_ID, EXPENDITURE_TYPE, TASK_ID, AWARD_ID, BUSINESS_GROUP_ID, SET_OF_BOOKS_ID FROM PSP_SUMMARY_LINES A WHERE A.DR_CR_FLAG = 'C' AND A.STATUS_CODE = 'A'

Two filters define the result set. DR_CR_FLAG = 'C' restricts rows to credit entries, and STATUS_CODE = 'A' restricts rows to active records. The INTERFACE_BATCH_NAME column is exposed under the alias BATCH_NAME. Because the view is a simple single-table projection, performance is effectively that of the base table, and no aggregation occurs. The metadata notes that referenced base objects are not further documented, confirming the direct one-to-one relationship with PSP_SUMMARY_LINES.

Key Columns

The columns exposed by PSPSUMMARYLINESCV mirror the base table, with the credit and active-status filters applied implicitly.

• SUMMARY_LINE_ID — Primary identifier for the summary line; the join key back to the base table and to related distribution detail.
• SUMMARY_AMOUNT — The monetary amount of the credit summary line. This is the column most frequently targeted by the search term "summaryamount," as it drives reconciliation totals.
• PERSON_ID and ASSIGNMENT_ID — Identify the employee and assignment to which the labor distribution credit relates.
• SOURCE_CODE and SOURCE_TYPE — Indicate the originating process or source of the summary line.
• TIME_PERIOD_ID — The time period against which the summarized labor was processed.
• BATCH_NAME — Derived from INTERFACE_BATCH_NAME; identifies the interface batch that produced the line.
• GL_CODE_COMBINATION_ID, SET_OF_BOOKS_ID, BUSINESS_GROUP_ID — Accounting and organizational context for posting to General Ledger.
• PROJECT_ID, TASK_ID, AWARD_ID, EXPENDITUREORGANIZATIONID, EXPENDITURE_TYPE — Project, task, award, and expenditure attributes supporting Projects and Grants integration.

Common Use Cases and Queries

Typical scenarios include reconciling credit labor distribution amounts by period or batch, validating that GL postings balance against debit-side lines, and feeding downstream interfaces that require credits only. Because the view already filters on active credit rows, queries need only add the desired grouping and date predicates.

Sample query for period credit totals:

• SELECT TIME_PERIOD_ID, SUM(SUMMARY_AMOUNT) FROM PSP_SUMMARY_LINES_C_V GROUP BY TIME_PERIOD_ID;

Sample query by batch and employee:

• SELECT BATCH_NAME, PERSON_ID, SUMMARY_AMOUNT FROM PSP_SUMMARY_LINES_C_V WHERE INTERFACE_BATCH_NAME = :batch;

Sample query by GL account to support reconciliation:

• SELECT GL_CODE_COMBINATION_ID, SUM(SUMMARY_AMOUNT) FROM PSP_SUMMARY_LINES_C_V GROUP BY GL_CODE_COMBINATION_ID;

In all cases, the STATUS_CODE and DR_CR_FLAG conditions are inherited from the view definition and should not be duplicated. Analysts requiring both debit and credit records must query PSP_SUMMARY_LINES directly or use a corresponding debit view.