Results for “psp_rep_da_grp1_v”

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

Overview

PSP_REP_DA_GRP1_V is a reporting view within the PSP (Labor Distribution) module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. Its purpose is to consolidate labor distribution records against awards by reconciling several distinct account derivation paths into a single, unioned result set. The view is documented as being based on PSP_REP_DIST_PRJ_V and is used to drive the Distribution History of Employees by Award report. It provides the reporting layer with a normalized projection of person, assignment, element type, time period, payroll, distribution amount, and award/expenditure detail, together with a label identifying the source from which each account was derived.

The view does not store data; it is a read-only construct. In the source environment documented by ETRM, the object is marked "Not implemented in this database," meaning the definition is cataloged for reference but the view is not instantiated in that particular instance. Organizations relying on the Distribution History report must ensure the view exists in the target database before running dependent reports.

Underlying Base Objects

Two categories of objects are referenced. The first is the report distribution view PSP_REP_DIST_PRJ_V, aliased as A, which supplies the core distribution facts: person, assignment, element type, time period, payroll, distribution amount, effective date, period name, and the various account identifiers. The second category comprises the award-mapping objects joined to those accounts, all aliased as B, each contributing AWARD_ID and EXPENDITURE_TYPE:

• PSP_ORGANIZATION_ACCOUNTS — joined twice, once on SUSPENSE_ORG_ACCOUNT_ID and once on DEFAULT_ORG_ACCOUNT_ID, producing AWARD_SOURCE values of 'SUSP' and 'DEF' respectively.
• PSP_ELEMENT_TYPE_ACCOUNTS — joined on ELEMENT_ACCOUNT_ID, producing AWARD_SOURCE 'EL_TYPE'. This branch is the specific source of the term the user searched for.
• PSP_DEFAULT_LABOR_SCHEDULES — joined on ORG_SCHEDULE_ID, producing AWARD_SOURCE 'LABOR'.
• A further branch keyed on SCHEDULE_LINE_ID continues the union, following the same pattern of selecting award and expenditure type metadata.

Documented metadata lists no additional base objects beyond these, and the view owner is not recorded in the provided ETRM extract.

Key Columns

• PERSON_ID, ASSIGNMENT_ID — identify the employee and their assignment for the distribution record.
• ELEMENT_TYPE_ID — the payroll element type to which the distribution relates.
• TIME_PERIOD_ID, PAYROLL_ID, PERIOD_NAME, EFFECTIVE_DATE — the time and payroll context of the distribution.
• DISTRIBUTION_AMOUNT — the monetary value charged for the distribution.
• ACCOUNT_ID — a unified column whose value is drawn from whichever account column the branch selected (suspense, default, element, schedule, or schedule line).
• AWARD_ID, EXPENDITURE_TYPE — the award and expenditure classification resolved through the joined mapping object.
• AWARD_SOURCE — a literal discriminator ('SUSP', 'DEF', 'EL_TYPE', 'LABOR') indicating which derivation path produced the row.
• BUSINESS_GROUP_ID, SET_OF_BOOKS_ID — the operating unit and ledger context.

Common Use Cases and Queries

The primary use case is award-level labor distribution reporting, particularly the Distribution History of Employees by Award report, where AWARD_SOURCE and ACCOUNT_ID drive drill-down and reconciliation. Analysts also query it directly to isolate records by derivation path.

Sample query returning all element-type derived distributions for a person:

• SELECT person_id, assignment_id, element_type_id, period_name, distribution_amount, award_id, expenditure_type
• FROM psp_rep_da_grp1_v
• WHERE award_source = 'EL_TYPE'
• AND person_id = :p_person_id;

Aggregate distribution by award:

• SELECT award_id, award_source, SUM(distribution_amount) total_amt
• FROM psp_rep_da_grp1_v
• GROUP BY award_id, award_source;

Because each source branch is unioned, consumers must anticipate multiple rows per distribution where an account maps through more than one derivation path, and should filter on AWARD_SOURCE when a single perspective is required.