Search Results per_letter_types




Overview
Explore in AI Chat

Overview

The PER_LETTER_TYPES table is a core reference table within the Oracle E-Business Suite Human Resources (PER) module. It serves as the master repository for defining the types of letters or documents that can be generated by the system, such as employment contracts, promotion letters, or termination notices. Its primary role is to establish the framework for automated letter generation, enabling organizations to standardize and control the creation of HR-related correspondence. Each record defines a specific letter template or category, which is then utilized by the letter generation and request processes to produce final documents for employees or other entities.

Key Information Stored

The table's structure is designed to uniquely identify and categorize letter definitions within the context of a specific business group. The critical columns include the surrogate primary key, LETTER_TYPE_ID, and the unique composite key formed by LETTER_TYPE_NAME and BUSINESS_GROUP_ID. This composite key ensures that letter type names are unique within each business group, a fundamental requirement for multi-organization implementations. Additional columns, implied by its purpose and common HR table design, would typically store attributes such as the letter's description, the associated report or template identifier, active status, and other control parameters that govern the auto-request and generation logic.

Common Use Cases and Queries

This table is central to any process involving system-generated HR letters. Common use cases include configuring new letter templates for mass communications, auditing available letter types for a business group, and troubleshooting letter generation workflows. A typical administrative query would list all active letter types for a specific business group. For example:

  • SELECT letter_type_name, description FROM per_letter_types WHERE business_group_id = &bg_id ORDER BY letter_type_name;

For integration or reporting purposes, developers often join this table to letter request tables to correlate generated documents with their master definitions, providing context for status tracking and historical reporting on letter issuance.

Related Objects

As documented in the ETRM metadata, PER_LETTER_TYPES maintains defined foreign key relationships with several key HR tables, establishing its role as a parent reference entity.

  • HR_ALL_ORGANIZATION_UNITS: The BUSINESS_GROUP_ID column in PER_LETTER_TYPES is a foreign key to this table, enforcing that each letter type is associated with a valid business group.
  • PER_LETTER_GEN_STATUSES: This child table references PER_LETTER_TYPES via the LETTER_TYPE_ID foreign key, storing status information for letter generation processes tied to a specific letter type.
  • PER_LETTER_REQUESTS: This child table also references PER_LETTER_TYPES via LETTER_TYPE_ID, storing the individual instances or queue of requests to generate a particular type of letter.

These relationships confirm that PER_LETTER_TYPES is a foundational object for the letter generation subsystem, with child tables managing the runtime execution and status of requests based on its definitions.