Time characteristic restriction in BW BPS

[Former Member]

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?

[Former Member]

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

[former_member311755]

Hi,

I don't want to speak for Chek Keong Ng. But as we've got the same problem I'd like to answer it for us if this is ok. I've tried putting 000000. The value 'not assigned' is definitely part of the master data table.

The amazing thing is that the error message only appears when time characteristics are concerned. All other characteristics are ok.

Thanks,

Thomas

[Former Member]

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?

[Former Member]

Hi Gupta,

Thanks for your guide. I already try as per your instruction but not work because when I create a planning level with only 0calmonth, system still not allow me to include unassigned (#) for time restriction. May be I could explain to you why I need to select unassigned (#) for 0calmonth.

My explanation is as follows:

Actually I already create a planning level with selected time characteristic calender year only for example Year 2008 and input value. Now I want to distribute the yearly figure to monthly, therefore I need to create another planning level and perform top down distribution. In the top down planning level, I have to select calender year/month for time characteristic and restrict the period to Jan 2008 to Dec 2008 and include unassigned(#) for the purpose of running distribution function.

As I have told you in the earlier note which mentioned that the above task was actually worked in the beginning time before we have upgrade our Netweaver service pack. Unfortunately, it not work anymore after the upgrading of Netweaver .

Do you have any idea regarding the scenario of before and after upgrading of Netweaver. Does it affect the previous settings?

Hope you can help me to find out more on this.

Tq.

[Former Member]

Chek,

I am not completely sure if IP allows to restrict 0calmonth to # in case only 0calmonth time char is present in the level. I cannot check that right now becuase I dont have a system. But I think, for sure you cannot have 0calmonth as # and 0calyear as 2008 because this combination will contradict with the one the time characteristic relationship will propose.

Why cant you have 0calmonth as, maybe, 01.2008 and then distribute this value to the 12 months?

[Former Member]

Hi Gupta,

Sorry to tell that actually this is happening in BPS workbench not BI-IP. Yes, may be I can use 01.2008 to distribute instead of #. But this still not solve my problem yet. I just would like to know whether upgrading NetWeaver service pack will affect the previous settings in BPS.

Thanks.

[former_member311755]

Hi Check,

we have exactly the same problem within our BW-system. Have you found an answer already? It would be very helpful.

Thanks,

Thomas