Results for “delete_irep_entry”
5 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The APPS.DELETE_FROM_IREP package body is an Oracle E-Business Suite utility that removes entries from the Interface Repository (IREP). The Interface Repository is the metadata store that EBS uses to describe classes, their attributes, associated datasources, parent/child assignments, and deferred load files. The package is classified as OTHER within the ETRM catalog, indicating it is an internal maintenance utility rather than a public business API. Its principal purpose is to provide a controlled, single-entry-point deletion routine that atomically purges a class definition and all dependent repository rows, preventing orphaned metadata from accumulating in the FND_IREP_* tables.
The package header is owned by APPS and the body was last updated under version 120.0.12020000.4, placing it in the 12.1.1 / 12.2.2 release line. The package is referenced by zero other packages per the ETRM metadata, confirming that it is invoked directly rather than through a chain of dependent APIs.
Key Procedures and Functions
The package exposes exactly one documented procedure:
DELETE_IREP_ENTRY— Accepts a single numeric key value, the repositorykey_id(internally mapped toclass_id), and performs the cascade removal of the corresponding IREP class. The procedure first resolves the owning source table by queryingFND_IREP_ALL_INTERFACES, then, when the class belongs toFND_IREP_CLASSES, retrieves the source file name, product, and version. It derives an ILDT file name by replacing periods with underscores and appending the.ildtsuffix, and updates the deferred load history so the affected file is flagged for reload. It then deletes child rows across the datasource, parent assignment, lookup assignment, child annotation, uses-tables, and uses-maps relationships. Diagnostic messages are emitted throughFND_LOGat procedure level when the runtime logging threshold permits.
No parameter lists are invented here; the single key_id argument is the only documented input.
Tables Accessed
The package reads and writes the following documented tables:
FND_IREP_ALL_INTERFACES— read to resolve the class's source table.FND_IREP_CLASSESandFND_IREP_CLASSES_TL— source of class file name, product, and version; the TL table carries translatable class text.FND_IREP_DEFERRED_LOAD_FILES— updated to set load status toNfor the derived ILDT file.FND_IREP_CLASS_DATASOURCES,FND_IREP_CLASS_PARENT_ASSIGNS,FND_IREP_USES_TABLES,FND_IREP_USES_MAPS— child entities deleted as part of the cascade.FND_LOOKUP_ASSIGNMENTS,FND_CHILD_ANNOTATIONS— assignment and annotation rows removed for the class instance.FND_OBJECTS,FND_OBJECTS_TL,FND_FORM_FUNCTIONS,FND_FORM_FUNCTIONS_TL,FND_IREP_FUNCTION_FLAVORS,FND_OBJECT_KEY_SETS— supporting repository and object definition tables touched during cleanup.
Usage Notes
DELETE_FROM_IREP is an internal maintenance utility. It is not exposed as a concurrent program, and no other package references it according to the ETRM catalog. It is therefore invoked either directly by a DBA or developer during repository cleanup, or indirectly from administrative scripts and forms that manage IREP class definitions. Because the procedure performs unrecoverable deletes against shared metadata, it should be run only within a controlled change window with a validated backup of the affected FND_IREP_* tables. Callers supply the target key_id, which corresponds to the repository class_id; supplying an incorrect identifier can remove legitimate class metadata. Logging behavior depends on FND_LOG.G_CURRENT_RUNTIME_LEVEL, so enabling FND_LOG at procedure level is advisable before execution to capture the diagnostic output.