Results for “g_debug_filename”
32 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The APPS.ENG_CHANGE_ROUTE_ASSOCS_UTIL package body is a utility package within the Oracle E-Business Suite Engineering (ENG) module. Its principal business function is to manage the associations between engineering change orders (ECOs) and their routing operations — the linkage records stored in the ENG_CHANGE_ROUTE_ASSOCS entity. During the engineering change management lifecycle, a change order frequently redefines the manufacturing routing steps of an item, and these routing associations must be created, updated, copied, or removed consistently as the change progresses through release and implementation. This package encapsulates the low-level DML and concurrency handling required to maintain those associations, ensuring that callers do not manipulate the base table directly and that locking, row versioning, and debug tracing are applied uniformly.
The body is classified as a UTIL package in the ETRM 12.2.2 metadata and, in the documented 12.1.1 / 12.2.2 environments, holds a status of VALID in the APPS schema. It exposes eight documented procedures and depends on the base table, its _S sequence, FND_PROFILE, UTL_FILE, V$PARAMETER, and DUAL. Notably, the package is not referenced by any other database object, indicating it is an entry-point utility rather than a shared library consumed internally by the database tier.
Key Procedures and Functions
- OPEN_DEBUG_SESSION — Initializes a debug trace session. It typically resolves a profile-option-driven flag and opens a
UTL_FILEhandle (with the directory resolved fromV$PARAMETER) so that subsequent operations write diagnostic output. - CLOSE_DEBUG_SESSION — Terminates the debug session opened above, flushing and closing the
UTL_FILEhandle and releasing session state. - WRITE_DEBUG — Emits a debug message to the active debug file, used by the other routines to record their activity when tracing is enabled.
- COPY_ASSOCIATIONS — Duplicates the set of routing associations belonging to a source change order onto a target change order. This supports ECO copy/duplicate scenarios where rework of an existing change should carry its routing linkage forward.
- INSERT_ROW — Inserts a single routing association record into
ENG_CHANGE_ROUTE_ASSOCS, assigning the primary key from theENG_CHANGE_ROUTE_ASSOCS_Ssequence. - LOCK_ROW — Acquires a row-level lock on an existing association to serialize concurrent modification, protecting against lost updates during multi-user change processing.
- UPDATE_ROW — Modifies the attributes of an existing routing association after the lock has been obtained.
- DELETE_ROW — Removes a routing association, typically when a routing step is dropped from the change or when the association is being re-created.
Tables Accessed
- ENG_CHANGE_ROUTE_ASSOCS — The primary entity table holding ECO-to-routing-step associations. All insert, lock, update, copy, and delete operations target this table.
- ENG_CHANGE_ROUTE_ASSOCS_S — The sequence supplying unique primary keys for new association rows inserted via
INSERT_ROW. - DUAL — Used for trivial single-row queries, such as sequence value retrieval.
- UTL_FILE and V$PARAMETER — Accessed indirectly for debug file output and to resolve database parameters (for example, the user-dump or log destination) supporting the debug session routines.
- FND_PROFILE — Queried to evaluate profile options, most likely the debug/trace enabling flag governing
OPEN_DEBUG_SESSIONandWRITE_DEBUG.
Usage Notes
Because the package body is not referenced by any other database object, it is invoked directly by client-side code rather than through database-tier chaining. Typical invocations occur from Oracle Forms or OAF pages within the Engineering Change Management module when a user duplicates or edits a change order and its routing associations, from concurrent programs that process ECO routing changes in batch, and from custom PL/SQL extensions that require controlled manipulation of ENG_CHANGE_ROUTE_ASSOCS. The presence of OPEN_DEBUG_SESSION/WRITE_DEBUG allows developers and support analysts to enable trace output via a profile option without code changes, which is valuable when diagnosing routing-association failures in a production 12.1.1 or 12.2.2 environment. Custom code calling these routines should mirror the package's own ordering — open a debug session where needed, lock before update or delete, and close the session on completion — to avoid orphaned file handles and lock contention.