Considerations During Online Patching Cycle in 12.2, PRODUCT Functionalities that will be disabled

 E-Business Suite 12.2 now gives users the ability to apply patches while the system is online. But you may not have heard that there’s a catch: certain functionality is disabled while online patching is in progress

.hen the adop prepare phase is run, an “Online Patching In Progress” (ADZDPATCH) concurrent request is submitted and stays running until cutover is performed. This prevents certain predefined concurrent programs from being started, requiring them to already be active while a patching cycle is in progress (that is, while a database patch edition exists). The flow of control is as follows:

1. If the ADZDPATCH program is running, a message is displayed to the user. If it isn’t running, it is started.
2. The status of ADZDPATCH is determined. If it is pending, it may be waiting for an incompatible program to finish. After any such programs finish, the status will change to running and it will allow the prepare phase to proceed. A message to this effect is displayed to the user.
3. The next stage depends on whether the concurrent managers are running:

-If the concurrent managers are all down, the prepare phase continues, with ADZDPATCH entering a status of pending (with the highest priority) until the managers are started.

-If the concurrent managers are partially up, but there is no manager defined that can run ADZDPATCH, then the prepare phase will exit with an error.

-If the concurrent managers are up, and there is one defined that can run ADZDPATCH, processing will loop until ADZDPATCH changes status from pending to running (as long as no incompatible programs are running). The prepare phase then continues.

Note: ADZDPATCH is cancelled when the cutover phase is complete.

If you don’t want a custom program to run while online patching is in progress, you’ll have to make that program incompatible with ADZDPATCH.

To see a list of all the programs that are incompatible with ADZDPATCH, run the concurrent requestConcurrent Program Details Report.

Products Disabled in Online Patching Cycle:

During an online patching cycle, the following product functions will be restricted. Before you commence patching, you should therefore ensure there will be no requirement for any these actions or features until the cycle is complete.

Accounts Receivable:

• Users will not be able to create new Transaction Sources

Payroll:

• Users will not be able to define fast formulas or use the Fast Formula Assistant.
• Users will not be able to perform dynamic trigger maintenance.
• Users will not be able to create, update, or delete US cities.
• Data pump meta-mapper generator will be disabled.
• The Japanese Balance Dimensions concurrent program will be deferred to after the cutover phase is complete.
• Pension Calculation Setup cannot be used.
• US Localization Earnings and Deduction Setup cannot be used.
• Tax Withholding Rules Setup cannot be used.
• Wage Attachment Earnings Rules Setup cannot be used.
• Garnishment Rules Setup cannot be used.
• Quick Paint Reports cannot be used.
• Quantum Program Update Installer execution is unavailable.

Order Management:

• Creation of a new Defaulting Condition in the Attribute Defaulting Rules form is disabled, unless the same seeded condition already exists for a given attribute.

Warehouse Management:

• WMS Rule creation is restricted.

Inventory:

• Concurrent program Generate Stock Locator Flexfield Definition for Mobile Transactions will be disabled.

Public Sector Financials International:

• Users will not be able to run the following concurrent programs: Subledger Security: Apply Security and Subledger Security: Import/Export Data Fix.

Subledger Accounting:

• Users will not be able to validate the application accounting definitions.

Oracle Demand Planning:

• Demand plans will not be available for users.

Incentive Compensation:

• Transaction collection process for new mappings will not be available and any changed mapping will continue to use previous mapping rules.
• Users will not be able to run the Synchronize Classification Rulesets program.
• Users will not be able to use the Formula Generation feature.
• Users will not be able to specify new formulas or changes to compensation rules.