Discussions
Categories
- 17.9K All Categories
- 3.4K Industry Applications
- 3.3K Intelligent Advisor
- 62 Insurance
- 536.1K On-Premises Infrastructure
- 138.2K Analytics Software
- 38.6K Application Development Software
- 5.7K Cloud Platform
- 109.4K Database Software
- 17.5K Enterprise Manager
- 8.8K Hardware
- 71.1K Infrastructure Software
- 105.2K Integration
- 41.6K Security Software
Open Interface Adapter Calender
Hi,
Hyperion Planning version: 11.1.2.4.005
FDMEE version: 11.1.2.4.210
I am trying to load data using Open Interface Adapter. When i try to execute my data load rule i can't see the required period. Below image shows that dec-16 is visible... jan-17 is missing and feb-16 is visible.
I have created global period mapping and then created source mapping (i haven't created application mapping of target application) as shown in the below image:
But when i created application mapping of my target application. I am able to see the required period.
My question is.
- Is this the proper way to create OIA period mapping (to create global, application and then source mapping)?.
- If i remember correctly earlier i don't have to create target application mapping? was it a bug earlier? or now?
Regards
Best Answer
-
Yup but I think that if you define at least 1 period mapping at Application level, then all periods you want to see in the data load rule execution must be defined at application level as well.
I would need to retest but this is what I recall
cheers
Answers
-
Hi,
See if this helps..!
Exploits in Hyperion: Managing data load in FDMEE using Open Interface table
Also there is a similar thread FDMEE No Records Warning on Import on TDATASEG , you can refer if needed.
Thanks
Amith
-
-
You don't need an application level mapping. As long as you have the peroiod defined in the Global mapping you will be able to define a Source Period Mapping for that same Period. This was certinly the case on FDMEE 11.1.2.3.700 so unless they have introduced a bug in 11.1.2.4 it should be the same
-
Yup but I think that if you define at least 1 period mapping at Application level, then all periods you want to see in the data load rule execution must be defined at application level as well.
I would need to retest but this is what I recall
cheers
-
-
It is still the same,
No application mappings for target app
Load rule all global mappings are picked up
Add one period mapping at application level
Load rule now only picks up target application mappings
-
I just deleted all the target application mapping. After that i was able to see all the global mapping. But when i added just one single mapping in my target application mapping i was only able to see that specific mapping which i just created in target application mapping.
Thanks for help guys.
Regards