Search Results get_profile_option

Overview

FV_CCR_UTIL_PVT is a private PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified as a PVT (private) API within the Federal Financials (FV) module. The package supports the Common Cost Reimbursement (CCR) functionality, which is used by federal agencies to process vendor and supplier information in compliance with government-wide requirements such as those defined by the Central Contractor Registration (CCR) / System for Award Management (SAM). The package encapsulates utility logic for validating, inserting, and updating supplier records, supplier sites, bank accounts, and associated organization data. Because it is a private package, it is not intended as a public integration API but rather serves as an internal utility layer invoked by other Federal Financials components, concurrent programs, and CCR processing workflows. Its status is VALID, and it depends only on the SYS.STANDARD package at the database level, meaning its functional dependencies on EBS objects are expressed through SQL statements referencing APPS synonyms rather than through declared package-level references.

Key Procedures and Functions

The ETRM metadata documents 25 procedures and functions, of which the following are named. They fall into several functional groupings:

• Organization context routines — EXISTING_ORG_CONTEXT, CHECK_NON_USER_ORG_ASGNMT, GET_ORG_PAYSITE_ID, GET_ORG_MAINADDRSITE_ID: establish and verify the operating unit / organization context for supplier and site processing.
• Bank and payment data routines — GET_BANK_BRANCH_INFORMATION, GET_BANK_ACCOUNT_INFORMATION, CREATE_BANK_ACCOUNT, UPDATE_BANK_ACCOUNT, PROCESS_BANK_ACCOUNT_USES: retrieve, create, and maintain external bank account and bank branch details for suppliers.
• Supplier and site maintenance routines — INSERT_VENDOR, UPDATE_VENDOR, INSERT_VENDOR_SITE, UPDATE_VENDOR_SITE, FV_PROCESS_VENDOR, CHECK_SUPPL_TOBE_MERGED: create and update supplier and supplier site records and evaluate suppliers against merge conditions.
• Validation and lookup routines — GET_FEDERAL_INDICATOR, GET_PROFILE_OPTION, GET_LOOKUP_DESC, CHECK_TAXPAYERID_DIFF, DELETE_PLUSFOUR_ASSIGNMENTS: validate federal-specific attributes, retrieve profile option and lookup values, compare taxpayer identifiers, and maintain Plus-Four postal code assignments.

The exact parameter lists are not published in the metadata and are therefore not reproduced here.

Tables Accessed

The package reads and writes data through APPS synonyms across supplier, party, location, and payment tables:

• AP_SUPPLIERS, AP_SUPPLIER_SITES_ALL, AP_DUPLICATE_VENDORS_ALL — core supplier and site storage, plus duplicate vendor detection.
• IBY_EXTERNAL_PAYEES_ALL, IBY_EXT_BANK_ACCOUNTS — external payee and bank account records maintained during bank account processing.
• HZ_PARTIES, HZ_PARTY_SITES, HZ_LOCATIONS, HZ_ORGANIZATION_PROFILES — TCA party, site, location, and organization profile data underpinning supplier identity and address information.
• FV_CCR_VENDORS, FV_CCR_ORGS, FV_CCR_CLASS_CODES, FV_CCR_FLAGS, FV_CCR_PROCESS_REPORT — Federal CCR-specific staging, classification, flag, organization, and reporting tables.
• FND_LOOKUP_VALUES — reference lookup values used by validation routines such as GET_LOOKUP_DESC and GET_FEDERAL_INDICATOR.

Usage Notes

As a private (PVT) package, FV_CCR_UTIL_PVT is not exposed as a supported public API and is referenced by zero other packages according to the metadata, indicating that it is invoked primarily by forms, concurrent programs, or other application logic internal to Federal Financials CCR processing rather than by external customizations. Developers integrating with supplier or bank account maintenance in a federal context should preferentially use the corresponding public APIs (for example, AP_VENDOR_PUB_PKG or IBY payment APIs); FV_CCR_UTIL_PVT should be treated as an internal implementation artifact. Because it is documented as VALID in both 12.1.1 and 12.2.2, it can be relied upon as present in those releases, but its private classification means its interface may change between patches without notice. Custom code should not call it directly without a formal supportability assessment.