Results for “psp_orig_acct_lines_v”

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

Overview

PSP_ORIG_ACCT_LINES_V is a reporting view owned by the APPS schema in Oracle EBS Release 12.1.1 and 12.2.2. It belongs to the PSP (Labor Distribution) product family and is documented as being based on PSP_TEMP_ORIG_SUMLINES. The view exposes summarized original accounting lines generated by the Labor Distribution process, presenting them together with descriptive attributes resolved through the PSP_GENERAL package and the PSP_ELEMENT_GROUPS lookup. Its role is to provide a denormalized, query-friendly projection of labor distribution data for reporting, reconciliation, and integration, without requiring the consumer to call the underlying PL/SQL retrieval functions directly. Users searching for the column expenditure_organization_name will find that this attribute is exposed by this view, making it the primary access point for expenditure organization descriptions on original distribution lines.

Underlying Base Objects

The view is defined over three documented base objects. The primary source is PSP_TEMP_ORIG_SUMLINES, aliased PTOS, which supplies the original summarized expenditure lines including account group, debit/credit indicator, code combination, project, task, award, distribution amount, run, element, and business group context. The second object is PSP_ELEMENT_GROUPS, aliased PEG, joined with an outer join (PEG.ELEMENT_GROUP_ID (+) = NVL(PTOS.ELEMENT_GROUP_ID, -99)) so that element group names are returned when available and rows are not dropped when the element group is null. The third object is the PSP_GENERAL package, invoked in the SELECT list to derive descriptive values. All three are referenced through synonyms visible to APPS. Because the view reads from a temporary staging object, it reflects data produced during a specific labor distribution run rather than a permanent transactional record.

Key Columns

• ACCT_GROUP_ID, DR_CR_FLAG, GL_CODE_COMBINATION_ID – Account grouping, debit/credit indicator, and the GL code combination for the accounting entry.
• PROJECT_ID, PROJECT_NUMBER – Project identifier and its descriptive number, the latter resolved through PSP_GENERAL.GET_PROJECT_NUMBER.
• EXPENDITURE_ORGANIZATION_ID, EXPENDITURE_ORGANIZATION_NAME – The expenditure organization identifier and its display name, with the name derived via PSP_GENERAL.GET_ORG_NAME. The name is returned only when PROJECT_ID is not null.
• EXPENDITURE_TYPE, TASK_ID, TASK_NUMBER, AWARD_ID, AWARD_NUMBER – Expenditure classification plus task and award identifiers and their descriptive numbers.
• DISTRIBUTION_SUM – The summarized distribution amount for the line.
• RUN_ID, BUSINESS_GROUP_ID, SET_OF_BOOKS_ID – Labor distribution run and organizational/ledger context.
• ELEMENT_NAME, ELEMENT_TYPE_ID, ELEMENT_GROUP_NAME, ELEMENT_GROUP_ID – Element and element group information; the element name is resolved for TRUNC(SYSDATE).
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE10 – Descriptive flexfield segments carried from the base line.

Common Use Cases and Queries

Typical uses include verifying the expenditure organization assigned to original labor distribution lines, reconciling distribution sums by project, task, or award, and feeding downstream reporting or integration extracts. A representative query to retrieve expenditure organization names for a given run is:

SELECT run_id, project_number, task_number, expenditure_organization_id, expenditure_organization_name, expenditure_type, distribution_sum FROM apps.psp_orig_acct_lines_v WHERE expenditure_organization_name IS NOT NULL ORDER BY run_id, project_number;

Because the view joins a temporary summary object, queries should be scoped to a specific RUN_ID and executed while the relevant distribution data remains available. Descriptive columns resolved through PSP_GENERAL depend on the current effective dates and project context.