Search Results okc_articles_import_grp




Overview
Explore in AI Chat

Overview

OKC_ARTICLES_IMPORT_GRP is a public PL/SQL package in the APPS schema that implements the bulk import of contract articles, variables, and relationships from the Oracle Contracts (OKC) interface tables into the production article repository. The package belongs to the Oracle Contracts Core product family and is classified in the ETRM metadata as an API group (GRP). Its primary consumers are the concurrent programs that drive the Articles Import process; the procedures convert staging rows held in OKC_ART_INTERFACE_ALL and OKC_ART_RELS_INTERFACE into validated records in OKC_ARTICLES_ALL, OKC_ARTICLE_VERSIONS, OKC_ARTICLE_VARIABLES, and OKC_ARTICLE_RELATNS_ALL. A key control exposed by the group is the p_validate_only parameter, present on the import procedures, which allows a batch to be validated without committing data — a critical capability when customers load large article libraries and want to detect format, setup, and reference errors before populating the production tables.

Key Procedures and Functions

The package exposes eight documented procedures. CONC_PURGE_INTERFACE is the concurrent-program entry point for purging processed or stale rows from the interface table based on a date range, process status, and batch number. CONC_IMPORT_ARTICLES is the concurrent wrapper that drives the full article import; it accepts the batch process identifier and batch number, along with the p_validate_only flag (default 'Y') and a fetch size controlling bulk collection sizes. IMPORT_ARTICLES performs the core article-loading logic, returning processed, failed, and warned row counts in addition to the standard return status and message outputs. IMPORT_VARIABLES loads article variable interface rows into OKC_ARTICLE_VARIABLES. IMPORT_RELATIONSHIPS loads article-to-article relationship records and likewise returns processed, failed, and warned counts. IMPORT_FND_FLEX_VALUE_SETS and IMPORT_FND_FLEX_VALUES load key flexfield value set definitions and their values so that imported articles can reference flexfield-based attributes. IMPORT_SCN_MAP loads section map data required to resolve interface article sections to their target identifiers. Each import procedure honors the same p_validate_only convention, distinguishing a dry-run validation pass from a committing load.

Tables Accessed

The package reads and writes the OKC interface tables OKC_ART_INTERFACE_ALL, OKC_ART_RELS_INTERFACE, OKC_ART_INT_BATPROCS_ALL (and its _S1 index), and OKC_ART_INT_ERRORS. It writes production article data into OKC_ARTICLES_ALL (and its _S1 index), OKC_ARTICLE_VERSIONS (and _S1), OKC_ARTICLE_VARIABLES, and OKC_ARTICLE_RELATNS_ALL. On the flexfield side it references FND_FLEX_VALUE_SETS, FND_FLEX_VALUES, FND_FLEX_VALUES_TL, and FND_LANGUAGES to resolve and translate flexfield values. Access is made through APPS synonyms, and the APPS_TS_TX_DATA tablespace is the typical storage location for these objects. The batch processor table OKC_ART_INT_BATPROCS_ALL tracks run-level status, while OKC_ART_INT_ERRORS captures per-row validation and load failures that users review after a validate-only or failed import run.

Usage Notes

The group is normally invoked indirectly. Standard Oracle Contracts setups submit the “Import Articles” and “Purge Articles Interface” concurrent programs, which call CONC_IMPORT_ARTICLES and CONC_PURGE_INTERFACE respectively. Oracle E-Business Suite 12.1.1 and 12.2.2 online forms do not call these routines directly; rather they submit the concurrent requests and then query OKC_ART_INT_BATPROCS_ALL and OKC_ART_INT_ERRORS to display batch status and errors. Custom integrations should call IMPORT_ARTICLES, IMPORT_VARIABLES, IMPORT_RELATIONSHIPS, IMPORT_FND_FLEX_VALUE_SETS, IMPORT_FND_FLEX_VALUES, or IMPORT_SCN_MAP with a distinct batch_processes_id and batch_number, and should first run with p_validate_only set to 'Y' to identify errors, then re-run with 'N' to commit. Because the procedures use bulk processing with a fetch size defaulting to 100, very large batches should tune this parameter to balance PGA usage against round trips. The group is not referenced by any other documented package (referenced by 0 packages), so it should be treated as a top-level load entry point. Note that the header comment shows the file as “noship,” indicating the package is not shipped as a patchable file and is delivered as part of the standard APPS schema installation.