Script logic *DESTINATION_APP and Time Dimension remapping

[Former Member]

I have two applications that don't share the time dimension. Source has a daily time structure and Destination has months as base level members.

I need to move data from one to another and in order to do the mapping I have a property on daily time dimension that maps each base level member (a day) to a base level member on monthly time dimension. Part of the logic is below:

*DESTINATION_APP=LEGAL

*RENAME_DIM DAILYTIME=TIME

*WHEN *

*IS *

*REC(DAILYTIME=DAILYTIME.MONTHID)

This kind of mapping always worked for me except it is the first time I need to remap a time dimension. Logic validates correctly but it doesn't run as it can't move beyond the SQL step that collects data from the destination area. It complains about time dimension invalid members.

To double check I don't have a installation issue I did the same kind of mapping with other pair of dimensions and hard coding the destination time dimension member:

*DESTINATION_APP=LEGAL

*SKIP_DIM=DAILYTIME

*ADD_DIM TIME=2010.MAY

*RENAME_DIMENSION SALESENTITY=ENTITY

*WHEN *

*IS *

*REC(SALESENTITY=SALESENTITY.ENTITY_MAP)

This works. I wonder if BPC is failing because at the DB level it deals with TIMEIDs in the fact table.

So question is: Has anybody else faced this kind of limitation with *DESTINATION_APP? If so how did you solve it?

Thanks

Paulo

[Former Member]

Hi Paulo

With your logic:

*DESTINATION_APP=LEGAL

*RENAME_DIM DAILYTIME=TIME

*WHEN *

*IS *

*REC(DAILYTIME=DAILYTIME.MONTHID)

I'm guessing that the values in your MONTHID property are "March.2009", "April.2009", etc. correct? As you already hinted, try using the TIMEID's instead: 20091200 (that's for dec 2009), 20091100 (nov 2009), and etc. Maybe you could use a 2nd property (MONTHTIMEID) for that as well.

P.S. i haven't tested the logic from my side. i'll let you know when I do. but if you get what i mean you can go ahead and test

P.P.S. didn't read John's post above before writing this. We basically have the same idea.

Edited by: James Carl Tiro on Apr 13, 2010 5:16 PM

[JohnL]

Hi Paulo,

What specific error message are you getting?

Why don't you try and create a property called MONTHTIMEID and put the month time ID's into that property (for each daily time ID member) and see if that works? i.e. The 2010.JAN Time Dim member has a TIMEID of 20100100

Thanks,

John