Enterprise PCM: move from the original agent and check diagnostic retention

Why it matters

Users tied to original agent interfaces can lose their familiar diagnostic workflow after the 26.11 update, while teams requiring more than the default recent 500 calculation-run statistics may lose historical performance evidence from the application UI.

First step

Confirm the environment's 26.11 status and the Enterprise PCM owner's diagnostics/retention needs; run one controlled enhanced-agent check before changing user instructions or configuration.

Suggested owner

Enterprise PCM finance/model owner and Cloud EPM Service Administrator

Who should check?

Organizations using Oracle Cloud Enterprise Profitability and Cost Management (Enterprise PCM) with users or runbooks tied to the original PCM Agent or PCM Agent Performance Assistant, or with calculation-performance reporting that needs diagnostic statistics older than the most recent 500 runs. NetSuite ERP customers who do not use Enterprise PCM are not automatically affected.

Important limits and exceptions

Oracle's August 2026 note expected original PCM Agent removal with 26.10 and Performance Assistant access exclusively through the enhanced agent starting 26.11, while the later October notice said both originals would become unavailable in 26.11. November guidance says both are decommissioned. Confirm the applicable tenant version and do not invent a universal removal day. The 26.11 removal applies to the original PCM Agent and original PCM Agent Performance Assistant, not the enhanced PCM Agent or every NetSuite AI feature. Oracle's November release documentation describes the originals as decommissioned, but a future-dated readiness notice alone does not prove any specific customer's environment has received 26.11. The enhanced agent supports calculation performance analysis; do not assume every prior user interaction, permission or output is identical without testing. The default retains diagnostic statistics for the latest 500 calculation runs; older runs' diagnostic statistics are purged from the Calculation Analysis experience. Oracle documents an optional EPCM_PURGE_JOB_RUNS_DAYS_OLDER substitution variable accepting 1 to 180 as a retention override. An override should be agreed with the finance/administration owner and tested against the actual environment; neither option is a promise of permanent audit-history storage. No customer environment has been inspected.

Published milestones

October 2026 / Cloud EPM 26.10 — replacement capability documentedOracle documents the enhanced PCM Agent's calculation-performance analysis, including completed run statistics, bottlenecks and follow-up questions, and announces removal of the original tools with 26.11.
November 2026 / Cloud EPM 26.11 — legacy tools removed in the documented updateThe original PCM Agent and its Performance Assistant are no longer available in the described 26.11 product experience. Verify the actual tenant update before concluding that a customer's interface has changed.
Current November readiness guidance — diagnostic retentionEnterprise PCM keeps statistics for the most recent 500 calculation runs by default; an approved 1–180-day substitution-variable override is available for differing retention needs.

Check your Oracle account notice before scheduling an update.

A practical response

Ask the Enterprise PCM owner to verify whether the environment is on 26.11 and identify any users, bookmarks or runbooks still tied to the original PCM Agent or Performance Assistant.
Test an approved calculation-performance analysis through the enhanced PCM Agent, comparing statistics, bottleneck findings, roles and expected user instructions without presuming equivalent results.
Document current calculation-run volume and the business need for retaining diagnostic statistics. If the default latest-500-run retention is insufficient, have the owner approve and test an appropriate EPCM_PURGE_JOB_RUNS_DAYS_OLDER value (1 to 180); preserve required evidence through authorized retention procedures.
Update one agreed operating guide, capture tested outcomes and obtain finance/administration UAT before wider adoption.

What we’ll review

With the Enterprise PCM owner and authorized Service Administrator, confirm actual environment update number and maintenance notice, affected user access and roles, saved instructions or bookmarks using the original agent, typical calculation volumes, reporting and retention obligations, plus an approved representative completed calculation run for comparing the enhanced agent's diagnostics. Do not collect or export production financial data without approval.

Sources and updates

Oracle documentation

Oracle October 2026 Cloud EPM: enhanced PCM Agent calculation performance capabilities and 26.11 retirement ↗Oracle publication/update date not stated on this page. · Last successful source check: 2026-11-11

Oracle August 2026 enhanced PCM Agent notice: earlier 26.10/26.11 timing ↗Oracle publication/update date not stated on this page. · Last successful source check: 2026-11-11

Oracle Cloud EPM November 2026 important actions: Financial Reporting stops working with 27.02 ↗Oracle publication/update date not stated on this page. · Last successful source check: 2026-11-07

Update history

2026-11-11 — First identified for Ebenstead and prepared as November 11 historical catch-up from October and November Oracle Cloud EPM 2026 readiness guidance. Oracle's 26.11 change is a product update, not an exact universal customer deployment date.

Follow this topic via RSS

How Ebenstead helps

Enterprise PCM Agent and Diagnostics Transition Pilot — proposed scoped one-off

Client-signed Functional Requirements Document for one authorized Enterprise PCM environment, one agreed calculation workflow and retention decisions
Original-to-enhanced agent workflow inventory, one controlled calculation-diagnostics comparison and approved role/access exceptions
Documented diagnostic retention decision, representative evidence and revised runbook with rollback/exception notes
Completed testing, documentation, client UAT and final client signoff

Scope

This is a proposed one-off delivery concept, not an individually approved package, fixed-price commitment or claim of customer exposure. Broader model/rule redesign, rebuilding diagnostic repositories, enterprise-wide AI adoption or cross-environment security changes require a separately scoped project.

Ongoing administration

Existing Administrator Subscription work may include bounded role, configuration and runbook assistance only where separately agreed scope, capacity and customer authorization permit; model redesign, new integrations and extensive historical data restoration are outside routine administration.