Search Results arc_history_for_entity_code




Overview
Explore in AI Chat

Overview

The PV_GE_HISTORY_LOG_B table is a core data object within Oracle E-Business Suite Release 12.1.1 and 12.2.2, specifically for the Partner Relationship Management (PRM) module. It functions as a global entity transaction log, systematically recording the historical progression of key business entities. Its primary role is to provide an auditable trail of all significant transactions and state changes that occur for an entity, such as an enrollment request or partner program. This history is critical for tracking entity lifecycle, supporting audit requirements, and enabling user-facing history displays within the application.

Key Information Stored

The table's structure is designed to link a history entry to a specific entity and categorize the type of transaction logged. The most critical columns for this purpose are ARC_HISTORY_FOR_ENTITY_CODE and HISTORY_FOR_ENTITY_ID, which together identify the exact entity instance (e.g., a specific enrollment request) that the log entry pertains to. The HISTORY_CATEGORY_CODE classifies the transaction type. For translatability, the detailed log message is not stored directly but is referenced via the MESSAGE_CODE, which points to translatable text in the FND_MESSAGES table. Each record is uniquely identified by ENTITY_HISTORY_LOG_ID and includes standard WHO columns for tracking creation and last update details. The PARTNER_ID column provides a direct link to the partner associated with the history transaction.

Common Use Cases and Queries

A primary use case is generating a complete history log for a specific entity, such as an Enrollment Request, to display in the user interface or for troubleshooting. The column HISTORY_FOR_ENTITY_ID is central to such queries. For example, to retrieve the history for a specific enrollment request ID (the searched term), one would use a query joining to the translation table for the message text:

  • SELECT log.HISTORY_FOR_ENTITY_ID, log.ARC_HISTORY_FOR_ENTITY_CODE, log.HISTORY_CATEGORY_CODE, tl.MESSAGE, log.CREATION_DATE
    FROM PV.PV_GE_HISTORY_LOG_B log,
         PV.PV_GE_HISTORY_LOG_TL tl
    WHERE log.ENTITY_HISTORY_LOG_ID = tl.ENTITY_HISTORY_LOG_ID
    AND log.ARC_HISTORY_FOR_ENTITY_CODE = 'ENROLLMENT_REQUEST'
    AND log.HISTORY_FOR_ENTITY_ID = :p_entity_id
    ORDER BY log.CREATION_DATE DESC;

Another common scenario is reporting on all history entries of a particular category (e.g., status changes) for a partner or within a date range, leveraging the PARTNER_ID and CREATION_DATE columns.

Related Objects

PV_GE_HISTORY_LOG_B has defined relationships with several other PRM tables, forming a key part of the data model. It is the base table for two dependent objects that extend its functionality:

  • PV_GE_HISTORY_LOG_TL: References this table via ENTITY_HISTORY_LOG_ID to provide translated message text for the MESSAGE_CODE.
  • PV_GE_HISTORY_LOG_PARAMS: References this table via ENTITY_HISTORY_LOG_ID to store additional parameterized data for the history log entry.

Furthermore, the HISTORY_FOR_ENTITY_ID column acts as a foreign key to the primary keys of major entity tables, primarily linking to: