Search Results update_path

Overview

APPS.DOM_REPOS_MIG_PKG is a repository migration utility package in Oracle E-Business Suite. Its name and structure indicate that it supports the migration of document repository path information used by the Oracle EBS Documents and Attachments framework (the DOM/FND_DOCUMENTS family of objects). The package header, identified by the version string relating to "DOMVRUGS.pls," carries an AUTHID CURRENT_USER declaration, meaning that its SQL statements execute with the privileges of the invoking user rather than the definer. This is significant for a migration package because it allows the calling session's context and privilege set to govern access to the underlying repository tables.

The package is classified under the ETRM metadata scheme as an "OTHER" API rather than a public or private interface, which suggests it is an internal or one-off utility rather than a supported integration point. Its small footprint—two documented procedures—and its arrangement around string substitution of repository paths indicate that it was written to address a targeted data-correctness scenario: rewriting stored document paths, for example when a repository is relocated, a file server path is changed, or a domain/short name mapping is altered.

Key Procedures and Functions

Two procedures are documented in the package specification.

• UPDATE_PATH — Performs the actual path migration. Based on the documented parameter pattern, it accepts a repository short name, a domain identifier, an old string value, and a new string value supplied as an IN OUT NOCOPY parameter, together with an IN OUT NOCOPY CLOB message accumulator. The IN OUT NOCOPY construction allows the procedure to return the resulting path (or related output text) to the caller efficiently while appending diagnostic output to a CLOB log. The presence of both an old and a new string confirms that the procedure is a search-and-replace or path-rebuild operation scoped by short name and domain.
• GET_NEW_PATH — Computes a candidate replacement path without necessarily committing it. It shares the short name, domain, old string, and new string IN OUT NOCOPY parameters with UPDATE_PATH, and additionally accepts a numeric document identifier and an IN OUT NOCOPY VARCHAR2 message parameter. The document ID allows the procedure to resolve and return the path relevant to a specific FND_DOCUMENTS row.

The differences in messaging parameters—a CLOB in UPDATE_PATH versus a VARCHAR2 in GET_NEW_PATH—are as delivered and should be preserved by any caller.

Tables Accessed

The package references five tables through APPS synonyms. DOM_REPOSITORIES holds repository definitions, including the short name and domain values used to scope each operation. FND_DOCUMENTS and FND_DOCUMENTS_TL are the base and translated document tables; they store the document records whose attachment paths are being migrated. ENG_ATTACHMENT_CHANGES records attachment change history and is consistent with a package that logs modifications to document paths. DUAL is used for scalar evaluation and no-data lookups. Collectively these tables show that the package is concerned with locating document rows, resolving repository locations, and recording or reflecting the path change.

Usage Notes

Because the package is not referenced by any other package, it is not part of a routine dependency chain. It is best understood as an administrative or support utility invoked directly—by a DBA or migration script—rather than through standard EBS forms or concurrent programs. In EBS 12.1.1 and 12.2.2 environments, such utilities are typically executed from an affected APPS session during repository relocation or data remediation, with the caller supplying short name, domain, and old/new path strings and capturing the LO output. Given its "OTHER" classification and noship version header, it should be used with caution and only against the specific migration scenario for which it was written.