Home › Discussions › Questions & Answers › Oracle E-Business Suite 12.2.11 upgrade to version 12.2.12

Oracle E-Business Suite 12.2.11 upgrade to version 12.2.12

Avatar photoCustomer Questions & Answers 9 replies

We are planning to upgrade our EBS from R12.2.10 to R12.2.12 (Path B). Our core modules are GL, AP, CE, FAH, SLA, and INV. We need confirmation on whether any major existing features or processes in these modules would be impacted, besides the new enhancements provided by ECC and dashboards.

9 replies

  • Support Enginatics

    For customers upgrading to R12.2.12, it is crucial to review the detailed Oracle documentation. Specifically, you should consult the R12.1 / R12.2 : Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Documents (Doc ID 1302189.1), which provides comprehensive detail divided into separate product families sections to confirm the impact on your GL, AP, and FAH processes.

  • Avatar photoCustomer

    We are simultaneously deploying the Oracle Enterprise Command Center Framework Release v11. What technical details should we confirm regarding the database connection configuration for ECC V11?

  • Support Enginatics

    During the ECC V11 installation and integration , key database parameters must be correctly defined in the configuration files (e.g., `ecc-config.properties`). You must specify the `EBS_DB_URL` using the JDBC thin connection string, ensuring the load balance and failover settings are correctly configured, along with the `EBS_DB_USERNAME` (typically APPS) and `EBS_ECC_USER` (DEVELOPER).

  • Avatar photoCustomer

    We need to ensure that our database patching, which is 19c, uses the correct OPatch version during the upgrade. Can you confirm the proper OPatch version for 19c databases in a recent context?

  • Support Enginatics

    While the OPatch version number remains 12 (e.g., OPatch 12.2.0.1.42), it is correctly designed for the Oracle Database 19c version. It is essential to ensure you are using the version that has been recently released and certified for your specific 19c update level.

  • Avatar photoCustomer

    After patching, we usually run checks for patch conflicts. If we are applying the 12.2.12 Release Update Pack (RUP), can we skip the manual patch conflict determination steps?

  • Support Enginatics

    It is generally safe to trust the official RUP patching documents regarding pre-patch analysis if you follow the prescribed path. However, for robust internal verification, you can always utilize the Blitz Report mechanism querying AD_PATCH.IS_PATCH_APPLIED to confirm if specific bug numbers were implicitly handled or applied correctly.

  • Avatar photoCustomer

    Since we rely heavily on financial reporting, how can we quickly validate the post-upgrade financial data integrity?

  • Support Enginatics

    Utilize the Blitz Report financial toolkit, which includes specialized reports for GL Account Analysis and Balance reporting. By running saved, validated reports pre- and post-upgrade, you can quickly verify that complex data like YTD figures and Parent Totals are accurate in the R12.2.12 environment.

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