Search Results eng_change_propagation_maps_s

Overview

APPS.ENG_PROPAGATION_LOG_UTIL is a utility package body in the Oracle E-Business Suite Engineering (ENG) module. Its principal business function is to manage the logging and tracking of engineering change propagation activity. In the EBS data model, an engineering change order (ECO) may be propagated across a hierarchy of change objects, such as revised items and their associated change relationships. The propagation process generates intermediate and composite log records that record which components were affected, what action was taken, and whether the attempted propagation succeeded. ENG_PROPAGATION_LOG_UTIL centralizes the write, query, and validation logic that surrounds this propagation log so that callers do not manipulate the underlying change-log tables directly.

The package is classified as a UTIL API. It defines an internal PL/SQL collection type, Entity_Map_Log_Tbl_Type, cached in the private global G_Entity_Map_Log_Table, which buffers entity-map log rows in memory before persistence. It also declares standard FND_API return-status constants and an error classification code of 'PROPAGATN', indicating that errors raised through this package are attributed to propagation processing. Debug output is routed to the concurrent manager log via Fnd_File.Put_Line, gated by the AFLOG_LEVEL profile option.

Key Procedures and Functions

• WRITE_PROPAGATION_LOG — The public entry point matching the search term. It writes a propagation log entry for a given change context, applying the package's logging level and mode settings and persisting to the engineering change log tables.
• CHECK_ENTITY_MAP_EXISTANCE — Determines whether an entity-map record already exists, allowing callers to avoid duplicate propagation entries.
• ADD_ENTITY_MAP — Adds a new entity-map association, populating the in-memory log table for subsequent writing.
• INITIALIZE — Performs package-level setup, resetting the cached log table and reading profile-based logging options.
• MARK_COMPONENT_CHANGE_TRANSFER — Flags a component as having its change transferred through propagation, supporting downstream status reporting.
• GET_COMPOSITE_LOGS_FOR_MAP — Returns the set of aggregated or composite log rows associated with a specific propagation map, used for reporting and review.
• DEBUG_LOG — Writes diagnostic messages to the concurrent log when debugging is enabled.
• GET_PROPAGATE_ACTION_FLAG — Returns the action flag indicating the propagation action applicable to the current context.

Tables Accessed

The package operates against the core Engineering Change tables through APPS synonyms. ENG_CHANGE_PROPAGATION_MAPS and ENG_CHANGE_PROPAGATION_MAPS_S hold the mapping definitions that drive propagation; these are read and updated by WRITE_PROPAGATION_LOG, CHECK_ENTITY_MAP_EXISTANCE, and ADD_ENTITY_MAP. ENG_CHANGE_LOGS_B and ENG_CHANGE_LOGS_S are the base and sequence tables into which propagation log rows are inserted. ENG_CHANGE_OBJ_RELATIONSHIPS supplies the object-relationship hierarchy used to derive composite logs. ENG_ENGINEERING_CHANGES and ENG_REVISED_ITEMS provide the ECO and item revision context required for each log entry. DUAL supports scalar queries, and PLITBLM is an internal PL/SQL table used for bulk processing.

Usage Notes

This utility is invoked internally by the Engineering Change propagation engine rather than by end-user forms directly; the ETRM metadata records it as referenced by two other packages. Typical invocation occurs when an ECO is released or a revised item is processed, at which point propagation logic calls INITIALIZE, evaluates actions via GET_PROPAGATE_ACTION_FLAG, and records each affected mapping through WRITE_PROPAGATION_LOG. Concurrent programs that submit propagation processing will accumulate the resulting rows in the change-log tables for later reporting and diagnosis. Custom extensions should call the documented procedures only, honor the FND_API return statuses, and avoid direct DML against the underlying change-log tables to preserve data integrity.