I will appreciate some clarification on the some points made in response to my previous post "Flat files and Business Contents: Any issues with this scenario?"
" ...youd better analyze those cubes for data redundancy and presence of data youll never use. " I will appreciate some clarification on the type of analysis you are referring to. Examples will help.
"If you want to combine several found IOs in your custom dataprovider, then again you must know (or figure out) relationships between these IOs." I will appreciate some clarification on the type of relationship you are referring to. Examples will help.
I am a bit confused with "..include into ODS structure ALL fields required for the cube" but you also noted noted that "...except navigational attributes and chars and KFs that are going to be determined in TRs or URs."
If you exclude ALL these, haven't you excluded all the fields you included in the ODS structure?
"Consider carefully the ODS key fields selection. Their combination should not allow data aggregation that you dont need."
I may be missing the point here, I understand that you need to select the fields which will form the unique ID for the records in the ODS under the Key Field (please correct me if I am wrong with the purpose of the Key Field), but I don't understand the discussion of "aggregation" in the context.
Thanks in advance