Search Results ap_sup_site_contact_int
The AP_SUP_SITE_CONTACT_INT
table in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 is a critical interface table used in the Accounts Payable (AP) module to facilitate the staging and validation of supplier site contact information before it is processed into the core system tables. This table plays a pivotal role in supplier management, particularly when importing or integrating contact details for supplier sites from external systems or during data migration.
Purpose and Functionality
The primary purpose ofAP_SUP_SITE_CONTACT_INT
is to serve as an intermediary storage area for supplier site contact data before it is validated and transferred to the base tables, such as AP_SUPPLIER_SITES
and AP_SUPPLIER_CONTACTS
. This ensures data integrity and compliance with Oracle EBS validation rules. The table is commonly used in scenarios involving bulk data imports, supplier onboarding, or system integrations where manual entry is impractical.
Key Columns and Structure
The table includes columns that capture essential supplier site contact attributes, such as:- VENDOR_SITE_CODE: Identifies the supplier site associated with the contact.
- VENDOR_CONTACT_CODE: A unique identifier for the contact record.
- FIRST_NAME, LAST_NAME: Stores the contact person's name details.
- EMAIL_ADDRESS, PHONE_NUMBER: Captures communication details.
- STATUS_FLAG: Indicates the processing status (e.g., 'P' for pending, 'E' for error).
- INTERFACE_LINE_ID: A unique identifier for each record in the interface table.
Integration and Data Flow
Data flows intoAP_SUP_SITE_CONTACT_INT
through manual inserts, SQL*Loader scripts, or integration tools like Oracle Integration Cloud (OIC). Once populated, the AP_SUPPLIER_INT_PKG
PL/SQL package processes the records, validating them against business rules (e.g., mandatory fields, format checks). Successful records are transferred to base tables, while failed records remain in the interface table with error details logged in AP_INTERFACE_REJECTIONS
.
Common Use Cases
- Supplier Data Migration: During EBS implementations, historical supplier contact data is loaded into this table before validation.
- Third-Party Integrations: External systems (e.g., CRM or procurement tools) push contact updates to this interface table.
- Bulk Updates Administrators use scripts to update multiple supplier contacts efficiently.
Best Practices
- Always validate data programmatically before loading to minimize errors.
- Monitor the
STATUS_FLAG
andAP_INTERFACE_REJECTIONS
to address processing failures promptly. - Schedule regular purges of processed records to maintain performance.
Conclusion
TheAP_SUP_SITE_CONTACT_INT
table is a cornerstone of Oracle EBS's supplier management framework, enabling efficient and error-resistant handling of supplier site contact data. Its design supports high-volume data operations while ensuring adherence to system validations, making it indispensable for organizations leveraging Oracle EBS for accounts payable and supplier lifecycle management.
-
Table: AP_SUP_SITE_CONTACT_INT
12.1.1
owner:AP, object_type:TABLE, fnd_design_data:SQLAP.AP_SUP_SITE_CONTACT_INT, object_name:AP_SUP_SITE_CONTACT_INT, status:VALID, product: AP - Payables , description: AP_SUP_SITE_CONTACT_INT holds Supplier contact data. The columns in the table map to corresponding columns in PO_VENDOR_CONTACTS table. The Oracle Payables application uses this information to create a new Supplier Contact record when th , implementation_dba_data: AP.AP_SUP_SITE_CONTACT_INT ,
-
Table: AP_SUP_SITE_CONTACT_INT
12.2.2
owner:AP, object_type:TABLE, fnd_design_data:SQLAP.AP_SUP_SITE_CONTACT_INT, object_name:AP_SUP_SITE_CONTACT_INT, status:VALID, product: AP - Payables , description: AP_SUP_SITE_CONTACT_INT holds Supplier contact data. The columns in the table map to corresponding columns in PO_VENDOR_CONTACTS table. The Oracle Payables application uses this information to create a new Supplier Contact record when th , implementation_dba_data: AP.AP_SUP_SITE_CONTACT_INT ,
-
APPS.AP_VENDOR_PUB_PKG dependencies on AP_SUP_SITE_CONTACT_INT
12.2.2
-
APPS.POS_BATCH_IMPORT_PKG dependencies on AP_SUP_SITE_CONTACT_INT
12.2.2
-
APPS.AP_VENDOR_PUB_PKG dependencies on AP_SUP_SITE_CONTACT_INT
12.1.1
-
APPS.AP_VENDOR_PUB_PKG dependencies on AP_SUP_SITE_CONTACT_INT
12.1.1
-
APPS.AP_VENDOR_PUB_PKG dependencies on AP_SUP_SITE_CONTACT_INT
12.2.2
-
APPS.POS_IMP_SUPP_PKG dependencies on AP_SUP_SITE_CONTACT_INT
12.2.2
-
SYNONYM: APPS.AP_SUP_SITE_CONTACT_INT
12.1.1
owner:APPS, object_type:SYNONYM, object_name:AP_SUP_SITE_CONTACT_INT, status:VALID,
-
APPS.AP_VENDOR_PUB_PKG dependencies on AP_SUPPLIER_INT_REJECTIONS
12.1.1
-
SYNONYM: APPS.AP_SUP_SITE_CONTACT_INT
12.2.2
owner:APPS, object_type:SYNONYM, object_name:AP_SUP_SITE_CONTACT_INT, status:VALID,
-
APPS.AP_VENDOR_PUB_PKG dependencies on AP_SUPPLIER_INT_REJECTIONS
12.2.2
-
VIEW: AP.AP_SUP_SITE_CONTACT_INT#
12.2.2
owner:AP, object_type:VIEW, object_name:AP_SUP_SITE_CONTACT_INT#, status:VALID,
-
VIEW: AP.AP_SUP_SITE_CONTACT_INT#
12.2.2
-
APPS.POS_IMP_SUPP_PKG dependencies on POS_PRODUCT_SERVICE_INT
12.2.2
-
PACKAGE BODY: APPS.POS_IMP_SUPP_PKG
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:POS_IMP_SUPP_PKG, status:VALID,
-
APPS.POS_BATCH_IMPORT_PKG dependencies on HZ_ORG_CONTACTS
12.2.2
-
APPS.POS_IMP_SUPP_PKG dependencies on AP_SUPPLIER_SITES_INT
12.2.2
-
APPS.POS_BATCH_IMPORT_PKG dependencies on AP_SUPPLIER_INT_REJECTIONS
12.2.2
-
APPS.POS_BATCH_IMPORT_PKG SQL Statements
12.2.2
-
TABLE: AP.AP_SUP_SITE_CONTACT_INT
12.2.2
owner:AP, object_type:TABLE, fnd_design_data:SQLAP.AP_SUP_SITE_CONTACT_INT, object_name:AP_SUP_SITE_CONTACT_INT, status:VALID,
-
PACKAGE: APPS.AP_VENDOR_PUB_PKG
12.2.2
owner:APPS, object_type:PACKAGE, object_name:AP_VENDOR_PUB_PKG, status:VALID,
-
PACKAGE: APPS.AP_VENDOR_PUB_PKG
12.1.1
owner:APPS, object_type:PACKAGE, object_name:AP_VENDOR_PUB_PKG, status:VALID,
-
APPS.POS_IMP_SUPP_PKG SQL Statements
12.2.2
-
PACKAGE BODY: APPS.POS_BATCH_IMPORT_PKG
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:POS_BATCH_IMPORT_PKG, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
APPS.AP_VENDOR_PUB_PKG SQL Statements
12.2.2
-
12.2.2 FND Design Data
12.2.2
-
APPS.AP_VENDOR_PUB_PKG SQL Statements
12.1.1
-
PACKAGE BODY: APPS.AP_VENDOR_PUB_PKG
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:AP_VENDOR_PUB_PKG, status:VALID,
-
12.1.1 FND Design Data
12.1.1
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
PACKAGE BODY: APPS.AP_VENDOR_PUB_PKG
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:AP_VENDOR_PUB_PKG, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
APPS.POS_BATCH_IMPORT_PKG dependencies on POS_SUPPLIER_INT_REJECTIONS
12.2.2
-
APPS.POS_BATCH_IMPORT_PKG dependencies on HZ_ORIG_SYS_REFERENCES
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.2.2 DBA Data
12.2.2
-
TABLE: AP.AP_SUP_SITE_CONTACT_INT
12.1.1
owner:AP, object_type:TABLE, fnd_design_data:SQLAP.AP_SUP_SITE_CONTACT_INT, object_name:AP_SUP_SITE_CONTACT_INT, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
PACKAGE BODY: APPS.POS_BATCH_IMPORT_PKG
12.2.2
-
APPS.POS_BATCH_IMPORT_PKG dependencies on HZ_PARTIES
12.2.2
-
APPS.AP_VENDOR_PUB_PKG dependencies on MO_GLOBAL
12.2.2
-
APPS.AP_VENDOR_PUB_PKG dependencies on AP_SUPPLIERS
12.1.1
-
PACKAGE BODY: APPS.POS_IMP_SUPP_PKG
12.2.2
-
PACKAGE BODY: APPS.AP_VENDOR_PUB_PKG
12.1.1
-
PACKAGE BODY: APPS.AP_VENDOR_PUB_PKG
12.2.2
-
APPS.AP_VENDOR_PUB_PKG dependencies on FND_API
12.1.1