Results for “letter_request_id”

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

Overview

OTA_LETTER_REQUEST_LINES_V is a query-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OTA (Learning Management) module. It presents the letter request lines that are generated for student enrollments. In the Oracle EBS architecture, letter requests are produced through the correspondence/letter generation process associated with enrollment activity; each request is decomposed into one or more request lines, and this view consolidates those lines together with the enrollment, event, and person context required for reporting and downstream consumption. The view carries a status of VALID and is documented for both 12.1.1 and 12.2.2.

Because the object is a view rather than a table, it holds no data of its own. Its principal role is to provide a stable, denormalized projection of the letter request line data for reporting, ad-hoc queries, and integration extracts, while shielding consumers from the joins and UNION logic that would otherwise be required against the base tables.

Underlying Base Objects

The view is documented over five referenced base objects:

• PER_LETTER_REQUEST_LINES — the primary source of letter request line records.
• OTA_DELEGATE_BOOKINGS — supplies booking, booking status type, and delegate person context for booking-linked lines.
• OTA_EVENTS — supplies event and course start date information.
• OTA_EVENTS_TL — the translated events table, supplying the event title filtered by the session language.
• PER_ALL_PEOPLE_F — the effective-dated person table, supplying person identifier and full name.

Internally the view is defined as a UNION of two branches. The first branch resolves lines that carry an OTA booking identifier, joining through OTA_DELEGATE_BOOKINGS, OTA_EVENTS, OTA_EVENTS_TL, and PER_ALL_PEOPLE_F, with the person join made outer (+) and constrained by the effective dates relative to LRL.DATE_FROM. The second branch resolves lines that carry an event identifier but no booking, substituting NULL for the booking and person columns. Both branches restrict the translated event row to the current session language via USERENV('LANG').

Key Columns

• LETTER_REQUEST_LINE_ID — the unique identifier of the letter request line.
• LETTER_REQUEST_ID — the parent letter request to which the line belongs; this is the column most frequently used as the driver predicate when users search by letter request identifier.
• BUSINESS_GROUP_ID — the business group that owns the line.
• OTA_BOOKING_ID / OTA_BOOKING_STATUS_TYPE_ID — booking and booking status of the associated delegate booking; NULL for event-level lines.
• OTA_EVENT_ID / EVENT_TITLE / COURSE_START_DATE — the learning event and its translated title and scheduled start date.
• PERSON_ID / FULL_NAME — the delegate or learner associated with the booking; NULL for event-level lines.
• DATE_FROM — the effective/from date used to resolve the person record and to anchor the letter line.
• CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns.
• ROW_ID — the row identifier of the underlying letter request line.

Common Use Cases and Queries

The most common use case is retrieving all lines belonging to a given letter request, for example to audit correspondence generated for a set of enrollments.

SELECT letter_request_line_id, letter_request_id, ota_event_id, event_title, full_name, course_start_date, date_from FROM apps.ota_letter_request_lines_v WHERE letter_request_id = :p_letter_request_id ORDER BY letter_request_line_id;

A second common scenario is reporting all letters produced for a specific learner or event within a date range, joining on PERSON_ID or OTA_EVENT_ID as appropriate. Because the view already resolves person name and translated event title, these reports avoid the multiple joins otherwise needed. Users searching on the term "letter_request_id" should note that LETTER_REQUEST_ID is exposed directly and is the recommended predicate for locating all lines of a single correspondence request.