Discussions
Categories
- 17.9K All Categories
- 3.4K Industry Applications
- 3.3K Intelligent Advisor
- 63 Insurance
- 535.7K On-Premises Infrastructure
- 138.1K Analytics Software
- 38.6K Application Development Software
- 5.6K Cloud Platform
- 109.3K Database Software
- 17.5K Enterprise Manager
- 8.8K Hardware
- 71K Infrastructure Software
- 105.2K Integration
- 41.5K Security Software
Period Key and Prior Key concept and purpose in FDMEE and Hyperion Planning

Hi,
I when i am loading data periodically i use to set prior period as the first date of month and period key as the last day of month. But i am not sure why i do this?
My question is when i try to execute data load rule.... will it look for the data against the defined period key or prior key? or will it look for the data against source gl period and gl year? (i am talking about pre-packaged interfacing and custom interfacing both).
As per from oracle documentation i understood that period key and prior key are used if am loading data weekly? this won't be used for monthly.
Global Mapping
Pre-Packaged Source Mapping
Custom Source Mapping
Regards
Answers
-
Usually, I'll use the first of each month for Prior and Period Key, but the way you are doing it would be very helpful if you ever have to add an additional period in. For example, a BegBalance member in the period dimension. You could use 12/30 - 12/31 for Beg Balance and then 12/31-1/1 for Jan.