Results for “generation_status_type”

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

Overview

PER_LETTER_TYPES is a core configuration table in the Oracle E-Business Suite Human Resources (PER) module, owned by the HR schema. It defines the letter types available for the generation of employee and applicant correspondence, along with the auto-request definitions that govern when such letters are produced automatically. In Oracle EBS 12.1.1 and 12.2.2, this table functions as the master reference for the letter generation framework, linking the definition of a letter to the concurrent program that renders it and to the transactional requests that instantiate it.

From a Data Vault modeling perspective, the mined foreign key structure suggests a hub-leaning classification. The table possesses a stable business key and is referenced by dependent transactional tables, which is consistent with hub behavior, although it also carries descriptive and configuration attributes that could be separated into a satellite. This classification is offered as a heuristic suggestion rather than an authoritative determination.

Key Information Stored

The table contains 36 documented columns. The most significant are summarized below.

• LETTER_TYPE_ID — the surrogate primary key, uniquely identifying each letter type. It is the target of foreign keys from dependent tables.
• BUSINESS_GROUP_ID — foreign key to HR_ALL_ORGANIZATION_UNITS, scoping the letter type to a specific business group.
• LETTER_TYPE_NAME — the user-facing name of the letter type; together with BUSINESS_GROUP_ID it forms the unique business key PER_LETTER_TYPES_UK2.
• CONCURRENT_PROGRAM_ID — identifies the concurrent program invoked to generate the letter.
• PROGRAM_APPLICATION_ID and PROGRAM_ID — further qualify the executable program associated with the letter generation.
• REQUEST_ID and PROGRAM_UPDATE_DATE — track the request context and last programmatic update.
• GENERATION_STATUS_TYPE — indicates the status classification used during letter generation.
• COMMENTS — free-text descriptive information about the letter type.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 — the standard Oracle EBS descriptive flexfield columns for extensibility.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — the standard WHO audit columns.

Common Use Cases and Queries

Typical usage involves validating configured letter types or reporting on the auto-request setup within a business group. A representative query retrieves active letter definitions alongside their generation program:

• Listing letter types for a business group: SELECT letter_type_id, letter_type_name FROM per_letter_types WHERE business_group_id = :p_bg_id;
• Joining to requests: SELECT r.letter_type_id, t.letter_type_name FROM per_letter_requests r, per_letter_types t WHERE r.letter_type_id = t.letter_type_id;
• Auditing configuration changes via the WHO columns for a date range.

These patterns support functional setup validation, letter generation troubleshooting, and HR correspondence reporting.

Related Objects

• HR_ALL_ORGANIZATION_UNITS — referenced by PER_LETTER_TYPES.BUSINESS_GROUP_ID.
• PER_LETTER_REQUESTS — references PER_LETTER_TYPES via LETTER_TYPE_ID; stores individual letter generation requests.
• PER_LETTER_GEN_STATUSES — references PER_LETTER_TYPES via LETTER_TYPE_ID; tracks generation status per letter type.
• FND_CONCURRENT_PROGRAMS — logically related through CONCURRENT_PROGRAM_ID for letter rendering.