Sorry, didn't see this one. Not sure what version of Khalix you are using or OS so I'll just say that each Khalix version has supported hardware and software prerequisites. You can find this in your supplied Khalix documnetation.
I have seen issues with Vista on certain early 3.X instances but the latest ones should work. It really is a corollary of when your version of Khalix came out vs when Windows came out as to whether it would be supported right, so you can do some logical debugging that way if you don't have access to the supplied documentation (i.e. if you are using Khalix 3.3 and are trying to use Vista, since Vista came out after 3.3, you can expect to have issues. In that case, only trial and error (and a certain amount of luck) would prove it out as you would not find this in your documentation.
I have started working as Khalix Administrator few months back.while doing switch parents change - I am getting few error like 1. Cycle detected in dimension - or Cycleing Dimension 2. Class overlap detected
Can you please explain me why this happens and what we should do to avoid it.
The "cycle detected in dimension" error refers to when, in Khalix for Windows, you are using the symbol hierarchy and have attempted to add a new or existing symbol to one of your dimension hierarchies that already exists in another hierarchy and would therefore violate referential integrity.
Let me give some symbol examples to illustrate few points:
You have two class tabs, Operating and Misc, let's say.
Well, you can't do that because Child2 already exists beneath SymPar2 under the same Root symbol.
The "cycle detected" technically refers to where you have added a symbol that refers to another symbol in the hierarchy. That is, you basically just tried to add a symbol to a hierarchy where the symbol already exists or is being referenced, most likely underneath another parent.
And you just tried to add Child1 somewhere because this is a totally different hierarchy (it's called RootPar2 after all), you only see SymPar3 and don't know Child1 has been attached under it.
The answer is to do a search on the hierarchy in which you are trying to add the symbol that error-ed out, and/or remove the problem symbol from the add list since it already exists or is being referenced.
Hope that long answer suffices. Kinda hard to illustrate in a blog window.
Ganesh, you need to familiarize yourself with the Month-End and Year-End Rollover process. The ME rollover updates your current month setting. The YE rollover updates the year.
There should be a variable to use in your server rule that refers to the currmonth--this is used in your rollovers. For the life of me I cannot think of the name of it right now but first step is to look in your other server rules and it will probably stand out.
Hi HTH, I initially tried something like this KLX(A20292,ICTIMEPER###,E500104,TOTDEPT###,K0000,CUSD,DIM6SET)=KLX(A30000,ICTIMEPER###,ELOC2TWN2,TOTDEPT###,K0000,TUSD,DIM6SET)
Which does it for all periods including history.
I then changed it to the following, based on the Month end procedure and it gives me a syntax error. KLX(A20292,[[SYSTEM,BSPER,DBDEFAULT]] ,E500104,TOTDEPT###,K0000,CUSD,DIM6SET)=KLX(A30000,[[SYSTEM,BSPER,DBDEFAULT]] ,ELOC2TWN2,TOTDEPT###,K0000,TUSD,DIM6SET)
Could you let me know what the syntax should be here?
In any case, I recall BSPER is a number (like 1 or 2), so that's probably why you are getting an error. If you have access to the Khalix/Longview database, you can see what the values are in the Parameters (klxparameter?) table. I'm sorry, I do not have a system in front of me to look right now.
Sorry, to clarify, BSPER will return a number--this is the numeric value that gets updated by the Month-End Rollover. So if BSPER is 6 then the system is saying that it's in June. You want the Timeper Value, not the number.
9 comments:
Can I use Khalix on Windows Vista?
How do I migrate the information to Windows Excel 2007?
Can I do that?
Sorry, didn't see this one. Not sure what version of Khalix you are using or OS so I'll just say that each Khalix version has supported hardware and software prerequisites. You can find this in your supplied Khalix documnetation.
I have seen issues with Vista on certain early 3.X instances but the latest ones should work. It really is a corollary of when your version of Khalix came out vs when Windows came out as to whether it would be supported right, so you can do some logical debugging that way if you don't have access to the supplied documentation (i.e. if you are using Khalix 3.3 and are trying to use Vista, since Vista came out after 3.3, you can expect to have issues. In that case, only trial and error (and a certain amount of luck) would prove it out as you would not find this in your documentation.
Hth
Hi ,
I have started working as Khalix Administrator few months back.while doing switch parents change - I am getting few error like
1. Cycle detected in dimension - or Cycleing Dimension
2. Class overlap detected
Can you please explain me why this happens and what we should do to avoid it.
Thank you so much in advance
Regards
Amol..
Hi Amol,
The "cycle detected in dimension" error refers to when, in Khalix for Windows, you are using the symbol hierarchy and have attempted to add a new or existing symbol to one of your dimension hierarchies that already exists in another hierarchy and would therefore violate referential integrity.
Let me give some symbol examples to illustrate few points:
You have two class tabs, Operating and Misc, let's say.
In Operating you have
RootPar1
|- SymPar1
| |-Child1 (under SymPar1)
|- SymPar2
|-Child2 (under SymPar2)
In Misc, you then attempt to do this:
RootPar1
|- SymPar1
| |-Child1 (under SymPar1)
| |-Child2 (under SymPar1)
|- SymPar2
Well, you can't do that because Child2 already exists beneath SymPar2 under the same Root symbol.
The "cycle detected" technically refers to where you have added a symbol that refers to another symbol in the hierarchy. That is, you basically just tried to add a symbol to a hierarchy where the symbol already exists or is being referenced, most likely underneath another parent.
As an example:
Operating contains:
RootPar1
|- SymPar1
| |-Child1 (under SymPar1)
|- SymPar2
|-Child2 (under SymPar2)
And in Misc there is an alternate hierarchy that doesn't look the same but actually references some of the same symbols somewhere:
RootPar2
|- SymPar3
| |-SymPar1 (under SymPar3)
| |-Child1 (under SymPar1)
|- SymPar2
|-Child2 (under SymPar2)
And you just tried to add Child1 somewhere because this is a totally different hierarchy (it's called RootPar2 after all), you only see SymPar3 and don't know Child1 has been attached under it.
The answer is to do a search on the hierarchy in which you are trying to add the symbol that error-ed out, and/or remove the problem symbol from the add list since it already exists or is being referenced.
Hope that long answer suffices. Kinda hard to illustrate in a blog window.
I am trying to create a server rule and would like this to apply only to current open period. This needs to be the dynamic period. How do I do this?
Ganesh, you need to familiarize yourself with the Month-End and Year-End Rollover process. The ME rollover updates your current month setting. The YE rollover updates the year.
There should be a variable to use in your server rule that refers to the currmonth--this is used in your rollovers. For the life of me I cannot think of the name of it right now but first step is to look in your other server rules and it will probably stand out.
Hth
Hi HTH,
I initially tried something like this
KLX(A20292,ICTIMEPER###,E500104,TOTDEPT###,K0000,CUSD,DIM6SET)=KLX(A30000,ICTIMEPER###,ELOC2TWN2,TOTDEPT###,K0000,TUSD,DIM6SET)
Which does it for all periods including history.
I then changed it to the following, based on the Month end procedure and it gives me a syntax error.
KLX(A20292,[[SYSTEM,BSPER,DBDEFAULT]]
,E500104,TOTDEPT###,K0000,CUSD,DIM6SET)=KLX(A30000,[[SYSTEM,BSPER,DBDEFAULT]]
,ELOC2TWN2,TOTDEPT###,K0000,TUSD,DIM6SET)
Could you let me know what the syntax should be here?
Thank you very much.
GI
Ganesh, HTH means 'Hope That Helps' lol!
In any case, I recall BSPER is a number (like 1 or 2), so that's probably why you are getting an error. If you have access to the Khalix/Longview database, you can see what the values are in the Parameters (klxparameter?) table. I'm sorry, I do not have a system in front of me to look right now.
Sorry, to clarify, BSPER will return a number--this is the numeric value that gets updated by the Month-End Rollover. So if BSPER is 6 then the system is saying that it's in June. You want the Timeper Value, not the number.
Post a Comment