Search Results ap_supplier_sites_all




Here's a comprehensive description of the AP_SUPPLIER_SITES_ALL table in Oracle E-Business Suite (EBS):

Table Name: AP_SUPPLIER_SITES_ALL

Purpose:
- Stores detailed information about supplier site locations and addresses
- Used in Accounts Payable (AP) module to track vendor site-specific details
- Supports multiple addresses/sites for a single vendor

Key Columns:
1. VENDOR_SITE_ID (Primary Key)
- Unique identifier for each supplier site
- Automatically generated sequence number

2. VENDOR_ID
- Links to PO_VENDORS table
- Identifies the parent vendor for this site

3. SITE_CODE
- Short code/identifier for the supplier site
- Used for quick reference and reporting

4. ADDR_LINE1, ADDR_LINE2, ADDR_LINE3
- Physical address details for the supplier site
- Street address, building, etc.

5. CITY
- City where the supplier site is located

6. STATE/PROVINCE
- State or province of the supplier site

7. POSTAL_CODE
- Zip or postal code for the site address

8. COUNTRY
- Country where the supplier site is located

9. PAYMENT_SITE_FLAG
- Indicates if this site can receive payments
- 'Y' or 'N' value

10. PURCHASING_SITE_FLAG
- Indicates if site can be used for purchasing
- 'Y' or 'N' value

11. RFQ_ONLY_SITE_FLAG
- Indicates if site is for Request for Quote purposes
- 'Y' or 'N' value

12. INACTIVE_DATE
- Date when the site becomes inactive
- Can be used to disable/retire a site

13. ORG_ID
- Operating unit identifier
- Supports multi-org architecture

14. TAX_REGISTRATION_NUMBER
- Tax ID or registration number for the site

15. PHONE_NUMBER
- Contact phone number for the site

16. FAX_NUMBER
- Fax number for the site

Additional Attributes:
- Supports multiple languages
- Tracks creation and last update dates/users
- Integrates with other EBS modules like Purchasing (PO)

Common Use Cases:
- Maintain vendor site information
- Support multiple addresses per vendor
- Enable site-specific purchasing and payment rules
- Track geographic distribution of suppliers

Performance Considerations:
- Indexed on VENDOR_ID and VENDOR_SITE_ID
- Large volume of records possible in multi-org environments

Related Tables:
- PO_VENDORS
- AP_SUPPLIER_SITES_ALL
- PO_VENDOR_SITES_ALL

Typical Query Example:
```sql
SELECT vendor_site_id,
vendor_id,
site_code,
addr_line1,
city,
country
FROM ap_supplier_sites_all
WHERE vendor_id = :specific_vendor
```

Important Notes:
- Part of Oracle's standard supplier management infrastructure
- Critical for vendor master data management
- Used across procurement and payables processes