Results for “pspbv_adjustment_approvers”

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

Overview

PSPBV_ADJUSTMENT_APPROVERS is a read-only reporting view within the Oracle E-Business Suite Labor Distribution module (product code PSP). It exposes approval-related information for distribution adjustments — the batch-level records that control how labor costs are redistributed across accounts, projects, and awards. Specifically, the view surfaces the identity of the approver, the batch being acted upon, the stated reason for the adjustment, and the associated free-text comments entered during the approval workflow.

The view is defined with a WITH READ ONLY clause, confirming that its purpose is exclusively inquiry and reporting. It plays a supporting role in Labor Distribution reporting and integration: rather than requiring report authors or interface developers to join directly against the base control table and resolve the approver identifier to a person, the view presents the approval attributes in a denormalized, query-friendly form. For users searching on the term adjustment_comments, this view is the documented source that exposes the adjustment comment text alongside the approver and reason, making it the natural target for audit, approval-tracking, and reconciliation reporting.

Underlying Base Objects

The view text documents a single base object: PSP_ADJUSTMENT_CONTROL_TABLE, aliased as PAC. The view is a direct projection of that table — there are no documented joins, unions, or aggregations in the view definition. Every column exposed by the view originates from PSP_ADJUSTMENT_CONTROL_TABLE, and the only transformation applied is the read-only restriction.

This direct relationship matters operationally. Filtering, sorting, and performance characteristics of the view are inherited entirely from the underlying control table. Because there is no join, approver lookups that resolve APPROVER_ID to a person name or employee number must be performed separately against the appropriate HR or FND person tables. The ETRM metadata notes that the view is not implemented in the reference database, so DBAs should confirm its presence in a given environment before referencing it in custom reports or concurrent programs.

Key Columns

• ADJUSTMENT_BATCH_NAME — The name of the adjustment batch, the primary business identifier for grouping adjustment activity.
• APPROVER_ID — The identifier of the person who approves the distribution adjustment. The column list also reflects an APPROVER display attribute, consistent with the view's stated purpose of showing approver information.
• REASON_FOR_ADJUSTMENT — The coded or textual reason associated with the adjustment batch.
• ADJUSTMENT_COMMENTS — The free-text comments captured on the adjustment approval record. This is the column most directly relevant to users searching on adjustment_comments.
• BUSINESS_GROUP_ID — The HR business group partition, enabling multi-organization and security filtering.
• SET_OF_BOOKS_ID — The ledger context for the adjustment, essential when reporting across multiple sets of books.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE — Standard Oracle WHO columns supporting audit trails and change tracking.

Common Use Cases and Queries

The view is typically used for approval audit reporting, adjustment batch reconciliation, and integration extracts that feed downstream labor cost analysis. A representative query retrieves approver and comment detail for a specific batch:

• SELECT ADJUSTMENT_BATCH_NAME, APPROVER_ID, REASON_FOR_ADJUSTMENT, ADJUSTMENT_COMMENTS FROM PSPBV_ADJUSTMENT_APPROVERS WHERE ADJUSTMENT_BATCH_NAME = :batch_name;
• SELECT ADJUSTMENT_BATCH_NAME, APPROVER_ID, ADJUSTMENT_COMMENTS, LAST_UPDATE_DATE FROM PSPBV_ADJUSTMENT_APPROVERS WHERE SET_OF_BOOKS_ID = :sob_id AND LAST_UPDATE_DATE >= :since_date ORDER BY LAST_UPDATE_DATE DESC;
• SELECT APPROVER_ID, COUNT(*) FROM PSPBV_ADJUSTMENT_APPROVERS GROUP BY APPROVER_ID;

Because APPROVER_ID is a numeric identifier, production reports generally join the view to person or user tables to render usable approver names. Where adjustment comments are subject to audit, the WHO columns allow change history to be reconstructed alongside the comment text.