Handle orphans data in TM1

[svchowdary83]

Hi,

How to handle orphans fact data in tm1.
What is the best approach

Thanks&Regards,
chowdary

[Alan Kirk]

How to handle orphans fact data in tm1.
What is the best approach

Adoption agencies. I find them to be extremely useful. I have neither the time nor inclination for nappy changing.

Another useful approach is to read the Request For Assistance Guidelines before posting a question, particularly (in this case) # 3: "Try to make the question as specific as possible." In this case a full explanation of what on Earth you are referring to when you speak of "orphans fact data" would be more than marginally useful.

[tomok]

I'm going to go out on a limb and assume that when you say "orphans" you actually mean fact records where one of the metadata tags don't match what you expect. An example would be data coming in from the source with a new G/L account or cost center or whatever. During a load process you can check the dimension for the existence of the metadata element and if it does not exist, add it to the dimension and have it roll up to a node called "Orphans". This is, IMO, a better option than rejecting the record. After the process(es) are run you can check the dimensions for orphan leafs, investigate, and place them in their correct spot in the hierarchy and you won't have to reload the data.