Search Results product_dependencies

Overview

ETRM_RPT is a PL/SQL package owned by APPS that forms the reporting and metadata-extraction core of Oracle eTRM (Enterprise Technical Reference Manual), the Oracle Applications repository browser and dependency report tool. Authored originally by Peter Goldthorp in October 2001 and maintained through the 12.2.x release cycle, the package provides the programmatic interface through which eTRM generates documentation describing the objects, structures, and cross-product dependencies stored in the E-Business Suite database dictionary. In the context of Oracle EBS 12.1.1 and 12.2.2, ETRM_RPT allows administrators, developers, and support engineers to produce human-readable and machine-consumable reports about the APPS schema and its underlying dictionary objects, without requiring direct ad hoc SQL against DBA_* views. The package is classified as API type OTHER, reflecting its role as an internal utility rather than a public business API.

Key Procedures and Functions

The documented interface exposes four callable units:

• GET_OBJECT_NAME — A function that returns the name of a database object given its object identifier. It accepts an object ID conforming to DBA_OBJECTS.OBJECT_ID and an optional mode selector defaulting to 'BOTH', which governs how the resolved name is presented or combined in the returned string. This function underpins the rest of the reporting logic by resolving numeric IDs to readable object names.
• CR_FILE (name-based overload) — A procedure that creates a report file for a specific database object, taking the object name, its owner, its object type, and an optional report type defaulting to 'FULL'. The FULL mode implies the report includes the complete object definition and metadata rather than a summary.
• CR_FILE (owner-based overload) — A procedure that creates a report file for an entire schema or owner, accepting the owner name and an optional report type. This overload supports bulk documentation of all objects belonging to a given Oracle schema.
• PRODUCT_DEPENDENCIES — A procedure that generates a dependency report for a named Oracle Applications product, enumerating the objects and relationships associated with that product. It supports the eTRM dependency-analysis use case for impact assessment and upgrade planning.

Tables Accessed

ETRM_RPT reads its source data exclusively from Oracle data dictionary views, resolved through APPS synonyms. The package draws on DBA_OBJECTS for object identity and type information; FND_APPLICATION and FND_APPLICATION_TL for product registration and translated product names; DBA_TABLES, DBA_VIEWS, DBA_TAB_COLUMNS, DBA_TAB_COMMENTS, and DBA_COL_COMMENTS for table and column structure and descriptive text; DBA_CONSTRAINTS and DBA_CONS_COLUMNS for integrity constraint definitions; DBA_INDEXES and DBA_IND_COLUMNS for index structures; and DBA_SOURCE for PL/SQL source text. FND_TABLES and FND_VIEWS provide Applications-specific registration metadata that links dictionary objects to their owning products. No tables are written by this package; all access is read-only against dictionary and Applications registration views.

Usage Notes

ETRM_RPT is invoked primarily through the eTRM repository browser and dependency report functionality rather than directly by end users. The overloaded CR_FILE procedures lend themselves to concurrent program or batch invocation, where a single owner-level call can generate documentation for an entire schema. The PRODUCT_DEPENDENCIES procedure supports product-level impact analysis, typically executed during upgrades or patching cycles to determine which objects a product touches. Custom code and diagnostic scripts may call GET_OBJECT_NAME to translate object IDs captured from trace files or performance views into readable names. Because the package is a documented internal utility with no other packages referencing it, direct invocation from custom code is viable but should be treated as unsupported and validated against each EBS release, particularly when moving between 12.1.1 and 12.2.2.