Search Results okl_cure_reports_all




Overview
Explore in AI Chat

Overview

The AP_SUPPLIER_CONTACTS table is a core data object within the Oracle E-Business Suite Payables (AP) module. It serves as the central repository for storing contact information associated with supplier sites. This table is essential for managing communication and operational relationships with vendors, enabling the storage of multiple contacts per supplier site for various purposes such as ordering, invoicing, and payment inquiries. Its role is to support business processes that require specific points of contact, ensuring accurate and efficient communication flow between an organization and its suppliers.

Key Information Stored

The table's primary key is the VENDOR_CONTACT_ID, a unique system-generated identifier for each contact record. A critical foreign key relationship exists via the VENDOR_SITE_ID column, which links each contact to a specific record in the AP_SUPPLIER_SITES_ALL table. While the provided ETRM metadata does not list all columns, typical and important columns in this table include the VENDOR_ID (linking to the main supplier), contact name fields (FIRST_NAME, LAST_NAME), functional roles (e.g., AREA_CODE for contact type), communication details (EMAIL_ADDRESS, PHONE), and status flags (INACTIVE_DATE). This structure allows for detailed management of contact hierarchies and responsibilities.

Common Use Cases and Queries

A primary use case is retrieving active contacts for a specific supplier site for purposes like generating remittance advice emails or populating contact lists on purchase orders. Common reporting needs include listing all contacts for a vendor across its sites or identifying the primary invoice contact for payment-related communications. Sample SQL patterns often involve joins to AP_SUPPLIERS and AP_SUPPLIER_SITES_ALL. For example, to find active contacts for a given vendor number:

  • SELECT ascnt.FIRST_NAME, ascnt.LAST_NAME, ascnt.EMAIL_ADDRESS, asite.VENDOR_SITE_CODE FROM AP_SUPPLIER_CONTACTS ascnt JOIN AP_SUPPLIER_SITES_ALL asite ON ascnt.VENDOR_SITE_ID = asite.VENDOR_SITE_ID WHERE asite.VENDOR_ID = :p_vendor_id AND ascnt.INACTIVE_DATE IS NULL;

Another common pattern is querying contacts by their functional role to support automated business workflows.

Related Objects

As indicated by the metadata, AP_SUPPLIER_CONTACTS has direct foreign key relationships with several key tables. The most significant is with AP_SUPPLIER_SITES_ALL, which is fundamental for contextualizing a contact within a specific physical or operational supplier location. The metadata also shows a foreign key relationship from the OKL_CURE_REPORTS_ALL table in the OKL (Oracle Lease and Finance Management) module, where VENDOR_CONTACT_ID is referenced, demonstrating cross-module integration. Furthermore, this table is typically accessed via standard Oracle APIs, such as the AP_VENDOR_PUB package, for creating and maintaining supplier contact data programmatically, ensuring data integrity.