In Oracle E-Business Suite, concurrent processing simultaneously executes programs running in the background with online operations. When a user runs a report, a request to run the report is generated. The command to run the report is a concurrent request. The program that generates the report is a concurrent program. Concurrent programs are started by a concurrent manager.

A new CPADMIN command line utility for E-Business Suite 12.2 consolidates various utilities for concurrent processing into a single menu-based utility. This ADADMIN-style utility can be used for multiple tasks, including:

• View Concurrent Manager status
• Clean CP tables
• Set Concurrent Manager diagnostics
• Start, stop, or verify an individual Concurrent Manager
• Rebuild Concurrent Manager views
• Move request files
• Analyze requests
• Configure request log/out file directory locations

Complete details for running the new CPADMIN utility are published here:

• Concurrent Processing Command-Line Utility (EBS 12.2 Setup Guide)

Related Articles

• Where should EBS Concurrent Managers be located?
• Webcast: Performance Tuning E-Business Suite Concurrent Manager

Source:https://blogs.oracle.com/stevenchan/new-cpadmin-utility-for-managing-concurrent-processing-now-available

The least invasive method of fine-tuning your E-Business Suite environment to your users’ needs is via personalizations.  If that approach is insufficient, you can create custom applications via Forms, Reports, and other technologies that segregate your customizations from the standard functionality provided with Oracle E-Business Suite.

If you’re considering that approach for customizing EBS 12.2, see:

• Creating a Custom Application in Oracle E-Business Suite Release 12.2 (Note 1577707.1)

This Note covers:

• Using adsplice to create a custom application
• Verifying the creation of custom products in the database 
• Running AutoConfig to set-up application servers
• Creating custom objects, including tables, indexes, and sequences
• Propagating changes to your file systems

Related Articles

• Webcast: “Migrating and Managing Customizations for Oracle E-Business Suite 12.2”
• New Whitepaper: Upgrading your Customizations to Oracle E-Business Suite Release 12
• To Customize or Not to Customize?
• Support Implications for Your EBS Customizations

Source: https://blogs.oracle.com/stevenchan/creating-custom-applications-in-ebs-122

Patch Wizard compares your EBS environment against a list of all recommended EBS patches. It creates a list of high-priority patches that your environment is missing.

You can use Patch Wizard to assess the impact of a specific patch on your environment.  Patch Wizard can report on a variety of areas, including:

• The applications patched
• File types installed
• New files introduced
• Existing files that are changed
• Flagged files that are changed
• Menu navigation trees affected — responsibilities that lead to patched functionality

Patch Wizard doesn’t have the ability to analyze business logic in the affected files, so it cannot report on functionality that is affected by new files delivered by a given patch.  You can review a patch’s README to see if there are functional changes introduced by a patch.

References

• Patch Tracking Utilities: EBS 12.1
• Patch Tracking Utilities EBS 12.2
• Patch Wizard FAQ (Note 976688.2)

Related Articles

• Providing Limited Patch Wizard Access to EBS End-Users
• Is it Possible to Run Patch Wizard Offline?

Source:https://blogs.oracle.com/stevenchan/using-patch-wizard-to-identity-files-affected-by-specific-patches

One of the most-common questions we see revolves around sizing for EBS upgrades — that is, the amount of resources required when upgrading from one EBS release to another. It is difficult to make general statements about these types of requirements that apply uniformly to all customer environments, since every customer’s database size, product usage mix, and concurrent end-user loads vary dramatically.

That said, our Applications Performance Group has published a whitepaper that describes an EBS 12.1.3 to EBS 12.2 upgrade:

• Oracle E-Business Suite 12.2: Upgrade Sizing and Best Practices (Note 1597531.1)

The upgrade scenario covers a 456 GB database prior to the upgrade, and compares the application tier sizes before and after the upgrade.  Individual tablespace requirements are listed in detail.

Related Articles

• Webcast: 12.2 Technical Upgrade Overview and Process Flow
• Creating Custom Applications in EBS 12.2
• Webcast: “Migrating and Managing Customizations for Oracle E-Business Suite 12.2”
• New Whitepaper: Upgrading your Customizations to Oracle E-Business Suite Release 12
• To Customize or Not to Customize?

Source: https://blogs.oracle.com/stevenchan/whitepaper%3a-e-business-suite-upgrade-sizing-and-best-practices