Home › Discussions › Questions & Answers › Oracle Enterprise Command Center Framework Release 12.2 installation and integration with Oracle EBS 12.2.8

Oracle Enterprise Command Center Framework Release 12.2 installation and integration with Oracle EBS 12.2.8

Avatar photoCustomer Questions & Answers 11 replies

During the Oracle Enterprise Command Center Framework installation and integration phase in our EBS 12.2.8 environment, specifically when running `perl patchEccFiles.pl`, we encountered an `ORA-00904: invalid identifier` error related to the package `FND_ECC_UTIL_MLS_PVT`. What is the likely cause and resolution for this critical error?

11 replies

  • Support Enginatics

    The `ORA-00904` error during `patchEccFiles.pl` execution, particularly referencing `FND_ECC_UTIL_MLS_PVT.CONVERTORALANGCODETOBCP47`, indicates that necessary database objects or prerequisite code (often related to multilingual support or base ECC objects) are either missing or invalid. This typically points to an issue where core ECC or required FND patches have not been fully or correctly applied, compiled, or loaded into the database.

  • We successfully completed the integration step, checking system profile options like `s_ecc_protocol` and running autoconfig. Why would this package still be missing or invalid?

  • Support Enginatics

    While basic integration steps like running autoconfig confirm profile option values and OHS configuration , the `patchEccFiles.pl` script runs post-database object application. The issue suggests a preceding database patch application failure or an environmental setup issue that prevented the necessary PL/SQL packages from compiling correctly in the APPS schema.

  • If we are troubleshooting similar HTTP 400 errors post-installation, what specific resource should we check? We are seeing ‘No function from PO_PCC_ECC_ODERS_FUNC is available to current logged in responsibility id’.

  • Support Enginatics

    That specific `400 Bad Request` error is commonly linked to missing security grants or functional exclusions for the ECC dashboards. You should check the corresponding MOS document, Error 400 Bad Request ‘No function from’ Is Appearing For Procurement ECC Dashboard (Doc ID 2660547.1), to ensure the responsibility ID has the necessary permissions and functions assigned.

  • We need to quickly diagnose if critical base patches (AD/TXK) are missing, which could cause compilation issues.

  • Support Enginatics

    The quickest diagnostic method is to use a customized Blitz Report to verify patch application status. Your DBA team can run an instantaneous check using the AD_PATCH.IS_PATCH_APPLIED function directly from EBS, bypassing SQL*Plus access latency.

  • Once the ECC installation is confirmed complete, can we use Blitz Report to export the data powering ECC dashboards?

  • Support Enginatics

    Yes, Blitz Report allows you to develop EBS reports using the Oracle Enterprise Command Center SQLs directly, often in under five minutes. This facilitates the export of enriched dashboard data to Excel for deeper analysis or archival.

  • We’ve confirmed ECC V5 installation is complete on 12.2.9. Thank you for the guidance.

  • Support Enginatics

    I am happy to hear that your installation and configuration were successful. Feel free to leverage the extensive features of Blitz Report for ongoing ECC administration and reporting needs.

  • You must be logged in to reply to this post.