Search Results jtf_fm_md_migration_pvt




Overview
Explore in AI Chat

Overview

APPS.JTF_FM_MD_MIGRATION_PVT is a private PL/SQL package body in the Oracle E-Business Suite Applications schema (APPS). It belongs to the CRM Foundation / JTF (Java Technology Foundation) family of utilities, and its documented status is VALID across Oracle EBS 12.1.1 and 12.2.2. The package handles master-document ("MD") migration within the JTF Foundation message and document framework, moving legacy content stored in the older AMV/JTF attachment and item structures into the current Foundation messaging and query model. The "PVT" suffix identifies it as a private API, meaning it is intended for internal use by other Foundation packages and concurrent programs rather than as a published integration point.

The package depends on standard EBS infrastructure components — FND_API, FND_GLOBAL, FND_MESSAGE, FND_MSG_PUB, and FND_PROFILE — for error handling, session context, and message resolution, and on FND_LOBS / FND_LOBS_S for large-object storage. It also references IBC utilities (IBC_UTILITIES_PUB, IBC_CITEM_ADMIN_GRP, IBC_CV_LABEL_GRP) and Foundation AMV tables, confirming that its scope spans both content items and their associated attachments.

Key Procedures and Functions

The documented package exposes two procedures:

  • MASTER_DOCUMENT_MIG — Orchestrates the migration of master documents. Its name indicates that it drives the conversion of source master-document records into the target JTF Foundation structures, coordinating the corresponding attachment and item rows.
  • OCMMIGRATION — Performs the underlying content migration. This entry point processes the migration of document content (including attachments and binary large objects, given the FND_LOBS dependency) from the AMV/JTF source tables into the destination query and history tables, and records the outcome in the migration history structures.

Parameter lists are not published in the available metadata, so callers must rely on wrapper packages or the EBS source to supply correct argument order. The two procedures are designed to work together: MASTER_DOCUMENT_MIG establishes the document context, and OCMMIGRATION carries out the actual content movement.

Tables Accessed

The package reads and writes the following documented tables through APPS synonyms:

  • JTF_AMV_ATTACHMENTS and JTF_AMV_ITEMS_B — source tables holding legacy attachment records and item master rows that are migrated.
  • FND_LOBS and FND_LOBS_S — the standard EBS LOB store and sequence used to persist migrated binary content.
  • JTF_FM_MIGRATION_HISTORY and JTF_FM_MIG_HISTORY_DETAILS — audit tables that record each migration run, its status, and per-record detail, providing traceability.
  • JTF_FM_QUERIES_ALL and JTF_FM_QUERY_MES — destination structures for the migrated query definitions and their message content.
  • DUAL and PLITBLM — utility references for single-row selection and PL/SQL table buffering.

Usage Notes

Because the package is classified as private, it is not intended for direct invocation from forms or customer-written code. It is typically called by concurrent programs and by other migration or Foundation packages during the JTF master-document migration process, and it records progress in the JTF_FM_MIGRATION_HISTORY tables for later review. The dependency metadata indicates the package is not referenced by any database object, so it functions as an orchestration layer invoked at run time rather than a compiled dependency of other packages. Administrators should confirm that FND_LOBS storage and the AMV source tables are fully populated before initiating a migration, and should review the history tables afterward to validate completion.