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
Data Load Mapping - Period/Year

Hi Gurus,
This is likely an easy question for you expert FDMEE users, but for some reason I am being required to create a mapping for Year/Period? However since I created my Period mapping already to correspond to the correct Month/Year, why doesn't FDMEE use the POV selected as the target Month/Period to load?
Source is a JDE view.
Any help is appreciated!
Best Answer
-
Maybe your target CAPEX application has not got the period dimension configured correctly, if you go to the target application, make sure for period the dimension class is period and there is no data column populated.
Cheers
John
Answers
-
Maybe your target CAPEX application has not got the period dimension configured correctly, if you go to the target application, make sure for period the dimension class is period and there is no data column populated.
Cheers
John
-
@JohnGoodwin - Thanks for the tip - that's 100% correct.
One more question however, once I remove the Period from the CAPEX application, I am no longer pulling in any values from the Source:
In the process log I see that 0 rows of data were inserted into TDATASEG, and this error occurs twice:
WARN [AIF]: Warning: The Import step has not been completed for period Jun-2018
Perhaps you could point me in the right direction again?
Thanks
-
You might need to check the query that is being run against JDE, it could be your source period mappings are not correct and that is why no data is being returned, verify your mappings are definitely correct.
-
Thanks John.
I'm able to extract data from JDE correctly when I hardcode the Source Options for Month/Year on the Data Load Rule. Whereas our existing loads to HFM have a 'BefImport' script that dynamically takes the MM/YY from the user's POV, I think we will need to configure it to work with the load specified above which will be into a target application.
Thanks for the assistance.