Oracle Planning RTM Interactive - Application Setup & Dimensions

0. Client, Project, Consultant & Requirement Owner Details

Client Name

Client Industry

Client Location

Project Name

Project Phase

Overall Requirement Status

Project Start Date

Target Design Sign-off

Target Go-Live Date

Functional Consultant Name

Consultant Email / Contact

Requirement Collected Date

Requirement Provided By

Provider Role

Provider Email / Contact

Requirement Notes

This section records who collected the requirement, who provided it, when it was collected, target timeline and approval status. This makes every RTM line auditable from Requirement → Design → Build → Test → Sign-off.

1. Application Setup Inputs

Start Year

End Year

First Month of Fiscal Year

Period Frequency

Weekly Distribution

Rolling Forecast

Rolling Forecast Duration

Main Currency

Multicurrency

Task Flow Type

This section captures core application design decisions. For example, if the business selects FY2023 to FY2029, monthly frequency, January fiscal start, USD currency and multicurrency enabled, the consultant must confirm reporting calendar, forecast cycle, exchange rate process, and alignment with FCCS or ERP reporting.

Reference Screenshot

This image shows the Oracle Planning Customize step where Time Period, Account, Year, Scenario, Version, Entity and Custom dimensions are configured.

2. Cube Details

No. of Cubes

Default Input Cube

Default Reporting Cube

Cubes separate data entry and reporting. A common design is Plan1 for input and calculations and FinPlan for reporting. Consultants should ask whether the customer needs additional cubes for Workforce, Capex, Projects, Funding, or ASO reporting.

3. Dimension Details

Update member names and metadata file requirements based on the Dimension Selection screen.

Dimensions define how planners enter, analyze, approve and report data. Standard dimensions normally include Period, Account, Years, Scenario, Version and Entity. Custom dimensions may include Product, Project, Fund, Customer, Program, Location, Employee or Grant depending on planning needs.

4. Rolling Forecast Example

This example explains how rolling forecast works for business users.

Forecast Start Month

Actual Months Locked

Forecast Months Open

Period	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
Current Year	Actual Locked	Actual Locked	Actual Locked	Forecast Open	Forecast Open	Forecast Open	Forecast Open	Forecast Open	Forecast Open	Forecast Open	Forecast Open	Forecast Open
Next Cycle	Actuals remain locked			Forecast window shifts forward automatically

Example: If actuals are available for Jan–Mar, planners should not edit those months. Forecast input starts from Apr and continues for the selected rolling forecast duration. In the next forecast cycle, the open planning window moves forward automatically, reducing manual year/period maintenance.

5. Generated RTM Summary

6. Example RTM with Visual

This example helps business users understand how screenshot choices become formal requirements.

$Oracle Planning RTM Infographic$