Hi to all,
I got one question for BW-BPS. This was happened after upgrade of Netweaver
service pack. Before that it was fine. My question is as follow:
Under DW workbench when I create an InfoProvider which included time dimension
that consist of fiscal year, fiscal year/period, posting period, calendar
year, calender year/ month. I try to select fiscal year, fiscal year/period
under a planning level, then I select unassigned(#) time characteristic for
fiscal year/period and save it. System allow for this restriction under time
characteristic fiscal year/period. However, if I deselect fiscal year, fiscal
year/period under a planning level and select calendar year, calender year/
month under the same planning level, then I select unassigned(#) time
characteristic for calender year/ month and save it. System was not allow for
this restriction for time characteristic and generate the following message:
Message: UPC003- Value# is not permitted for characteristic calendar
year/month.
There was no characteristic relationship set for time dimension
characteristics. I still not understand why system is not allow for
unassigned(#) time characteristic selection for calender year/ month
Therefore, I would like to need a support for this. Is it a system error?
Hi Chek,
I dont think it is a system error. In BI-IP, there is an automatic characteristic relationship that is provided for the time characteristics like 0calday, 0calweek, 0calmonth, 0calquarter, 0calyear which we earlier needed to model in the planning application in BPS. You can check this very easily by creating an aggr. level with only 0calmonth (but not 0calquarter, 0calyear which should be in the cube), and populating the cube with record(s). You will see that 0calquarter, 0calyear will get automatically populated with corresponding values (using derivation).
That should be the reason why system is not taking # as restriction for 0calmonth, because it cannot derive the corresponding value of 0calyear.
Why do you want 0calmonth to be blank?
Hi Chek Keong Ng,
Can you put value 000000 instead of # in 0Cal Year/month and then check....
I believe, in the master data table # does not exit. That is why you are getting error. (check in the master data table /BI0/PCALMONTH).
Similarly put Cal year 0000 and calmonth 00.
This is all due to master data tables..... where # is not there.....
Please check and let me know..
Thanks
Abhijit Misra
Add a comment