Search Results okc_articles_migrate_grp




Overview
Explore in AI Chat

Overview

OKC_ARTICLES_MIGRATE_GRP is a PL/SQL group package in the Oracle Contracts (OKC) application schema, owned by APPS and classified as a GRP-type API within Oracle E-Business Suite 12.1.1 and 12.2.2. Its business purpose is to migrate article and clause content into the standard Oracle Contracts repository from the staging interface table OKC_ART_INTERFACE_ALL. Articles in Oracle Contracts represent reusable contract text such as clauses, boilerplate terms, and legal provisions. Organizations that maintain article libraries outside EBS, or that inherit article content during upgrades and consolidations, load that content through the interface table and then invoke this package to promote it into the production article tables. The package header carries the source identifier OKCGARTMIGS.pls, version 120.0, dated 2005/05/25, indicating a long-stable interface that has remained consistent across the 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

The documented package exposes two procedures:

  • CONC_MIGRATE_ARTICLES — A concurrent program wrapper for the main migration routine. It declares the standard concurrent manager OUT parameters errbuf and retcode, together with a configurable fetch size that governs the BULK COLLECT and commit granularity. Oracle EBS registers this procedure as the executable for the article migration concurrent program, so it is the entry point used when the migration is scheduled from the Concurrent Programs form or submitted programmatically.
  • MIGRATE_ARTICLES — The principal migration API. It returns the standard API status triplet (x_return_status, x_msg_count, x_msg_data) and accepts the same fetch-size parameter that controls batch and commit sizing. Per the package comments, the caller can restrict processing to a single organization, or allow the default behavior of processing every organization configured through HR Organization EITs. When the requested organization is the Global Org, the routine executes as a regular migration rather than an organization-scoped one.

No additional public functions or procedures are documented beyond these two.

Tables Accessed

The package reads from the staging table OKC_ART_INTERFACE_ALL and writes to the core article model. The target tables include OKC_ARTICLES_ALL and its sequence-backed index OKC_ARTICLES_ALL_S1, OKC_ARTICLE_VERSIONS and OKC_ARTICLE_VERSIONS_S1 (version history for each article), OKC_ARTICLE_RELATNS_ALL (article-to-article relationships), and OKC_ARTICLE_ADOPTIONS (records of which operating units or organizations have adopted a given article). Folder placement is maintained in OKC_FOLDERS_ALL_B, OKC_FOLDERS_ALL_B_S1, and OKC_FOLDERS_ALL_TL, allowing migrated articles to be cataloged within the contract folder hierarchy in a multilingual environment. Reference and descriptive data are resolved from FND_LANGUAGES, FND_LOOKUP_VALUES, HR_ALL_ORGANIZATION_UNITS, and HR_ORGANIZATION_INFORMATION, which supply language codes, lookup meanings, and the organization definitions that determine the migration scope. Finally, FND_ATTACHED_DOCUMENTS is accessed to preserve or recreate attachments associated with migrated article content.

Usage Notes

OKC_ARTICLES_MIGRATE_GRP is customarily invoked through its concurrent program rather than from a form. Administrators populate OKC_ART_INTERFACE_ALL from legacy systems, external clause libraries, or data extracts, then submit the concurrent program that executes CONC_MIGRATE_ARTICLES. The fetch-size parameter should be tuned to balance undo and redo generation against throughput; the default of 100 rows per batch is conservative and may be raised for large volumes. Custom code may call MIGRATE_ARTICLES directly, but must first validate that all required columns in the interface table are populated and that the target organizations exist in HR. The API does not appear to be referenced by any other shipped package, so its use is isolated to migration scenarios. Because the package commits in batches, a failed run can leave partially migrated data, and any restart should be preceded by an assessment of rows already promoted within the selected organization scope.