PCMCS - Data Management Load Rule Does Not Filter Proper Period Key
(Doc ID 2322850.1)
Last updated on JULY 07, 2021
Applies to:
Oracle Hyperion Profitability and Cost Management Cloud Service - Version N/A and laterInformation in this document applies to any platform.
Symptoms
In Data Management load rule to export data from Source, when select/input the start and end period eg: Feb-17 in "Execution Rule" parameters, the log shows that the period filter showing more periods than specified period druing Execution eg: periodFilter="Feb","Jan"
Error in Data Management Process log having below Entries
2017-10-30 14:49:44,216 INFO [AIF]: Period Name : Feb-17 (Period Key:2/28/17 12:00 AM)
2017-10-30 14:49:44,216 INFO [AIF]: Category Name: Plan (Category key:3)
2017-10-30 14:49:44,216 INFO [AIF]: Rule Name : Plan_Jan (Rule ID:96)
2017-10-30 14:49:52,430 INFO [AIF]: FDM Version: 11.1.2.4.220
.
.
.
.
2017-10-30 14:49:53,896 DEBUG [AIF]: periodSQL - periodParams: [u'OracleTest_1482.dat', 1482]
2017-10-30 14:49:53,914 DEBUG [AIF]: insertRowCount: 2
2017-10-30 14:49:53,916 DEBUG [AIF]: CommData.insertEpmPeriods - END
2017-10-30 14:49:53,916 DEBUG [AIF]: CommData.updateBalRuleLoadParams - START
2017-10-30 14:49:53,923 DEBUG [AIF]: yearDimensionName=Years, yearFilter="FY17"
2017-10-30 14:49:53,923 DEBUG [AIF]: periodDimensionName=Period, periodFilter="Feb","Jan"
2017-10-30 14:49:53,931 DEBUG [AIF]: CommData.updateBalRuleLoadParams - END
2017-10-30 14:49:53,932 DEBUG [AIF]: CommData.getPovList - START
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |