In Financial Consolidation & Close Cloud Service (FCCS), Why Does The Test Pod's Version Change When Production Pods Are Patched And At Other Times Aside From The Weekend Of The Monthly Patch?
(Doc ID 2576571.1)
Last updated on FEBRUARY 19, 2020
Applies to:Oracle Financial Consolidation and Close Cloud Service - Version 18.04.62 and later
Information in this document applies to any platform.
When a monthly patch is applied on a Test system, a certain build number is seen (e.g., 19.06.50). When the montly patch is applied to the Production system a couple of weeks later, a different version number is subsequently seen in both machines. This is expected in Production as there may be code changes throughout the interim, but why does the version in Test also get updated at that time?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document