Search Results pv_ge_history_log_tl




Overview
Explore in AI Chat

Overview

The PV_GE_HISTORY_LOG_TL table is a core data object within the Oracle E-Business Suite (EBS) Partner Management (PV) module, specifically in versions 12.1.1 and 12.2.2. It functions as a translation table (denoted by the "_TL" suffix), designed to store multilingual versions of user-entered comments associated with historical changes. Its primary role is to support the application's globalization features by capturing translatable text for audit logs and history entries, ensuring that comments logged during partner-related transactions are accessible in the user's preferred language. This table works in conjunction with its base table, PV_GE_HISTORY_LOG_B, to provide a complete, language-aware audit trail for partner management activities.

Key Information Stored

The table's structure is centered on enabling multilingual content storage. Its primary key is a composite of ENTITY_HISTORY_LOG_ID and LANGUAGE, which enforces uniqueness for each language translation of a given history log entry. The ENTITY_HISTORY_LOG_ID is a foreign key that links each row of translatable text to a specific record in the base history log table (PV_GE_HISTORY_LOG_B). The LANGUAGE column stores the language code (e.g., 'US' for American English) for the translated comment. The most critical data column, though not explicitly named in the provided metadata but inherent to a translation table's purpose, would typically be named COMMENT_TEXT or a similar descriptor, which holds the actual translated comment text for the audit log. Additional standard columns like CREATED_BY and CREATION_DATE are also typically present to track the origin of each translation.

Common Use Cases and Queries

This table is primarily accessed by the application's user interface to display history log comments in the session language. Common scenarios include reviewing the audit trail of changes made to a partner profile or a partner program enrollment. A standard query would join this table with its base table to retrieve the language-specific comments for a specific entity or transaction. For example, to retrieve the history log for a particular partner in the current session language, a query might follow this pattern:

  • SELECT hb.log_date, hb.action_code, htl.comment_text
  • FROM pv_ge_history_log_b hb,
  • pv_ge_history_log_tl htl
  • WHERE hb.entity_history_log_id = htl.entity_history_log_id
  • AND hb.entity_id = :partner_id
  • AND htl.language = USERENV('LANG')
  • ORDER BY hb.log_date DESC;

Reporting use cases often involve extracting comprehensive audit data for compliance or analysis, requiring joins across the partner management schema to contextualize the history entries.

Related Objects

The PV_GE_HISTORY_LOG_TL table has a direct and critical relationship with its corresponding base table, as documented in the provided metadata. The primary related object is:

  • PV_GE_HISTORY_LOG_B: This is the base table that stores the non-translatable attributes of the history log, such as the date, user ID, and entity ID of the change. The relationship is enforced by a foreign key constraint where PV_GE_HISTORY_LOG_TL.ENTITY_HISTORY_LOG_ID references PV_GE_HISTORY_LOG_B.ENTITY_HISTORY_LOG_ID. Any query for a complete, localized history log entry must join these two tables on this column.