Results for “psp_rep_org_grp1_v”

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

Overview

PSP_REP_ORG_GRP1_V is a reporting view within the Oracle E-Business Suite Labor Distribution (PSP) module. It is one of a set of reporting views grouped under the Distribution History by Organization report, which presents the flow of labor distribution amounts against the organizations and accounts that ultimately received them. The view is defined over the distribution history reporting layer and is intended to expose, in a single flattened result set, the account attribution for each distribution line, together with the source that determined that attribution.

The name of the view carries the GRP1 suffix, indicating that it is the first grouping variant in a family of related reporting views built on the same reporting base. Its purpose is to answer the question of which organization account was charged for a given payroll distribution line, distinguishing between a suspense organization account, a default organization account, and an element type account. This distinction is central to Labor Distribution reconciliation, since suspense accounts represent amounts that could not be attributed to a valid charging organization and therefore require clearing.

Underlying Base Objects

The view is documented as being based on the PSP_DISTRIBUTION_LINES_HISTORY table, which is the historical store of distribution lines used by the Distribution History by Organization report. However, the view text operates indirectly: it selects from PSP_REP_DIST_ORG_V, a reporting view built over the distribution history data, and joins that to the organization account definition tables.

The join targets are conditional on the attribution path being reported:

• PSP_ORGANIZATION_ACCOUNTS — joined in the first two UNION ALL branches, once against SUSPENSE_ORG_ACCOUNT_ID and once against DEFAULT_ORG_ACCOUNT_ID, to resolve the organization account identifier to its project, task, award, expenditure organization, expenditure type, and GL code combination attributes.
• PSP_ELEMENT_TYPE_ACCOUNTS — joined in the third UNION ALL branch, where the account is derived from the element type rather than the organization.

Because the view is documented as not implemented in the source ETRM database snapshot, and no base objects are formally registered against it in that metadata, dependencies should be confirmed against the target instance before use in custom reporting.

Key Columns

The view exposes the descriptive columns of a distribution line alongside the resolved account identifier and an ORG_SOURCE discriminator. Principal columns include:

• PERSON_ID, ASSIGNMENT_ID — the worker and assignment to which the distribution amount belongs.
• ELEMENT_TYPE_ID, TIME_PERIOD_ID, PAYROLL_ID — the element, time period, and payroll run context of the distribution.
• DISTRIBUTION_AMOUNT, DISTRIBUTION_DATE, PERIOD_NAME — the distributed amount and its accounting date and period.
• ACCOUNT_ID — the resolved organization account, aliased from SUSPENSE_ORG_ACCOUNT_ID, DEFAULT_ORG_ACCOUNT_ID, or ELEMENT_ACCOUNT_ID depending on the branch.
• ORG_SOURCE — a literal discriminator with values SUSP, DEF, or EL_TYPE, indicating whether the account was taken from the suspense organization account, the default organization account, or the element type account.
• ORGANIZATION_ID, BUSINESS_GROUP_ID, SET_OF_BOOKS_ID — the organization and set of books context of the line.
• PROJECT_ID, TASK_ID, AWARD_ID, EXPENDITURE_ORGANIZATION_ID, EXPENDITURE_TYPE, GL_CODE_COMBINATION_ID — project and GL attributes inherited from the joined account definition.

Common Use Cases and Queries

The most frequent use of this view is to determine how much labor cost landed in suspense organization accounts for a given period, and to identify the population of workers and assignments affected. Because the branches are mutually exclusive by construction — the first requires SUSPENSE_ORG_ACCOUNT_ID to be populated while DEFAULT_ORG_ACCOUNT_ID and ELEMENT_ACCOUNT_ID are null, and so on — the ORG_SOURCE column provides a clean partitioning of the result set.

A representative query isolating suspense attribution follows:

• SELECT person_id, assignment_id, period_name, distribution_amount, account_id, organization_id FROM psp_rep_org_grp1_v WHERE org_source = 'SUSP' AND period_name = :period ORDER BY person_id, assignment_id;

For a reconciliation by GL account, filtering on GL_CODE_COMBINATION_ID and grouping by ORG_SOURCE allows a report to contrast amounts charged through suspense, default, and element type paths within the same period. Joining ACCOUNT_ID back to GL_CODE_COMBINATIONS where a code combination is populated provides the accounting flexfield string for posting-level reconciliation.