Search Results apps_debug




Overview
Explore in AI Chat

Overview

JTF_FM_MD_MIGRATION_PVT is a private PL/SQL package in the APPS schema that supports migration of master document and attachment metadata within the Oracle E-Business Suite. It belongs to the JTF (Java Technology Framework) foundation modules associated with the CRM/Forms-based content and attachment framework (JTF_AMV). The package header carries the version constant g_api_version set to 1.0 and the package name g_pkg_name defined as JTF_FM_M_MIGRATION_PVT, with the source header identifying the file as JTFFMVMS.pls (revision 120.0, dated 2005). Its stated purpose, per the embedded comment, is to carry out migration for IBE.O object content, moving master document records and their associated query metadata between the source structures and the target framework tables. Consistent with Oracle's naming conventions, the PVT suffix designates this as a private API intended for internal invocation rather than direct customer-facing use.

Key Procedures and Functions

Two procedures are documented for this package:

  • MASTER_DOCUMENT_MIG — The primary migration driver. It performs the master document migration and returns an OUT status indicator (x_status) reflecting the outcome of the operation. This procedure encapsulates the bulk of the record transfer logic from the legacy/master document query structures into the AMV content and attachment tables.
  • OCMMIGRATION — The externally callable migration wrapper that returns the standard concurrent program error buffer (errbuf) and return code (retcode). It accepts a debug flag (p_debug_flag), allowing callers to enable trace-style output during execution. The errbuf/retcode signature indicates that this procedure is designed to be invoked as a concurrent program.

Tables Accessed

The package reads from and writes to the following documented tables via APPS synonyms:

  • JTF_AMV_ITEMS_B and JTF_AMV_ATTACHMENTS — the target AMV content item and attachment tables into which migrated master documents, file identifiers, content types and version identifiers are placed.
  • JTF_FM_QUERIES_ALL and JTF_FM_QUERY_MES — source query and query-message definitions whose records are read during migration.
  • FND_LOBS and FND_LOBS_S — the Oracle EBS large-object repository where attachment file content is stored and referenced by LOB identifiers.
  • JTF_FM_MIGRATION_HISTORY and JTF_FM_MIG_HISTORY_DETAILS — audit and history tables used to record each migration run and its per-record detail results.
  • DUAL and PLITBLM — utility references used for single-row selection and PL/SQL index-by table manipulation.

Usage Notes

JTF_FM_MD_MIGRATION_PVT is a private package (API classification PVT) and is not intended for direct customer invocation; Oracle documents no calling packages for it (referenced by 0 other packages), so it is typically driven from a concurrent program definition or an internal seeding/correction script rather than from a form. OCMMIGRATION is the entry point exposed in that pattern, since its errbuf/retcode signature conforms to the Oracle Application Object Library concurrent program standard — register it as a PL/SQL concurrent program with the debug flag as a parameter, then submit it from the System Administrator or application responsibility when master document migration is required.

Regarding the user's search term apps_debug, the package source declares a global g_debug VARCHAR2(1) initialized from fnd_profile.value('APPS_DEBUG') and defaulted to 'N'. This means diagnostic behaviour is controlled by the site-level profile option APPS_DEBUG, independent of the p_debug_flag parameter passed to OCMMIGRATION. When enabling tracing through APPS_DEBUG, exercise caution: the package is a migration utility that writes to JTF_AMV and JTF_FM_MIGRATION_HISTORY, and these tables are not transactional with respect to interactive work. Testing on a cloned environment before running migration against production data is strongly recommended. The 2005 header date and low revision number also indicate that the package is legacy code that has remained stable across the 12.1.1 and 12.2.2 releases.