Search Results kasih keluarga jiwa madani logo




The PON_APPLICATION_LOGO table in Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2 is a critical repository for storing logo-related metadata used in the Procurement (iProcurement) and Sourcing modules. This table is part of the Oracle Purchasing (PO) schema and plays a key role in branding and customization within the application, particularly for supplier-facing portals and documents. Below is a detailed breakdown of its structure, purpose, and usage:

1. Purpose and Functional Context

The PON_APPLICATION_LOGO table stores binary or reference data for logos displayed in Oracle iProcurement, Sourcing, and Supplier Portal interfaces. These logos are typically used in:
  • Supplier Portal: Branding for supplier-facing pages.
  • Print Documents: Purchase orders, RFQs, and other procurement documents.
  • Email Notifications: Logos embedded in automated communications.
This table ensures consistent branding across procurement workflows, adhering to organizational or client-specific visual identity requirements.

2. Table Structure and Key Columns

The table's structure includes columns to manage logo metadata, storage, and associations. Key columns may include:
  • LOGO_ID: Primary key, uniquely identifying each logo entry.
  • LOGO_NAME: Descriptive name for the logo (e.g., "Corporate_Logo").
  • LOGO_TYPE: Specifies the logo's format (e.g., JPEG, PNG) or usage context.
  • LOGO_DATA: BLOB column storing the actual binary logo image (or a reference path).
  • APPLICATION_ID: Links to FND_APPLICATION to associate the logo with a specific EBS module.
  • CREATION_DATE, CREATED_BY: Audit columns for tracking record creation.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY: Audit columns for modifications.

3. Integration with Oracle EBS Modules

The table integrates with:
  • iProcurement: Logos appear on self-service requisition pages.
  • Sourcing (Negotiations): Branding for auction/RFQ event pages.
  • Supplier Portal: Customizes the supplier login and dashboard.
Logos are typically assigned via profile options (e.g., POR: Logo Image) or backend configurations.

4. Technical Considerations

  • Storage: Large BLOB data may impact performance; some implementations use file system references instead.
  • Customization: Logos can be updated via APIs (e.g., PO_LOGO_PUB) or direct SQL (with caution).
  • Cache: Logo images may be cached by the Oracle Application Framework (OAF) for faster rendering.

5. Version-Specific Notes

  • 12.1.1: Basic BLOB storage with limited metadata.
  • 12.2.2: Enhanced support for high-resolution logos and additional metadata columns.

6. Best Practices

  • Use standard APIs for logo updates to avoid corruption.
  • Optimize logo file sizes to balance quality and performance.
  • Test logo visibility across all modules after deployment.
In summary, the PON_APPLICATION_LOGO table is a foundational component for branding in Oracle EBS Procurement, ensuring visual consistency while adhering to technical and functional constraints.