Search Results get_composite_logs_for_map
Overview
APPS.ENG_PROPAGATION_LOG_UTIL is a utility package in the Oracle E-Business Suite Engineering (ENG) module that supports the change propagation and logging infrastructure used by Oracle Engineering Change Management (ECM). The package does not execute engineering change business rules itself; rather, it provides shared constants, logging helpers, and entity-mapping utilities that other engineering propagation programs rely on when an engineering change order (ECO) is released and its revisions must be propagated to affected items, components, and attachments.
The package is declared with AUTHID CURRENT_USER and is classified as an API/UTIL object within the ETRM repository. Its source header indicates a build revision of 120.3, and the constants defined at the top of the specification establish the vocabulary used across the propagation subsystem: processing status codes, revised line types, entity name identifiers, log types, and log verbosity levels. It is referenced by two other packages, confirming its role as a shared dependency rather than a standalone executable unit.
Key Procedures and Functions
The documented package exposes eight procedures and functions:
- WRITE_PROPAGATION_LOG — Writes a diagnostic message to the engineering change log, honoring the log type (INFO, WARNING, ERROR) and verbosity constants defined in the specification.
- CHECK_ENTITY_MAP_EXISTANCE — Verifies whether a mapping already exists for a given entity, preventing duplicate registrations in the propagation map tables.
- ADD_ENTITY_MAP — Inserts a new entity mapping record, associating an entity (such as a revised item or revised line) with its propagation context.
- INITIALIZE — Performs package-level initialization, commonly resetting session state or resolving the current user environment before propagation logic begins.
- MARK_COMPONENT_CHANGE_TRANSFER — Flags a component change as transferred, recording the outcome of a propagation attempt.
- GET_COMPOSITE_LOGS_FOR_MAP — Retrieves the set of log entries associated with a given propagation map identifier.
- DEBUG_LOG — Emits debug-level output when diagnostic logging is enabled, typically gated by the G_LOG_* constants.
- GET_PROPAGATE_ACTION_FLAG — Returns the propagation action flag that determines whether a given change should proceed through the propagation pipeline.
Tables Accessed
The package reads and writes through APPS synonyms. The principal tables are ENG_CHANGE_PROPAGATION_MAPS and its sequence-bearing sibling ENG_CHANGE_PROPAGATION_MAPS_S, which together store the entity-to-change mapping used to route propagation. ENG_CHANGE_LOGS_B and ENG_CHANGE_LOGS_S hold the base and sequence log records written by WRITE_PROPAGATION_LOG and DEBUG_LOG. ENG_CHANGE_OBJ_RELATIONSHIPS captures relationships between change objects. ENG_ENGINEERING_CHANGES and ENG_REVISED_ITEMS supply the authoritative change and revised-item context. DUAL is used for simple single-row queries. PLITBLM is the standard Oracle Applications PL/SQL table-to-database utility, used to store and flush collections of log records efficiently.
Usage Notes
ENG_PROPAGATION_LOG_UTIL is typically invoked indirectly rather than from a form directly. Engineering Change Management concurrent programs and the propagation engine call its logging and mapping routines during ECO release and propagation runs. The searched identifier, g_entity_revised_item, is a package constant equal to 'ENG_REVISED_ITEM', used as the entity name when registering an entity map for a revised item. Custom extensions that perform supplementary propagation or diagnostics should reference these constants rather than hard-coded literals. Because the package uses AUTHID CURRENT_USER, privileges are resolved against the invoking schema, so callers must be granted appropriate access to the underlying ENG tables. Debug logging should remain disabled in production, as GET_COMPOSITE_LOGS_FOR_MAP and DEBUG_LOG can generate significant log volume during large propagation runs.