Search Results fv_ccr_data_load_pkg




Overview
Explore in AI Chat

Overview

The APPS.FV_CCR_DATA_LOAD_PKG package is a component of the Oracle E-Business Suite Federal Government reporting infrastructure, specifically associated with the Central Contractor Registration (CCR) integration for vendor and trading partner data. In Oracle EBS 12.1.1 and 12.2.2, CCR-related processing supports the validation, registration, and synchronization of supplier information with external government registries. The package encapsulates the programmatic logic required to ingest external CCR data files, transform their contents, and load or update the corresponding records within the EBS vendor and organization schema.

The package header carries the RCS identifier FVCCRLDS.pls 120.0, dated 2004/12/06, indicating that the package has been a stable element of the FV (Federal Vendor/CCR) module for many release cycles. As an OTHER-classified API, it is not part of Oracle's published public API surface, and its procedures are intended for controlled internal invocation rather than broad customer extension.

Key Procedures and Functions

The ETRM metadata documents two callable elements within the package:

  • MAIN — The primary driver procedure. Its signature exposes parameters for file location, file name, file type, update type, a DUNS number, an XML import indicator, and an insert-data indicator. This confirms that MAIN orchestrates the end-to-end file-based load process: it accepts an external data file, determines the processing mode based on the supplied flags, and dispatches the appropriate load, update, or insert logic. The presence of errbuf and retcode out-parameters indicates the procedure is designed to be called from an Oracle concurrent program, with standard success/failure reporting back to the concurrent manager.
  • GET_TERRITORY_CODE — A helper function that resolves a territory (country) code, most likely translating external CCR country references into the internal territory identifiers used by Oracle EBS. It supports the data normalization step within MAIN.

Tables Accessed

The documented tables referenced through APPS synonyms reflect the package's role as a data-loading utility:

  • FV_CCR_FILE_TEMP — A staging table holding the raw contents of the incoming file prior to validation and transformation.
  • FV_CCR_BPN_CLOB_DATA — Stores CLOB-based payload data, consistent with XML or large-text CCR extracts.
  • FV_CCR_VENDORS and FV_CCR_VENDORS_S — The base and secondary (translation) vendor tables where CCR supplier records are persisted.
  • FV_CCR_ORGS — Stores organization-level CCR registration data.
  • FV_CCR_PROCESS_GT — A global temporary table used for intermediate processing within a session.
  • FV_CCR_PROCESS_REPORT — Captures processing outcomes and error reporting for review.
  • FND_TERRITORIES and FND_LOOKUP_VALUES — Standard reference tables used to validate and decode territory and lookup values, supporting GET_TERRITORY_CODE.
  • DUAL and PLITBLM — Utility references for scalar selection and PL/SQL table handling.

Usage Notes

FV_CCR_DATA_LOAD_PKG is not referenced by any other documented package, which indicates it is a top-level entry point rather than a reusable library. It is most appropriately invoked from a concurrent program registration, with MAIN serving as the executable procedure and its file-location, file-name, file-type, update-type, and flag parameters mapped to concurrent program arguments. The errbuf/retcode pair confirms this pattern.

Because the package is classified as OTHER and carries an noship header marker, direct custom calls should be undertaken with caution. In 12.2.2 online patching environments, any custom wrapper must respect editioning and the APPS synonym layer. Typical runtime flow is: stage the file into FV_CCR_FILE_TEMP, validate against FND_TERRITORIES and FND_LOOKUP_VALUES, process through FV_CCR_PROCESS_GT, and persist results into the vendor, organization, and report tables.