Results for “psp_summary_lines_v”

4 results




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

Overview

PSP_SUMMARY_LINES_V is a reporting view in the Oracle E-Business Suite Labor Distribution module (PSP). It exposes summarized labor cost distribution records that have been processed and are currently active. The view is defined over the PSP_SUMMARY_LINES table and filters records to those holding a STATUS_CODE of 'A', presenting only active summary lines to consuming reports, concurrent programs, and integration interfaces. In the EBS 12.1.1 and 12.2.2 releases, the object serves as a read-only presentation layer that shields downstream consumers from obsolete or unprocessed rows, ensuring that only finalized distribution summaries are surfaced to inquiry screens, custom reports, and outbound interfaces.

Underlying Base Objects

The view is defined over a single base object, PSP_SUMMARY_LINES (aliased as A in the view text). No other base tables are documented as referenced objects. The defining query selects the full set of summary attributes from the base table and applies the restrictive predicate A.STATUS_CODE = 'A'. Because the view is a simple projection with a single-row filter, it is inherently non-updatable through the view definition and is intended for query and reporting purposes only. The ETRM metadata notes that the view is not implemented in the reference database, meaning the definition should be validated against the target instance before being relied upon in a specific environment.

Key Columns

The view exposes the following columns, which mirror the base table structure:

Common Use Cases and Queries

Because the user search term was "summary_line_id", the most common access path is a direct lookup or join on that key. Typical scenarios include reconciling labor distribution summaries to General Ledger, retrieving summarized costs for a person or period, and extracting batch details for interface troubleshooting.

Retrieve a single summary line by its identifier:

  • SELECT summary_line_id, person_id, summary_amount, gl_code_combination_id FROM psp_summary_lines_v WHERE summary_line_id = :p_summary_line_id;

List active summaries for an employee within a time period:

  • SELECT summary_line_id, time_period_id, summary_amount, project_id, task_id FROM psp_summary_lines_v WHERE person_id = :p_person_id AND time_period_id = :p_time_period_id;

Join to interface batch information for reconciliation:

  • SELECT s.summary_line_id, s.batch_name, s.summary_amount, s.set_of_books_id FROM psp_summary_lines_v s WHERE s.batch_name = :p_batch_name;

These queries reflect the documented column set and the active-status filter imposed by the view definition, and they represent the principal ways the object is consumed in PSP reporting and integration work.