Results for “per_letter_request_lines_v”

28 results




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

Overview

PER_LETTER_REQUEST_LINES_V is a VALID Oracle E-Business Suite view owned by the APPS schema within the PER (Human Resources) product family. Its documented purpose is to "support user interface" — meaning it exists primarily as a presentation-layer object rather than as a standalone transactional entity. The view surfaces a single unified row set for letter request lines, denormalising person, assignment, and organisation attributes alongside OTA booking-related identifiers so that HR forms, OAF pages, and concurrent programs can render letter request data without issuing multiple joins themselves.

Because the view is defined with a UNION between an inner case (people having an assignment) and an outer case (people without), it guarantees that every letter request line is returned at least once, with organisation name populated where an assignment exists and set to NULL where it does not. This defensive design reflects the reality that letter requests can be raised against applicants or ex-employees who have no active assignment record.

Underlying Base Objects

The view is defined over PER_LETTER_REQUEST_LINES (the driving synonym over the base table), joined to PER_ALL_PEOPLE and PER_ASSIGNMENTS (both documented as views over PER_PEOPLE and related entities), HR_ALL_ORGANIZATION_UNITS and its translation table HR_ALL_ORGANIZATION_UNITS_TL. The translation join is filtered on ORGTL.LANGUAGE = USERENV('LANG'), ensuring the organisation name is returned in the session language.

Documented dependencies also include the HR_GENERAL, HR_PERSON_NAME, HR_PERSON_TYPE_USAGE_INFO and HR_SECURITY packages. HR_SECURITY is significant: it indicates that the view's behaviour is influenced by security profile enforcement at the package level, so rows visible to a user depend on their HR security profile.

Key Columns

Common Use Cases and Queries

The user's search term, ota_booking_status_type_id, points directly at the OTA linkage columns, typically used when HR letters must be generated or tracked against a training enrolment. A representative query:

  • SELECT letter_request_id, person_id, full_name, ota_booking_status_type_id, ota_booking_id FROM per_letter_request_lines_v WHERE ota_booking_id IS NOT NULL;
  • SELECT full_name, employee_number, name FROM per_letter_request_lines_v WHERE letter_request_id = :p_request_id; — powers the LOV or form block showing recipients.
  • SELECT * FROM per_letter_request_lines_v WHERE person_id = :p_person ORDER BY creation_date DESC; — the standard drill-down from a person record.

Because the view is a UNION, developers should avoid relying on ROWID stability when filtering on the outer case, and should expect one row per qualifying branch. The view should be treated as read-only.