Search Results pon_auc_doctypes_tl




Overview
Explore in AI Chat

Overview

The PON_AUC_DOCTYPES_TL table is a core translation table within the Oracle E-Business Suite (EBS) Sourcing (PON) module for versions 12.1.1 and 12.2.2. As indicated by the "_TL" suffix, it is a translatable table designed to store multilingual content. Its specific role is to store the translated names for sourcing document types, such as auctions, requests for quotation (RFQs), and other sourcing events. This table enables the Sourcing application to present user interfaces, reports, and document type selections in the language of the user, supporting global deployments. It functions as a child table to the base data table PON_AUC_DOCTYPES, holding one or more translated records for each document type defined in the system.

Key Information Stored

The table's primary purpose is to map document type identifiers to their human-readable names in various languages. Its structure is defined by a composite primary key and a critical descriptive column. The DOCTYPE_ID column is a foreign key that links directly to the PON_AUC_DOCTYPES base table, identifying the specific sourcing document type. The LANGUAGE column stores the language code (e.g., 'US' for American English, 'KO' for Korean) and is a foreign key to the FND_LANGUAGES table, which maintains the application's installed languages. The most significant data column is the user-facing DOCUMENT_TYPE_NAME, which holds the actual translated text for the document type in the corresponding language. This design is standard for EBS translation tables, ensuring data integrity through enforced referential integrity to both the base data and language tables.

Common Use Cases and Queries

This table is primarily accessed by the application's internal logic to display localized lists of document types during creation or search of sourcing events. Common reporting and data extraction use cases include generating a list of all available document types with their translations for setup documentation or audit purposes. A typical query would join this table with its base table to get a complete view. For example, to retrieve all translations for a specific document type ID, one might use: SELECT language, document_type_name FROM pon_auc_doctypes_tl WHERE doctype_id = :1 ORDER BY language;. To see all document types with their base and translated English names, a join such as SELECT b.doctype_id, t.document_type_name FROM pon_auc_doctypes b, pon_auc_doctypes_tl t WHERE b.doctype_id = t.doctype_id AND t.language = 'US' would be standard. Developers may also query this table when debugging multilingual display issues within the Sourcing module.

Related Objects

PON_AUC_DOCTYPES_TL has defined, critical relationships with two other key EBS objects, as confirmed by the foreign key metadata. Its primary relationship is with the PON_AUC_DOCTYPES table, which stores the base, non-translated definition of sourcing document types. The DOCTYPE_ID foreign key enforces that every translation record must correspond to a valid base record. Secondly, it references the FND_LANGUAGES table, a central Application Object Library (FND) table that defines all languages installed and available in the EBS instance. This ensures translations are only stored for valid, active languages. The table is also implicitly related to any application screens, reports, or APIs in the Sourcing module that present document type selections, as they will rely on this table for localized labels.