FCCS data forms are the structured web-based input grids in Oracle Financial Consolidation and Close Cloud Service through which entity finance teams enter or review their financial submission data — the period-end balances for the income statement, balance sheet, and statistical accounts that feed the group consolidation. FCCS data forms serve a different purpose from planning forms in Oracle PBCS or EPBCS: where planning forms are designed for forward-looking budgeting and forecasting input, FCCS forms are primarily designed for actual period-end submission — the entity’s trial balance data for the current close period, often loaded from the ERP through Data Management but requiring supplemental adjustments entered directly by the entity finance team. Form design in FCCS must balance the completeness of the account set presented (all accounts the entity might need to adjust) with the performance of the form load (which degrades as the number of retrievable intersections increases).
FCCS Form Architecture
| Form Component | FCCS-Specific Consideration |
|---|---|
| Row definition | Account members — typically the full chart of accounts by IFRS category (P&L, balance sheet, statistical) |
| Column definition | Value members — Entity Currency (input), Parent Currency (translated view), and Adjustments columns |
| Page selector | Entity and Scenario — the submitting entity and the submission scenario (Actual, etc.) |
| Point of View (POV) | Year and Period — controls which period the form displays |
| Currency view | Entity Currency view shows values in functional currency; Reporting Currency shows translated values |
| Read-only intersections | Parent Currency and translated columns are typically read-only — populated by the translation process, not by direct input |
FCCS vs Planning Forms: Key Differences
FCCS forms are structurally similar to Oracle Planning forms but serve different purposes and have different default configurations. FCCS forms typically show the Value dimension on the column axis — displaying Entity Currency (functional currency input), Parent Currency (translated value), and Adjustment members side by side — because the consolidation team needs to review both the entity’s local currency submission and the translated group currency equivalent in the same form. Planning forms typically show period on the column axis. FCCS forms also expose the Intercompany dimension for accounts where intercompany coding is required — allowing entity finance teams to tag intercompany balances with their counterparty entity code directly in the submission form.
Data Form Design for GCC Multi-Entity Submissions
In GCC group consolidations where 20 or more entities each submit their period-end data through FCCS forms, the form design must consider the submission workflow: which accounts each entity type submits (an operating subsidiary submits different accounts from a treasury entity or a real estate holding entity), whether the form should be a single comprehensive form or a set of focused forms by financial statement area (P&L form, balance sheet form, intercompany form), and whether Arabic-language account labels should appear alongside English labels for entities whose finance teams work primarily in Arabic. FCCS’s alias table capability enables Arabic account descriptions to be configured as a parallel alias set — allowing Arabic-language users to see Arabic account labels in the FCCS forms while English-language users see English descriptions from the same form definition.
What Goes Wrong in Practice
The most common FCCS form performance problem is a form that attempts to display all accounts for all entities in a single grid — producing a retrieval query that generates hundreds of thousands of data points and takes minutes to load. The user experience drives the close cycle timeline: a form that takes three minutes to load is a form that entity finance teams avoid using for data review, defaulting instead to exported spreadsheets. FCCS forms should be scoped to the accounts and entities relevant to a specific review task — a regional controller reviewing a specific entity’s submission sees only that entity’s accounts, not the full group-level account set for all entities simultaneously.
How Loop Wise Solutions Designs FCCS Forms
We design FCCS forms with the entity finance team’s workflow as the primary design driver — understanding which accounts each user role needs to input or review, and building focused forms for each workflow step rather than a single comprehensive form that serves all purposes poorly. Form performance is validated against representative data volumes before go-live.
