Results for “psp_rep_ssp_chg1_v”

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

Overview

PSP_REP_SSP_CHG1_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, belonging to the PSP (Labor Distribution) product family. It is derived from PSP_REP_SSP_CHG_V and exists specifically to support the Suspense Account Charging report, which identifies labor distribution amounts that could not be charged to a valid project, task, award, or expenditure combination and were therefore routed to a suspense organization account. Bug 2209306, corrected on 5-FEB-02 by Ritesh, is documented as the change that produced this revised view text. The view is marked VALID in ETRM 12.2.2 metadata and is available in both 12.1.1 and 12.2.2 environments.

The view serves as a reconciliation-and-correction staging layer. It presents each suspense distribution line alongside both the originally intended charging attributes and the suspense "actual" attributes captured at the moment of distribution, allowing report consumers to see precisely where a cost landed versus where it was meant to land.

Underlying Base Objects

The view is defined over a join of PSP_DISTRIBUTION_LINES_HISTORY (the primary suspense driver, aliased A), PSP_PAYROLL_CONTROLS, PSP_PAYROLL_LINES, PER_ALL_ASSIGNMENTS_F, and HR_ALL_ORGANIZATION_UNITS, plus a set of account-resolution sources: PSP_ORGANIZATION_ACCOUNTS (used twice — once as the suspense account S, once as POD), PSP_ELEMENT_TYPE_ACCOUNTS (PEA), PSP_DEFAULT_LABOR_SCHEDULES (PDLS), and PSP_SCHEDULE_LINES (B). Documented referenced objects additionally include PSP_PAYROLL_SUB_LINES, PSP_ADJUSTMENT_LINES_HISTORY, PSP_PRE_GEN_DIST_LINES_HISTORY, and PER_TIME_PERIODS.

All base objects are referenced through APPS synonyms, consistent with standard EBS view conventions. The driving filter restricts output to rows where SUSPENSE_ORG_ACCOUNT_ID is not null and REVERSAL_ENTRY_FLAG is null, excluding reversals and non-suspense distributions.

Key Columns

• ACTUAL_TASK_ID — the task identifier recorded on the suspense organization account row (S.TASK_ID); the counterpart to the intended TASK_ID resolved via NVL chains.
• ACTUAL_PROJECT_ID, ACTUAL_EXP_ORG_ID, ACTUAL_EXPENDITURE_TYPE, ACTUAL_AWARD_ID, ACTUAL_GL_CCID — the "as-charged" charging attributes persisted on the suspense row.
• PROJECT_ID, TASK_ID, EXPENDITURE_TYPE, AWARD_ID, GL_CODE_COMBINATION_ID, EXPENDITURE_ORGANIZATION_ID — the intended charging attributes, resolved by nested NVL across PSP_SCHEDULE_LINES, PSP_DEFAULT_LABOR_SCHEDULES, PSP_ORGANIZATION_ACCOUNTS, and PSP_ELEMENT_TYPE_ACCOUNTS in that precedence order.
• DISTRIBUTION_AMOUNT — signed via DECODE on DR_CR_FLAG, negating amounts flagged 'C' so that credits and debits present consistently.
• SUSPENSE_ORG_ACCOUNT_ID, SUSPENSE_REASON_CODE, DISTRIBUTION_DATE — the suspense account, the coded reason the charge could not be applied, and the accounting date.
• PAYROLL_ID, TIME_PERIOD_ID, PERSON_ID, ASSIGNMENT_ID, ELEMENT_TYPE_ID, ORGANIZATION_ID — payroll and assignment context for drill-down to the originating run.
• BUSINESS_GROUP_ID, SET_OF_BOOKS_ID, CURRENCY_CODE — ledger and security context.

Common Use Cases and Queries

The principal use case is the Suspense Account Charging report, but the view is equally suitable for ad hoc suspense aging, root-cause analysis, and correction validation. Because it exposes both intended and actual charging attributes, it is the natural source for comparing where labor should have been charged against where it actually landed.

Locating suspense lines for a specific task or assignment:

• SELECT person_id, assignment_id, payroll_id, actual_task_id, task_id, distribution_amount, suspense_reason_code, distribution_date FROM apps.psp_rep_ssp_chg1_v WHERE actual_task_id = :task_id;
• SELECT suspense_org_account_id, suspense_reason_code, COUNT(*), SUM(distribution_amount) FROM apps.psp_rep_ssp_chg1_v WHERE distribution_date BETWEEN :start_date AND :end_date GROUP BY suspense_org_account_id, suspense_reason_code;
• SELECT a.* FROM apps.psp_rep_ssp_chg1_v a WHERE a.task_id IS NULL AND a.actual_task_id IS NOT NULL; — identifies rows where a task was intended but only the suspense task was recorded.

Queries should restrict on PAYROLL_ID, TIME_PERIOD_ID, or DISTRIBUTION_DATE to bound the history-table scan, and joins back to PSP_PAYROLL_LINES or PSP_DISTRIBUTION_LINES_HISTORY can restore full audit context.