Period close is not the best time to discover that a new workspace has no data.
Oracle's Cost Accounting Close Workspace is designed to help cost accountants and financial controllers see the exceptions that matter, understand what is blocking close, and take the next priority action. It is a very useful addition. But it is not magic. It depends on the same foundations that make every close successful: correct access, current processing, clean data, and the right operating sequence.
If the workspace is blank, incomplete, or confusing, start with the basics before assuming the AI feature is broken.
What the workspace is designed to help with
Oracle provides six main areas in the workspace.
- Period Close Validation Exceptions shows blockers around Inventory, Cost Processing, Final Accounting, and Transfers.
- Inventory Valuations helps compare current and previous periods and highlights valuation trends.
- Gross Margins brings revenue, cost, and margin movement into one view.
- Subledger Period Status shows the status across General Ledger, Payables, Receivables, and Cost Accounting.
- Priority Actions highlights important pending processes and gives direct access to the required work.
- Communications helps create a context-aware close update for stakeholders.
The workspace is there to guide the close. It does not replace the accounting judgement, reconciliation, or controls your organisation already follows.
Step 1: Confirm the feature is enabled
The first check is simple but easy to miss.
Go to Setup and Maintenance and open Manage Cost Accounting Profile Options. Search for:
ORA_CST_PERIOD_CLOSE_AGENTIC_APP_ENABLED
Set the Site-level value to Yes, save, and sign in again.
If this profile option is still No, the workspace will not behave as expected regardless of any other setup work.
Step 2: Confirm the user can reach the workspace
Oracle's documented navigation is:
Home -> Supply Chain Execution -> Quick Actions -> Show More -> Cost Processing -> Cost Accounting Close Workspace
If a user cannot see it, do not begin with the agent settings. First confirm the job role, page access, and assigned privileges.
Step 3: Treat security as part of the configuration
The workspace does not bypass Fusion security. Users need a configured role with the required Cost Management web-service privileges, the AI runtime duty role, and permission groups enabled in Security Console.
That means a user may be able to open the workspace but still not see the cost organisation or information they expect. Access to the underlying data remains important.
This is a good time to involve the security owner. Do not try to solve a data-access issue by giving the whole team a broad administrative role.
Step 4: Check the cost organisation context carefully
The workspace works one cost organisation, one cost book, and one period at a time.
When you use Ask Oracle to change context, names are case-sensitive and must match the values defined in Fusion exactly.
For example:
"Change Cost Organization to ZCST-Vision Ops, Cost Book to Primary, Period to APR-26."
If the workspace says that a cost organisation cannot be found, check the exact spelling, case, cost book, period, and user access before raising a defect.
Step 5: Make sure the underlying processes are current
The workspace reads the results of real processes. It cannot show a useful close picture if those processes are behind.
The most important checks are:
- The Cost Reports processor runs on a schedule.
- Inventory valuation, COGS, and gross margin information are current.
- Upstream invoice information from Payables and Receivables has been processed.
- Cost Accounting has processed the relevant invoices and transactions.
- Subledgers are being closed in the agreed sequence.
This is the point many teams miss. The workspace is not a replacement for the close process. It gives you a better view of that process.
A simple "no data" troubleshooting path
When the workspace has no data or limited data, use this order.
- Is the feature profile option enabled at Site level?
- Has the user signed out and signed back in after the change?
- Can the user open the workspace from the documented navigation?
- Does the user have access to the selected cost organisation, cost book, and period?
- Are the organisation, book, and period names entered exactly, including case?
- Is the Cost Reports processor scheduled and completing successfully?
- Have upstream subledger and Cost Accounting processes completed for the period?
- Is the period really the one you intend to review?
- Does the issue occur for one user, one cost organisation, or everyone?
That final question is important. It quickly separates a security problem from a data-processing problem or a broad feature issue.
Do not let AI recommendations become automatic actions
The workspace can recommend priority actions and provide quick access to processes. That is helpful during close, but it does not remove the need for review.
Before running a recommended action, the accountant should still understand:
- What is the exception?
- What will this process change or submit?
- Is it safe at this stage of close?
- Is there a dependency on Inventory, Payables, Receivables, or General Ledger?
- Who owns the outcome if the action fails?
The right operating model is not "the AI told us to run it". It is "the workspace helped us find the right action faster, and the accountable person validated it."
Final thought
This workspace can make close calmer. But it works best when you treat it as a guided operational workspace, not as an alternative to the underlying Cost Management setup and close discipline.
Get the profile option, roles, context, and processing schedule right first. Then the AI layer can do what it is meant to do: bring the right exceptions to the surface before they become last-minute surprises.
Checked The enabling profile option ORA_CST_PERIOD_CLOSE_AGENTIC_APP_ENABLED and setup steps verified 25 Jul 2026 against Oracle's Cost Accounting Close Workspace readiness documentation. Behavior varies by release and configuration; verify in your own instance and test before acting.