Search Results per_letter_requests




Overview
Explore in AI Chat

Overview

The PER_LETTER_REQUESTS table is a core data object within the Oracle E-Business Suite (EBS) Human Resources (HR) module, specifically under the PER product family. As documented, it serves as the central repository for requests to generate specific types of standard letters. This table functions as the master header record for letter generation workflows, tracking the initiation, type, and key contextual parameters of each letter request. Its role is integral to the automated and standardized communication processes within HR operations, such as generating employment contracts, promotion letters, or termination notices.

Key Information Stored

The table stores metadata and control information for each letter request. While the full column list is not provided in the excerpt, the documented foreign keys and primary key reveal critical data points. The primary identifier is LETTER_REQUEST_ID. Each record is linked to a specific letter template via LETTER_TYPE_ID, which references the PER_LETTER_TYPES table. The organizational context is established through BUSINESS_GROUP_ID, linking to HR_ALL_ORGANIZATION_UNITS. Other typical columns in this table, based on standard HR table structures, would include status, request date, person or assignment ID for whom the letter is generated, and attributes to track the requestor and process flow.

Common Use Cases and Queries

This table is primarily accessed for tracking and reporting on letter generation activities. Common operational and reporting scenarios include auditing all letters generated for a specific employee or within a date range, monitoring pending letter requests, and verifying the types of letters issued by a business group. A typical query would join PER_LETTER_REQUESTS with PER_LETTER_TYPES for description and with person tables for employee details.

  • Sample Query (Find Letter Requests for an Employee):
    SELECT plr.letter_request_id, plt.name letter_type, plr.creation_date
    FROM per_letter_requests plr,
    per_letter_types plt
    WHERE plr.letter_type_id = plt.letter_type_id
    AND plr.person_id = :p_person_id
    ORDER BY plr.creation_date DESC;
  • Use Case: A compliance report listing all termination letters generated in the last quarter, showing the employee name and business group.

Related Objects

As per the provided metadata, PER_LETTER_REQUESTS has defined relationships with several key HR objects, forming a logical data model for letter management.

  • PER_LETTER_REQUEST_LINES: This is a critical child table, linked via the foreign key on LETTER_REQUEST_ID. It likely holds the detailed, line-level data or variable substitutions (like salary, job title) used to populate the standard letter template for each specific request.
  • PER_LETTER_TYPES: Provides the definition and template information (name, format, content) for the type of letter being requested via the LETTER_TYPE_ID foreign key.
  • HR_ALL_ORGANIZATION_UNITS: Establishes the business group context for the letter request through the BUSINESS_GROUP_ID foreign key, enforcing data security and multi-org integrity.