Implementing Corporate Branding and Custom Logo Configuration in Oracle EBS 12.2.x

Corporate Branding in Oracle E-Business Suite (EBS) enables organizations to customize the application's visual appearance by displaying company logos, banners, and brand-specific images. This customization enhances the user experience, strengthens corporate identity, and provides a consistent look and feel across Oracle Applications. In Oracle EBS 12.2.x, branding images are typically configured through profile options and stored in the OA Framework media repository, allowing organizations to replace default Oracle branding with their own corporate identity.

Purpose

• Display company logo in Oracle EBS pages.
• Provide a customized look and feel.
• Improve user recognition and corporate identity.
• Commonly used after Oracle EBS upgrades, clones, or new implementations.

Where It Appears

Typically in:

• Login page
• Home page
• Navigator page
• Self-Service (OA Framework) pages
• Application headers

Example Steps

1. Create a logo image (PNG/JPG/GIF).

2. Upload it to the EBS web server under: $OA_MEDIA

Action is performed on the Application server:

i. Open a telnet/PuTTY session to the Application server and source Applications environment.

ii. Navigate to the $OA_MEDIA directory.

iii. Copy the custom image file to this directory and make sure the image size is 155*20 pixels and permissions are set properly.

3. Set the profile option: 

Change profile option:

i. Login to Applications as System Administrator.

ii. Select: System Administrator > Profile - System.

iii. Query profile "Corporate Branding Image for Oracle Applications".

iv. Change the SITE level value to "(OA_MEDIA_PATH)/Company_Name_logo.gif"

v. Save the change.

4. Clear cache:

Functional Administrator -> Core Services -> Caching Framework -> Clear All Cache

5. Restart Apache if necessary.

Compilation of Invalid APPS Schema Objects After Oracle EBS 12.2.x Upgrade

In Oracle EBS 12.2.x upgrades, compiling invalid objects in the APPS schema is a critical post-upgrade activity. You can use the following notes in your upgrade documentation or interview discussions.

Why APPS Invalid Objects Occur

Invalid objects in the APPS schema may occur due to:

• Database upgrade (11g → 19c)
• Oracle EBS upgrade (12.1.x → 12.2.x / 12.2.14)
• Failed ADOP patching cycle
• Missing grants or synonyms
• Dependency changes in packages, views, and materialized views
• Custom objects referencing obsolete Oracle objects

Check Invalid Objects

SELECT object_name, object_type FROM dba_objects WHERE owner='APPS' AND status='INVALID';

Compile invalid object whole APPS Schema:

$ . /apps/EBS122/EBSapps.env run

[applmgr@proderpappl ~]$ sqlplus apps/apps_pwd

SQL*Plus: Release 10.1.0.5.0 - Production on Thu Jan 15 10:42:43 2026

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

Connected to:

Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production

SQL>@$AD_TOP/sql/adutlrcmp.sql 

Session Information:

INSTANCE_NAME    SCHEMA_NAME     EDITION_NAME    SYSDATE

---------------- --------------- --------------- ----------------

PRODCDB          APPS            ORA$BASE        2026-01-15 10:42

Invalid Objects per Owner (before compile):

OWNER                              ACTUAL       STUB      TOTAL

------------------------------ ---------- ---------- ----------

APPS                                   26          0         26

Compiling Objects...

PL/SQL procedure successfully completed.

Elapsed: 00:00:08.58

Invalid Objects per Owner (after compile):

OWNER                              ACTUAL       STUB      TOTAL

------------------------------ ---------- ---------- ----------

APPS                                   26          0         26

Commit complete.

Disconnected from Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production

Parallel recompilation:

SQL>EXEC UTL_RECOMP.RECOMP_PARALLEL(); 

                                        OR

SQL>EXEC UTL_RECOMP.RECOMP_PARALLEL(8);

Run AD Administration

[applmgr@proderpappl ~]$ adadmin

Navigate to:

            AD Administration Main Menu
   --------------------------------------------------
   1.    Generate Applications Files menu
   2.    Maintain Applications Files menu
   3.    Compile/Reload Applications Database Entities menu
   4.    Maintain Applications Database Entities menu
   5.    Change Maintenance Mode
   6.    Exit AD Administration

Enter your choice [6] : 3

        Compile/Reload Applications Database Entities
   ---------------------------------------------------
   1.    Compile APPS schema
   2.    Compile menu information
   3.    Compile flexfields
   4.    Reload JAR files to database
   5.    Return to Main Menu

Enter your choice [5] : 1

One by one compile invalid object:

[applmgr@proderpappl ~]$ sqlplus apps/apps_pwd

SQL*Plus: Release 10.1.0.5.0 - Production on Thu Jan 15 13:53:42 2026

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

Connected to:

Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production

SQL> ALTER PACKAGE APPS.xx_package COMPILE;
SQL> ALTER PACKAGE APPS.xx_package COMPILE BODY;
SQL> ALTER VIEW APPS.xx_view COMPILE;

SQL> ALTER SYNONYM APPS.xx_synonym COMPILE;

Oracle Recommended Script

Run Oracle's recompilation utility:

Connect as SYSDBA and run the script through SQL*Plus:
$sqlplus "/ as sysdba"

SQL> @?/rdbms/admin/utlrp.sql