How to resolve a Could not load Century Cutoff cache alert

Subscribe to Clarity's Could not load Century Cutoff cache alerts to catch a rare Oracle bug.

We don’t see Could not load Century Cutoff cache alerts often at ERP Suites. So when they do occur we look to the UBE job log first to verify it is true.

This type of alert typically appears when using RUNUBEXML to override Processing Options and Report Interconnects. If the associated XML files are longer than 256 characters, the XML parse code in the engine will not be able to read them correctly.

Could not load Century Cutoff cache is a reported Oracle bug. Open a service request with Oracle to initiate a fix.